Bug #39300
openIdentify LED on operation fails due to invalid IndicatorLED value On
Description
Summary¶
Chassis IndicatorLED identify action uses invalid Redfish value On instead of Lit, causing LED identification to fail.
Description¶
In the BMC LED identification implementation, the identifyon method sends IndicatorLED: On via the Redfish API. However, according to the Redfish specification, the valid value for turning on the indicator LED is Lit, not On.
As a result, the identify-on operation silently fails and the chassis indicator LED does not turn on.
The valid values for IndicatorLED in the Redfish specification are Lit, Blinking, and Off.
Steps to Reproduce¶
- Execute the chassis identify-on command via API:
curl -u 'USER:PASSWORD' -X GET 'http://<Smart-Proxy-FQDN>:8000/bmc/<BMC_ADDRESS>/chassis/identify/on?bmc_provider=redfish' - Observe the indicator LED state on the target chassis by either physically checking the hardware or querying the Redfish API directly (e.g.
curl -u 'USER:PASSWORD' -X GET 'https://<BMC_ADDRESS>/redfish/v1/Chassis/0'and check theIndicatorLEDfield in the response)
Actual Behavior¶
The API request completes, but the chassis indicator LED does not turn on. The Redfish API rejects or ignores the invalid On value, as it is not a valid IndicatorLED state per the Redfish specification.
Expected Behavior¶
The chassis indicator LED should turn on (lit) when the identify-on command is executed. The Redfish API payload should use Lit instead of On.
Updated by Yusuke Hirota about 1 month ago
- Project changed from Foreman to Smart Proxy
- Category changed from BMC to BMC
Updated by The Foreman Bot about 1 month ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/939 added