Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
tsmetana wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

tsmetana wants to merge 1 commit into from

Conversation

@tsmetana
Copy link
Member

@tsmetana tsmetana commented Dec 4, 2025

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

@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 Dec 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 4, 2025

@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 openshift-ci bot requested review from RomanBednar and rhrmo December 4, 2025 10:12
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

[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:

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 Dec 4, 2025
@tsmetana
Copy link
Member Author

tsmetana commented Dec 4, 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 Dec 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 4, 2025

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

@openshift-ci openshift-ci bot requested a review from chao007 December 4, 2025 10:28
@tsmetana
Copy link
Member Author

tsmetana commented Dec 5, 2025

/retest

@jsafrane
Copy link
Contributor

jsafrane commented Dec 8, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2025
@tsmetana
Copy link
Member Author

tsmetana commented Dec 8, 2025

/retest-required

@tsmetana
Copy link
Member Author

tsmetana commented Dec 9, 2025

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

3 similar comments
@chao007
Copy link

chao007 commented Dec 10, 2025

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

@tsmetana
Copy link
Member Author

tsmetana commented Dec 10, 2025

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

@chao007
Copy link

chao007 commented Dec 11, 2025

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

@tsmetana
Copy link
Member Author

tsmetana commented Dec 11, 2025

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
Copy link
Member Author

tsmetana commented Dec 11, 2025

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

@openshift-bot
Copy link

openshift-bot commented Dec 12, 2025

/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 openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 12, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 12, 2025

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

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21.0" 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.

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.

@tsmetana
Copy link
Member Author

tsmetana commented Dec 12, 2025

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

1 similar comment
@chao007
Copy link

chao007 commented Dec 15, 2025

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

@tsmetana
Copy link
Member Author

tsmetana commented Dec 15, 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 Dec 15, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 15, 2025

@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
Copy link
Member Author

tsmetana commented Dec 15, 2025

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

@chao007
Copy link

chao007 commented Dec 16, 2025

cluster is not ready.

@openshift-ci-robot openshift-ci-robot mentioned this pull request Dec 17, 2025
Merged
@chao007
Copy link

chao007 commented Dec 18, 2025

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

1 similar comment
@chao007
Copy link

chao007 commented Dec 26, 2025

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

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

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

Reviewers

@rhrmo rhrmo Awaiting requested review from rhrmo

@RomanBednar RomanBednar Awaiting requested review from RomanBednar

@chao007 chao007 Awaiting requested review from chao007

Assignees

@jsafrane jsafrane

@chao007 chao007

@duanwei33 duanwei33

@Phaow Phaow

@radeore radeore

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate 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.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@tsmetana @openshift-ci-robot @jsafrane @chao007 @openshift-bot @duanwei33 @Phaow @radeore