| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
It was spelled wrong. Also, there is no need to compare
against the local object if it is globally critical, so
make the check easier.
Tested: Made a drive error and the led blinked
Change-Id: I52590f0888380a6d7460e9220d814174cb17a52b
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
Mapper no longer supports the old one.
Tested: Mapper shows associations again, available in
redfish
Change-Id: I876c7b9be4d24e3bc73e4b5ff0e9290e422baaa9
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
Based on redfish design, there is global and non global
critical / warning to monitor health. Take these and
use them to trigger the led.
Tested: Created IPMI ME health event and saw led turn
to blinking yellow
Change-Id: I0ddcd142355b148b6ae07b6d0e9274c3e99a049e
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
This adds an association manager based on Redfish health
whitepaper to do a rollup of subcomponent health.
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/21380
Tested:
Chassis health rollup works with upstream patch 21798
{
"@odata.context": "/redfish/v1/$metadata#Chassis.Chassis",
"@odata.id": "/redfish/v1/Chassis/WFP_Baseboard",
"@odata.type": "#Chassis.v1_4_0.Chassis",
"ChassisType": "RackMount",
"Id": "WFP_Baseboard",
"Links": {
"ComputerSystems": [
{
"@odata.id": "/redfish/v1/Systems/system"
}
],
"ManagedBy": [
{
"@odata.id": "/redfish/v1/Managers/bmc"
}
]
},
"Manufacturer": "Intel Corporation",
"Model": "S2600WFT",
"Name": "WFP_Baseboard",
"PartNumber": "123456789",
"Power": {
"@odata.id": "/redfish/v1/Chassis/WFP_Baseboard/Power"
},
"PowerState": "Off",
"SerialNumber": "123454321",
"Status": {
"Health": "Warning",
"HealthRollup": "Critical",
"State": "StandbyOffline"
},
"Thermal": {
"@odata.id": "/redfish/v1/Chassis/WFP_Baseboard/Thermal"
}
}
Change-Id: I1d944f31749f6eae952573078ad410547ae9faea
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
RetriggerLEDUpdate method added in callback-manager serivce. Used
to re-init the LED state in xyz.openbmc_project.LED.GroupManager.
This can be used by manufacturing revert function to re-init the
LED to the correct state, after any testing.
Tested:
1. Manually updated the LED state and called RetriggerLEDUpdate
method, which re-init the LED status, and set's to the correct one.
Change-Id: I4272ae0e02c81bea36db587f83e0a7ef2b91059e
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
|
|
The led-manager priority doesn't work as well as we'd
hoped and we can occasionally see both blinking yellow
and green at the same time. To fix this handle priorities
in the callback manager.
Tested-by: Set warning and critical at the same time, only
saw critcial.
Change-Id: If0c5b7c2411ca1fd3dc74e407773e8f56e6c675f
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
Callback manager setups matches and sets properties on
dbus.
Tested-by: used sensor override to make sensors assert
critical and warning interfaces and saw led change. also
caught a few buggy threshold settings using led.
Change-Id: I06c164b749febbc3e81cb3db5f7a0a2b72b3678f
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
