Wallaby OVB jobs are failing node provision step - ironic conductor: PowerStateFailure: Failed to set node power state to power off
Bug #2034704 reported by
Ronelle Landy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Incomplete
|
Critical
|
Unassigned |
Bug Description
Wallaby OVB jobs are failing node provision step with the following error:
Example logs:
The issue started on 09/01:
Jobs running on internal show the same traces.
https:/
Changed in tripleo: | |
milestone: | none → antelope-1 |
importance: | Undecided → Critical |
status: | New → Triaged |
tags: | added: promotion-blocker |
To post a comment you must log in.
The fundamental issue is the "openstackbmc" is failing to power off the machine, but with the way that is all architected and setup, we have no way of knowing why as far as I can see.
All we have is the console log from the BMC:
https:/ /logserver. rdoproject. org/73/ 37973/86/ check/periodic- tripleo- ci-centos- 9-ovb-3ctlr[…]tureset001- wallaby/ d478e78/ logs/bmc_ 86_67346- console. log
And if you look for:
[ 3807.890716] openstackbmc[ 14525]: Powered off 90a12976- 17f7-4ded- 9f6d-5537c71a69 4d
You can see the VM power status continues to report that it is on. The ironic conductor service logs mirror this. In other words, it very much doesn't look like service code, but possibly openstackbmc. Openstack- virtual- baremetal last saw changes back in 2022, so could an underlying libvirt change have broken things?