OCPBUGS-66113: Some containers do not have readOnlyRootFilesystem #476

tsmetana · 2025-12-04T10:11:16Z

This should fix the part of OCBPBUGS-66113 that is caused by the csi-operator.

openshift-ci-robot · 2025-12-04T10:11:23Z

@tsmetana: This pull request references Jira Issue OCPBUGS-66113, which is invalid:

expected the bug to target the "4.21.0" version, but no target version was set

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 should fix the part of OCBPBUGS-66113 that is caused by the csi-operator.

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 · 2025-12-04T10:12:40Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tsmetana

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~~ [tsmetana]

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

tsmetana · 2025-12-04T10:28:33Z

/jira refresh

openshift-ci-robot · 2025-12-04T10:28:41Z

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

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.21.0) matches configured target version for branch (4.21.0)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @chao007

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.

tsmetana · 2025-12-05T08:13:21Z

/retest

jsafrane · 2025-12-08T13:13:32Z

/lgtm

tsmetana · 2025-12-08T15:12:20Z

/retest-required

tsmetana · 2025-12-09T11:35:20Z

/test hypershift-e2e-openstack-aws-csi-manila

chao007 · 2025-12-10T02:37:27Z

/test hypershift-e2e-openstack-aws-csi-manila

tsmetana · 2025-12-10T12:20:20Z

/test hypershift-e2e-openstack-aws-csi-manila

chao007 · 2025-12-11T07:42:03Z

/test hypershift-e2e-openstack-aws-csi-manila

tsmetana · 2025-12-11T13:00:34Z

I have checked the Manila operator logs: there are no errors there... It looks like CAPI provided start times out so the cluster never comes up completely.

tsmetana · 2025-12-11T13:00:41Z

/test hypershift-e2e-openstack-aws-csi-manila

openshift-bot · 2025-12-12T08:26:48Z

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

chao007 · 2025-12-15T07:27:11Z

/test hypershift-e2e-openstack-aws-csi-manila

tsmetana · 2025-12-15T10:10:47Z

/jira refresh

openshift-ci-robot · 2025-12-15T10:10:54Z

@tsmetana: This pull request references Jira Issue OCPBUGS-66113, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @chao007

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.

tsmetana · 2025-12-15T13:32:35Z

/test hypershift-e2e-openstack-aws-csi-manila

chao007 · 2025-12-16T08:05:29Z

cluster is not ready.

chao007 · 2025-12-18T06:36:40Z

/test hypershift-e2e-openstack-aws-csi-manila

chao007 · 2025-12-26T02:15:49Z

/test hypershift-e2e-openstack-aws-csi-manila

openshift-bot · 2026-01-01T00:01:46Z

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

openshift-ci-robot · 2026-01-01T00:02:35Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-66113, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @chao007

Details

In response to this:

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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.

chao007 · 2026-01-04T03:06:56Z

hypershift-e2e-openstack-aws-csi-manila failed is related with cluster installation timeout, not by this pr. I prefer to merge this pr first.

tsmetana · 2026-01-05T09:53:16Z

/retest-required

tsmetana · 2026-01-06T14:02:26Z

