Please be more specific.

What exactly fails?
 * the load of SELinux policy
 * the whole boot sequence
 * important systemd services

Thank you.

Created attachment 1973299 [details]
log

(In reply to Milos Malik from comment #1)
> Please be more specific.
> 
> What exactly fails?
>  * the load of SELinux policy
>  * the whole boot sequence
>  * important systemd services
> 
> Thank you.

Hi Milos,

Seems to be important systemd services but I'm not 100% sure. Just attached log, can you please take a look?

Thanks

Hi any updates?

Please boot the machine with the enforcing=0 kernel parameter.

Once the machine boots, please collect SELinux denials that appeared via the following command:

# ausearch -m avc -m user_avc -m selinux_err -i -ts boot

After looking into the attached log, we still don't know what is the main cause.

Thank you.

If the ausearch command does not produce any output, please search for SELinux denials in the systemd journal:

# journalctl -b | grep -i -e avc -e selinux_err

Thank you.

Hello yzho,

We need additional data to troubleshoot further. Off the log provided, we can see the journald service and subsequently some others failed to start, but we don't know the reason and it is not clear if the system recovered afterwards. You can also run:

systemctl status systemd-journald.service
systemctl list-units --state failed 
semodule -lfull | grep -v ^100

to gather more information.

As every important service is expected to start without an error on a clean system, it is possible e. g. some related configuration change was made, or an unusual hardware is in place, or some other service interferes with default setup.

Hi Zdenek,

I can reproduce this issue with image RedHat:rhel-raw:8_8:8.8.2023300515.

1. After set SELINUX=enforcing in /etc/selinux/config, run "fixfiles onboot" and reboot VM, it starts with many failed services and then it auto reboot again.
2. I enter the grub and add "enforcing=0" in the kernel parameters then start the VM, it can start the VM and autorelabel the whole file system. Then it auto reboot again.
3. After that, the VM can boot up successfully and the selinux status is Enforcing.

Hello,

Off the log I can see the system booted successfully, but some units failed.

[FAILED] Failed to start Remount Root and Kernel File Systems.
[FAILED] Failed to mount Kernel Debug File System.
[FAILED] Failed to start Load Kernel Modules.
[FAILED] Failed to mount Huge Pages File System.
[FAILED] Failed to mount POSIX Message Queue File System.
[FAILED] Failed to start Monitoring of LVM2 …sing dmeventd or progress polling.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Apply Kernel Variables.
[FAILED] Failed to start Create Static Device Nodes in /dev.
[FAILED] Failed to start Load/Save Random Seed.
[FAILED] Failed to start Create Volatile Files and Directories.
[FAILED] Failed to start Update UTMP about System Boot/Shutdown.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Journal Service.
[FAILED] Failed to start Azure temporary res…sk dataloss warning file creation.
[FAILED] Failed to start Azure temporary res…sk dataloss warning file creation.

In the previous report there were reasonably more failed services. There is no reason logged though. Can you get more information from the system? Are there AVC denial, either in audit log or in journal?

(In reply to Zdenek Pytela from comment #11)
> Hello,
> 
> Off the log I can see the system booted successfully, but some units failed.
> 
> [FAILED] Failed to start Remount Root and Kernel File Systems.
> [FAILED] Failed to mount Kernel Debug File System.
> [FAILED] Failed to start Load Kernel Modules.
> [FAILED] Failed to mount Huge Pages File System.
> [FAILED] Failed to mount POSIX Message Queue File System.
> [FAILED] Failed to start Monitoring of LVM2 …sing dmeventd or progress
> polling.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Apply Kernel Variables.
> [FAILED] Failed to start Create Static Device Nodes in /dev.
> [FAILED] Failed to start Load/Save Random Seed.
> [FAILED] Failed to start Create Volatile Files and Directories.
> [FAILED] Failed to start Update UTMP about System Boot/Shutdown.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Journal Service.
> [FAILED] Failed to start Azure temporary res…sk dataloss warning file
> creation.
> [FAILED] Failed to start Azure temporary res…sk dataloss warning file
> creation.
> 
> In the previous report there were reasonably more failed services. There is
> no reason logged though. Can you get more information from the system? Are
> there AVC denial, either in audit log or in journal?

Hi Zdenek,

When this issue happened the VM cannot boot up. It keeps rebooting. (Please see the step 1 in comment9)
Only when I edit the grub menu while booting and add "enforcing=0", the VM can boot up, and because I added the /.autorelabel in step 1, it relabel the whole file system then then reboot. (see comment9 step 2 and 3)

So, if I don't set "enforcing=0" in kernel parameters, the VM cannot boot up. So maybe I cannot collect logs in that status.

Hello,

I am afraid there are still no data we can work with. Please gather selinux denials (see #c5 and #c6) which should be logged even when the system fails to start all services.

One finding: Reading again #c9 it looks the image is mislabeled. Can you check how it was created? Can you reach out to its maintainer for further explanation?