Fixed event id issue on Hardware deconfiguration page

[vedangimittal]

• Event id now getting updated for deconfigured core on Hardeware deconfiguration page
• Defect: https://jazz07.rchland.ibm.com:13443/jazz/web/projects/CSSD#action=com.ibm.team.workitem.viewWorkItem&id=670225

[Nikhil-Ashoka]

I don't think there is difference in change that would fix this issue...
The new change is accessing the same path....

[vedangimittal]

Previously, the value for 'Event Id' in the code was being accessed from this redfish key - Status.Conditions.LogEntry, which was undefined because there is no such parameter as 'LogEntry' under Status.Contiditions

---

That's why in the current Redfish, the 'Event Id' value needs to be fetched from the key - '/Status/Conditions/0/LogEntry'
That is the only change made in the code

[Nikhil-Ashoka]

@vedangimittal, Which all releases this change is applicable?

[deepakala-k]

Please abandon this fix. It will break the earlier version. The redfish output is wrong. Just identified the issue and fixed it. Will raise a PR and provide a link shortly. @vedangimittal please close this PR.

[deepakala-k]

This is the correct and the expected output

curl -k -H "X-Auth-Token: $bmc_token" -XGET https://${BMC_IP}/redfish/v1/Systems/system/Processors/dcm0-cpu0/SubProcessors/core2
{
  "@odata.id": "/redfish/v1/Systems/system/Processors/dcm0-cpu0/SubProcessors/core2",
  "@odata.type": "#Processor.v1_18_0.Processor",
  "Enabled": false,
  "Id": "core2",
  "Name": "core2",
  "Status": {
    "Conditions": [
      {
        "LogEntry": {
          "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/492"
        },
        "Message": "The reason for the resource isolation: Predictive",
        "MessageArgs": [
          "Predictive"
        ],
        "MessageId": "OpenBMC.0.2.HardwareIsolationReason",
        "Severity": "Warning",
        "Timestamp": "2025-01-27T17:01:53+00:00"
      }
    ],
    "Health": "Critical",
    "State": "Disabled"
  }
}

[vedangimittal]

Will close the PR, since its a backend issue.