Project

General

Profile

Actions

Bug #38973

closed

IP address not retrieved when using SSH API of BMC

Added by Susumu Sakamoto 6 months ago. Updated 8 days ago.

Status:
Closed
Priority:
Normal
Category:
BMC
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Summary

This issue is related to #38972 (Foreman issue). A Foreman PR that fixes #38972 is being prepared.
However, applying this PR introduces the following problem, requiring a simultaneous Smart Proxy PR to fix it.

When an FQDN is configured for the BMC interface, during IP address retrieval using SSH API of BMC, Smart Proxy returns the FQDN that was used as the connection target.
Consequently, the FQDN is displayed in the "IP" field of the BMC tab in the Host Details (Legacy UI) of the Foreman Web UI.

Details

This issue is specific to SSH API of BMC.
The Foreman Pull Request (PR) prepared to resolve the existing issue #38972 modifies how the Smart Proxy BMC API is called.
Specifically, it changes Foreman to pass the FQDN specified in the BMC interface settings as the :host parameter.
This modification enables Smart Proxy to communicate with the BMC using the specified FQDN.
However, when attempting to retrieve the BMC's IP address using SSH API of BMC, the current Smart Proxy implementation returns the FQDN it received as the connection target itself back to Foreman, treating it as the IP address.
Since the "IP" field in the BMC tab of the Host Details (Legacy UI) within the Foreman Web UI is expected to display the BMC's IP address, receiving an FQDN from Smart Proxy results in the FQDN being directly displayed in that field.
This behavior deviates from the original user expectation of obtaining IP address information and leads to an incorrect UI display.

Steps to Reproduce

  1. Apply the Foreman PR that fixes #38972 and restart Foreman.
  2. Prepare a machine that can be shut down via SSH commands. Configure /etc/foreman-proxy/settings.d/bmc.yml to allow Foreman to execute SSH commands, and then restart Smart Proxy.
  3. In the Foreman Web UI, configure the BMC interface for the machine from step 1) with an FQDN and SSH API of BMC. Navigate to the Host Details (Legacy UI) and display the BMC tab.
  4. The FQDN will be displayed in the "IP" field of the BMC tab.

Expected Behavior

Even when an FQDN and SSH API of BMC are configured for the BMC interface, Smart Proxy should return the actual IP address of the BMC during IP address retrieval.
The correct IP address should then be displayed in the "IP" field of the BMC tab in the Host Details (Legacy UI) of the Foreman Web UI.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #38972: Redfish power operation fails due to certificate authentication error with FQDNClosedSusumu SakamotoActions
Actions #1

Updated by Susumu Sakamoto 6 months ago

  • Related to Bug #38972: Redfish power operation fails due to certificate authentication error with FQDN added
Actions #2

Updated by The Foreman Bot 6 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/933 added
Actions #3

Updated by The Foreman Bot 4 months ago

  • Fixed in Releases 3.19.0 added
Actions #4

Updated by Susumu Sakamoto 4 months ago

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

Updated by Ewoud Kohl van Wijngaarden 8 days ago

  • Red Hat JIRA set to SAT-42081
Actions

Also available in: Atom PDF