Bug ID 475829: AWS - VE is locked out after live install on 2nd slot.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP MA-VE(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF4, 11.5.2

Opened: Aug 17, 2014

Severity: 1-Blocking

Symptoms

SSH access might be blocked on VE (launched in AWS) after live install on 2nd slot is performed and VE is booted to 2nd slot.

Impact

SSH access to the box might be lost. It's effectively locked out since there is no console access to this VM.

Conditions

VE running in AWS Live install performed on 2nd slot and VE is booted to it.

Workaround

None

Fix Information

The public key for ssh access is obtained from AWS metadata service on 1st boot.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips