Skip to content

Conversation

@dusk125
Copy link
Contributor

@dusk125 dusk125 commented Jul 1, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 1, 2025

@dusk125: This pull request references OTA-1480 which is a valid jira issue.

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.

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 2, 2025

/retest-required

@jacobsee
Copy link
Member

jacobsee commented Jul 3, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2025
@dusk125
Copy link
Contributor Author

dusk125 commented Jul 9, 2025

/assign @DavidHurta

Comment on lines 267 to 269
SecurityContext: &corev1.SecurityContext{
ReadOnlyRootFilesystem: ptr.To(true),
},
Copy link
Member

Choose a reason for hiding this comment

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

Should the init containers (L236-L262) have this too? If not, can the commit + pr description contain reasoning for that?.

Or even better, change the setContainerDefaults to default to true so that the right thing is default and whatever needs a false would need to override?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah it wouldn't hurt to have everything as read only and only turn off what explicitly needs it.

Copy link
Contributor Author

@dusk125 dusk125 Jul 10, 2025

Choose a reason for hiding this comment

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

So looks like the init containers (specifically move-operator-manifests-to-temporary-directory, move-release-manifests-to-temporary-directory) do need to write to the filesystem as they do a file move on the /manifests and /release-manifests directories.

The destination is a volume mount so there's no issue there, but since they're moving the filesystem, they can't delete the files in the source directories as those are built into the container image.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So I'm thinking I either remove the read only filesystem from those init containers or I change them to copy instead of move and leave read only enabled on all. Do you have a preference @petr-muller ?

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 9, 2025
Copy link
Member

@petr-muller petr-muller left a comment

Choose a reason for hiding this comment

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

Thanks!

@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 Jul 9, 2025
@jacobsee
Copy link
Member

/retest-required

2 similar comments
@jacobsee
Copy link
Member

/retest-required

@ShazaAldawamneh
Copy link

/retest-required

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2025
@gangwgr
Copy link

gangwgr commented Jul 17, 2025

/qe-approved

@gangwgr
Copy link

gangwgr commented Jul 17, 2025

/label qe-approved

@jiajliu
Copy link

jiajliu commented Jul 17, 2025

/label qe-approved

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 17, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 17, 2025

@dusk125: This pull request references OTA-1480 which is a valid jira issue.

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.

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 17, 2025

/hold
for questions to Petr

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 17, 2025
@dusk125
Copy link
Contributor Author

dusk125 commented Jul 23, 2025

@petr-muller if you have a chance to review again, please see my comments about the "move" containers.

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 28, 2025

/retest

1 similar comment
@hongkailiu
Copy link
Member

/retest

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 30, 2025

/retest

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 30, 2025

/test e2e-agnostic-operator-devpreview

@dusk125
Copy link
Contributor Author

dusk125 commented Jul 30, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 30, 2025
Copy link
Member

@wking wking 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 Jul 30, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, jacobsee, petr-muller, wking

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
Copy link
Contributor

openshift-ci bot commented Jul 30, 2025

@dusk125: The following test 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-agnostic-operator-devpreview 4e5f950 link false /test e2e-agnostic-operator-devpreview

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.

@openshift-merge-bot openshift-merge-bot bot merged commit a7d6e43 into openshift:main Jul 30, 2025
17 of 18 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-version-operator
This PR has been included in build cluster-version-operator-container-v4.20.0-202507310219.p0.ga7d6e43.assembly.stream.el9.
All builds following this will include this PR.

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. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.