Bug 2091044

Summary:	new host ui details,ansible roles, submitting form without any roles should show warning
Product:	Red Hat Satellite	Reporter:	Peter Dragun <pdragun>
Component:	Ansible - Configuration Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Dragun <pdragun>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	oezr, rlavi, zhunting
Target Milestone:	6.12.0	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman_ansible@7.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:33:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Dragun 2022-05-27 12:15:53 UTC

This bug was initially created as a copy of Bug #2069456

I am copying this bug because: 
Created a new bug from tstrych comment on the original bug


> 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? 
>

Comment 2 Ron Lavi 2022-06-23 08:33:39 UTC

Created redmine issue https://projects.theforeman.org/issues/35100 from this bug

Comment 3 Bryan Kearney 2022-07-07 12:04:33 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35100 has been resolved.

Comment 4 Peter Dragun 2022-07-11 15:28:24 UTC

Failed QA.
Using Satellite 6.12 snap 1, I am still able to reproduce this bug.
Installed package: rubygem-foreman_ansible-7.1.0-3.el8sat.src.rpm

Comment 5 Ron Lavi 2022-07-11 16:02:13 UTC

Opened a cherry-pick into the foreman_ansible-7.x branch: https://github.com/theforeman/foreman_ansible/pull/542

Comment 6 Ron Lavi 2022-07-25 06:47:24 UTC

Fixed in foreman_ansible.1,
moving to POST

Comment 7 Peter Dragun 2022-07-28 07:29:20 UTC

Verified on Sat 6.12 snap 4
The submit button is disabled until any changes to roles are made.

Comment 11 errata-xmlrpc 2022-11-16 13:33:51 UTC

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 (Important: Satellite 6.12 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:8506