Bug 1837210
| Summary: | [manila-csi-driver-operator] manila csi driver install failed for manila csi driver operator is not installed in manila-csi namespace | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Storage | Assignee: | Mike Fedosin <mfedosin> |
| Status: | CLOSED ERRATA | QA Contact: | Wei Duan <wduan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5 | CC: | aos-bugs, egarcia, jsafrane, mfedosin, wduan |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:39:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1832661, 1839984 | ||
| Bug Blocks: | |||
Verified pass with images in https://errata.devel.redhat.com/advisory/54130. [wduan@MINT verification-tests]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-06-10-201008 True False 23h Cluster version is 4.5.0-0.nightly-2020-06-10-201008 Manila operator installed in "openshift-manila-csi-driver-operator" and all the driver's components installed in "openshift-manila-csi-driver". For manila operator, only "all-namespaces" support as "Installation Mode" and "openshift-manila-csi-driver-operator" is recommended namespace. For ManilaDriver instance, all driver's components installation is only allowed in "openshift-manila-csi-driver" namespace. Mike, could you help confirm above? Thanks. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: manila csi driver install failed for manila csi driver operator did not installed in manila-csi namespace Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-17-235851 "Operator Version: 0.0.1" How reproducible: Always Steps to Reproduce: 1. Login into the webconsole 2. Install csi-driver-manila-operator from operator hub into manila-csi-1 namespace 3. Create manilacsi instance to install manila csi driver Actual results: 1. No driver is installed. 2. cluster operator cloud-crendtial is in degraded status. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-17-235851 True False 24h Error while reconciling 4.5.0-0.nightly-2020-05-17-235851: the cluster operator cloud-credential is degraded check the operator log, we can see: {"level":"info","ts":1589863185.4884112,"logger":"controller_manilacsi","msg":"No installer-cloud-credentials secret was found in manila-csi namespace. Retrying...","Request.Namespace":"manila-csi-1","Request.Name":"manilacsi-1"} When create manila-csi namespace manually, the installer-cloud-credentials secret in created in manila-csi namespace, the operator still report can not find this secret. Expected results: Install manila csi driver successfully. 1. If we want the manila csi driver operator must be installed in manila-csi namespace, then when we insall the operator in other namespace, the operator installation should be failed and report clear err msg. 2. If we can install manila csi driver operator in any namespace, the operotor should create manila-csi namespace if the namespace is not exist and ensure the manali csi driver is installed in manila-csi namespace sucessfully. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: