Last Modified: Apr 23, 2022
See more info
Known Affected Versions:
1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2.1
Opened: Sep 01, 2021
After upgrading the system to F5OS-C version 1.1.4, when you remove old chassis partition images from the system, tenants might not start up correctly after a reboot of the blade hosting the chassis partition.
Tenants will not start correctly, will not pass traffic, or be accessible on their management interfaces.
This might occur if the tenant was started after the system was upgraded to an interim release (such as F5OS-C 1.1.1, 1.1.2, 1.1.3), after originally running F5OS-C version 1.1.0.
To work around this issue: 1. Upgrade the system controller to F5OS-C1.1.4. 2. Wait for the system controller upgrade to complete. 3. Upgrade the chassis partition(s) to F5OS-C 1.1.4. 4. Wait for chassis partition upgrade(s) to complete. 5. Configure all tenants to return to the "Provisioned" state. 6. Wait for all tenants to stop. 7. Configure all tenants back to the "Deployed" state. 8. Remove the old chassis partition and system controller software versions.