Bug ID 739955: Masterkey change does not remain after boot into new volume

Last Modified: Jan 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 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.1, 13.1.1.2, 13.1.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.0.1, 14.1.0, 14.1.0.1

Fixed In:
15.0.0, 14.1.0.2, 14.0.1.1, 13.1.1.4, 12.1.4.1, 11.6.4

Opened: Aug 10, 2018
Severity: 3-Major

Symptoms

After changing the master key on a BIG-IP system and loading a UCS file associated with that master key, the configuration loads successfully as expected. However, booting into a volume with a fresh install causes configuration load failures if encrypted secrets are in the configuration.

Impact

The configuration fails to load.

Conditions

The reproduction conditions are: 1. Change the master key on a BIG-IP system to one associated with a UCS file from a different BIG-IP device. 2. Load the UCS file onto the BIG-IP system, which should succeed. 3. Install a new version of the software onto a fresh volume. 4. Boot into the fresh volume. 5. Observe a configuration load failure.

Workaround

1. On the fresh volume, change the master key to the value from step 1. 2. Reload the config using the following command: tmsh load sys config

Fix Information

None

Behavior Change