OCPBUGS-70304: Fix azure-file secret namespace/name

[jsafrane]

--cloud-config-secret-name="" in a yaml file sets the Secret name to a string with two double quote characters. We need the name to be an empty string.

Similarly, fix the secret namespace.

@openshift/storage

[openshift-ci-robot]

@jsafrane: This pull request references Jira Issue OCPBUGS-70304, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

--cloud-config-secret-name="" in a yaml file sets the Secret name to a string with two double quote characters. We need the name to be an empty string.

Similarly, fix the secret namespace.

@openshift/storage

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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:

• OWNERS [jsafrane]

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

[dfajmon]

/lgtm

[duanwei33]

/unassign @Phaow @chao007 @radeore

[jsafrane]

The driver now logs, which is what we want:

I0126 14:55:39.438430 1 azure.go:103] reading cloud config from secret /

[mpatlasov]

/override ci/prow/hypershift-e2e-aks
The test fails with:

*v1beta1.HostedCluster: client rate limiter Wait returned an error: context deadline exceeded

the same way as NOOP #487 (compare here vs. there). This test does not give us any signals about quality of PR.

[openshift-ci]

@mpatlasov: Overrode contexts on behalf of mpatlasov: ci/prow/hypershift-e2e-aks

Details

In response to this:

/override ci/prow/hypershift-e2e-aks
The test fails with:

*v1beta1.HostedCluster: client rate limiter Wait returned an error: context deadline exceeded

the same way as NOOP #487 (compare here vs. there). This test does not give us any signals about quality of PR.

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.

[mpatlasov]

/test e2e-azure

[duanwei33]

See multi-PR test result:
openshift/azure-file-csi-driver#114 (comment)

/verified by @duanwei33

[openshift-ci-robot]

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

Details

In response to this:

See multi-PR test result:
openshift/azure-file-csi-driver#114 (comment)

/verified by @duanwei33

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]

/retest-required

Remaining retests: 0 against base HEAD 06f7672 and 2 for PR HEAD b9a38a8 in total

[openshift-ci]

@jsafrane: all tests passed!

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-ci-robot]

@jsafrane: Jira Issue Verification Checks: Jira Issue OCPBUGS-70304
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-70304 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

--cloud-config-secret-name="" in a yaml file sets the Secret name to a string with two double quote characters. We need the name to be an empty string.

Similarly, fix the secret namespace.

@openshift/storage

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-robot]

Fix included in accepted release 4.22.0-0.nightly-2026-01-28-225830