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.
Bug 1776470 - BMC feature is not able to select correct proxy if configured on the multiple Capusle Server
Summary: BMC feature is not able to select correct proxy if configured on the multiple...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Power & BMC
Version: 6.6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: 6.9.0
Assignee: Lukas Zapletal
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-25 18:09 UTC by Surjeet Salvi
Modified: 2024-06-13 22:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:12:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28357 0 Normal Closed Associate BMC with proxies 2021-02-16 12:43:20 UTC

Description Surjeet Salvi 2019-11-25 18:09:21 UTC 
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.
Comment 3 Lukas Zapletal 2019-11-26 07:05:59 UTC 
I can confirm this misbehavior.
Comment 6 Surjeet Salvi 2020-01-29 09:03:47 UTC 
Hello Team,

Can we have an update on the Bugzilla.

Regards
Surjeet
Comment 7 Lukas Zapletal 2020-01-31 13:24:48 UTC 
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.
Comment 12 Bryan Kearney 2020-07-17 20:03:50 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/28357 has been resolved.
Comment 15 Brad Buckingham 2020-11-13 19:53:14 UTC 
Fix is in Satellite 6.9 SNAP 1 with foreman-2.3.0-0.7.rc1.el7sat.noarch
Comment 19 errata-xmlrpc 2021-04-21 13:12:13 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.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
Note You need to log in before you can comment on or make changes to this bug.