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:

If hosts are not configured correctly for pull-transport, the script provider jobs run against these hosts end up hanging indefinitely in pending state.


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

How reproducible:
Always

Steps to Reproduce:

1. Have a satellite with a pull provider enabled capsule
2. Register a host, but don't enable mqtt client (or simply run a job against satellite itself)
3. Run a script job against the host

Actual results:
The job hangs. 

Expected results:
The job should fail with a meaningful error message

Well, yes. Satellite does not know (and imo should not know) if and how a client is configured. Not knowing it makes it hard to distinguish between "a client will never pick a job because it is misconfigured" and "the client has not picked a job *yet*"

There's https://issues.redhat.com/browse/SAT-1668 which could help in here, once implemented.

Verified on Satellite 6.13 snap 7, the problem of hanging pull jobs is solved by the "time to pickup" setting introduced in 6.13

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