ibm: Error interfaces for VPD parse failure.
This commit defines interfaces to log errors with respect to the
type of failure in processing VPD data by parser.
In case there is failure to process and publish VPD data by the
parser, respective interface will be used to log respective PEL
in the system.
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Iaac10ab96c9e8d6482ea6a713c78a5e6ffc793fb
diff --git a/com/ibm/VPD.errors.yaml b/com/ibm/VPD.errors.yaml
index c2708ac..ee4b735 100644
--- a/com/ibm/VPD.errors.yaml
+++ b/com/ibm/VPD.errors.yaml
@@ -13,3 +13,15 @@
On IBM systems, certain VPD data must be available
for the system to boot. This error is used to
indicate that no valid data was found by the BMC.
+- name: InvalidEepromPath
+ description: EEPROM path is invalid. Parser failed to access the
+ path.
+- name: InvalidVPD
+ description: VPD file is not valid. Mandatory records are missing
+ in VPD file.
+- name: EccCheckFailed
+ desciption: Invalid VPD data. Ecc check for the data failed.
+- name: InvalidJson
+ description: Invalid Json file.
+- name: DbusFailure
+ description: DBus error occurred.