Skip to content
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.

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

OCPBUGS-22443: manila: Add missing CSI_FSGROUP_POLICY env var #412

Closed
wants to merge 1 commit into from

Conversation

stephenfin
Copy link

This was mistakenly introduced to the wrong set of manifests in a previous change to the Manila CSI Driver Operator [1]. Correct this mistake.

/cc @fmount

[1] openshift/csi-driver-manila-operator@660bbb7

Signed-off-by: Stephen Finucane stephenfin@redhat.com

This was mistakenly introduced to the wrong set of manifests in a
previous change to the Manila CSI Driver Operator [1]. Correct this
mistake.

[1] openshift/csi-driver-manila-operator@660bbb7

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Cc: Francesco Pantano <fpantano@redhat.com>
@openshift-ci-robot openshift-ci-robot added 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 Oct 26, 2023
@openshift-ci-robot
Copy link
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-22443, which is invalid:

  • expected the bug to target the "4.15.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.

In response to this:

This was mistakenly introduced to the wrong set of manifests in a previous change to the Manila CSI Driver Operator [1]. Correct this mistake.

/cc @fmount

[1] openshift/csi-driver-manila-operator@660bbb7

Signed-off-by: Stephen Finucane stephenfin@redhat.com

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/test-infra repository.

@openshift-ci openshift-ci bot requested a review from fmount October 26, 2023 16:59
@stephenfin
Copy link
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 26, 2023
@openshift-ci-robot
Copy link
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-22443, 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.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request.

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 kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 26, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 26, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stephenfin
Once this PR has been reviewed and has the lgtm label, please assign mpatlasov for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 26, 2023

@stephenfin: 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-ibmcloud-csi da9bf5a link false /test e2e-ibmcloud-csi

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/test-infra repository. I understand the commands that are listed here.

@jsafrane
Copy link
Contributor

@stephenfin in openshift/csi-driver-manila-operator#142 (comment) @gouthampacha it's for development and testing only. Is it now intended for cluster admins? You will need some API for that.

/hold

@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 Oct 27, 2023
@gouthampacha
Copy link

openshift/csi-driver-manila-operator#142 (comment)

still useful only for developers/testing @jsafrane @stephenfin

@jsafrane
Copy link
Contributor

jsafrane commented Nov 7, 2023

The operator already uses a good default when it's not set. I think it makes very little sense to set the env. variable to the default value here.

I am still not sure what do you want. You already have a quick & dirty env. variable for any testing you may need. If you want it usable by cluster admins, then please add a real Manila-specific API field to ClusterCSIDriver object - it already allows for driver specific configurations.

@stephenfin
Copy link
Author

tbc, I only added this because I wanted to remove the misleading assets from the Manila CSI Driver Operator. This is the sole addition on that side that is not reflected here, but from what I'm hearing we don't need/want this particular change here. If so, should I just abandon this and proceed with the removal of manifests from manila-csi-driver-operator?

@jsafrane
Copy link
Contributor

jsafrane commented Nov 7, 2023

Yeah, I think this PR does not really belong here. And removing manifests from manila-csi-driver-operator is a good thing to do.

@stephenfin stephenfin closed this Nov 7, 2023
@openshift-ci-robot
Copy link
Contributor

@stephenfin: This pull request references Jira Issue OCPBUGS-22443. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

This was mistakenly introduced to the wrong set of manifests in a previous change to the Manila CSI Driver Operator [1]. Correct this mistake.

/cc @fmount

[1] openshift/csi-driver-manila-operator@660bbb7

Signed-off-by: Stephen Finucane stephenfin@redhat.com

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants