search

HewlettPackard / python-redfish-utility

Python-based utility for interacting with devices supporting a Redfish Service
Other
86 stars 41 forks source link

ilorest v4.0.0.0 connect times out on flashfwpkg push #69

Closed pandatracs closed 1 year ago

pandatracs commented 1 year ago

ilorest v4.0.0.0 flashfwpkg connection times out when pushing a fwpkg to a destination across a wan.

ilorest v3.6.0.0 does not experience this problem when pushing the identical fwpkg from the same source to the same destination.

ilorest v4.0.0.0 Example:

C:>ilorest flashfwpkg U32_2.68_07_14_2022.fwpkg --update_srs --url -u -p *** iLOrest : RESTful Interface Tool version 4.0.0.0 Copyright (c) 2014-2022 Hewlett Packard Enterprise Development LP

Discovering data...Done Uploading firmware: U32_2.68_07_14_2022.signed.flash Successfully checked 'U32_2.68_07_14_2022.signed.flash'. Uploading component U32_2.68_07_14_2022.signed.flash. ERROR: ('Connection aborted.', timeout('The write operation timed out'))

ilorest v3.6.0.0 Example:

C:>ilorest flashfwpkg U32_2.68_07_14_2022.fwpkg --update_srs --url -u -p *** iLOrest : RESTful Interface Tool version 3.6.0.0 Copyright (c) 2014-2022 Hewlett Packard Enterprise Development LP

Discovering data...Done Uploading firmware: U32_2.68_07_14_2022.signed.flash Successfully checked 'U32_2.68_07_14_2022.signed.flash'. Uploading component U32_2.68_07_14_2022.signed.flash. The operation completed successfully. Component U32_2.68_07_14_2022.signed.flash uploaded successfully. Waiting for iLO UpdateService to finish processing the component 00 hour(s) 03 minute(s) 10 second(s) Firmware has successfully been flashed and a reboot is required for this firmware to take effect.

donzef commented 1 year ago

Experienced the same problem with ilO 5 firmware 2.78.

rajeevkallur commented 1 year ago

Looking into it

rajeevkallur commented 1 year ago

image

rajeevkallur commented 1 year ago

was able to upload and flash successfully. Please feel free to reopen if you find it with some platforms.

pandatracs commented 1 year ago

@rajeevkallur Was your testing restricted to local uploads? ilorest v4.0.0.0 works fine when uploading/flashing to systems located across nearby networks. It only fails when uploading to distant systems. This issue does not exist with ilo v3.6.0.0.

I work for a data center company. We have HPE systems distributed across the US, Canada, Europe and Asia. We have VPN interconnects between data centers for such management. Using ilorest v3.6.0.0 I can upload the firmware from a distribution point based in the US to all of our other data centers without issue. However with ilorest v4.0.0.0 this fails with the errors I originally posted. ilorest v4.0.0.0 seems to be sensitive to latency; whereas, v3.6.0.0 was not.

Unless you're testing the upload/flash across long distances, its unlikely you'll see the error.

rajeevkallur commented 1 year ago

ok, we will check this

rajeevkallur commented 1 year ago

This will be fixed in the upcoming release of ilorest 4.2