So mostly we use foreman/katello just for syncing operating systems out to
capsules/smart proxies, and for managing system lifecycle (basically, just
kickstarts). I went last week to add a XenServer 7.2 OS into my Katello
Products, and started having tons of issues, specifically in that I had
2
That is very strange, this may be a good candidate for a foreman-debug so
we can dig through logs. Can you create one and send it to me privately?
-John
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
On Tue, Jun 13, 2017 at 3:34 PM, wrote:
> So mostly we use foreman/katello just
Certainly. Going to let that run overnight :)
On Tue, Jun 13, 2017 at 5:00 PM John Mitsch wrote:
> That is very strange, this may be a good candidate for a foreman-debug so
> we can dig through logs. Can you create one and send it to me privately?
>
> -John
>
> John Mitsch
> Red Hat Engineering
Seems like something funny is going on with the pulp tasks, can you install
pulp-admin and take a look at the tasks? We may need to kill something at
that level
to install:
https://gist.github.com/johnpmitsch/866fb430780ba0e95a5554566b989416
-John
John Mitsch
Red Hat Engineering
(860)-967-7285
i
Neil,
Pulp is really backed up with tasks, my guess would be there was some sort
of deadlock in qpid and it "unlocked", releasing all of these tasks. My
advice would be first try stopping then starting these services
pulp_celerybeat.service pulp_workers.service pulp_resource_manager.service,
and
Updating here for posterity in the list:
I ultimately had to go nuclear and destroy all the tasks using pulp-admin.
This got me unstuck enough to be able to go in and take care of the rest of
the 'stuck' tasks (orphaned stuff from hosts now deleted, etc).
On Thu, Jun 15, 2017 at 10:26 AM John Mit
