Bug 2251030

Summary:	Clarification Needed on Determining Capsule for Remote Execution in Pull Mode with Yggdrasild Registration when using load-balancer
Product:	Red Hat Satellite	Reporter:	Ganesh Payelkar <gpayelka>
Component:	Remote Execution	Assignee:	Aneta Šteflová Petrová <apetrova>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.14.0	CC:	alazik, apetrova, aruzicka, ehelms, smajumda
Target Milestone:	Unspecified	Keywords:	Documentation, 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:36:45 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-22 13:01:22 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/configuring_capsules_with_a_load_balancer/index#Verifying_the_Load_Balancing_Configuration_load-balancing

Section Number and Name: 

Chapter 5. Setting the Load Balancer for Host Registration

Describe the issue: 

How can the capsule for a client with Yggdrasild be determined, considering the registration process involves going through a VIP/Load-Balancer?

What are the steps required to configure remote execution for a pull client when a load balancer is involved?

Suggestions for improvement: 

If this process is not supported or has any limitation then it should be added to the documentation.

Additional information: 


update existing content to provide guidance on how to determine the precise capsule (content source) for a client using yggdrasild. 

Consider incorporating step-by-step instructions or clarifications on the process to ensure that remote execution in pull mode functions correctly and does not result in timeouts. Include any relevant configuration details or best practices that users should be aware of when dealing with hosts registered through capsules with a VIP/Load-balancer and a master satellite content source.

Comment 1 Marie Hornickova 2023-11-22 18:48:25 UTC

Hello Ganesh,
Many thanks for raising this issue.
After the BZ has gone through proper team triage, the documentation team will look into this and will informs about the progress on the implementation in this ticket.
Thank you!

Comment 6 Aneta Šteflová Petrová 2024-03-13 13:13:03 UTC

We confirmed that the support limitations documented in Configuring Capsules with a Load Balancer[1] are still valid. Remote execution pull mode falls outside of what is supported for load balancing. The following BZ tracks an RFE to add that functionality: https://bugzilla.redhat.com/show_bug.cgi?id=2251858

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/configuring_capsules_with_a_load_balancer/index#Load_Balancing_Solution_Architecture_load-balancing

From the documentation perspective, we cannot provide the requested step-by-step instructions. What we can do is help make these support limitations clearer, perhaps by highlighting them throughout the document at relevant places.

Comment 7 Eric Helms 2024-06-06 16:36:45 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.