Skip to content

ci: download libnexthopgroup deb for the sonic-swss build stage#1197

Closed
bhouse-nexthop wants to merge 1 commit into
sonic-net:masterfrom
bhouse-nexthop:ci-libnexthopgroup-deb
Closed

ci: download libnexthopgroup deb for the sonic-swss build stage#1197
bhouse-nexthop wants to merge 1 commit into
sonic-net:masterfrom
bhouse-nexthop:ci-libnexthopgroup-deb

Conversation

@bhouse-nexthop

Copy link
Copy Markdown
Contributor

Description of PR

Summary:
sonic-swss commit e6c482ca ("[fpmsyncd]: add libnexthopgroup in Makefile.am to support rib/fib", PR sonic-net/sonic-swss#4394) added -lnexthopgroup to fpmsyncd's link line, expecting libnexthopgroup_*.deb to already be installed when the swss build runs. sonic-swss-common's downstream "Compile sonic swss" stage in .azure-pipelines/build-swss-template.yml installs everything it needs from the common-lib artifact, but its pattern list never picked up the new package, so the link now fails with cannot find -lnexthopgroup whenever this pipeline cascades into a sonic-swss build.

Fix: add the libnexthopgroup*.deb pattern next to the other Azure.sonic-buildimage.common_libs entries so dpkg picks it up in the existing install step.

Reviewer entry point: .azure-pipelines/build-swss-template.yml (one-line addition).

Fixes # (no issue filed)

Type of change

  • Bug fix
  • New feature
  • Refactor / cleanup
  • Documentation update
  • Test improvement

Approach

What is the motivation for this PR?

Unblock the sonic-swss build stage of the sonic-swss-common pipeline, which is currently failing at fpmsyncd's link step on any PR that cascades into a sonic-swss build.

How did you do it?

Added one pattern (libnexthopgroup*.deb) to the existing DownloadPipelineArtifact@2 step that pulls common_libs from Azure.sonic-buildimage. The deb is built upstream by sonic-buildimage and already present in the artifact; the pipeline just wasn't asking for it.

How did you verify/test it?

Local verification: confirmed via the failing build log that fpmsyncd is linking against -lnexthopgroup and failing because the lib isn't present on the build agent. CI re-run on this PR will exercise the fix end-to-end.

Any platform specific information?

None. The pattern is parameterized by ${{ parameters.debian_version }} like every other entry in the same list.

Documentation

N/A — CI plumbing only, no public-facing change.

sonic-swss commit e6c482ca ("[fpmsyncd]: add libnexthopgroup in
Makefile.am to support rib/fib") added -lnexthopgroup to fpmsyncd's
link line, expecting libnexthopgroup_*.deb to already be installed
when the swss build runs. sonic-swss-common's downstream "Compile
sonic swss" stage installs everything it needs from the common-lib
artifact, but its pattern list never picked up the new package, so
the link now fails with `cannot find -lnexthopgroup`. Add the
libnexthopgroup pattern next to the other Azure.sonic-buildimage.
common_libs entries in build-swss-template.yml so dpkg picks it up
in the existing install step.

Signed-off-by: Brad House <bhouse@nexthop.ai>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@lguohan

lguohan commented May 27, 2026

Copy link
Copy Markdown
Contributor

#973 merged.

@lguohan lguohan closed this May 27, 2026
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.

3 participants