Bug ID 664304: Waagent data isn't rolled forward to the new slot after upgrading from pre-v13.1.x Azure VE

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP Install/Upgrade, MA-VE(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Opened: May 11, 2017

Severity: 3-Major

Symptoms

Waagent data saved in "/var/lib/waagent" isn't rolled forward to the new slot after upgraded from pre-v13.1.x Azure VE

Impact

Azure VE is in "soft failure" status: - the most important authentication data is rolled forward - however, all other data, such as Custom Data and Extensions and their data are left in the old slot Waagent still works without any issues

Conditions

It happens on Azure when upgrading VE from pre-v13.1.x

Workaround

VE admin can manually copy Waagnet lib-dir to "/shared/vadc/azure/waagent" directory, and create a symbolic link in the new slot after upgrade (from "/shared/vadc/azure/waagent" to "/var/lib/waagent")

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips