Bug ID 1195261: Occasionally Selinux modules are getting corrupted when the system reboots

Last Modified: Apr 28, 2025

Affected Product(s):
F5OS F5OS(all modules)

Known Affected Versions:
F5OS-A 1.1.0, F5OS-A 1.1.1, F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2

Fixed In:
F5OS-A 1.4.0

Opened: Nov 25, 2022

Severity: 3-Major

Symptoms

In rSeries appliances, if Selinux modules are corrupted: -> Virt-handler pod crashes continuously -> Tenant will be in pending state -> Semodule file size is 0 in dir "/etc/selinux/targeted/active/modules/400/" -> No or missing files under /etc/selinux/targeted/active/modules/ dir

Impact

-> Virt-handler pod is crashes continuously. -> Tenant functionality is impacted.

Conditions

If interruption happens during Selinux modules building on system bootup, the interruption can be an abrupt power off.

Workaround

Execute below commands: -> cp -r /usr/etc/selinux/targeted/active/modules/* /etc/selinux/targeted/active/modules/ -> semodule -B

Fix Information

Issue is fixed in F5OS-A 1.4.0 release.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips