Bug #11411

pulp_celerybeat pulp_resorce_manager fail to start on boot.

Added by alvin starr over 7 years ago. Updated over 3 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


I am running a CentOS 7.1.1503 with a fairly minimal install and katello on top of that.

On system reboot the pulp processes do not run up but the about info shows pulp as running.

restarting the services using "katello-services restart" works however.

katello.notes katello.notes 15.5 KB alvin starr, 08/20/2015 09:43 AM


#1 Updated by Eric Helms over 7 years ago

  • Status changed from New to Need more information
  • Triaged changed from No to Yes

Sounds like this is a Pulp bug to me - the issue with Pulp status showing as running even if the background services are not sounds fishy. We ask Pulp for all of that status, so all in all seems like a Pulp issue. I would file an issue with them at . I am inclined to close this unless we can figure out that Katello is falsely reporting.

#2 Updated by alvin starr over 7 years ago

Ok. give me a couple days to verify if katello is reporting the problem or not.
I am in the middle of some other testing and rebooting right now would be a problem.

#3 Updated by alvin starr over 7 years ago

I just checked and in fact the about panel shows that pulp is running.
Attached is a dump of katello-services status and systemctl status pulp_resource_manager.

I will push an issue to the pulp people.
Would they be the Pulpians?

#4 Updated by alvin starr over 7 years ago

It turns out the problem was because I moved /var/lib/pulp to a remote mount.
fixing the systemd start file so that pulp will not start until the remote filesystems are mounted fixes the problem.

I believe that a fix is in the works but I can post a patch if desired.

#5 Updated by John Mitsch over 3 years ago

  • Status changed from Need more information to Closed

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF