-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redfish_idrac_firmware_update: fails after initial apply #232
Comments
Thanks @dkaser . we are looking into this. Will get back to you soon. |
@dkaser, could you also please share your TF plan? |
@anupamaloke , TF plans contain sensitive data, so I can't share that here. |
@dkaser , May I know the update versions of Firmware ('From' and 'To' version)? Are you updating to '7.10.50.10'? |
@dkaser , My test environment is the following, I met the same 400 error when I upgrade to the same firmware version 7.00.00.00. I think it is the expectation. The error prompt the upgrade package is invalid or the same so that the upgrade process couldn't been applied. @gokul-srivathsan , what's your thought? |
@dkaser I tested two scenarios for firmware update resource, which scenario did you make?
Scenario 2:
|
@dkaser your reply would be much helpful. |
I think the issue that I was having was related to the order that the updates installed in.... it was doing the iDRAC update last, which then caused the apply to fail when the iDRAC reset. On the subsequent applies, there were no firmware updates to apply, and so the update failed because there was nothing to do. I ended up abandoning redfish_idrac_firmware_update and writing my own logic using simple_update and count to select the updates to apply. |
Terraform CLI and Terraform Redfish Provider Version
Terraform 1.9.5
Redfish Provider Version 1.4.0
Server(s) details and firmware version
Dell R760
iDRAC 9
BIOS Version 2.2.8
Firmware Version 7.10.50.10
Affected Resource(s)
resource "redfish_idrac_firmware_update"
Expected Behavior
The documentation for redfish_idrac_firmware_update directs to have the firmware catalog applied on every run. On the initial apply run, the firmware updates should be applied to the server. On subsequent runs, firmware updates should be applied if the catalog has changed; otherwise, the module should finish successfully.
Actual Behavior
If the catalog has not changed since the last apply, the module fails with an error:
Steps to Reproduce
The text was updated successfully, but these errors were encountered: