Description of problem: Ironic fails to complete the deployment even though the disk creation is successful and shutdown the node Version-Release number of selected component (if applicable): RH OSP 10 How reproducible: Always Steps to Reproduce: 1. Import baremetal nodes with pxe_ilo driver with appropriate profile. configure deploy images, introspect the nodes. 2. Run openstack overcloud deploy 3. Controllers were able to finish and the provisioning state is active but the compute node is going into deploy_failed Actual results: Compute node deployment failing Expected results: compute node deployment failing with error "iLO failed to change state to power on within 12 sec" Additional info: Increased the power_wait timeout to 75 seconds, still facing the same issue. As observed from iLO web-ui, the power state was off for much time until the error message. Manual power on via web-ui is a current pseudo-workaround.
The customer is using the version(2.2.0-3) that was release in the following errata: https://access.redhat.com/errata/RHBA-2018:0365 Issue returned after they upgraded the firmware. A case has also been opened with HP.
Created attachment 1417025 [details] ris.py
Created attachment 1417026 [details] Ironic conductor logs
After adding some debug logs, we see that ris.py is never entering the retry loop because the model returned is matching for Proliant BL but the new model is ProLiant BL. I've opened a LaunchPad with a fix: https://bugs.launchpad.net/proliantutils/+bug/1761243
David - nice find! I assume that the Product Name is a fixed string and can't be changed through the iLO UI?
Thanks David for the RCA.
The fix in proliantutils has been released for this issue as proliantutils v2.5.2. the fix URL is https://review.openstack.org/559906.
Sai - this will be in the OSP-10z9 release and will be tested when the puddle is available.
Hi there, If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -. Thanks, Alex
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2671