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:
In the Ansible Roles tab of the host group only 10 roles are shown while more are available.
The forward button is grayed out and showing the next 10 roles is not possible.

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

How reproducible:
- Only when more than 10 roles are available

Steps to Reproduce:
1. Go to a Host Group and select the Ansible Roles tab
2. If you have more than 10 roles the forward button is still disabled
3.

Actual results:
- Forward button is disabled even if more than 10 roles are available

Expected results:
- If more than 10 roles are available the foreward button should work as expected

Additional info:
- Workaround is to go to the drop-down filed and select 5 roles to show.
- Then the forward button is enabled.

The entire tab lives in foreman-ansible, I expect the fix will need to happen there.

BZ #2145258 has been reviewed and confirmed as a duplicate of #2166466. To streamline our bug tracking system and avoid redundancy, we have closed BZ #2145258. 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 2166466 ***