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.
DescriptionLukáš Hellebrandt
2019-07-08 14:34:59 UTC
Description of problem:
When I select an erratum to be applied to the host and click "via remote execution" or "via remote execution - customize first", nothing happens. No traceback.
Version-Release number of selected component (if applicable):
Reproduced on Sat 6.6 snap 10. Regression since this worked at some point.
How reproducible:
Deterministic
Steps to Reproduce:
1. Have a Satellite, a content host fully registered to it (bootstrap, katello-agent)
2. Have some erratum applicable to that content host
3. Go to the content host page, Errata
4. Select some erratum
5. In the "Apply Selected" dropdown, select "via remote execution"
Actual results:
Nothing happens
Expected results:
The erratum should be applied
Additional info:
Note that remote execution in general does work on that particular content host
Notes from the reproducer - the js console says:
```
bastion-bd772a8917bc…3fa4e5ab237bc3.js:4 TypeError: t.join is not a function
at i.a.performViaRemoteExecution (bastion_katello-9839…2aaa982824e77e.js:4)
at fn (eval at compile (bastion-bd772a8917bc…3fa4e5ab237bc3.js:6), <anonymous>:4:278)
at e (bastion-bd772a8917bc…3fa4e5ab237bc3.js:5)
at t (bastion-bd772a8917bc…3fa4e5ab237bc3.js:7)
at i.$eval (bastion-bd772a8917bc…3fa4e5ab237bc3.js:5)
at i.$apply (bastion-bd772a8917bc…3fa4e5ab237bc3.js:5)
at HTMLAnchorElement.<anonymous> (bastion-bd772a8917bc…3fa4e5ab237bc3.js:7)
at HTMLAnchorElement.dispatch (jquery.js:4737)
at HTMLAnchorElement.b.handle (jquery.js:4549)
(anonymous) @ bastion-bd772a8917bc…3fa4e5ab237bc3.j
```
Comment 8Lukáš Hellebrandt
2019-07-16 10:29:44 UTC
Verified on Sat 6.6 snap 11 using reproducer from OP. The errata was applied, package updated, no traceback, no related browser console errors, status reported as completed.
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-2019:3172