Bug ID 811053: REBOOT REQUIRED prompt appears after failover and clsh reboot

Last Modified: Aug 08, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 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, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 15.0.0, 15.0.1

Opened: Jul 30, 2019
Severity: 3-Major

Symptoms

In rare circumstances, when a reboot immediately follows a VIPRION blade failover, a REBOOT REQUIRED prompt will appear on one blade after the system starts up again.

Impact

Following the clsh reboot, the REBOOT REQUIRED prompt appears on one blade: [root@vip4480-r44-s18:/S2-yellow-S::REBOOT REQUIRED:Standalone] config # Any blade with this prompt must be rebooted again.

Conditions

This issue can be created by doing the following: - using a VIPRION system with at least 2 blades running - AAM is not provisioned - reset the primary blade - immediately following the blade reset, run 'clsh reboot' on a secondary blade.

Workaround

None currently known.

Fix Information

None

Behavior Change