Repository navigation
Return N/A when host interface auto speed is unsupported - #474
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
APIC 4.2(7u) defines
fabricHIfPol.speedas an enum withoutauto. Filtering on that value returns code 301 (Incorrect filter format for fabricHIfPol.speed, value 'auto' is not valid), causing Host Interface Policy Set to Auto to report an unexpected error.Return N/A with
Current APIC does not support fabricHIfPol.speed="auto".for that specific response. Preserve APIC error details on the existing filter exception so the check can match both code and text; other API failures retain ERROR. The existing query and supported-release findings remain unchanged. Document the compatibility behavior and add regression coverage based on the captured APIC response.Validation: reproduced the original failure before the fix; 54 affected unit tests pass on Python 3.9.6:
The tests cover unsupported enum handling, existing PASS/FAIL/MANUAL results and policy-group reporting, unrelated filter errors, missing properties/classes, access errors, server errors, and timeouts. Python 2.7/3.8 and live integration runs were not performed locally.
Upstream CI passed the full Python 2.7 and Python 3.8 test jobs: Pytest run.