Comment 13 for bug 2008822

It does seem like a timing issue, but from what I can tell the molecule job should be mocking a bunch of stuff [1].

[1] https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ansible/roles/tripleo_compute_node/molecule/default/prepare.yml#L40

When I look at the failing job's logs, the timestamps show <1 second between the time the iscsid service is restarted and when they declare the restart failed.

2023-03-09 14:14:17.106941 | centos-9-stream | TASK [Run iscsid containers] **************************************************
2023-03-09 14:14:17.107124 | centos-9-stream | TASK [tripleo_container_manage : Manage container systemd services and cleanup old systemd healthchecks for /var/lib/tripleo-config/container-startup-config/iscsid] ***
2023-03-09 14:14:17.107128 | centos-9-stream | An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None
2023-03-09 14:14:17.107132 | centos-9-stream | fatal: [tripleo_compute_node]: FAILED! => changed=false
2023-03-09 14:14:17.107144 | centos-9-stream | msg: Service iscsid has not started yet