Bug 2111373

Summary:	new host ui details, edit ansible roles, when assigned, wait and not confirmed, role is unassigned automatically
Product:	Red Hat Satellite	Reporter:	Peter Dragun <pdragun>
Component:	Ansible - Configuration Management	Assignee:	Ron Lavi <rlavi>
Status:	CLOSED ERRATA	QA Contact:	Sam Bible <sbible>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	ahumbe, oezr, osousa, pcreech, rlavi, zhunting
Target Milestone:	6.12.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_ansible-7.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:34: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-07-27 07:52:58 UTC

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

I am copying this bug because: 
BZ was fixed for 6.11 but the same bug can be found on 6.12 snap 3


Description of problem:
The Summary says it all. 

Version-Release number of selected component (if applicable):
sat 6.11 snap 14

How reproducible:
Always

Steps to Reproduce:
1. Open host details -> click on Assign ansible role
2. Now move, the role to the right column (assign) and wait, do not confirm
3. after a short period of time, up to 10 seconds, the role will bounce back to left column


Actual results:
automatically moves back to left column 

Expected results:
stays in the assigned column


Additional info:
number of roles moved to the right, doesn't affect the bounce back. So, it doesn't matter whether only one role is moved to right column or all of them


I have created a short video, can send it to easily understand the BZ. 
Not attaching it due to  file size.

Comment 1 Ron Lavi 2022-07-31 13:00:55 UTC

Hello, I am a bit confused,
for 6.12 we created https://rubygems.org/gems/foreman_ansible/versions/7.1.1
which contains commit https://github.com/theforeman/foreman_ansible/commit/77df91b86e3c387c90c01e94ead45ad5fb16e902.

On 6.12 snap 3, there's `rubygem-foreman_ansible-7.1.0-3`

@osousa @pcreech Hi, I noticed that in 6.12 snap 4, foreman_ansible was bumped to rubygem-foreman_ansible-8.0.1-1.el8sat.noarch.rpm
while it should really be 7.1.z

Moving this bug to POST

Comment 2 Zach Huntington-Meath 2022-07-31 22:08:50 UTC

Hi Ron, that's because https://bugzilla.redhat.com/show_bug.cgi?id=2055979 listed the only fix in 8.0.0, and 8.0.1 had the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2091044. I'll move it back, but would it be possible to get a version of 7.0.z that has 2055979?

Comment 3 Zach Huntington-Meath 2022-07-31 22:10:27 UTC

Sorry, s/7.0.z/7.1.z/.

Comment 4 Ron Lavi 2022-08-04 10:16:05 UTC

https://rubygems.org/gems/foreman_ansible/versions/7.1.2 is out,
and include this fix :)

Comment 5 Sam Bible 2022-08-17 20:10:52 UTC

Version-Release number of selected component (if applicable):
sat 6.12.0 - 6.1

Steps to Reproduce:
1. Open host details -> click on Assign Ansible Role
2. Move a role to the right column, but don't confirm the dialogue. 

Actual results:
Stays in the right column

Expected results:
Stays in the right column

Comment 9 errata-xmlrpc 2022-11-16 13:34: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