Issue #543
closedWhen httpd fails to start, it tells users they probably haven't run pulp-manage-db
Description
Description of problem:
When httpd fails to start for any reason, it tells users they likely need to run pulp-manage-db, even when that's not the case. This leads to lots of confusion and just isn't helpful. Also, it is possible for it to detect for sure whether pulp-manage-db needs to be run, so it should give the user the real error.
Version-Release number of selected component (if applicable):
2.4.0-1
How reproducible:
Every time
Steps to Reproduce:
1. Break Pulp in some way, perhaps by inserting a raise Exception during its initialization.
Actual results:
It will tell you that you likely need to run pulp-manage-db.
Expected results:
It should tell you what really happened.
Additional info:
Of course, if it really is that you need to run pulp-manage-db, it should tell you that, without the word "likely".
+ This bug was cloned from Bugzilla Bug #1145734 +
Updated by jortel@redhat.com about 9 years ago
Update the language.
+ This comment was cloned from Bugzilla #1145734 comment 1 +
Updated by amacdona@redhat.com about 9 years ago
https://github.com/pulp/pulp/pull/1270
+ This comment was cloned from Bugzilla #1145734 comment 2 +
Updated by cduryee about 9 years ago
***** Bug 1004855 has been marked as a duplicate of this bug. ***
+ This comment was cloned from Bugzilla #1145734 comment 3 +
Updated by cduryee about 9 years ago
fixed in pulp 2.6.0-0.2.beta
+ This comment was cloned from Bugzilla #1145734 comment 4 +
Updated by pthomas@redhat.com about 9 years ago
verified
[root@ibm-x3550m3-07 ~]# rpm -qa pulp-server
pulp-server-2.6.0-0.5.beta.el6.noarch
[root@ibm-x3550m3-07 ~]#
+ This comment was cloned from Bugzilla #1145734 comment 5 +
Updated by rbarlow almost 9 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE