Skip to content

[release-4.16] OCPBUGS-60897: Revert "40rhcos-fips: include fips.so in initrd"#1858

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-1855-to-release-4.16
Sep 3, 2025
Merged

[release-4.16] OCPBUGS-60897: Revert "40rhcos-fips: include fips.so in initrd"#1858
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
openshift-cherrypick-robot:cherry-pick-1855-to-release-4.16

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Aug 26, 2025

This is an automated cherry-pick of #1855

/assign openshift-ci-robot

@mike-nguyen
Revert "40rhcos-fips: include fips.so in initrd"
f053aa9 
This reverts commit f21c511.

This was fixed upstream in in RHEL so this patch is no longer
needed.

9.4 - https://issues.redhat.com/browse/RHEL-104864
9.2 - https://issues.redhat.com/browse/RHEL-104863
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 26, 2025
Merged
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 26, 2025

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-60201 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.16] OCPBUGS-60897: Revert "40rhcos-fips: include fips.so in initrd"

Details

In response to this:

This is an automated cherry-pick of #1855

/assign openshift-ci-robot

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.16] OCPBUGS-60201: Revert "40rhcos-fips: include fips.so in initrd" [release-4.16] OCPBUGS-60897: Revert "40rhcos-fips: include fips.so in initrd" Aug 26, 2025
@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 Aug 26, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 26, 2025

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

  • expected dependent Jira Issue OCPBUGS-60896 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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 #1855

/assign openshift-ci-robot

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 marmijo and travier August 26, 2025 14:20
marmijo
marmijo approved these changes Aug 26, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@marmijo marmijo 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 lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 26, 2025
@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Aug 28, 2025

/test all

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Aug 28, 2025

@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.

@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Aug 28, 2025

fips.failure passed

/label cherry-pick-approved
/label backport-risk-assessed

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Aug 28, 2025
@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Sep 3, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 3, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 3, 2025

@mike-nguyen: This pull request references Jira Issue OCPBUGS-60897, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-60896 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-60896 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

Details

In response to this:

/jira refresh

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 a review from mike-nguyen September 3, 2025 15:29
@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Sep 3, 2025

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Sep 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marmijo, mike-nguyen, 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:
  • OWNERS [marmijo,mike-nguyen]

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

@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Sep 3, 2025

/verified

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 3, 2025

@mike-nguyen: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified

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.

@mike-nguyen
Copy link
Copy Markdown
Member

mike-nguyen commented Sep 3, 2025

/verified by fips.enabled, fips.failure

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 3, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 3, 2025

@mike-nguyen: This PR has been marked as verified by fips.enabled,fips.failure.

Details

In response to this:

/verified by fips.enabled, fips.failure

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-merge-bot openshift-merge-bot bot merged commit 4392d4f into openshift:release-4.16 Sep 3, 2025
5 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 3, 2025

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-60897
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-60897 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #1855

/assign openshift-ci-robot

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.

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

Reviewers

@mike-nguyen mike-nguyen mike-nguyen approved these changes

@travier travier Awaiting requested review from travier

+1 more reviewer

@marmijo marmijo marmijo approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@mike-nguyen mike-nguyen

@openshift-ci-robot openshift-ci-robot

@marmijo marmijo

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @mike-nguyen @marmijo