Bug ID 1349465: Partition s/w upgrade compatibility check doesn't use correct target version

Last Modified: May 29, 2024

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

Known Affected Versions:
F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1, F5OS-C 1.6.0

Fixed In:
F5OS-C 1.6.1, F5OS-A 1.7.0, F5OS-A 1.5.2

Opened: Sep 07, 2023

Severity: 3-Major


When performing the partition database compatibility upgrade check (check-version/set-version), the check logic does not always use the correct target version. This potentially can cause the compatibility check to pass, but the actual database upgrade can fail and automatically roll back.


The check-version/set-version database compatibility check might pass even though the actual upgrade would fail.


When the target partition version is a patch release (such as 1.5.1, 1.6.1), the compatibility check will use the wrong (base release) version.


Upgrade the controller s/w to version F5OS-C 1.6.1 or later prior to attempting upgrade to a partition patch release.

Fix Information

The controller OS services uses the correct partition patch version for the compatibility check.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips