[release-4.19] OCPBUGS-61476: UPSTREAM: 961: fix: enable to use secrets with special characters

[openshift-cherrypick-robot]

This is an automated cherry-pick of #30

/assign mpatlasov

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-61374 has been cloned as Jira Issue OCPBUGS-61476. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-61476: UPSTREAM: 961: fix: enable to use secrets with special characters

In response to this:

This is an automated cherry-pick of #30

/assign mpatlasov

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61476, which is invalid:

• expected dependent Jira Issue OCPBUGS-61374 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #30

/assign mpatlasov

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-cherrypick-robot: all tests passed!

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.

[mpatlasov]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov, openshift-cherrypick-robot

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:

• OWNERS [mpatlasov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mpatlasov]

/jira refresh

[openshift-ci-robot]

@mpatlasov: This pull request references Jira Issue OCPBUGS-61476, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-61374 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-61374 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), 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 openshift-eng/jira-lifecycle-plugin repository.

[mpatlasov]

/label backport-risk-assessed

[Phaow]

/verified by @Phaow
Pre verify passed with self build operator bundle and index with this driver fix commit.

Follow the reproducer step use a special password "foo,bar" for the smb server and create pod and consume the smb csi pvc, I could the pod running well mount succeed.

$ oc get po,pvc
NAME        READY   STATUS    RESTARTS   AGE
pod/mypod   1/1     Running   0          19s

NAME                          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
persistentvolumeclaim/mypvc   Bound    pvc-495cabd8-21e6-4650-ab4d-24978b5a5b8c   10Gi       RWO            samba          <unset>

[openshift-ci-robot]

@Phaow: This PR has been marked as verified by @Phaow.

In response to this:

/verified by @Phaow
Pre verify passed with self build operator bundle and index with this driver fix commit.

Follow the reproducer step use a special password "foo,bar" for the smb server and create pod and consume the smb csi pvc, I could the pod running well mount succeed.

$ oc get po,pvc
NAME        READY   STATUS    RESTARTS   AGE
pod/mypod   1/1     Running   0          19s

NAME                          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
persistentvolumeclaim/mypvc   Bound    pvc-495cabd8-21e6-4650-ab4d-24978b5a5b8c   10Gi       RWO            samba          <unset>

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-cherrypick-robot: Jira Issue OCPBUGS-61476: All pull requests linked via external trackers have merged:

• openshift/csi-driver-smb#31

All linked pull requests have the verified tag. Jira Issue OCPBUGS-61476 has been moved to the VERIFIED state.

In response to this:

This is an automated cherry-pick of #30

/assign mpatlasov

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.

[mpatlasov]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@mpatlasov: new pull request created: #32

In response to this:

/cherry-pick release-4.18

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.