Actions
Bug #28357
closedAssociate BMC with proxies
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
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.
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7208 added
Updated by Lukas Zapletal over 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset b81286b353292f117af088776dfaf79c632674c9.
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/7975 added
Updated by Tomer Brisker almost 4 years ago
- Related to Bug #31417: Failed to fetch power status: ERF88-9474 [Foreman::BMCFeatureException] added
Actions