Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Today load balanced capsules requires sticky sessions enabled on the load balancer and when one capsule goes down, the clients must "yum clean all" to get its metadata from the other Capsule. This probably means the same RPM repository on 2 different Capsules should contain the same metadata path and actual metadata so the client doesn't warn against newer/older repo metadata when requesting something from the other Capsule.
As a user, I should not have to refresh clients yum metadata when a request hits a different Capsule than it has previously so that Capsule fail-overs are transparent to the client.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Here is the doc describing the configuration of load balancer with sticky sessions:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html-single/load_balancing_guide/index#installing-the-load-balancer
Comment 4pulp-infra@redhat.com
2020-03-31 17:48:07 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2020-03-31 17:48:09 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 6Tanya Tereshchenko
2020-05-01 13:25:56 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 (Moderate: Satellite 6.11 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-2022:5498