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 changing the order of Ansible roles assigned to a host group, the changes appear to revert after they have been submitted.
Version-Release number of selected component (if applicable):
Satellite 6.10.0, snap 6
tfm-rubygem-foreman_ansible-6.3.0-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Import multiple Ansible roles to Satellite.
2. Create a host group, assign multiple roles on the Ansible tab, then click Submit.
3. Click the name of the host group again and go to the Ansible tab. Change the order of the roles again and click Submit.
4. Click the name of the host group again and go to the Ansible tab.
Actual results:
The roles appear in the original order, as if the previous change had not been made.
Expected results:
Changes in the order are persistent in the webUI.
Additional info:
- This behavior is not present when assigning roles to an individual host, only when assigning roles to a host group.
- Though changes do not appear persistent in the webUI, when the roles are run against any hosts in the host group, the last-submitted order seems to be consistently respected.
Steps to Test:
1. Import multiple Ansible roles to Satellite.
2. Create a host group, assign multiple roles on the Ansible tab, then click Submit.
3. Click the name of the host group again and go to the Ansible tab. Change the order of the roles again and click Submit.
4. Click the name of the host group again and go to the Ansible tab.
Expected results:
Changes in the order of roles assigned to a host group are persistent in the webUI.
Actual results:
Changes in the order of roles assigned to a host group are persistent in the webUI.
Verified on Satellite 6.10, snap 9 (tfm-rubygem-foreman_ansible-6.3.1-1.el7sat.noarch).
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 (Moderate: Satellite 6.10 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-2021:4702