The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Changing component since the next steps are for Katello to take.

Upstream bug assigned to mbacovsk@redhat.com

Upstream bug assigned to mbacovsk@redhat.com

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17298 has been resolved.

tested on Sat 6.3.0 snap 9, i believe that some change did not make the build.  


the pids of my workers don't seem to change after syncing:

# ps aux | grep worker | grep python | awk '{print $2}' | sort
16600
16655
16658
16793
16794
16797

and it does not seem to be set (note its commented out):

in /etc/default/pulp_workers

# PULP_MAX_TASKS_PER_CHILD=2

FYI, there is a bug - BZ#1472584 PULP_MAX_TASKS_PER_CHILD is disabled in 6.3.0.

verified ON 6.3 SNAP 14.0

PID changes between syncs:

[root@jsherrill-test ~]# ps aux | grep worker | grep python | awk '{print $2}' | sort
2156
30940
30943
31027
31043
31139
[root@jsherrill-test ~]# ps aux | grep worker | grep python | awk '{print $2}' | sort
2156
30940
30943
31027
31043
31139


and PULP_MAX_TASKS_PER_CHILD is set to 2

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336