Bug 2249905

Summary:	Issue when checking the ansible task via satellite, after checking multiple servers
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Ansible - Configuration Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.6	CC:	nalfassi, rlavi
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-21 11:44:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2023-11-15 21:36:10 UTC

Description of problem:
After selecting multiple servers and running the ansible roles, we can see all the tasks on all the servers, even if the role is not assigned to them.

Version-Release number of selected component (if applicable):
6.13.z

How reproducible:
100%

Steps to Reproduce:
1. Create and import a role (in this example, one for rhel7 and another one for rhel8)
2. Assign them to hg respectively, hg_rhel7 with role7 and hg_rhel8 with role8
3. Select both servers and check to deploy the roles

Actual results:
The play will be executed correctly and will deploy only the content for that specific hg, for example, for the server on hg_rhel7, only the role7 will be deployed. However, when clicking on top of the server, we can see the task for rhel7 and also the task for rhel8

Expected results:
When clicking on rhel7 server, be able to see ONLY the tasks related to the hg_rhel7/role7 and nothing else.

Additional info:

Comment 4 nalfassi 2023-11-21 11:44:02 UTC

BZ #2249905 has been reviewed and confirmed as a duplicate of #2156532. To streamline our bug tracking system and avoid redundancy, we have closed BZ #2249905. However, if you believe that the closure was made in error or if there are valid reasons to reconsider, we encourage you to reopen the BZ.

*** This bug has been marked as a duplicate of bug 2156532 ***