Bug ID 984753: Unable to read key from storage.

Last Modified: Aug 17, 2021

Bug Tracker

Affected Product:  See more info
F5OS Install/Upgrade, Velos(all modules)

Fixed In:
1.1.0

Opened: Jan 19, 2021
Severity: 1-Blocking

Symptoms

The checksum changed from size 256 to 512. Systems that created the encryption keys using 256 would fail when upgrading.

Impact

The upgrade does not accept the key since the hash does not match.

Conditions

System must have been configured with old software that wrote 256-bit hashes and upgraded to a newer version that expected 512-bit hashes.

Workaround

Going into the vcc-confd container and requesting the key twice would change the key and store a new 512 hash. From the System Controller: # docker exec -it vcc-confd bash # getConfdMasterKey.sh --storage eeprom # exit

Fix Information

With the fix, either 256 or 512 hash keys are accepted so upgrading from an older system does not fail as before.

Behavior Change

The checksum