blob: 514a4496a229db1b20f0d88e65685d63983981e1 [file] [log] [blame]
SunnySrivastava198426ff1c82020-02-26 05:48:39 -06001- name: LocationNotFound
2 description: Location is not found.
3- name: NodeNotFound
4 description: Node number is not found.
5- name: PathNotFound
6 description: Inventory path is not found.
7- name: RecordNotFound
8 description: Record not found.
9- name: KeywordNotFound
10 description: Keyword is not found.
SunnySrivastava19842eba3cb2020-08-18 08:14:08 -050011- name: BlankSystemVPD
Patrick Williamsa1347412022-12-06 10:56:22 -060012 description:
13 System VPD is blank on both hardware and cache. On IBM systems, certain
14 VPD data must be available for the system to boot. This error is used to
Patrick Williams8da396c2022-03-14 14:21:02 -050015 indicate that no valid data was found by the BMC.
SunnySrivastava19849c5f64a2020-08-24 02:00:00 -050016- name: InvalidEepromPath
Patrick Williamsa1347412022-12-06 10:56:22 -060017 description: EEPROM path is invalid. Parser failed to access the path.
SunnySrivastava19849c5f64a2020-08-24 02:00:00 -050018- name: InvalidVPD
Patrick Williamsa1347412022-12-06 10:56:22 -060019 description: VPD file is not valid. Mandatory records are missing in VPD file.
SunnySrivastava19849c5f64a2020-08-24 02:00:00 -050020- name: EccCheckFailed
21 desciption: Invalid VPD data. Ecc check for the data failed.
22- name: InvalidJson
23 description: Invalid Json file.
24- name: DbusFailure
25 description: DBus error occurred.
Alpana074450b762022-01-27 22:11:08 +053026- name: UnknownSystemType
27 description:
28 Could not determine which device tree to switch to, as system type is
29 unknown. Please check the HW and IM keywords in the system VPD and check
30 if they are programmed correctly.