Bug 2251858

Summary:	[RFE] Enable Load Balancing support for pull-mqtt
Product:	Red Hat Satellite	Reporter:	Ganesh Payelkar <gpayelka>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	akapse, aruzicka, dsinglet
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
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:	2024-06-06 16:37: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 Ganesh Payelkar 2023-11-28 05:23:27 UTC

Description of problem:

[RFE] Enable Load Balancing support for pull-mqtt

When a host is registered on the satellite through a capsule and utilizes a VIP that consolidates multiple capsules, the content source is the master satellite. For remote execution in pull mode to execute jobs properly, a specific capsule (content source) is required; otherwise, timeouts may occur.

There is a need for additional support in the load balancer to facilitate load-balanced remote execution in pull mode.
The load balancer/VIP should be capable of supporting pull mode operations, ensuring seamless functionality for jobs executed via the load balancer.

Comment 2 Eric Helms 2024-06-06 16:37:00 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.