Skip to content
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

[BUG]: idrac_reset fails when idrac is InUse state #652

Closed
markatdxb opened this issue Apr 30, 2024 · 4 comments · Fixed by #675
Closed

[BUG]: idrac_reset fails when idrac is InUse state #652

markatdxb opened this issue Apr 30, 2024 · 4 comments · Fixed by #675
Assignees
Labels
needs-triage Issue requires triage. type/bug Something isn't working
Milestone

Comments

@markatdxb
Copy link

markatdxb commented Apr 30, 2024

Bug Description

issue started recently - used to work without any problems in the past - i started observing this in collection 9.2.0
we run deployment from ISO where ISO is mounted for default 120min
as deployments usually finish faster, we have process to reset idrac in order to unmount the ISO from iDrac after deployment is done
recently we started getting error "Lifecycle controller status check is InUse after 50 number of retries, Exiting.."

Component or Module Name

idrac_reset

Ansible Version

2.16.6

Python Version

Python 3.11.7

iDRAC/OME/OME-M version

IDRAC 7.00.00.171(Build 05)

Operating System

Linux OS

Playbook Used

  • name: "Reset iDRAC"
    dellemc.openmanage.idrac_reset:
    idrac_ip: "{{ lom_ip }}"
    idrac_user: "{{ lom_username }}"
    idrac_pwd: "{{ lom_password }}"
    validate_certs: false
    register: idrac_reset_result

Logs

``{
"msg": "Lifecycle controller status check is InUse after 50 number of retries, Exiting..",
"invocation": {
"module_args": {
"idrac_ip": "10..10.10.10",
"idrac_user": "root",
"idrac_pwd": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"validate_certs": false,
"idrac_password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"wait_for_idrac": true,
"job_wait_timeout": 600,
"force_reset": false,
"idrac_port": 443,
"timeout": 30,
"reset_to_default": null,
"custom_defaults_file": null,
"custom_defaults_buffer": null,
"ca_path": null
}
},
"_ansible_no_log": false,
"changed": false,
"_ansible_delegated_vars": {
"ansible_host": "localhost",
"ansible_port": null,
"ansible_user": "user",
"ansible_connection": "local"
}
}

Steps to Reproduce

run task to put idrac into the InUse state
run task to try reset idrac

Expected Behavior

expected is to have idrac reset

Actual Behavior

error message - Lifecycle controller status check is InUse after 50 number of retries, Exiting..
and module fail state

Screenshots

No response

Additional Information

No response

@markatdxb markatdxb added needs-triage Issue requires triage. type/bug Something isn't working labels Apr 30, 2024
@ABHISHEK-SINHA10
Copy link
Contributor

Hi @markatdxb

can you please add/replace line 336 in idrac_reset.py like below and retry once again.

image

@sachin-apa sachin-apa added this to the v9.4.0 milestone May 31, 2024
@markatdxb
Copy link
Author

markatdxb commented May 31, 2024

hi, i just tested the proposed change but it didnt have any impact. Still getting the same error

331 'CustomDefaults': self.reset_custom_defaults,
332 'None': self.graceful_restart
333 })
334 msg_res, job_res = reset_status_mappingstr(self.reset_to_default)
335 if is_idrac9 and self.wait_for_idrac and self.reset_to_default:
336 self.check_lcstatus()
337 return msg_res, job_res
338
339 def check_mode_output(self, is_idrac9):

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Lifecycle controller status check is InUse after 50 number of retries, Exiting.."}

@sachin-apa
Copy link
Collaborator

@ABHISHEK-SINHA10 @singh-lovepreet1 Please verify the scenario as part of validation.

@sachin-apa sachin-apa linked a pull request Jun 12, 2024 that will close this issue
8 tasks
@ABHISHEK-SINHA10
Copy link
Contributor

Hi @markatdxb,

Can you try once with PR #675, we have validated it from our side. If you can validate, it will be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue requires triage. type/bug Something isn't working
Projects
Development

Successfully merging a pull request may close this issue.

4 participants