Skip to content

fix: pin osc to 1.23.0 in k8s-cloud-builder#4331

Closed
saschagrunert wants to merge 1 commit intokubernetes:masterfrom
saschagrunert:fix/pin-osc-version
Closed

fix: pin osc to 1.23.0 in k8s-cloud-builder#4331
saschagrunert wants to merge 1 commit intokubernetes:masterfrom
saschagrunert:fix/pin-osc-version

Conversation

@saschagrunert
Copy link
Member

/kind bug

What this PR does / why we need it:

Pin osc to 1.23.0 in the k8s-cloud-builder Dockerfile. osc 1.25.0 changed the config file lookup order to prefer XDG paths over ~/.oscrc, causing OBS stage/release Cloud Build jobs to fail with HTTP Error 401: Unauthorized on osc whois.

The proper fix is in kubernetes-sigs/release-sdk#531, this is the immediate workaround.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

osc is currently installed via pip3 install osc without a pinned version. Every k8s-cloud-builder image rebuild picks up the latest version from PyPI. The February patches used osc 1.23.0 (working), the March rebuilds pulled 1.25.0 (broken).

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority labels Mar 19, 2026
@k8s-ci-robot k8s-ci-robot requested a review from jimangel March 19, 2026 08:05
@k8s-ci-robot k8s-ci-robot added the area/release-eng Issues or PRs related to the Release Engineering subproject label Mar 19, 2026
@k8s-ci-robot k8s-ci-robot requested a review from jrsapi March 19, 2026 08:05
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 19, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 19, 2026
osc 1.25.0 changed the config file lookup order to prefer XDG paths
over ~/.oscrc, causing OBS stage/release Cloud Build jobs to fail with
HTTP 401 on osc whois. Pin to 1.23.0 which is the last known working
version and track it in dependencies.yaml.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 19, 2026
@saschagrunert
Copy link
Member Author

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 19, 2026
@saschagrunert
Copy link
Member Author

Transient failure.

@saschagrunert saschagrunert deleted the fix/pin-osc-version branch March 19, 2026 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. needs-priority release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants