Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

On spinning disks during the pulp3 migration the disk i/o can become saturated and the pulp3 worker timeout may become too small.  For 6.9 we plan to hard code this to 300, as the down sides are low.  In the future we will allow the timeout to be configurable.


Version-Release number of selected component (if applicable):

6.9.0

How reproducible:

cat /usr/lib/python3.6/site-packages/pulpcore/tasking/constants.py

check 
WORKER_TTL=XYZ

XYZ should be 300

*** This bug has been marked as a duplicate of bug 1929344 ***