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.
Connecting redmine issue https://projects.theforeman.org/issues/32913 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32913 has been resolved.
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