Remove link from Chassis to PCIeDevice
The commit removes current support that assumes 1:1 system:Chassis for
Chassis/PCIeDevices.
Current implementation populates the same collection of PCIeDevices
with chassis and with system.
Since the path is /redfish/v1/Systems/system/PCIeDevices and we already
have a link from /redfish/v1/Systems/system/, removing the link here in
Chassis.
The link from Chassis to /redfish/v1/Systems/system/PCIeDevices is
unexpected.
For systems with multiple chassis the current assumption does not hold
true. It breaks there, as it assumes all PCIeDevices are in all Chassis.
This is just a link and since another link from system resource already
exists. The case of walking the whole tree isn't broke.
And so, this should not break clients.
Validator has been executed with no new errors.
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Id3af01ec99708c36b5fff2a63f04ffd722f6c3a2
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
diff --git a/Redfish.md b/Redfish.md
index 93105eb..91c2c01 100644
--- a/Redfish.md
+++ b/Redfish.md
@@ -197,7 +197,6 @@
- HotPluggable
- Links/ComputerSystems
- Links/ManagedBy
-- PCIeDevices
- Power
- Shall be included if component contains voltage/current sensing components,
otherwise will be omitted.
diff --git a/redfish-core/lib/chassis.hpp b/redfish-core/lib/chassis.hpp
index e827f03..6d5e587 100644
--- a/redfish-core/lib/chassis.hpp
+++ b/redfish-core/lib/chassis.hpp
@@ -508,9 +508,6 @@
.jsonValue["Actions"]["#Chassis.Reset"]["@Redfish.ActionInfo"] =
boost::urls::format("/redfish/v1/Chassis/{}/ResetActionInfo",
chassisId);
- asyncResp->res.jsonValue["PCIeDevices"]["@odata.id"] =
- "/redfish/v1/Systems/system/PCIeDevices";
-
dbus::utility::getAssociationEndPoints(
path + "/drive",
[asyncResp, chassisId](const boost::system::error_code& ec3,