Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
For pull-mqtt rex jobs, the "time to pickup" kills a long running job, so it behaves like the "timeout to kill" setting. In the same scenario, timeout to kill does not kill a long running pull-mqtt job
Version-Release number of selected component (if applicable):
Satellite 6.13 snap 5
How reproducible:
always
Steps to Reproduce:
1. have a satellite with pull-mqtt rex mode and a registered host with mqtt client
2. Prepare a command job that will execute for some time, e.g: "echo start; sleep 60s; echo done"
3. In rex wizard, set "time to pickup" to 20s
4. Run job
Actual results:
The job fails after 20s with Proxy error: RuntimeError - The job was not picked up in time.
Furthermore, using "timeout to kill" in step 3 above doesn't result in stopping the job.
Expected results:
Time to pickup should distinguish between "not picked yet" and "already running" states. Timeout to kill should work on pull jobs as expected
Additional info:
Confirmed that timeout to kill works correctly in non-pull scenarios
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 (Important: Satellite 6.13 Release), 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-2023:2097