NewValidation: CSCwu91693 - APIC OOB connectivity before upgrade

[monrog2]

(use upvote 👍 for attentions)

Validation Type

[ ] - Fault

[x] - Config

[x] - Bug

[ ] - Other

What needs to be validated

CSCwu91693 describes broken OOB management connectivity between APIC controllers, which can cause a partial or failed cluster upgrade.

The defect is Verified and customer visible. The validation should verify that every APIC has complete, usable OOB configuration and that the required APIC-to-APIC HTTPS paths are reachable before upgrade.

Expected behavior

• Inspect the complete APIC controller inventory.
• Determine the effective HTTPS port deterministically from the active commHttps policy.
• Validate every required APIC-to-APIC OOB path, rather than testing all peers only from the APIC running the script.
• Return FAIL_UF when required OOB connectivity is unavailable.
• Return ERROR when required controller, OOB address, or HTTPS-policy inventory is missing, malformed, partial, or ambiguous.
• Return MANUAL when the target version required for applicability cannot be determined.
• Do not silently skip controllers without usable OOB addresses or convert incomplete evaluation into PASS or N/A.
• Preserve malformed controller evidence in the reported result.
• Reconcile the target-version gate and fixed-release behavior with the authoritative CSCwu91693 record.

Testing requirements

Include Python 2.7 and Python 3.8 coverage for:

• All controllers reachable.
• One or more controllers unreachable.
• Empty and partial controller inventory.
• Missing, malformed, link-local-only, and mixed OOB addresses.
• Default, custom, missing, malformed, and multiple commHttps policies.
• Missing target version.
• Target-version applicability boundaries.
• Mixed valid and malformed controller objects.
• Effective string-normalized result payloads.