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:
Rex via pull-mqtt method doesnt work on hosts registered via capsule
Version-Release number of selected component (if applicable):
6.14
How reproducible:
Always
Steps to Reproduce:
1. Register host to the capsule via global registration template with REX pull mode
set to NO.
2. Now install katello-pull-transport-migrate on client and restart the yggdrasild service on client
3. Run any command on client via job invocation template.
Actual results:
The task remains in pending state while a blank screen is populated as output on web ui
Expected results: Result should be displayed and task should complete
Additional info:
Administer > Settings. On the Content tab, set the value of Prefer registered through Capsule for remote execution to Yes. => This also doesnt make any change.
After talking about this we came to an agreement that the behaviour is correct and this was a case of misconfiguration. I'll go ahead and close this as a notabug, if you feel there is something for us to do, feel free to reopen.