check_redfish: No network adapter result in "Unable to connect to Host '0.0.0.0', max retries exhausted"
Hi,
found a small bug on a HPE ProLiant RL300 Gen11 (CPU: 1, MEM: 512GB) - BIOS: R11 v1.20 (04/14/2023)
https://github.com/bb-Ricardo/check_redfish/blob/next-release/cr_module/nic.py#L295
On one host “system_response” only contains “Links/EthernetInterfaces/@odata.id” but not “Links/NetworkAdapters/@odata.id”
That results in
ethernet_interfaces_path = /redfish/v1/Systems/1/EthernetInterfaces/
network_adapter_path = None
network_adapter_response now tries to fetch data: https://github.com/bb-Ricardo/check_redfish/blob/next-release/cr_module/nic.py#L303
INFO: Attempt 1 of None?$expand=.
2023-06-01 14:17:17,505 - DEBUG: Starting new HTTPS connection (1): 0.0.0.0none:443
2023-06-01 14:17:17,510 - INFO: Retrying None?$expand=. [HTTPSConnectionPool(host='0.0.0.0none', port=443): Max retries exceeded with url: /?$expand=. (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fecc10f0f70>: Failed to establish a new connection: [Errno -2] Name or service not known'))]
2023-06-01 14:17:18,512 - DEBUG: HTTP REQUEST (GET) for None?$expand=.:
[CRITICAL]: Unable to connect to Host '0.0.0.0', max retries exhausted.
It added the “None” to the IP which results in the Name or service not known Error.
When I manually set
network_adapter_path = f"{redfish_url}/NetworkInterfaces"
then it exits correctly:
[UNKNOWN]: Request error: No network adapter or interface data returned for API URL '/redfish/v1/Systems/1//NetworkInterfaces'
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- fixes issue with network information on iLO 6 interfaces #116 — committed to bb-Ricardo/check_redfish by bb-Ricardo 6 months ago
- fixes issue with non existing chassi NetworkAdapters #116 — committed to bb-Ricardo/check_redfish by bb-Ricardo 6 months ago
Happy new year!
We are using the new version in prod now and I haven’t noticed any problems so far, thanks!
Sometimes we have checks flapping to UNKNOWN because of this: [UNKNOWN]: None : Request error: No ‘chassis’ property found in root path ‘/redfish/v1’
But this also happened in the old version and I believe it’s a Dell Redfish API problem. It doesn’t return the data sometimes (but unrelated to this issue, so I will close it)
Great, thank you for testing.
Just test it once you have time and just close the issue if everything looks good.
Also enjoy the holidays and all the best for 2024.
Yes it is an iLO 6 server, but apparently AMS - Agentless Management Service isn’t installed on that system yet, maybe that’s the reason why it doesn’t work.
I need to check if it’s okay to provide a mockup.