Skip to content

[release-4.21] OCPBUGS-82523: post-process: Remove workaround for openvswitch additional group#1926

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-1918-to-release-4.21
Open

[release-4.21] OCPBUGS-82523: post-process: Remove workaround for openvswitch additional group#1926
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-1918-to-release-4.21

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Apr 10, 2026

This is an automated cherry-pick of #1918

/assign travier

@travier
post-process: Remove workaround for openvswitch additional group
5b7e6c3 
We are moving the group inclusion directly to the RHEL base image
instead of working around it here in the OCP node layer.

See: openshift#1917
See: coreos/rhel-coreos-config#224
See: https://redhat.atlassian.net/browse/OCPBUGS-64841
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 10, 2026
Merged
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 10, 2026

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-64841 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.21] OCPBUGS-82523: post-process: Remove workaround for openvswitch additional group

Details

In response to this:

This is an automated cherry-pick of #1918

/assign travier

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 changed the title [release-4.21] OCPBUGS-64841: post-process: Remove workaround for openvswitch additional group [release-4.21] OCPBUGS-82523: post-process: Remove workaround for openvswitch additional group Apr 10, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate 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 Apr 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 10, 2026

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

  • expected dependent Jira Issue OCPBUGS-64841 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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 #1918

/assign travier

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 requested review from gursewak1997 and travier April 10, 2026 14:50
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 10, 2026

@openshift-cherrypick-robot: all tests passed!

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.

aaradhak
aaradhak approved these changes Apr 10, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@aaradhak aaradhak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 10, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, openshift-cherrypick-robot

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gursewak1997 gursewak1997 Awaiting requested review from gursewak1997

@travier travier Awaiting requested review from travier

1 more reviewer

@aaradhak aaradhak aaradhak approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@travier travier

@aaradhak aaradhak

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @aaradhak @travier