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 addresses a protocol mismatch in the Management HA OTG test suite. By correcting the L4 payload type for IPv6 flows, the change ensures that traffic generation aligns with standard networking protocols, improving the reliability of the test environment. 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 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. Footnotes
|
Pull Request Functional Test Report for #5279 / 0b52bedVirtual Devices
Hardware Devices
|
There was a problem hiding this comment.
Code Review
This pull request updates the createFlowV6 function in the management HA test to correctly use ICMPv6 methods (Icmpv6 and NewFlowIcmpv6Echo) for IPv6 traffic flows, replacing the previous ICMPv4-specific calls. I have no feedback to provide as there were no review comments.
|
duplicate of #5185 |
Summary
This change fixes IPv6 traffic generation in the Management HA OTG test by using ICMPv6 instead of ICMPv4 on an IPv6 packet stack.
Issue
The IPv6 flow builder in feature/system/management/otg_tests/management_ha_test/management_ha_test.go was creating:
Ethernet
IPv6
ICMP (v4)
This is a protocol mismatch. For an IPv6 flow, the correct L4 payload is ICMPv6.
Root cause
The flow used ICMPv4 APIs: