Bug ID 1055397: Platform registry ports could become mismatched depending on import timing

Last Modified: May 29, 2024

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.3.0

Opened: Oct 15, 2021

Severity: 2-Critical

Symptoms

Under certain conditions, it is possible for the platform registry port configuration to become mismatched between the two system controllers. This can lead to a number of cascading issues with tenant deployments later.

Impact

Tenants that reference a version of imported software with mismatched ports may attempt to pull images from the wrong registry port, resulting in tenant failure or starting up with the wrong version of platform software images.

Conditions

If a platform image import succeeds on one system controller and fails on the other, or a sync of multiple images leads to them being imported in a different order on the standby system controller compared to the active, it is possible to encounter this scenario.

Workaround

It is possible to fix the port mismatch by removing and re-importing the images with mismatched port assignments.

Fix Information

Fixed issue where platform registry ports could become mismatched depending on import timing

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips