Skip to content

Conversation

@bertinatto
Copy link
Member

This ensures that CRD updates are applied earlier during a cluster upgrade process. This prevents CSI operators from accessing new/updated fields of the CR before the corresponding CRDs been updated.

CC @openshift/storage

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2024

Hello @bertinatto! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 19, 2024
@openshift-ci openshift-ci bot requested review from bparees and sjenning November 19, 2024 18:18
@deads2k
Copy link
Contributor

deads2k commented Nov 19, 2024

You may re-number as you wish, but I think the default is 80, so moving 50 to 80 is probably bad.

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.

Makes sense to me, since the other *csi* manifests are in the default run-level 50

$ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.18.0-ec.3-x86_64
$ ls manifests/*csi* | sort
manifests/0000_50_cluster-csi-snapshot-controller-operator_01_config.crd.yaml
manifests/0000_50_cluster-csi-snapshot-controller-operator_02_operator_cr.yaml
...
manifests/0000_50_cluster-csi-snapshot-controller-operator_10_clusteroperator.yaml
manifests/0000_50_cluster-storage-operator_02_csi_driver_operators_namespace.yaml
...
manifests/0000_50_cluster-storage-operator_09_openshift-csi-resizer-storageclass-reader-role.yaml
manifests/0000_90_csi-driver_01_clustercsidrivers.crd.yaml

Although I'm not sure which of those would be trying to interact with the ClusterCSIDriver API.

@deads2k
Copy link
Contributor

deads2k commented Nov 19, 2024

/lgtm
/approve

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Nov 19, 2024
@wking
Copy link
Member

wking commented Nov 19, 2024

...but I think the default is 80...

The default is 50 (code and docs).

@bertinatto bertinatto force-pushed the decrease-runlevel-clustercsidrivers branch from 931ca42 to cb82e6c Compare November 19, 2024 18:38
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 19, 2024
@bertinatto bertinatto force-pushed the decrease-runlevel-clustercsidrivers branch from 05e974f to 1ed01cd Compare November 19, 2024 19:01
Copy link
Contributor

Choose a reason for hiding this comment

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

weird that this is a new file, not a move.

Copy link
Member Author

Choose a reason for hiding this comment

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

interesting, the script just added a new file

Copy link
Member Author

Choose a reason for hiding this comment

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

manually removed it

Copy link
Member Author

Choose a reason for hiding this comment

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

seems like a bug in the script. I'll add to my queue, but I'm not sure when I'll be able to get to it (CC @JoelSpeed )

Copy link
Member Author

Choose a reason for hiding this comment

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

pushed a commit to clean the CRDs directory before cloning the CRDs into it. PTAL

@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 19, 2024
This helps when a runlevel for a CRD is changed. In that case,
the old CRD should be deleted.
@bertinatto bertinatto force-pushed the decrease-runlevel-clustercsidrivers branch from 4bf9b38 to 15f5718 Compare November 20, 2024 11:51
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@bertinatto: 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/okd-scos-e2e-aws-ovn 15f5718 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.

@JoelSpeed
Copy link
Contributor

Looks better now, schema checker error is not fixable

/lgtm
/override ci/prow/verify-crd-schema-checker

Does this need the ack critical fixes label?

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@JoelSpeed: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/verify-crd-schema-checker

Only the following failed contexts/checkruns were expected:

  • ci/prow/build
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-hypershift
  • ci/prow/e2e-aws-ovn-techpreview
  • ci/prow/e2e-aws-serial
  • ci/prow/e2e-aws-serial-techpreview
  • ci/prow/e2e-azure
  • ci/prow/e2e-gcp
  • ci/prow/e2e-upgrade
  • ci/prow/images
  • ci/prow/integration
  • ci/prow/minor-e2e-upgrade-minor
  • ci/prow/minor-images
  • ci/prow/okd-scos-e2e-aws-ovn
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-client-go
  • ci/prow/verify-crd-schema
  • ci/prow/verify-deps
  • pull-ci-openshift-api-master-build
  • pull-ci-openshift-api-master-e2e-aws-ovn
  • pull-ci-openshift-api-master-e2e-aws-ovn-hypershift
  • pull-ci-openshift-api-master-e2e-aws-ovn-techpreview
  • pull-ci-openshift-api-master-e2e-aws-serial
  • pull-ci-openshift-api-master-e2e-aws-serial-techpreview
  • pull-ci-openshift-api-master-e2e-azure
  • pull-ci-openshift-api-master-e2e-gcp
  • pull-ci-openshift-api-master-e2e-upgrade
  • pull-ci-openshift-api-master-images
  • pull-ci-openshift-api-master-integration
  • pull-ci-openshift-api-master-minor-e2e-upgrade-minor
  • pull-ci-openshift-api-master-minor-images
  • pull-ci-openshift-api-master-okd-scos-e2e-aws-ovn
  • pull-ci-openshift-api-master-unit
  • pull-ci-openshift-api-master-verify
  • pull-ci-openshift-api-master-verify-client-go
  • pull-ci-openshift-api-master-verify-crd-schema
  • pull-ci-openshift-api-master-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

Looks better now, schema checker error is not fixable

/lgtm
/override ci/prow/verify-crd-schema-checker

Does this need the ack critical fixes label?

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

openshift-ci bot commented Nov 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, deads2k, JoelSpeed, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@bertinatto
Copy link
Member Author

Looks better now, schema checker error is not fixable

/lgtm /override ci/prow/verify-crd-schema-checker

Does this need the ack critical fixes label?

Adding the label, as this can fix an issue that has been blocking the Storage team:

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Nov 21, 2024
@JoelSpeed
Copy link
Contributor

/override ci/prow/verify-crd-schema

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2024

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema

In response to this:

/override ci/prow/verify-crd-schema

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

/retest-required

Remaining retests: 0 against base HEAD caf9796 and 2 for PR HEAD 15f5718 in total

@gnufied
Copy link
Member

gnufied commented Nov 21, 2024

This indeed appears to fix the issue. I made a build from this PR and upgraded from 4.17 and operator logs appeared to be calm.

@openshift-merge-bot openshift-merge-bot bot merged commit ec9bf3f into openshift:master Nov 21, 2024
19 of 20 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-config-api
This PR has been included in build ose-cluster-config-api-container-v4.19.0-202411211638.p0.gec9bf3f.assembly.stream.el9.
All builds following this will include this PR.

dobsonj added a commit to dobsonj/vmware-vsphere-csi-driver-operator that referenced this pull request Nov 21, 2024
@dobsonj
Copy link
Member

dobsonj commented Nov 25, 2024

/jira refresh

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

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants