Symptoms

It is possible for the internal registry ports assigned to imported F5OS software images to get out of sync between the 2 chassis controllers. This leads to upgrade issues when trying to upgrade to an F5OS image that has a registry port inconsistency between the 2 controllers.

Impact

Since the registry ports differ between the controllers, when the system fails over to the chassis controller after being installed, it can fail to pull some of the needed software containers, causing the system to not startup correctly.

Conditions

This issue can occur if the image partition on the active controller is above 40% usage. The issue can also occur if an image is imported only on the standby chassis controller, and then a different image is imported on the active chassis controller.

Workaround

The workaround is to correct the port mismatch before upgrading to a new software version. A knowledge base article is being created with the procedure for doing this.

Fix Information

Added a script to detect the port mismatch issues that can be run after importing new images to the chassis, and before running an upgrade.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips