cs9 fs02 ovb job is failing at image build dib-run-parts Ignoring non-executable files: 05-selinux-9-stream

Bug #1978456 reported by Soniya Murlidhar Vyas
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master is failing during image build

https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/ef019ba/logs/undercloud/home/zuul/build.log.txt.gz

```
diskimage_builder/lib/img-functions:run_in_target:59 : sudo -E chroot /home/zuul/dib_build.UXVwcKgp/mnt env -u TMPDIR -u VIRTUAL_ENV 'PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' sh -c '/tmp/in_target.d/dib-run-parts /tmp/in_target.d/post-install.d'
2022-06-13 01:34:47.184 | dib-run-parts Ignoring non-executable files: 05-selinux-9-stream

```
Leading to

```
 + /home/zuul/dib_build.UXVwcKgp/hooks/cleanup.d/99-selinux-fixfiles-restore:main:95 : sudo runcon -t setfiles_mac_t -- chroot /home/zuul/tmp.xRkGMTwDtl /usr/sbin/setfiles -F /etc/selinux/targeted/contexts/files/file_contexts /
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/device.map: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_idea.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/adler32.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_md4.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/affs.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_md5.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/afs.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_rfc2268.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/afsplitter.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/div.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/ahci.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_rijndael.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/all_video.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/div_test.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/aout.mod: No such file or directory
2022-06-13 01:36:41.753 | /usr/sbin/setfiles: Could not set context for /boot/grub2/i386-pc/gcry_rmd160.mod: No such file or directory

```
Reason: https://review.opendev.org/c/openstack/diskimage-builder/+/845189 script is ignored due to non-executabe file.

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... .'
Revision history for this message
Harald Jensås (harald-jensas) wrote : Re: cs9 fs02 ovb job is failing with error - 'No configuration methods succeeded... iPXE boot failed, retrying... .'

It looks like ths issue is actually an error when building the image:
https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/eaefbe0/logs/undercloud/home/zuul/overcloud-hardened-uefi-full.log.txt.gz

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
2022-06-11 17:38:56.446 | Traceback (most recent call last):
2022-06-11 17:38:56.446 | File "/usr/lib/python3.9/site-packages/diskimage_builder/lib/dib-block-device.py", line 7, in <module>
2022-06-11 17:38:56.446 | sys.exit(main())
2022-06-11 17:38:56.446 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/cmd.py", line 120, in main
2022-06-11 17:38:56.450 | return bdc.main()
2022-06-11 17:38:56.450 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/cmd.py", line 115, in main
2022-06-11 17:38:56.450 | self.args.func()
2022-06-11 17:38:56.450 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/cmd.py", line 39, in cmd_umount
2022-06-11 17:38:56.450 | self.bd.cmd_umount()
2022-06-11 17:38:56.450 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/blockdevice.py", line 442, in cmd_umount
2022-06-11 17:38:56.453 | node.umount()
2022-06-11 17:38:56.453 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/level1/lvm.py", line 284, in umount
2022-06-11 17:38:56.454 | lvs._umount()
2022-06-11 17:38:56.454 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/level1/lvm.py", line 217, in _umount
2022-06-11 17:38:56.454 | exec_sudo(['lvchange', '-an',
2022-06-11 17:38:56.455 | File "/usr/lib/python3.9/site-packages/diskimage_builder/block_device/utils.py", line 143, in exec_sudo
2022-06-11 17:38:56.456 | raise e
2022-06-11 17:38:56.456 | diskimage_builder.block_device.exception.BlockDeviceSetupException: exec_sudo failed

I belive the iPXE output is what we expect when no introspection/node provisioning is active.

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

https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-ovb-1ctlr_1comp-featureset002-master/ef019ba/logs/undercloud/home/zuul/build.log.txt.gz

```
 diskimage_builder/lib/img-functions:run_in_target:59 : sudo -E chroot /home/zuul/dib_build.UXVwcKgp/mnt env -u TMPDIR -u VIRTUAL_ENV 'PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' sh -c '/tmp/in_target.d/dib-run-parts /tmp/in_target.d/post-install.d'
2022-06-13 01:34:47.184 | dib-run-parts Ignoring non-executable files: 05-selinux-9-stream
```

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ci (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ci/+/845573

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-ci (master)

Reviewed: https://review.opendev.org/c/openstack/tripleo-ci/+/845573
Committed: https://opendev.org/openstack/tripleo-ci/commit/b48f287493088b70f87de436d61b2c6283617fe3
Submitter: "Zuul (22348)"
Branch: master

commit b48f287493088b70f87de436d61b2c6283617fe3
Author: Chandan Kumar (raukadah) <email address hidden>
Date: Mon Jun 13 15:09:08 2022 +0530

    Make sure 05-selinux-9-stream is executable

    In FS02 CS9 job, 05-selinux-9-stream script is ignored due
    to non-executable files.

    It was added to workaround libselinux-3.4-1 issue[1].

    This patch adds the workaround to make it executable for
    CentOS-Stream-9.
    It will fix image build issue in all ovb jobs.

    Closes-Bug: #1978456
    Related-Bug: #1977873

    [1]. https://review.opendev.org/c/openstack/diskimage-builder/+/845189
    Signed-off-by: Chandan Kumar (raukadah) <email address hidden>
    Change-Id: I8957aa5181835194d98df4ee2e4d3100ef50f027

Changed in tripleo:
status: In Progress → Fix Released
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.