Bug ID 862937: Running cpcfg after first boot can result in daemons stuck in restart loop

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.3, 14.1.4

Opened: Dec 17, 2019

Severity: 3-Major

Symptoms

After running cpcfg and booting into the volume, daemons such as named and gtmd are stuck restarting. Additionally the SELinux audit log contains denial messages about gtmd and named being unable to read unlabeled_t files.

Impact

Services do not come up.

Conditions

Running cpcfg on a volume that has already been booted into.

Workaround

In the bash shell, force SELinux to relabel at boot time. Then reboot: # touch /.autorelabel # reboot On multi-blade VIPRION systems, including multi-blade vCMP guests: # clsh touch /.autorelabel # clsh reboot

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips