Add tests for container placement with LC_PRIMARY, LC_BACKUP, and LC_ALL#5567
Add tests for container placement with LC_PRIMARY, LC_BACKUP, and LC_ALL#5567chitadi wants to merge 7 commits into
Conversation
Subtest numbering according to PR - 5562
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 automated testing for container placement policies, specifically covering LC_PRIMARY, LC_BACKUP, and LC_ALL configurations. The changes ensure that containers are correctly deployed and persist or migrate as expected during route processor switchovers, validating the container orchestration logic on the device. 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
|
Pull Request Functional Test Report for #5567 / de7c0d0Virtual Devices
Hardware Devices
|
There was a problem hiding this comment.
Code Review
This pull request introduces three new integration tests (TestContainerPlacementLCPRIMARY, TestContainerPlacementLCBACKUP, and TestContainerPlacementLCALL) to verify container placement behavior during supervisor switchovers. However, there are critical logic errors in the post-switchover assertions for both the LCPRIMARY and LCBACKUP tests. Specifically, TestContainerPlacementLCPRIMARY incorrectly asserts that the container does not exist on the new primary supervisor, and TestContainerPlacementLCBACKUP incorrectly asserts that the container is running on the new primary supervisor instead of the new standby supervisor.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…test.go Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…test.go Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces three new container placement failover tests: TestContainerPlacementLCPRIMARY, TestContainerPlacementLCBACKUP, and TestContainerPlacementLCALL. The feedback highlights swapped log messages in the primary and backup placement tests, as well as a redundant wait call in the LC_ALL placement test that could introduce test flakiness.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…test.go Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…test.go Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…test.go Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Subtest numbering according to PR - 5562