Skip to content

Fix LAG operational status for disabled member ports on Juniper devices#5183

Open
priyaranjannanda wants to merge 3 commits intoopenconfig:mainfrom
priyaranjannanda:gNMI-1.25
Open

Fix LAG operational status for disabled member ports on Juniper devices#5183
priyaranjannanda wants to merge 3 commits intoopenconfig:mainfrom
priyaranjannanda:gNMI-1.25

Conversation

@priyaranjannanda
Copy link
Copy Markdown
Contributor

Changes for Juniper Devices

  • when LAG member port is disabled, the LAG oper status goes to LOWER_LAYER_DOWN instead of DOWN

… oper status goes to LOWER_LAYER_DOWN instead of DOWN
@priyaranjannanda priyaranjannanda requested a review from a team as a code owner February 27, 2026 16:46
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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

  • Juniper LAG Operational Status: Adjusted the expected operational status for Juniper devices in LAG flap tests to 'LOWER_LAYER_DOWN' when a member port is disabled, aligning with actual device behavior.
  • Test Logic Refinement: Modified the 'performLAGFlapTest' function to apply the Juniper-specific 'LOWER_LAYER_DOWN' status only for 'LAGMemberFlap' and 'OTGLAGFlap' test scenarios.
Changelog
  • feature/interface/otg_tests/telemetry_interface_last_change_test/telemetry_interface_last_change_test.go
    • Updated the conditional logic for Juniper devices to correctly set the expected LAG operational status to 'LOWER_LAYER_DOWN' when a member port is disabled, specifically for 'LAGMemberFlap' and 'OTGLAGFlap' tests.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@OpenConfigBot
Copy link
Copy Markdown

OpenConfigBot commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants