Cisco Bug: CSCvv18827 - Enforce upgradeInProgress indicator and Backup APIC DB before dataconversion
Sep 18, 2020
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: APIC DB may lose during 3.0/3.1 to 4.0/4.1 upgrade if the target version is rolled back to current running version within 2 minutes after upgrade started. The upgrade will continue anyway and however APIC would lose all DB and fail to login by admin credentials, only rescue-user/admin credential allows the log in. All process' shard shows as unexpected, and DB files were removed. The last working ex-upgrade DB are copied to purgatory directory. Conditions: 1, During 3.0/3.1 to 4.0/4.1 upgrade, if the target version was rolled back to beginning version within first two minutes. All APICs would experience DB loss and Fabric ID recovery will be required. Or 2,APIC manual upgrade from 3.0/3.1 to 4.0/4.1. However the impact is contained because APIC can recover DB from rest of APICs by snapshot.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases