Bug ID 726622: Entropy start-up sentinel file is not cleared on successful start

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Fixed In:
14.1.0

Opened: Jul 03, 2018

Severity: 3-Major

Symptoms

When the entropy start-up fails, a file is created that will prevent a reboot loop. However, if the entropy start-up succeeds, the file remains.

Impact

The entropy start-up sentinel file is not cleared as it should be. If an entropy failure happens again, then all subsequent rebooting for a failed entropy is disabled. Should the entropy succeed and then later fail, the reboot to handle the failed entropy start-up will not happen.

Conditions

Entropy start-up fails and then succeeds.

Workaround

User can manually remove the start-up failure sentinel file using the following command: /bin/rm -f /.entropy_failure_sentinal_file

Fix Information

Now, if the entropy start-up succeeds, the system removes that file, so that subsequent failures reboot at least once. This is correct behavior.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips