Open bluikko opened 2 years ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @mraineri @renxulei @tomasg2012 @xmadsen click here for bot help
After a bit of troubleshooting, I have found out that idrac_redfish_command
is not needed after modifying the boot order.
So the idrac_redfish_command
fails if there are no changes to apply.
Doesn't this mean it does not work in an idempotent way?
The module should just return with changed=false
in that case and not fail.
cc @bhavya06 @rajeevkallur click here for bot help
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @jyundt click here for bot help
Summary
On Dell r730xd trying to submit a BIOS configuration job with
idrac_redfish_command
first gives a HTTP Error 403 about not enough privileges, but then later gives a HTTP Error 400 about configuration job already submitted. At no point did the module succeed without failure.On the surface it looks like some of the errors were not valid, and the job was actually submitted even though the Ansible module gave an error.
The BIOS configuration job does indeed run when the server is restarted, so either the first 2 errors or the last error are false. The BIOS configuration job was successfully submitted to the Dell BMC even though only errors were output.
In the log below the task was first run when the user
drac_user
had following privileges set in iDRAC:Operator
Login
,Configure
,Logs
,System Control
,System Operations
The second error was with following privileges set in iDRAC:
Operator
Login
,Configure
,Logs
,System Control
,System Operations
,Debug
And the third error was with following privileges set in iDRAC:
Administrator
Login
,Configure
,Configure Users
,Logs
,System Control
,Access Virtual Console
,Access Virtual Media
,System Operations
,Debug
(all privileges)So how could the third attempt fail with 400 job already submitted, if the previous 2 tries failed because of not enough privileges?
One of the errors must be false because the job was indeed submitted.
Edit:
Had a chance to run a BIOS configuration apply job again, this time with the maximum privileges. Just a single execution of
idrac_redfish_command
gives the 400 error as before. So the problem is that error 400 is displayed, task fails, but the configuration apply job is scheduled on the Dell server.Issue Type
Bug Report
Component Name
idrac_redfish_command
Ansible Version
Community.general Version
Configuration
OS / Environment
Steps to Reproduce
Expected Results
The configuration job was submitted without error and when server reboots it runs the configuration job.
Actual Results
The third attempt seems to be correct, because when server is restarted the BIOS configuration job is actually run.
The first 2 attempts indeed failed (seems maximum privileges are needed) and the third one was successful in submitting the BIOS configuration job but somehow still ended in an error about an already committed job.
Edit:
HTTP Error 400 is always displayed and the task execution fails. But the BIOS configuration job is submitted successfully and on server reboot the BIOS configuration job runs.
Code of Conduct