Skip to content

[202511][supervisor] Updating supervisor pointer to 4.3.0 release#25861

Open
mattkim25 wants to merge 1 commit intosonic-net:202511from
mattkim25:fix_supervisor_202511_commit_pointer
Open

[202511][supervisor] Updating supervisor pointer to 4.3.0 release#25861
mattkim25 wants to merge 1 commit intosonic-net:202511from
mattkim25:fix_supervisor_202511_commit_pointer

Conversation

@mattkim25
Copy link

Why I did it

Fixes Issue: #25857

For the 202511 branch, the supervisor submodule points to the commit for 4.2.5, but the build process is expecting 4.3.0. This fails the build

The build rule expected Supervisor 4.3.0, but the source package and pinned Python versions are 4.2.5, so the generated wheel name did not match the target artifact path.

Work item tracking
  • Microsoft ADO (number only):

How I did it

I updated the following in 202511 to match master

202511 Branch
Line 36 in files/build/versions/build/build-sonic-slave-bookworm/versions-py3.
Supervisor ref pointer is 99a3e3e240d9d13e143b306818731e224e1e73d2
Line 3 in rules/supervisor.mk has supervisor-4.2.5-py2.py3-none-any.whl

Master Branch
Line 36 in files/build/versions-public/build/build-sonic-slave-bookworm/versions-py3
Correct supervisor ref pointer is dbca8d457e61d8707c40f99c78330b87939483a3 and this exists in the master branch.
Line 3 in rules/supervisor.mk has supervisor-4.3.0-py2.py3-none-any.whl

How to verify it

Rebuild 202511 image

Which release branch to backport (provide reason below if selected)

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

image

For the 202511 branch, the supervisor submodule points to
the commit for 4.2.5, but the build process is expecting 4.3.0

Signed-off-by: Matthew Kim <mkim@upscaleai.com>
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

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.

2 participants