Skip to content

STOR-1767: add env var OPERATOR_NAME to vsphere csi operator deployment#485

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
mpatlasov:STOR-1767-add-env-OPERATOR_NAME-to-vsphere-deployment
Jul 3, 2024
Merged

STOR-1767: add env var OPERATOR_NAME to vsphere csi operator deployment#485
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
mpatlasov:STOR-1767-add-env-OPERATOR_NAME-to-vsphere-deployment

Conversation

@mpatlasov
Copy link
Contributor

openshift/vmware-vsphere-csi-driver-operator#233 will do allowOperatorRemovedState=True for vsphere csi operator. This will trigger finalazer check in library-go:

	if management.IsOperatorRemovable() {
		if err := v1helpers.EnsureFinalizer(ctx, c.operatorClient, c.name); err != nil {

EnsureFinalizer(), in turn, calculates finalizer name either as os.Getenv("OPERATOR_NAME") or os.Args[0]. The latter doesn't work for vsphere because leading slash in /usr/bin/vmware-vsphere-csi-driver-operator is not allowed:

E0701 19:43:32.342151       1 base_controller.go:268] VMwareVSphereDriverControllerServiceController reconciliation failed: ClusterCSIDriver.operator.openshift.io "csi.vsphere.vmware.com" is invalid: metadata.finalizers: Invalid value: "/usr/bin/vmware-vsphere-csi-driver-operator.operator.openshift.io/VMwareVSphereDriverControllerServiceController": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')

openshift/vmware-vsphere-csi-driver-operator#233 will do `allowOperatorRemovedState=True` for vsphere csi operator. This will trigger finalazer check in library-go:

```
	if management.IsOperatorRemovable() {
		if err := v1helpers.EnsureFinalizer(ctx, c.operatorClient, c.name); err != nil {
```

`EnsureFinalizer()`, in turn, calculates finalizer name either as `os.Getenv("OPERATOR_NAME")` or `os.Args[0]`. The latter doesn't work for vsphere because leading slash in `/usr/bin/vmware-vsphere-csi-driver-operator` is not allowed:

```
E0701 19:43:32.342151       1 base_controller.go:268] VMwareVSphereDriverControllerServiceController reconciliation failed: ClusterCSIDriver.operator.openshift.io "csi.vsphere.vmware.com" is invalid: metadata.finalizers: Invalid value: "/usr/bin/vmware-vsphere-csi-driver-operator.operator.openshift.io/VMwareVSphereDriverControllerServiceController": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')
```
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 1, 2024

@mpatlasov: This pull request references STOR-1767 which is a valid jira issue.

Details

In response to this:

openshift/vmware-vsphere-csi-driver-operator#233 will do allowOperatorRemovedState=True for vsphere csi operator. This will trigger finalazer check in library-go:

  if management.IsOperatorRemovable() {
  	if err := v1helpers.EnsureFinalizer(ctx, c.operatorClient, c.name); err != nil {

EnsureFinalizer(), in turn, calculates finalizer name either as os.Getenv("OPERATOR_NAME") or os.Args[0]. The latter doesn't work for vsphere because leading slash in /usr/bin/vmware-vsphere-csi-driver-operator is not allowed:

E0701 19:43:32.342151       1 base_controller.go:268] VMwareVSphereDriverControllerServiceController reconciliation failed: ClusterCSIDriver.operator.openshift.io "csi.vsphere.vmware.com" is invalid: metadata.finalizers: Invalid value: "/usr/bin/vmware-vsphere-csi-driver-operator.operator.openshift.io/VMwareVSphereDriverControllerServiceController": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2024
@openshift-ci openshift-ci bot requested review from RomanBednar and tsmetana July 1, 2024 20:50
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov

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 Jul 1, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 1, 2024

@mpatlasov: 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 c529a03 link false /test e2e-openstack
ci/prow/e2e-ibmcloud-csi c529a03 link false /test e2e-ibmcloud-csi

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.

@dobsonj
Copy link
Member

dobsonj commented Jul 2, 2024

/lgtm

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

/label docs-approved
/label px-approved

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels Jul 2, 2024
@mpatlasov
Copy link
Contributor Author

/label no-qe

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2024

@mpatlasov: The label(s) no-qe cannot be applied, because the repository doesn't have them.

Details

In response to this:

/label no-qe

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.

@duanwei33
Copy link

/label qe-approved

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

openshift-ci-robot commented Jul 3, 2024

@mpatlasov: This pull request references STOR-1767 which is a valid jira issue.

Details

In response to this:

openshift/vmware-vsphere-csi-driver-operator#233 will do allowOperatorRemovedState=True for vsphere csi operator. This will trigger finalazer check in library-go:

  if management.IsOperatorRemovable() {
  	if err := v1helpers.EnsureFinalizer(ctx, c.operatorClient, c.name); err != nil {

EnsureFinalizer(), in turn, calculates finalizer name either as os.Getenv("OPERATOR_NAME") or os.Args[0]. The latter doesn't work for vsphere because leading slash in /usr/bin/vmware-vsphere-csi-driver-operator is not allowed:

E0701 19:43:32.342151       1 base_controller.go:268] VMwareVSphereDriverControllerServiceController reconciliation failed: ClusterCSIDriver.operator.openshift.io "csi.vsphere.vmware.com" is invalid: metadata.finalizers: Invalid value: "/usr/bin/vmware-vsphere-csi-driver-operator.operator.openshift.io/VMwareVSphereDriverControllerServiceController": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')

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-merge-bot openshift-merge-bot bot merged commit 5c50083 into openshift:master Jul 3, 2024
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-storage-operator-container-v4.17.0-202407030818.p0.g5c50083.assembly.stream.el9 for distgit cluster-storage-operator.
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. docs-approved Signifies that Docs has signed off on this PR 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. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants