Skip to content

[release-5.1] OCPBUGS-123732: Re-enable sandboxed-containers extension for 5.0 - #1970

Closed
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.1from
openshift-cherrypick-robot:cherry-pick-1965-to-release-5.1
Closed

[release-5.1] OCPBUGS-123732: Re-enable sandboxed-containers extension for 5.0#1970
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.1from
openshift-cherrypick-robot:cherry-pick-1965-to-release-5.1

Conversation

@openshift-cherrypick-robot

@openshift-cherrypick-robot openshift-cherrypick-robot commented Sep 16, 2026

Copy link
Copy Markdown

This is an automated cherry-pick of #1965

/assign aaradhak

@aaradhak @openshift-cherrypick-robot
OCPBUGS-115309: Re-enable sandboxed-containers extension for 5.0
8213101 
KATA-4726 made kata-containers available again for RHCOS 9.8 and 10.2.
Restore the sandboxed-containers extension in those definitions so 5.0
builds can ship it.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 16, 2026
Merged
@openshift-merge-bot

openshift-merge-bot Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot

openshift-ci-robot commented Sep 16, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-115309 has been cloned as Jira Issue OCPBUGS-123732. Will retitle bug to link to clone.
/retitle [release-5.1] OCPBUGS-123732: Re-enable sandboxed-containers extension for 5.0

Details

In response to this:

This is an automated cherry-pick of #1965

/assign aaradhak

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign aaradhak for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@openshift-ci openshift-ci Bot changed the title [release-5.1] OCPBUGS-115309: Re-enable sandboxed-containers extension for 5.0 [release-5.1] OCPBUGS-123732: Re-enable sandboxed-containers extension for 5.0 Sep 16, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 16, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 16, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-123732, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1965

/assign aaradhak

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images 8213101 link true /test images

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@dustymabe

dustymabe commented Sep 17, 2026

Copy link
Copy Markdown
Member

IIUC you should open a PR against master branch. the release-5.1 branch is auto-synced with master during this time period of development.

@aaradhak

aaradhak commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

IIUC you should open a PR against master branch. the release-5.1 branch is auto-synced with master during this time period of development.

Ah I see, I will open it against 'master'.

@aaradhak

aaradhak commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

/close

@openshift-ci openshift-ci Bot closed this Sep 17, 2026
@openshift-ci

openshift-ci Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

@aaradhak: Closed this PR.

Details

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci-robot

openshift-ci-robot commented Sep 17, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-123732. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

This is an automated cherry-pick of #1965

/assign aaradhak

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@aaradhak

aaradhak commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

IIUC you should open a PR against master branch. the release-5.1 branch is auto-synced with master during this time period of development.

@dustymabe I have opened the PR against the master branch - #1971

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@joelcapitao joelcapitao Awaiting requested review from joelcapitao
@Rolv-Apneseth Rolv-Apneseth Awaiting requested review from Rolv-Apneseth

Assignees

@aaradhak aaradhak

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @dustymabe @aaradhak