Skip to content

Conversation

@RishabhAgarwal-2001
Copy link

@RishabhAgarwal-2001 RishabhAgarwal-2001 commented Dec 22, 2025

This PR covers the auditing efforts for the following deviation flags -

  • mpls_exp_ingress_classifier_oc_unsupported
  • network_instance_import_export_policy_oc_unsuppored
  • mpls_label_classification_unsupported
  • bgp_rib_oc_path_unsupported
  • config_acl_with_prefixlist_unsupported

Also fixes #4947

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @RishabhAgarwal-2001, 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 addresses an audit of existing and missing deviation flags within the system. It primarily focuses on correcting a widespread typo in the network_instance_import_export_policy_oc_unsupported flag and integrating several new deviation definitions for various network features. These updates aim to improve the accuracy and completeness of platform-specific deviation handling, ensuring better test coverage and compatibility across different network devices.

Highlights

  • Typo Correction: Fixed a consistent typo from "unsuppored" to "unsupported" across multiple files related to the network_instance_import_export_policy_oc_unsupported flag, ensuring correct spelling and functionality.
  • New Deviation Flags Added: Introduced several new deviation flags in deviations.textproto for various network features, including config_acl_with_prefixlist_unsupported, mpls_label_classification_unsupported, mpls_exp_ingress_classifier_oc_unsupported, and the corrected network_instance_import_export_policy_oc_unsupported.
  • Platform-Specific Deviations: Enhanced deviation definitions with platform-specific details (e.g., ARISTA and CISCO vendors, CLI commands) for better accuracy and targeting of network device capabilities.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

OpenConfigBot commented Dec 22, 2025

Pull Request Functional Test Report for #4952 / 72dde8d

Virtual Devices

Device Test Test Documentation Job Raw Log
Arista cEOS status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
943f5b47 Log
Cisco 8000E status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
8d86a3c2 Log
Cisco XRd status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
fda705b3 Log
Juniper ncPTX status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
26f128c4 Log
Nokia SR Linux status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
e25b23fb Log
Openconfig Lemming status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
c25c813f Log

Hardware Devices

Device Test Test Documentation Raw Log
Arista 7808 status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
Cisco 8808 status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
Juniper PTX10008 status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF
Nokia 7250 IXR-10e status
status
status
URPF-1.1: uRPF validation from non-default network-instance
TE-6.3: Route Leakage between Non Default VRF
PF-2.3: Multiple VRFs and GUE DECAP in Default VRF

Help

Copy link
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 corrects a typo in the network_instance_import_export_policy_oc_unsupported deviation flag and adds several new deviations as part of an audit. The changes are straightforward and correctly apply the typo fix across multiple files. However, all newly added deviations in internal/deviations/deviations.textproto are missing the required issue_url. The repository's contribution guidelines state that each deviation should have an associated issue tracker URL to facilitate tracking its eventual removal. Please add the appropriate issue URLs for all new deviations.

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

}
}
platforms: {
issue_url: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The issue_url is empty. As per the repository's deviation guidelines, a URL to an issue tracker should be provided to track the removal of this deviation.

References
  1. Deviation guidelines require an issue_url to track the removal of the deviation. See internal/deviations/README.md, lines 83-86. (link)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unused Deviation network_instance_import_export_policy_oc_unsuppored in feature/urpf/otg_tests/urpf_vrf_test

4 participants