Adding AFT-6.3: AFT Prefix Filtering Resilience Test#5522
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a comprehensive test suite for AFT Prefix Filtering Resilience (AFT-6.3). The new test validates the device's ability to correctly filter AFT entries under various conditions, including device reboots, high-scale route advertisements, and independent filtering policies across different network instances. Supporting changes include platform-specific deviations for Arista and new utilities for configuration management during testing. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request implements the AFT Prefix Filtering Resilience test (AFT-6.3), adding a new test suite, metadata, backup/restore config helpers, and a deviation for unsupported global filter policies. The review identifies critical bugs in the test implementation: the telemetry validation helpers mustVerifyPrefixEventuallyPresent and mustVerifyPrefixesEventuallyPresent are broken because they poll a static cache without running ListenUntil to process incoming gNMI notifications. Furthermore, the scale policies are never configured on the DUT's routing policy during the scale test, and several policy creation helpers ignore errors from AppendNewStatement, risking nil pointer dereference panics.
Readme Location: https://github.com/openconfig/featureprofiles/blob/main/feature/afts/filtered_streaming/otg_tests/afts_prefix_filtering_resilience/README.md
One failed out of 3 test cases due to the defect: https://partnerissuetracker.corp.google.com/u/1/issues/517809756
Attached logs here: https://partnerissuetracker.corp.google.com/u/2/issues/517817938