Upgrading from 32.1.x to a higher version via the UI can rollback the system to an older version instead of upgrading
Article ID: 456265
Updated On:
Products
Issue/Introduction
On an Avi Controller version 32.1.1 through 32.1.3 which has been upgraded from a previous Avi version, a subsequent upgrade or patch operation initiated via the UI may result in a rollback to the previous version, resulting in config rollback and traffic disruption.
For example if the upgrade path is 30.2.7(prev) -> 32.1.2(current) -> 32.1.3(target) or 32.1.2-2p2(patch), then due to this bug, the system will rollback to 30.2.7 version instead of upgrading to 32.1.3 or target patch version.
Environment
This specifically affects upgrades or patch operations that are triggered from the UI on any 32.1.x to a higher version.
Below is a list of the impacted operations when upgrading/patching to a later release
| Scenario (upgrade to 32.1.x) | Example | Status |
|---|---|---|
| 32.1.1 through 32.1.3, reached by upgrade from an earlier version | 30.2.7 (previous) → 32.1.2 (current), now upgrading to 32.1.3 | Affected |
22.x, 30.x or 31.x | 30.2.7 (current), now upgrading to 32.1.3 | Not Affected |
Greenfield deployment On 32.1.x, deployed fresh on that version (never upgraded) | Greenfield 32.1.1, now upgrading to 32.1.3 | Not Affected |
Upgrades started from the CLI are not affected.
Cause
Controller experiences an unexpected rollback when upgrading or applying patch on 32.1.x if the user has initiated the upgrade from the UI.
This rollback overwrites all the configuration changes made in the current 32.1.x version.
Resolution
Workaround: Upgrade from the CLI/API
Run the upgrade or patch operation from the Avi CLI instead of the UI. This avoids the problem entirely. See the Avi upgrade documentation for the CLI/API procedure.
CLI: Avi Upgrade from CLI
API: Avi Upgrade from API
Mitigation plan:
The fix for the issue will be available in the next maintenance release (32.1.4). The fix will also be available in 32.1.2-2p3 and 32.1.3-2p1 patches.
The fix will prevent this issue from occurring in any future upgrade/patch operations.
The upgrade to 32.1.4 or these patches should still be applied through CLI/API.
Additional Information
If the system has already rolled back to a previous version, configuration changes made on 32.1.x will be overwritten.
Locate Backup: Identify the most recent configuration backup taken while the Controller was running on the 32.1.x release.
Restore Configuration: Follow standard Avi configuration restoration procedures to apply the backup file and restore lost configuration state.
Contact Broadcom Support for assistance with the same. Scroll to the bottom of the Contact Support and click on your respective region.
- Refer to Contact Broadcom Support for standard support procedures.
- Subscribe to this article to be updated on the fix status; see Subscribe to a Broadcom knowledge article by article or product
Feedback
