Request issue: No processor data returned for API URL

[Napsty]

Hi there,

Seen this error, which results in an UNKNOWN exit state, the first time today:

Request issue: No processor data returned for API URL '/redfish/v1/Systems/FCHXXXXXXXX/Processors/CPUnil': got '{'code': 'InternalError', 'message': "/opt/flash/cisco/bin/redfish/req_handler.lua:474: attempt to index local 'rv' (a boolean value)"}' for API path '/redfish/v1/Systems/FCHXXXXXXXX/Processors/CPUnil', Returned data from API URL '/redfish/v1/Systems/FCHXXXXXXXX/Processors' contains no processor information

This is on a UCS C220 M4.

Ever seen this before? Any ideas how to fix it?

[bb-Ricardo]

Hi @Napsty,

I have never seen this error before. Does this happen permanently or just randomly and then resolves itself again?

It seems like a bug in the Cisco CIMC. The list of processors returned this processor /redfish/v1/Systems/FCHXXXXXXXX/Processors/CPUnil. I suspect that it meant to return CPU0 or another CPU. But instead did not find the CPU id and returned a nil.

Best is to report this to Cisco. Maybe an update of the CIMC sollves this issue.

[Napsty]

It came out of the blue, the same CIMC returned the API information fine before. Now the plugin flaps between "too many retries" and this UNKNOWN error. I will try with a CIMC reboot.

[Napsty]

Found this hint: https://community.cisco.com/t5/devnet-general-discussions/receiving-empty-response-for-certain-resource-from-cisco-ucs-xml/m-p/4894632/highlight/true#M2025

if Cisco UCS is reset, it will not have detailed CPU, memory, or adapter inventory information until the next time the host is powered on

As the CIMC was rebooted previously, maybe I need a full server reboot as well.

[bb-Ricardo]

and, could you solve the mistery?

[Napsty]

Not yet. Needs a maintenance (night) window. Will let you know if this resolves after a full reboot.

[bb-Ricardo]

I will close this issue as there was no response for six month. If you think this is still an issue related to the plugin, please fell free to open a new issue

[Napsty]

In the meantime the server had been rebooted and this issue.was resolved, CPU information can be obtained again from CIMC. Thanks for the ping. ☺️