Last Modified: Dec 07, 2023
F5OS-C 1.6.0, F5OS-C 1.5.1, F5OS-A 1.5.0
Opened: Nov 02, 2022 Severity: 3-Major
When the admin upgrades the system software from 1.3.x to 1.5.0, the platform updates the tenant's table with additional entries that are not running as part of the tenant's original configuration.
There will not be any impact on the critical functionality of the tenant, and traffic continues to work. However, it does show some unwanted information in the health which could be confusing.
Power cycle or system software upgrades from 1.3.x to 1.5.0.
Toggling the affected tenant's running state from "Deployed" to "Provisioned" and back to "Deployed" will fix the state of the tenant in the table.
During the power cycle/system upgrade, the platform re-populates the tenant oper status from Openshift and publishes it to Partition. If the REST response of the tenants from Openshift is incomplete, the platform is populating entries under the wrong key/value. As a result, the partition tenant's table ends up with some unwanted entries. It is a cosmetic issue and will not impact any tenants.