RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
An 'image-installer' image type boots up in enforcing SELinux mode as opposed to the regular boot ISO or DVD ISO. This can cause unexpected issues within the environment - I originally discovered this when I was getting failures to copy files via scp from the installer environment with 'inst.sshd' Anaconda boot option.

Version-Release number of selected component (if applicable):
osbuild-composer-33.3-1.el9_b.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Build an 'image-installer' image
2. Boot the prepared image and switch into console
3. cat /sys/fs/selinux/enforce

Actual results:
1 -> SELinux in the installer environment is in enforcing mode

Expected results:
0 -> SELinux in the installer environment is in permissive mode as in regular installation ISOs

Additional info:
A workaround to this is to add 'enforcing=0' to kernel command line.

Another note - compared to the regular installer ISOs, there are some additional selinux binaries present in the ISOs built by osbuild-composer.

Upstream PR: https://github.com/osbuild/osbuild-composer/pull/2359 (merged)
Included in Release 46: https://github.com/osbuild/osbuild-composer/releases/tag/v46

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: osbuild-composer), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2522