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: BMC feature is not selecting the correct smart proxy/Capsule if multiple Capusle Server are having BMC feature enabled.
Version-Release number of selected component (if applicable):
Satellite server 6.5
Capsule server 6.5
How reproducible:
Steps to Reproduce:
1. Configure BMC feature on both Satellite and Capsule Server.
2. Configure few baremetal host with Satellite Server and few with Capsule server
3. If the BMC feature is enabled on Satellite and when we try to access the host connected to Capsules it is using Satellite server to connect to the baremetal server and its failing due to connectivity.
Actual results:
When the BMC feature is enabled on Satellite and Capsule when we try to access the host connected to Capsules it is using Satellite server to connect to the baremetal server and its failing due to connectivity.
Expected results:
BMC feature should able to select Capsule Server while connecting with the Capsule server.
Additional info:
Scenario -
Configure BMC fetaure on both Satellite and Capsule server.
Configure two baremetal server with each Satellite and Capsule server.
Try to access baremetal server configure with Capsule and it fails due to connetivity. By default it uses Satellite Server to connect with the baremetal server configure with Capsule server.
There is a patch ready for review, see the links above. We will not be backporting this issue into any release, it will eventually become part of future Satellite version.
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.9 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-2021:1313