Bug ID 707100: Potentially fail to create user in AzureStack

Last Modified: Apr 17, 2024

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

Known Affected Versions:
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, 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, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Fixed In:
14.0.0.1, 13.1.0.7

Opened: Feb 17, 2018

Severity: 2-Critical

Symptoms

Using Microsoft Azure Stack on the BIG-IP Virtual Edition (VE) configured with password authentication, the system sometimes fails to create the provided user, which means that the VE admin cannot ssh in after deployment. Note that an unexpected reboot causes this to occur during provisioning, and that Microsoft might have already fixed this issue.

Impact

Admin loses provisioned VE instance because there is no way to ssh in.

Conditions

Azure Stack VE provisioned with password authentication.

Workaround

Deploy VE with key authentication.

Fix Information

Extra handling was added to make user creation work even with unexpected reboots happening during Azure Stack provisioning.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips