Skip to content

[release-4.19] OCPBUGS-78457: Explicitly set the ReadOnlyRootFilesystem flag to false#574

Open
hroyrh wants to merge 3 commits intoopenshift:release-4.19from
hroyrh:OCPBUGS-78457
Open

[release-4.19] OCPBUGS-78457: Explicitly set the ReadOnlyRootFilesystem flag to false#574
hroyrh wants to merge 3 commits intoopenshift:release-4.19from
hroyrh:OCPBUGS-78457

Conversation

@hroyrh
Copy link
Copy Markdown
Contributor

@hroyrh hroyrh commented Mar 13, 2026

No description provided.

hroyrh added 3 commits March 13, 2026 15:00
…so that SCC during deployment cannot override it

Signed-off-by: Himanshu Roy <hroy@redhat.com>
(cherry picked from commit 6ef8811)
The support for ReadOnlyRootFilesystem was only introduced in 4.21,
and in ocp 4.20 and earlier, it's not set explicitly which defaults it
to false. But, SCCs during deployment of ocp 4.20 led to setting this
flag to true, which causes failures during deployment. Therefore,
setting it explicitly so it doesn't get overwritten.

Signed-off-by: Himanshu Roy <hroy@redhat.com>
(cherry picked from commit 9d73ca2)
@openshift-ci-robot openshift-ci-robot added 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 Mar 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: This pull request references Jira Issue OCPBUGS-78457, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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:

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 13, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 07877242-fee7-4d2f-957d-fe4425e00ec0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from andfasano and sadasu March 13, 2026 09:40
@hroyrh
Copy link
Copy Markdown
Contributor Author

hroyrh commented Mar 13, 2026

/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 Mar 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hroyrh: This pull request references Jira Issue OCPBUGS-78457, 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.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-76340 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-76340 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

Requesting review from QA contact:
/cc @jadhaj

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 jadhaj March 13, 2026 10:13
@hroyrh
Copy link
Copy Markdown
Contributor Author

hroyrh commented Mar 13, 2026

/cherrypick release-4.18

@openshift-cherrypick-robot
Copy link
Copy Markdown

@hroyrh: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.18

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.

@hroyrh
Copy link
Copy Markdown
Contributor Author

hroyrh commented Mar 13, 2026

/retest-required

1 similar comment
@hroyrh
Copy link
Copy Markdown
Contributor Author

hroyrh commented Mar 14, 2026

/retest-required

@MahnoorAsghar
Copy link
Copy Markdown
Contributor

/test unit

@hroyrh
Copy link
Copy Markdown
Contributor Author

hroyrh commented Mar 27, 2026

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

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

@iurygregory
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2026
sgoveas added a commit to sgoveas/release that referenced this pull request Mar 27, 2026
@dtantsur
Copy link
Copy Markdown
Member

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 30, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtantsur, hroyrh

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 Mar 30, 2026
sgoveas added a commit to sgoveas/release that referenced this pull request Mar 30, 2026
@sgoveas
Copy link
Copy Markdown

sgoveas commented Mar 31, 2026

/verified by sgoveas link

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@sgoveas: This PR has been marked as verified by sgoveas [link](https://redhat.atlassian.net/browse/OCPBUGS-78457?focusedCommentId=16584571).

Details

In response to this:

/verified by sgoveas link

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

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

Development

Successfully merging this pull request may close these issues.

7 participants