Bug 2174403

Summary:	job wizard host selection ignores pagination if triggered from the hosts page
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	aruzicka
Target Milestone:	Unspecified	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-08 08:59:48 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:

Description Peter Ondrejka 2023-03-01 13:51:43 UTC

Description of problem:
Basically it is the same thing as 1477550 only with new rex wizard

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

How reproducible:
Always

Steps to Reproduce:
1. Have more than one page of hosts
2. In the hosts table click a checkbox to select all hosts
3. in the info modal confirm selection of all hosts from all pages
4. select action > schedule remote job

Actual results:
In the wizard step 2, see the host selection applies only to 20 hosts (= 1st page)

Expected results:
All selected hosts are recognized in wizard

Additional info:

Comment 1 Adam Ruzicka 2023-03-17 11:47:24 UTC

Note:
It works when you first search for something in host list and then select all. If you don't search, then we pass the right parameter, but with a null value, which is then treated as if it was not provided at all. Passing an empty string instead should work.

Comment 2 Adam Ruzicka 2023-06-08 08:59:48 UTC

This looks like a duplicate of BZ2196076, so I'll go ahead and close this one. If you feel the two BZs are about different things, feel free to reopen.

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