Guest

Preview Tool

Cisco Bug: CSCvu82498 - MSO UI - Verification checks inconsistent post config rollback on APIC

Last Modified

Sep 17, 2020

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases

2.1(2g)

Description (partial)

Symptom:
Following workflow produces inconsistent/incorrect behavior for Template Verification in MSO UI

--------- WORKFLOW ---------
/// Step 1 ///  SITE1 APIC: Take a config backup
/// Step 2 ///  MSO UI: BOTH SITES: Add one new BD and EPG
/// Step 3 ///  SITE1 APIC: perform config rollback (config import) using cfg backup from Step1
/// Step 4a ///  MSO UI: TEMPLATE: Perform verification
/// Step 4b /// As expected  Left nav pane shows icon with Verification check failed for SITE1 and succeeded for 
                     SITE2
/// Step 4c /// HOWEVER, when opening the Verification Summary window we show failed verification checks for 
                    SITE2 which did NOT undergo any changes
/// Step 4d /// Because of the failed verification checks it is NOT possible to deploy the config to site
/// Step 5a ///  Added another new BD/EPG with prefix "FORCE_" to force ability to deploy
/// Step 5b /// After pressing the "DEPLOY TO SITES" button the summary window only shows the "FORCE_" BD/EPGs being added to BOTH sites. It does not show the EPG/BD that were created in Step2 and which are still missing for SITE1
/// Step 5c /// When checking SITE1 APIC it shows the EPG/BD from step being deployed fine as per audit records

Conditions:
### MultiSite deployment running ACI fw rel 4.1(2m) and MSO fw rel 2.1(2g)
### Executing above workflow
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.