The hypershift-e2e-openstack-aws-csi-manila will not work until hypershift gets CAPI v1beta2 support on TechPreviewNoUpgradeClusters. The failures for the job are unrelated to our (or any other) PR. :(

chao007 · 2026-01-07T07:59:41Z

/verified by CI

openshift-ci-robot · 2026-01-07T07:59:53Z

@chao007: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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-robot · 2026-01-07T08:32:36Z

/retest-required

Remaining retests: 0 against base HEAD 390ff75 and 2 for PR HEAD 15ed1f6 in total

openshift-ci-robot · 2026-01-08T05:32:42Z

/retest-required

Remaining retests: 0 against base HEAD e27d70e and 1 for PR HEAD 15ed1f6 in total

stephenfin · 2026-01-08T12:13:12Z

/override ci/prow/hypershift-e2e-openstack-aws-csi-manila

openshift-ci · 2026-01-08T12:14:06Z

@stephenfin: Overrode contexts on behalf of stephenfin: ci/prow/hypershift-e2e-openstack-aws-csi-manila

Details

In response to this:

/override ci/prow/hypershift-e2e-openstack-aws-csi-manila

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 · 2026-01-08T15:32:29Z

/retest-required

Remaining retests: 0 against base HEAD 33e93a6 and 0 for PR HEAD 15ed1f6 in total

openshift-ci-robot · 2026-01-08T17:32:49Z

/hold

Revision 15ed1f6 was retested 3 times: holding

tsmetana · 2026-01-09T09:25:28Z

/hold cancel

tsmetana · 2026-01-09T09:25:36Z

/retest-required

openshift-ci-robot · 2026-01-09T11:29:40Z

/retest-required

Remaining retests: 0 against base HEAD 21e84b7 and 2 for PR HEAD 15ed1f6 in total

openshift-ci · 2026-01-09T12:57:07Z

@tsmetana: The following tests 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/e2e-openstack	`15ed1f6`	link	false	`/test e2e-openstack`
ci/prow/e2e-azurestack-csi	`15ed1f6`	link	false	`/test e2e-azurestack-csi`
ci/prow/hypershift-e2e-openstack-aws-csi-cinder	`15ed1f6`	link	true	`/test hypershift-e2e-openstack-aws-csi-cinder`
ci/prow/hypershift-e2e-aks	`15ed1f6`	link	true	`/test hypershift-e2e-aks`
ci/prow/hypershift-e2e-openstack-aws-csi-manila	`15ed1f6`	link	true	`/test hypershift-e2e-openstack-aws-csi-manila`

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.

OCPBUGS-66113: Some containers do not have readOnlyRootFilesystem

15ed1f6

openshift-ci bot requested review from RomanBednar and rhrmo December 4, 2025 10:12

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025

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 Dec 4, 2025

openshift-ci bot requested a review from chao007 December 4, 2025 10:28

openshift-ci bot assigned jsafrane Dec 8, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2025

openshift-ci bot assigned chao007, duanwei33, Phaow and radeore Dec 8, 2025

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 Dec 15, 2025

openshift-ci-robot mentioned this pull request Dec 17, 2025

OCPBUGS-66113: Some containers do not have readOnlyRootFilesystem openshift/gcp-pd-csi-driver-operator#157

Merged

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 7, 2026

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 8, 2026

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 9, 2026

OCPBUGS-66113: Some containers do not have readOnlyRootFilesystem #476

Are you sure you want to change the base?

OCPBUGS-66113: Some containers do not have readOnlyRootFilesystem #476

Uh oh!

Conversation

tsmetana commented Dec 4, 2025

Uh oh!

openshift-ci-robot commented Dec 4, 2025

Uh oh!

openshift-ci bot commented Dec 4, 2025

Uh oh!

tsmetana commented Dec 4, 2025

Uh oh!

openshift-ci-robot commented Dec 4, 2025

Uh oh!

tsmetana commented Dec 5, 2025

Uh oh!

jsafrane commented Dec 8, 2025

Uh oh!

tsmetana commented Dec 8, 2025

Uh oh!

tsmetana commented Dec 9, 2025

Uh oh!

chao007 commented Dec 10, 2025

Uh oh!

tsmetana commented Dec 10, 2025

Uh oh!

chao007 commented Dec 11, 2025

Uh oh!

tsmetana commented Dec 11, 2025

Uh oh!

tsmetana commented Dec 11, 2025

Uh oh!

openshift-bot commented Dec 12, 2025

Uh oh!

chao007 commented Dec 15, 2025

Uh oh!

tsmetana commented Dec 15, 2025

Uh oh!

openshift-ci-robot commented Dec 15, 2025

Uh oh!

tsmetana commented Dec 15, 2025

Uh oh!

chao007 commented Dec 16, 2025

Uh oh!

chao007 commented Dec 18, 2025

Uh oh!

chao007 commented Dec 26, 2025

Uh oh!

openshift-bot commented Jan 1, 2026

Uh oh!

openshift-ci-robot commented Jan 1, 2026

Uh oh!

chao007 commented Jan 4, 2026

Uh oh!

tsmetana commented Jan 5, 2026

Uh oh!

tsmetana commented Jan 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chao007 commented Jan 7, 2026

Uh oh!

openshift-ci-robot commented Jan 7, 2026

Uh oh!

openshift-ci-robot commented Jan 7, 2026

Uh oh!

openshift-ci-robot commented Jan 8, 2026

Uh oh!

stephenfin commented Jan 8, 2026

Uh oh!

openshift-ci bot commented Jan 8, 2026

Uh oh!

openshift-ci-robot commented Jan 8, 2026

Uh oh!

openshift-ci-robot commented Jan 8, 2026

Uh oh!

tsmetana commented Jan 9, 2026

Uh oh!

tsmetana commented Jan 9, 2026

Uh oh!

tsmetana commented Jan 6, 2026 •

edited

Loading