Description of problem: when all ansible roles are assigned, it is no longer possible to unassign the roles in new host details UI Version-Release number of selected component (if applicable): sat 6.11 snap 14 How reproducible: Always Steps to Reproduce: 1. navigate to all hosts -> host detail -> Ansible tab -> Edit ansible roles ( or add if there were none before) 2. add all of them -> confirm 3. click on edit ansible roles again Actual results: Nothing found (attached picture) Expected results: Ansible editing works properly Additional info: this occurs only when all ansible roles are attached
also additional feedback from uxd research, about new UI, user is allowed to confirm the addition of roles even if he didn't change anything, this confuses the users mainly when you are trying to add roles at first. The new way of adding roles is also new to the users, and I made the same mistake when I started to work with widget. I saw the widget I just clicked on the role, it stays on the left side and I click on the submit. All other widgets in sat work in a different way. When you click on them they move to the other column. In this case, they do not and an additional click on the arrow is required. I like it and I believe it is a step forward but it is confusing at first. 1. no ansible roles assigned 2. the widget to assign them is open, 3. click on some widgets in the left column 4. submit Actual results: You are allowed to submit without a change, which is okay, it is just a new design that is confusing Expected results: maybe some warning popup do you really want to submit with no change? I can create a separate BZ if you want me to :)
Based on UXD user testing, all testing users struggled to perform this action. Moving to high severity.
Created redmine issue https://projects.theforeman.org/issues/34912 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34912 has been resolved.
Verified based on problem description from comment#1. Creating a new bug from comment#3
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.11 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-2022:5498