[Redfish] redfish/update_service/test_firmware_tftp_upload_image.robot check FirmwareInventory state failed

[ckstyle001]

I use openbmc-test-automation v3.0-stable branch and run the redfish/update_service/test_firmware_tftp_upload_image.robot test case.

After uploading the BMC image via TFTP, when checking the FirmwareInventory status, it is confirmed that it is "Enabled" and not "Disabled" & "Updating". Do we need to validate the "Disabled" & "Updating" status in the robot source code?

---

robot -v OPENBMC_HOST:100.100.100.64 -v TFTP_SERVER:x.x.x.x -v IMAGE_FILE_NAME:v2.12.2.all.tar --include TFTP_Download_Install_With_ApplyTime_OnReset_Policy redfish/update_service/test_firmware_tftp_upload_image.robot

$ curl -H "X-Auth-Token: $token" -k https://${bmc}/redfish/v1/UpdateService/FirmwareInventory/ece98953
{
  "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory/ece98953",
  "@odata.type": "#SoftwareInventory.v1_1_0.SoftwareInventory",
  "Description": "BMC image",
  "Id": "ece98953",
  "Name": "Software Inventory",
  "RelatedItem": [
    {
      "@odata.id": "/redfish/v1/Managers/bmc"
    }
  ],
  "[email protected]": 1,
  "Status": {
    "Health": "OK",
    "HealthRollup": "OK",
    "State": "Enabled"
  },
  "Updateable": true,
  "Version": "v2.12.2"
}

[gkeishin]

@susilsi7 please take a look into this.

[susilsi7]

This code is designed on old API and has to be migrated on Task API.