Closed gtmills closed 1 year ago
@gtmills We double checked this issue and there are a couple of qeustion:
org.openbmc.control.Chassis
is a very old interface and has been discarded [1].[1] https://github.com/openbmc/phosphor-net-ipmid/blob/master/command/guid.cpp#L35
So, my question is: If IBM's system-GUID and system-UUID are the same, we can get the GUID by reading the bmc_persistent_data file[2], otherwise IBM needs to define a new way to get it.
[2] https://github.com/ibm-openbmc/bmcweb/blob/1050/include/persistent_data.hpp
Also, I suspect that the system-UUID used by IBM should have come from VPD[1] on P9, but I did not find this key on the rainier machine.
Can some IBM experts confirm this problem?
@mzipse FYI
There are some discussions on Discord: https://discord.com/channels/775381525260664832/867820390406422538/1106044329635631215
How did this work on 1020? Can we match that? https://github.com/openbmc/phosphor-net-ipmid/blob/master/command/guid.cpp#L35 should be moved to the correct interface and apps such as bmcweb should use it
GUID by reading the bmc_persistent_data file[2]
I find this hacky. Would prefer a D-Bus solution.
I agree with Patrick here:
And... no, you shouldn't read a bmcweb json file in another process.
You're creating an undocumented API expectation by doing that.
How did this work on 1020? Can we match that? https://github.com/openbmc/phosphor-net-ipmid/blob/master/command/guid.cpp#L35 should be moved to the correct interface and apps such as bmcweb should use it
GUID by reading the bmc_persistent_data file[2]
I find this hacky. Would prefer a D-Bus solution.
Well, That's just my suggestion, and the specific implementation method should be done by IBM experts.
I agree with Patrick here:
And... no, you shouldn't read a bmcweb json file in another process. You're creating an undocumented API expectation by doing that.
How did this work on 1020? Can we do the same?
Can we do the same?
Yes, I think it's a legacy problem, and even this problem occurs on our fp5280g2 system
After talking with our own testers, we agree that since this problem has been there all along and this error is only logged in the journal, with no error surfaced to the customer, we are going to close this as a permanent restriction.
Internal defect https://jazz07.rchland.ibm.com:13443/jazz/web/projects/CSSD#action=com.ibm.team.workitem.viewWorkItem&id=430264
Could IPS have a look? Thanks!