Bug ID 1280881: User-generated SSH identity breaks multi-bladed REST storage sync

Last Modified: Mar 30, 2024

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

Opened: Mar 24, 2023

Severity: 4-Minor

Symptoms

If the user generates their own SSH key on a multi-bladed system, the restjavad storage sync between the primary slot and secondary slots fails. This happens because the system attempts to use this private key to authenticate to the secondary slots but the secondary slots do not have the matching public key in their authorized_keys file, so authentication falls back to password auth, which ultimately fails.

Impact

Users will not be able to generate their own SSH keys on multi-bladed systems since the restjavad storage sync between the primary slot and secondary slots will fail.

Conditions

The user generates their own SSH key pair with a default name of id_[rsa|dsa|ecdsa|ed25519] and stores it in /root/.ssh on a multi-bladed system.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips