Last Modified: Apr 05, 2023
Known Affected Versions:
F5OS-A 1.1.0, F5OS-A 1.1.1
F5OS-A 1.3.0, F5OS-A 1.2.0
Opened: May 05, 2022 Severity: 3-Major
On upgrading from one F5OS-A version to another, the appropriate webUI changes are not reflected, and the older changes still persist.
Appropriate changes with respect to the version are not reflected on the webUI.
Upgrading from one F5OS-A version to another.
Refreshing the containers is a known workaround using /usr/libexec/platform-deployment stop and /usr/libexec/platform-deployment start.
The fix is to clean up stale volumes so that new volumes are mounted after system reboot. A --remove-orphans flag was added to docker-compose down to remove volumes which were created in the previous run of docker-compose. Also, appliance_orchestration_manager was called to stop separately, as it was using a volume called config_vlogsev, which was also being used by other containers, because it is not a part of the platform.yml file. Also docker-compose down has been added before starting service in the beginning of the platform-deployment service to handle the scenario of upgrading from broken ISO to fix ISO.