Bug 1879151

Summary:	Remote execution status not updating with large number of hosts
Product:	Red Hat Satellite	Reporter:	Brian Smith <briasmit>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	aruzicka, lstejska, nkim
Target Milestone:	6.8.0	Keywords:	Triaged
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:	2020-10-27 13:09:00 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 Brian Smith 2020-09-15 14:28:41 UTC

Description of problem:
If you run a remote execution job on a large number of hosts (for example, 180 hosts), the host status at the bottom does not refresh automatically, and an error is shown "There was an error while updating the status, try refreshing the page.".  Same issue occurs with Chrome and Firefox web browsers.  


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


How reproducible:  Every time


Steps to Reproduce:
1. Select around 180 hosts and run a remote execution job on them


Actual results:
- Host status's at bottom remain "N/A" and do not automatically update
- Message shown: "There was an error while updating the status, try refreshing the page."


Expected results:
- Host status automatically updates (which does work if you select fewer hosts, such as 10)


Additional info:
Javascript console on browser shows a "414 (Request-URI Too Long)" error message, and the URL contains references for each host ID for "host_ids_needing_name_update" and "host_ids_needing_status_update", so the URL is extremely long.

Comment 3 Leos Stejskal 2020-09-16 07:02:11 UTC

Hi,
this issue have been fixed in REX 3.3.x (Sat 6.8.0),
where Hosts status table have been refactored to ReactJS and we don't use JQuery anymore.
Now we don't send all the host ids, just search parameters, so the URL is shorter than before.
I tried to replicate the issue on latest develop branch on job with 1001 hosts and everything went.

Comment 4 Adam Ruzicka 2020-09-17 06:44:02 UTC

Still I find this odd, I recall running much bigger jobs on various version of satellite. It should ask only for statuses of hosts on the current page so it should be limited to 25 or so by default. I could reproduce on 6.7.2 if I manually changed per_page to 1000, but it worked fine for all the values that the ui allows the user to set. Was per_page changed by hand by any chance?

Comment 8 Peter Ondrejka 2020-09-24 15:06:15 UTC

Verified on Satellite 6.8 snap 17

Comment 11 errata-xmlrpc 2020-10-27 13:09:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366