Project

General

Profile

Bug #28357

Associate BMC with proxies

Added by Lukas Zapletal about 1 year ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Category:
BMC
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
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.

Associated revisions

Revision b81286b3 (diff)
Added by Lukas Zapletal 4 months ago

Fixes #28357 - BMC Subnet-Proxy association

History

#1 Updated by The Foreman Bot about 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 4 months ago

  • Fixed in Releases 2.2.0 added

#3 Updated by Lukas Zapletal 4 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by The Foreman Bot 3 months ago

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

Also available in: Atom PDF