Fix LAG operational status for disabled member ports on Juniper devices#5183
Fix LAG operational status for disabled member ports on Juniper devices#5183priyaranjannanda wants to merge 3 commits intoopenconfig:mainfrom
Conversation
… oper status goes to LOWER_LAYER_DOWN instead of DOWN
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 refines the test logic for Juniper devices within the 'telemetry_interface_last_change_test' suite. It specifically addresses how the operational status of a Link Aggregation Group (LAG) is expected to behave when a member port is disabled, ensuring that the test correctly anticipates a 'LOWER_LAYER_DOWN' status for Juniper devices under specific LAG flap test conditions. Highlights
Changelog
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 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 counter productive. 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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Pull Request Functional Test Report for #5183 / ac1dee7Virtual Devices
Hardware Devices
|
There was a problem hiding this comment.
Code Review
This pull request correctly fixes an issue with the expected LAG operational status on Juniper devices when a member port is disabled. The logic now correctly distinguishes between a full LAG flap and a member port flap. My feedback focuses on a minor improvement to enhance code maintainability by replacing magic strings with constants, which aligns with general Go style guidelines.
Changes for Juniper Devices