[DO-NOT-MERGE][test] VPP: use #1907 and #267

[lunyue-ms]

Why I did it

Test-only combination branch for building a full VPP image with two dependent in-review fixes:

• src/sonic-sairedis -> 537765268cc827497d7a6bdd2dec5c5253679104 ([vslib/vpp] Fix sub-port and LAG sub-port datapath on SONiC-VPP platform sonic-sairedis#1907)
• platform/vpp -> 9d27570922412dc45475654b0c5350e56eed6c1f ([sonic_ext] Add glean-redirect node: punt unresolved-nexthop transit to the kernel sonic-platform-vpp#267)

The .gitmodules URLs for only these submodules temporarily point to the lunyue-ms forks so Azure CI can fetch them. This PR must not be merged.

How I did it

• Rebased onto current sonic-buildimage master.
• Rebased both dependent PRs onto current master.
• Removed docker connect failure in the build #267 code duplicated by merged sonic-platform-vpp#257 while retaining Revert "Conform with new Docker build method" #257's bond/aggregate behavior.
• Changed docker connect failure in the build #267's VPP package version to 2606-0.5; published 2606-0.4 packages were stale and lacked the glean node.

Verification

• Built target/docker-syncd-vpp.gz successfully from local VPP 2606-0.5 sources.
• Loaded it on vlab-vpp-01 and verified the running syncd image matched the new tag.
• Verified the active sonic-ext-glean-redirect node and glean redirect counter.
• Targeted LAG routing and balancing cases passed.
• Full test_sub_port_interfaces.py: 29 passed, 3 skipped. Two teardown errors came only from existing VPP loganalyzer messages during SVI cleanup; all dataplane and post-test health checks passed.
• 8 PortChannels and 24 BGP neighbors remained up.

Cleanup

After both dependent PRs merge, restore the two .gitmodules URLs to sonic-net and update the gitlinks to their merged commits.

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mssonicbld]

/azp run Azure.sonic-buildimage

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[Copilot]

Pull request overview

This PR is a test-only (DO-NOT-MERGE) sonic-buildimage change that repoints submodule remotes so the build can fetch fork-only commits for Elastictest regression coverage (VPP promisc/sub-port related fixes).

Changes:

• Repoint src/sonic-sairedis submodule URL from sonic-net to lunyue-ms fork.
• Repoint platform/vpp submodule URL from sonic-net to lunyue-ms fork.

Comments suppressed due to low confidence (1)

.gitmodules:131

• Pointing the submodule URL at a personal fork can break consumers that don’t have access to that fork and reduces build reproducibility if the fork is force-pushed or deleted. For a mergeable change, keep .gitmodules pointing at the canonical upstream and override the submodule URL only in the test pipeline when needed.

	url = https://github.com/lunyue-ms/sonic-platform-vpp.git

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

.gitmodules:9

• This changes the sonic-sairedis submodule URL to a personal fork. Committing fork URLs into .gitmodules makes the build non-reproducible for other developers/CI and introduces supply-chain risk. Keep the canonical upstream URL here and override the submodule URL only in the test pipeline/workspace if you need to fetch fork-only commits.

[submodule "sonic-sairedis"]
	path = src/sonic-sairedis
	url = https://github.com/lunyue-ms/sonic-sairedis

.gitmodules:131

• This changes the platform/vpp submodule URL to a personal fork. Fork URLs in .gitmodules can break downstream clones and create a supply-chain/trust issue; prefer keeping the upstream sonic-net URL and applying any fork override in the CI job (e.g., via git config submodule.platform/vpp.url) for this test-only run.

[submodule "platform/vpp"]
	path = platform/vpp
	url = https://github.com/lunyue-ms/sonic-platform-vpp.git

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (2)

.gitmodules:131

• This commits a submodule URL pointing to a personal fork. That creates a supply-chain/trust risk and can break builds later if the fork/branch becomes unavailable. For integration testing, keep upstream URL in-tree and override the submodule remote in CI/local workflows instead (or revert this before merging).

	url = https://github.com/lunyue-ms/sonic-platform-vpp.git

.gitmodules:9

• This commits a submodule URL pointing to a personal fork. That creates a supply-chain/trust risk and can break builds later if the fork/branch becomes unavailable. For integration testing, keep upstream URL in-tree and override the submodule remote in CI/local workflows instead (or revert this before merging).

This issue also appears on line 131 of the same file.

	url = https://github.com/lunyue-ms/sonic-sairedis

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (2)

.gitmodules:9

• Changing the submodule URL to a personal fork makes the build non-reproducible for other developers/CI and increases supply-chain risk. Keep the canonical sonic-net URL in .gitmodules and, if you need fork-only commits for a temporary test branch, override the submodule URL in CI/local git config (e.g., git config submodule.<name>.url ...) instead of committing it.

	url = https://github.com/lunyue-ms/sonic-sairedis

.gitmodules:131

• Changing the platform/vpp submodule URL to a personal fork should not be committed: it breaks consumers that expect the canonical upstream remote and weakens provenance. Keep the sonic-net URL in .gitmodules and use a CI/local override for temporary fork testing.

	url = https://github.com/lunyue-ms/sonic-platform-vpp.git

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (2)

.gitmodules:9

• Pointing the sonic-sairedis submodule at a personal fork makes the build dependent on a non-canonical remote and increases supply-chain/availability risk if this is ever merged (fork could be deleted or rewritten). Keep .gitmodules URLs pointing at the official upstream and rely on the submodule commit SHA (or CI-only override) for testing fork-only commits.

[submodule "sonic-sairedis"]
	path = src/sonic-sairedis
	url = https://github.com/lunyue-ms/sonic-sairedis

.gitmodules:131

• Pointing the platform/vpp submodule at a personal fork makes the build dependent on a non-canonical remote and increases supply-chain/availability risk if this is ever merged (fork could be deleted or rewritten). Keep .gitmodules URLs pointing at the official upstream and rely on the submodule commit SHA (or CI-only override) for testing fork-only commits.

[submodule "platform/vpp"]
	path = platform/vpp
	url = https://github.com/lunyue-ms/sonic-platform-vpp.git