Bug 2171874

Summary:	Clicking on "Run all Ansible roles" via Host Groups shows a blank page with no indication of running jobs
Product:	Red Hat Satellite	Reporter:	Jayant Bhatia <jbhatia>
Component:	Ansible	Assignee:	nalfassi
Status:	POST ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.12.0	CC:	aruzicka, bbuckingham, jsenkyri, karnsing, magaphon, msunil, nalfassi, rlavi, smallamp
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_ansible-7.1.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Jayant Bhatia 2023-02-20 16:56:57 UTC

Description of problem:


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


How reproducible: Always


Steps to Reproduce:

1. Navigate to Satellite WebUI -> Configure -> Host Groups and create a host group with relevant information. Ensure 'Ansible Roles' are added to the host group.

2. Assign this newly created host group to hosts registered with Satellite.

3. Navigate to Satellite WebUI -> Configure -> Host Groups -> For the listed hostgroup, within 'Actions' column, select drop down and click on 'Run all Ansible Roles'.


Actual results: A blank page in the main frame is shown but no indication of any progress or result of the running jobs


Expected results: A blank page should not get displayed and some indication about the status of running jobs should be shown.


Additional info: This issue is also reproducible on Satellite 6.12

Comment 4 Adam Ruzicka 2023-02-22 09:25:26 UTC

Per #1 and #3, it is already fixed in 6.13, it was fixed by the upstream issue and pull request I just linked.

If we decide to bring it in for 6.12, it should be a fairly straightforward cherry pick.

Comment 5 Sudhir Mallamprabhakara 2023-02-28 04:36:54 UTC

should we change the version on this to 6.12?

Comment 6 nalfassi 2023-03-07 13:59:47 UTC

*** Bug 2169986 has been marked as a duplicate of this bug. ***