Bug 1921556
| Summary: | [OCS with Vault]: OCS pods didn't comeup after deploying with Vault details from UI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | shylesh <shmohan> |
| Component: | Console Storage Plugin | Assignee: | gowtham <gshanmug> |
| Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.7 | CC: | anbehl, aos-bugs, ebenahar, jefbrown, madam, nberry, nthomas, ocs-bugs, oviner, rgeorge, shan |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.7.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:57:05 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: | |||
|
Comment 2
gowtham
2021-02-01 04:24:27 UTC
The existing UI is creating secrets for certificates with the following key names: for ocs-kms-client-key -> tls.key for ocs-kms-client-cert-> tls.cert for ocs-kms-ca-secret -> ca.cert But rook expecting: for ocs-kms-client-key -> key for ocs-kms-client-cert-> cert for ocs-kms-ca-secret -> cert I'd say that the UI team used something that existed and was different from Rook. I have been pointing to our Rook doc several times: https://rook.io/docs/rook/v1.5/ceph-cluster-crd.html#vault-kms and it's pretty clear what needs to be done, as stated in the doc: Each secret keys are expected to be: VAULT_CACERT: cert VAULT_CLIENT_CERT: cert VAULT_CLIENT_KEY: key Anyway, it's a small fix. I dont know where the miscommunication happened is happened in UI, But yes it is a small fix. PR: https://github.com/openshift/console/pull/8008 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 Same issue: Procedure: 1.Install OCS via UI 2.Configure KMS Settings: Service Name: vault IP: https://vault.qe.rh-ocs.com PORT:8200 TOKEN:*** advanced settings: CA Certificate: fullchain.pem Client Certificate: cert.pem Client Private Key: privkey.pem 3.Check OSD pods status OSD PODs status is Error $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk error: a container name must be specified for pod rook-ceph-osd-0-5d459565bd-zq7qk, choose one of: [osd log-collector] or one of the init containers: [blkdevmapper encryption-kms-get-kek encryption-open blkdevmapper-encryption encrypted-block-status expand-encrypted-bluefs activate expand-bluefs chown-container-data-dir] $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk -c encryption-kms-get-kek curl: (60) SSL certificate problem: unable to get issuer certificate More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. (In reply to Oded from comment #14) > Same issue: > > Procedure: > 1.Install OCS via UI > 2.Configure KMS Settings: > Service Name: vault > IP: https://vault.qe.rh-ocs.com > PORT:8200 > TOKEN:*** > > advanced settings: > CA Certificate: fullchain.pem > Client Certificate: cert.pem > Client Private Key: privkey.pem > > 3.Check OSD pods status > OSD PODs status is Error > > $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk > error: a container name must be specified for pod > rook-ceph-osd-0-5d459565bd-zq7qk, choose one of: [osd log-collector] or one > of the init containers: [blkdevmapper encryption-kms-get-kek encryption-open > blkdevmapper-encryption encrypted-block-status expand-encrypted-bluefs > activate expand-bluefs chown-container-data-dir] > > > $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk -c encryption-kms-get-kek > curl: (60) SSL certificate problem: unable to get issuer certificate > More details here: https://curl.haxx.se/docs/sslcerts.html > > curl failed to verify the legitimacy of the server and therefore could not > establish a secure connection to it. To learn more about this situation and > how to fix it, please visit the web page mentioned above. https://bugzilla.redhat.com/show_bug.cgi?id=1931839 (In reply to Oded from comment #14) > Same issue: > > Procedure: > 1.Install OCS via UI > 2.Configure KMS Settings: > Service Name: vault > IP: https://vault.qe.rh-ocs.com > PORT:8200 > TOKEN:*** > > advanced settings: > CA Certificate: fullchain.pem > Client Certificate: cert.pem > Client Private Key: privkey.pem > > 3.Check OSD pods status > OSD PODs status is Error > > $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk > error: a container name must be specified for pod > rook-ceph-osd-0-5d459565bd-zq7qk, choose one of: [osd log-collector] or one > of the init containers: [blkdevmapper encryption-kms-get-kek encryption-open > blkdevmapper-encryption encrypted-block-status expand-encrypted-bluefs > activate expand-bluefs chown-container-data-dir] > > > $ oc logs rook-ceph-osd-0-5d459565bd-zq7qk -c encryption-kms-get-kek > curl: (60) SSL certificate problem: unable to get issuer certificate > More details here: https://curl.haxx.se/docs/sslcerts.html > > curl failed to verify the legitimacy of the server and therefore could not > establish a secure connection to it. To learn more about this situation and > how to fix it, please visit the web page mentioned above. https://bugzilla.redhat.com/show_bug.cgi?id=1931839 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |