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".
Update the language.
https://github.com/pulp/pulp/pull/1270
*** Bug 1004855 has been marked as a duplicate of this bug. ***
fixed in pulp 2.6.0-0.2.beta
verified [root@ibm-x3550m3-07 ~]# rpm -qa pulp-server pulp-server-2.6.0-0.5.beta.el6.noarch [root@ibm-x3550m3-07 ~]#
Moved to https://pulp.plan.io/issues/543