Bug 1702876
| Summary: | Service Catalog api-server pod crashed at 'Unable to create storage backend' | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Zihan Tang <zitang> |
| Component: | Service Catalog | Assignee: | Dan Geoffroy <dageoffr> |
| Status: | CLOSED ERRATA | QA Contact: | Zihan Tang <zitang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | chezhang, chuo, deads, jiazha, juzhao |
| Target Milestone: | --- | Keywords: | Regression, TestBlocker |
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:48:02 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 1
David Eads
2019-04-25 11:46:20 UTC
From the timestamps alone alone I agree - looks like this build had the change on the etcd side but not the change within service catalog operator. I have an install from openshift-install-linux-4.1.0-0.ci-2019-04-24-094913 which had both changes and works properly. I just verified this works properly in openshift-install-linux-4.1.0-0.nightly-2019-04-25-043235. As David said above, looks like a "bad" build for Service Catalog in that core had a change moving etcd to a new namespace but the Service Catalog operator changes were no in the same build. Fixed by https://github.com/openshift/cluster-svcat-apiserver-operator/pull/49 Thanks David and Jay. @zitang, please help verify this issue, thanks! Verified. It works on 4.1.0-0.nightly-2019-04-25-121505 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-2019:0758 |