Bug ID 1069917: Platform registry ports can become de-synchronized, impacting Openshift deployment

Last Modified: Aug 21, 2022

Bug Tracker

Affected Product:  See more info
F5OS None(all modules)

Fixed In:
1.5.0

Opened: Dec 22, 2021
Severity: 3-Major

Symptoms

Under certain circumstances, platform services on the active and standby controllers can end up residing in docker registries that use different port numbers. This can result in Openshift pods failing to start, because they expect these port assignments to be synchronized.

Impact

Openshift pods cannot start.

Conditions

Varied causes, which lead to inconsistent registry port assignments on active and standby controllers.

Workaround

None

Fix Information

Added more checks to ensure platform registry ports are synchronized between controllers.

Behavior Change