In the past I used the output of 'lsblk' [1] in the file bootstrap-subnodes.log.txt.gz, from the CI report for scenario001-multinode-containers, to verify that /dev/loop3 was created. The output the lsblk command would appear in undercloud/var/log/ from the CI job.
However, I am clicking around this CI job's undercloud/var/log [2] but don't see it. Thus I am unable to verify that the task which should have set up the block device failed in some way that might explain this issue.
In the past I used the output of 'lsblk' [1] in the file bootstrap- subnodes. log.txt. gz, from the CI report for scenario001- multinode- containers, to verify that /dev/loop3 was created. The output the lsblk command would appear in undercloud/var/log/ from the CI job.
However, I am clicking around this CI job's undercloud/var/log [2] but don't see it. Thus I am unable to verify that the task which should have set up the block device failed in some way that might explain this issue.
[1] https:/ /review. openstack. org/#/c/ 484963/ 13/scripts/ bootstrap- overcloud- full-minimal. sh
[2] https:/ /logs.rdoprojec t.org/openstack -periodic/ periodic- tripleo- ci-centos- 7-multinode- 1ctlr-featurese t016-queens/ 8b4282d/ undercloud/ var/log/