Comment 14 for bug 1954456

Revision history for this message
chandan kumar (chkumar246) wrote :

Based on my testing https://logserver.rdoproject.org/13/36713/10/check/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/7a8c750/logs/undercloud/home/zuul/overcloud_node_provision.log.txt.gz

We are back to the same issue as mentioned in the description of the bug
```
Wait for provisioned nodes to boot | overcloud-controller-0 | error={"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python3"}, "changed": false, "elapsed": 600, "msg": "Timeout waiting for provisioned nodes to become available"}
2021-12-16 07:32:42.746243 | fa163ef6-a9f3-ffa8-8583-00000000000a | TIMING | Wait for provisioned nodes to boot | overcloud-controller-0 | 0:10:01.492139 | 601.46s

```

and https://logserver.rdoproject.org/13/36713/10/check/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/7a8c750/logs/baremetal_10_12994_1-console.log

```
 [ -e "/dev/disk/by-uuid/cedbc2ac-f3e9-4607-a15e-5e5f3b7aa817" ]
[ 199.790085] dracut-initqueue[425]: fi"
[ 199.791612] dracut-initqueue[425]: Warning: dracut-initqueue: starting timeout scripts
[ 200.307447] dracut-initqueue[425]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 200.310897] dracut-initqueue[425]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fcedbc2ac-f3e9-4607-a15e-5e5f3b7aa817.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 200.319710] dracut-initqueue[425]: [ -e "/dev/disk/by-uuid/cedbc2ac-f3e9-4607-a15e-5e5f3b7aa817" ]
[ 200.323687] dracut-initqueue[425]: fi"
[ 200.325472] dracut-initqueue[425]: Warning: dracut-initqueue: starting timeout scripts
[ 200.328932] dracut-initqueue[425]: Warning: Could not boot.
         Starting [0;1;39mDracut Emergency Shell[0m...
Warning: /dev/disk/by-uuid/cedbc2ac-f3e9-4607-a15e-5e5f3b7aa817 does not exist

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to coPress Enter for maintenance
(or press Control-D to continue):
```

Apart from that https://logserver.rdoproject.org/13/36713/10/check/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/7a8c750/logs/undercloud/var/log/extra/errors.txt.gz

```
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall Traceback (most recent call last):
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 154, in _run_loop
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall idle = idle_for_func(result, self._elapsed(watch))
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 349, in _idle_for
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall raise LoopingCallTimeOut(
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 72.24 seconds
2021-12-16 07:07:25.056 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR oslo.service.loopingcall
2021-12-16 07:07:25.059 ERROR /var/log/containers/ironic/ironic-conductor.log: 2 ERROR ironic.conductor.utils [req-d8a28afb-3cb8-4e3d-af21-b40fb09a5142 admin - - - -] Timed out after 60 secs waiting for power off on node 3e3c840d-00af-4c40-8aea-40accd558771.: oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 72.24 seconds
```

I am not sure what is going on here.