cs9 fs02 ovb job is failing at image build dib-run-parts Ignoring non-executable files: 05-selinux-9-stream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
periodic-
```
diskimage_
2022-06-13 01:34:47.184 | dib-run-parts Ignoring non-executable files: 05-selinux-9-stream
```
Leading to
```
+ /home/zuul/
2022-06-13 01:36:41.752 | /usr/sbin/setfiles: Could not set context for /: No such file or directory
2022-06-13 01:36:41.752 | /usr/sbin/setfiles: Could not set context for /boot: No such file or directory
2022-06-13 01:36:41.752 | /usr/sbin/setfiles: Could not set context for /boot/efi: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/
```
Reason: https:/
summary: |
- cs9 fs02 is failing with error - 'No configuration methods succeeded - (https://ipxe.org/040ee186) iPXE boot failed, retrying .' + cs9 fs02 ovb job is failing with error - 'No configuration methods + succeeded (https://ipxe.org/040ee186) iPXE boot failed, retrying .' |
summary: |
cs9 fs02 ovb job is failing with error - 'No configuration methods - succeeded (https://ipxe.org/040ee186) iPXE boot failed, retrying .' + succeeded... iPXE boot failed, retrying... .' |
description: | updated |
summary: |
- cs9 fs02 ovb job is failing with error - 'No configuration methods - succeeded... iPXE boot failed, retrying... .' + cs9 fs02 ovb job is failing at image build dib-run-parts Ignoring non- + executable files: 05-selinux-9-stream |
It looks like ths issue is actually an error when building the image: /logserver. rdoproject. org/openstack- periodic- integration- main/opendev. org/openstack/ tripleo- ci/master/ periodic- tripleo- ci-centos- 9-ovb-1ctlr_ 1comp-featurese t002-master/ eaefbe0/ logs/undercloud /home/zuul/ overcloud- hardened- uefi-full. log.txt. gz
https:/
2022-06-11 17:38:56.420 | DEBUG diskimage_ builder. block_device. utils [-] exec_sudo: Logical volume vg/lv_root contains a filesystem in use. exec_sudo /usr/lib/ python3. 9/site- packages/ diskimage_ builder/ block_device/ utils.py: 135 python3. 9/site- packages/ diskimage_ builder/ lib/dib- block-device. py", line 7, in <module> python3. 9/site- packages/ diskimage_ builder/ block_device/ cmd.py" , line 120, in main python3. 9/site- packages/ diskimage_ builder/ block_device/ cmd.py" , line 115, in main python3. 9/site- packages/ diskimage_ builder/ block_device/ cmd.py" , line 39, in cmd_umount cmd_umount( ) python3. 9/site- packages/ diskimage_ builder/ block_device/ blockdevice. py", line 442, in cmd_umount python3. 9/site- packages/ diskimage_ builder/ block_device/ level1/ lvm.py" , line 284, in umount python3. 9/site- packages/ diskimage_ builder/ block_device/ level1/ lvm.py" , line 217, in _umount ['lvchange' , '-an', python3. 9/site- packages/ diskimage_ builder/ block_device/ utils.py" , line 143, in exec_sudo builder. block_device. exception. BlockDeviceSetu pException: exec_sudo failed
2022-06-11 17:38:56.446 | Traceback (most recent call last):
2022-06-11 17:38:56.446 | File "/usr/lib/
2022-06-11 17:38:56.446 | sys.exit(main())
2022-06-11 17:38:56.446 | File "/usr/lib/
2022-06-11 17:38:56.450 | return bdc.main()
2022-06-11 17:38:56.450 | File "/usr/lib/
2022-06-11 17:38:56.450 | self.args.func()
2022-06-11 17:38:56.450 | File "/usr/lib/
2022-06-11 17:38:56.450 | self.bd.
2022-06-11 17:38:56.450 | File "/usr/lib/
2022-06-11 17:38:56.453 | node.umount()
2022-06-11 17:38:56.453 | File "/usr/lib/
2022-06-11 17:38:56.454 | lvs._umount()
2022-06-11 17:38:56.454 | File "/usr/lib/
2022-06-11 17:38:56.454 | exec_sudo(
2022-06-11 17:38:56.455 | File "/usr/lib/
2022-06-11 17:38:56.456 | raise e
2022-06-11 17:38:56.456 | diskimage_
I belive the iPXE output is what we expect when no introspection/node provisioning is active.