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:

Can't save more than 10 ansible roles or whatever the default display number per page from hostgroup

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

Red Hat Satellite 6.6

Steps to Reproduce:

1) have 11 or more ansible roles in satellite
2) edit a hostgroup, go to "Ansible Roles"
3) make sure "10 per page" is selected
4) add 11 ansible roles to the hostgroup
5) save
6) edit the hostgroup again, go to "Ansible Roles"
7) only the first 10 roles are applied
8) change "10 per page" to "20 per page"
9) add 11 ansible roles to the hostgroup
10) save
11) edit the hostgroup again, go to "Ansible Roles"
12) all 11 ansible roles should be applied to the hostgroup

Actual results:

Unable to add more ansible roles.

Expected results:

Should be able to add more than 10 ansible roles.

seems as duplicate of BZ 1766906

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