Bug #28357
Associate BMC with proxies
Pull request:
Fixed in Releases:
Found in Releases:
Description
Subnet has no association with Proxy, therefore Foreman picks up proxies with BMC features "randomly". When there is nothing found, it uses first proxy with BMC feature available. This is based on an assumption that all BMC proxies has direct access to all servers which is not the case.
The solution is to create new BMC association so Foreman uses the correct BMC proxy for operations associated with the BMC interface. To prevent confusion, I suggest also to remove the fallback mechanism - if no association is found than use the "first" proxy available. We should explicitly error out instead.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot over 1 year ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7208 added
#2
Updated by The Foreman Bot 8 months ago
- Fixed in Releases 2.2.0 added
#3
Updated by Lukas Zapletal 8 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset b81286b353292f117af088776dfaf79c632674c9.
#4
Updated by The Foreman Bot 6 months ago
- Pull request https://github.com/theforeman/foreman/pull/7975 added
#5
Updated by Tomer Brisker 3 months ago
- Related to Bug #31417: Failed to fetch power status: ERF88-9474 [Foreman::BMCFeatureException] added
Fixes #28357 - BMC Subnet-Proxy association