Bug 1807335

Summary: Wrong pagination while adding ansible roles
Product: Red Hat Satellite Reporter: Prakash Ghadge <pghadge>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Pramuk <lpramuk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: dmatoule, mhulan
Target Milestone: UnspecifiedKeywords: Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-10 11:57:57 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:
Attachments:
Description Flags
Ansible pagination issue. none

Description Prakash Ghadge 2020-02-26 06:47:05 UTC
Created attachment 1665860 [details]
Ansible pagination issue.

Description of problem:

Wrong pagination while adding ansible roles. 

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

Red Hat Satellite 6.7 Beta

How reproducible:

Always

Steps to Reproduce:
1. add more than 10 ansible roles on the satellite server.
2. Hosts > All Hosts > Select any host and edit > ansible roles > try to add roles
3. While adding the roles, monitor the available roles pagination.

Actual results:

Please find attached a screenshot for more information.

I had 13 ansible roles which are divided into 2 pages.
First page with 10 roles and second page with 13 roles.

I added 10 roles on the client, but the first page is reporting only 1 role when it should report 3. The remaining roles are still on the second page.

Expected results:

After adding the roles, the pagination should update the correct information and should report the roles from the second page to the first page.
Additional info:

Comment 3 Dominik Matoulek 2020-06-10 11:57:57 UTC

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