Red Hat Bugzilla – 2036338 – [regression]The "Host Configuration status for Ansible" widget on the Satellite WebUI Dashboard returns zero instead of correct numbers of host
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
"Host Configuration status for Ansible" widget on the Satellite WebUI returns zero for all options mentioned in the widget instead of returning the correct number of hosts. The value does not change at all.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Actual results:
The widget returns value as zero for all hosts. It does not matter if the ansible command/playbook was successfully executed or failed.
Expected results:
Should return the correct number of hosts
Additional info:
Accoridng to bz, issue should be fixed in 6.10, but it still remains.
https://bugzilla.redhat.com/show_bug.cgi?id=1978337