| commit | 6a9553c819147db065966a1b9c4e8264487511fe | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Fri Feb 07 01:16:32 2025 -0600 |
| committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Fri Feb 14 08:34:30 2025 +0000 |
| tree | 2646b682efd76e7b50f122333b9ddff295de5ab5 | |
| parent | 59f91a84fc0456a452741a17d1ca703e977322d8 [diff] |
Fix Present property update in prime inventory This commit adds changes in vpd-manager prime inventory flow to skip updating Present property for FRUs for which vpd-manager doesn't handle Present property. This commit also adds changes to skip updating Present property for a FRU if vpd-manager is not supposed to handle Present property for the FRU, in the scenario where VPD parsing fails for the FRU. Test: ``` Tested on an Everest system. - Reboot BMC with Chassis Off and fan3 plugged in. After reboot, fan3 name and Present property appears properly on GUI. - Reboot BMC with Chassis Off and fan3 plugged out. After reboot, fan3 name and Present property appears properly on GUI. Fan Health shows critical on GUI. - Reboot BMC with Chassis On and fan3 plugged out. After reboot, fan3 name and Present property appears properly on GUI. fan3 Health shows critical on GUI. - Reboot BMC with Chassis On and fan3 plugged in. After reboot, fan3 name and Present property appears properly on GUI. - Recreate genesis boot scenario and reboot BMC with fan3 plugged in. After reboot, fan3 name and Present property appears properly on GUI. - Recreate genesis boot scenario and reboot BMC with fan3 plugged out. After reboot, fan3 name and Present property appears properly on GUI. fan3 Health shows critical on GUI. ``` Change-Id: Ifa6a8909df059a7d3bddd34338d89f0fd8dd5098 Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:
# and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.