Fix typo in YAML for 1-020_validate_redis_ha_nonha

[jgwest]

What type of PR is this?
/kind bug

What does this PR do / why we need it:

• Fix typo in YAML for 1-020_validate_redis_ha_nonha
• I somewhat suspect this is causing tests after it that depend on openshift-gitops namespace to break (e.g. 1-041_validate_argocd_sync_alert)

[jgwest]

/retest

[jgwest]

Cluster init error

level=info msg=Cluster operator insights SCAAvailable is False with Forbidden: Failed to pull SCA certs from https://api.openshift.com/api/accounts_mgmt/v1/certificates: OCM API https://api.openshift.com/api/accounts_mgmt/v1/certificates returned HTTP 403: {"code":"ACCT-MGMT-11","href":"/api/accounts_mgmt/v1/errors/11","id":"11","kind":"Error","operation_id":"feef97fd-3838-4d8f-ab70-844be11696d3","reason":"Account with ID 2DUeKzzTD9ngfsQ6YgkzdJn1jA4 denied access to perform create on Certificate with HTTP call POST /api/accounts_mgmt/v1/certificates"}
level=error msg=Cluster operator kube-controller-manager Degraded is True with MissingStaticPodController_SyncError::StaticPods_Error: MissingStaticPodControllerDegraded: static pod lifecycle failure - static pod: "kube-controller-manager" in namespace: "openshift-kube-controller-manager" for revision: 6 on node: "ip-10-0-144-217.us-west-2.compute.internal" didn't show up, waited: 3m0s
level=error msg=StaticPodsDegraded: pod/kube-controller-manager-ip-10-0-144-217.us-west-2.compute.internal container "cluster-policy-controller" is terminated: Completed: 
level=error msg=StaticPodsDegraded: pod/kube-controller-manager-ip-10-0-144-217.us-west-2.compute.internal container "kube-controller-manager" is terminated: Completed: 
level=error msg=StaticPodsDegraded: pod/kube-controller-manager-ip-10-0-144-217.us-west-2.compute.internal container "kube-controller-manager-cert-syncer" is terminated: Error: .ConfigMap: Get

/retest

[jgwest]

/retest

[chetan-rns]

Thanks @jgwest

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chetan-rns

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 [chetan-rns]

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