Project

General

Profile

Actions

Bug #28357

closed

Associate BMC with proxies

Added by Lukas Zapletal almost 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
BMC
Target version:
-
Difficulty:
Triaged:
Yes
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 1 (0 open1 closed)

Related to Foreman - Bug #31417: Failed to fetch power status: ERF88-9474 [Foreman::BMCFeatureException]ClosedActions
Actions #1

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
Actions #2

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases 2.2.0 added
Actions #3

Updated by Lukas Zapletal over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by The Foreman Bot about 4 years ago

  • Pull request https://github.com/theforeman/foreman/pull/7975 added
Actions #5

Updated by Tomer Brisker almost 4 years ago

  • Related to Bug #31417: Failed to fetch power status: ERF88-9474 [Foreman::BMCFeatureException] added
Actions

Also available in: Atom PDF