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:
When selecting a security item for an impacted host and running insights Ansible pre-created playbook it throws an error.
How reproducible:
Every time select a playbook to run on the client from Insights.
Steps to Reproduce:
- Goto Insights tab>Actions>Select the Security Action>Select the impacted host>Actions.Create Playbook and Run playbook.
Actual results:
We see the error when we run playbook.
"Failed to create job. Ensure your systems are registered in Foreman"
Expected results:
It should run the playbook to fix the issues.
All other Ansible roles and remote execution working between the client and the Satellite.
Additional info:
Hi,
This is because the hosts_ids returns the full array instead of an ID, which make the insights playbook run fails
irb(main):028:0> Host.where(:name => hostname_rules_relation.keys).pluck(&:id)
=> [[3, "rhel7.acme.lab", Sun, 24 Feb 2019 02:31:46 UTC +00:00, nil, Sun, 24 Feb 2019 02:31:47 UTC +00:00, Sun, 24 Feb 2019 02:28:03 UTC +00:00, nil, 1, 1, nil, nil, nil, false, nil, nil, nil, 1, nil, 1, "User", true, nil, false, nil, nil, nil, nil, nil, nil, nil, 1, 2, "Host::Managed", nil, nil, nil, nil, "", nil, 1, "fqdn=rhel7.acme.lab", nil, nil, nil, nil]]
After changing the syntax
irb(main):029:0> Host.where(:name => hostname_rules_relation.keys).pluck(:id)
=> [3]
So, here is a simple fix
# vi /opt/theforeman/tfm/root/usr/share/gems/gems/redhat_access-2.2.0/app/models/redhat_access/concerns/host_managed_extensions.rb
Change
host_ids = Host::Managed.where(:name => hostname_rules_relation.keys).pluck(&:id)
To
host_ids = Host::Managed.where(:name => hostname_rules_relation.keys).pluck(:id)
Restart httpd
# systemctl restart httpd
Opened an upstream PR for this https://github.com/redhataccess/foreman-plugin/pull/33
Verified on tfm-rubygem-redhat_access-2.2.3-1.el7sat.
I was able to successfully run an Ansible playbook created by the planner in the Insights module, or by going through the Actions as described in the initial report. No error, playbook was processed and executed as expected.
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:1222
Comment 23Red Hat Bugzilla
2023-09-15 00:15:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days