Bug 1768820
| Summary: | Projects get stuck in Terminating status with "object *v1beta1.ServiceBindingList does not implement the protobuf marshalling interface and cannot be encoded to a protobuf message ..." | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | Service Catalog | Assignee: | Fabian von Feilitzsch <fabian> |
| Status: | CLOSED ERRATA | QA Contact: | Fan Jia <jfan> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.3.0 | CC: | aos-bugs, bandrade, chuo, fabian, jesusr, jfan, lxia, mfojtik, piqin, tbuskey, xjiang |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.3.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-01-23 11:10:52 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: | |||
|
Description
Jian Zhang
2019-11-05 10:15:18 UTC
Take the project "qitang3" for example:
oc get project qitang3 -o yaml # shows below ContentDeletionFailed message about service catalog objects
apiVersion: project.openshift.io/v1
kind: Project
metadata:
annotations:
openshift.io/description: ""
openshift.io/display-name: ""
openshift.io/requester: system:admin
openshift.io/sa.scc.mcs: s0:c29,c9
openshift.io/sa.scc.supplemental-groups: 1000830000/10000
openshift.io/sa.scc.uid-range: 1000830000/10000
creationTimestamp: "2019-11-05T07:32:23Z"
deletionTimestamp: "2019-11-05T07:32:36Z"
name: qitang3
resourceVersion: "582633"
selfLink: /apis/project.openshift.io/v1/projects/qitang3
uid: 0896cf23-332c-43a6-8bd5-cfedc2615e68
spec:
finalizers:
- kubernetes
status:
conditions:
- lastTransitionTime: "2019-11-05T07:38:12Z"
message: All resources successfully discovered
reason: ResourcesDiscovered
status: "False"
type: NamespaceDeletionDiscoveryFailure
- lastTransitionTime: "2019-11-05T07:32:43Z"
message: All legacy kube types successfully parsed
reason: ParsedGroupVersions
status: "False"
type: NamespaceDeletionGroupVersionParsingFailure
- lastTransitionTime: "2019-11-05T07:38:12Z"
message: 'Failed to delete all resource types, 5 remaining: object *v1beta1.ServiceBindingList
does not implement the protobuf marshalling interface and cannot be encoded
to a protobuf message, object *v1beta1.ServiceBrokerList does not implement
the protobuf marshalling interface and cannot be encoded to a protobuf message,
object *v1beta1.ServiceClassList does not implement the protobuf marshalling
interface and cannot be encoded to a protobuf message, object *v1beta1.ServiceInstanceList
does not implement the protobuf marshalling interface and cannot be encoded
to a protobuf message, object *v1beta1.ServicePlanList does not implement the
protobuf marshalling interface and cannot be encoded to a protobuf message'
reason: ContentDeletionFailed
status: "True"
type: NamespaceDeletionContentFailure
- lastTransitionTime: "2019-11-05T07:32:43Z"
message: All content successfully removed
reason: ContentRemoved
status: "False"
type: NamespaceContentRemaining
- lastTransitionTime: "2019-11-05T07:32:43Z"
message: All content-preserving finalizers finished
reason: ContentHasNoFinalizers
status: "False"
type: NamespaceFinalizersRemaining
phase: Terminating
Can you please give me a bit more information? The original comment reproducer simply states to create a namespace then delete it. Comment #2 seems to indicate that the Service Catalog has been enabled explicitly because by default it is not enabled. How was the environment deployed? Are these service catalog deployed projects or not? Jesus, Yes, ServiceCatalog was enabled manually. And, the ASB was deployed. Hit this issue too.
At the same time, found the service-catalog-apiserver clusteroperator is not in the correct status.
$ oc describe co service-catalog-apiserver
Name: service-catalog-apiserver
Namespace:
Labels: <none>
Annotations: <none>
API Version: config.openshift.io/v1
Kind: ClusterOperator
Metadata:
Creation Timestamp: 2019-11-13T02:28:44Z
Generation: 1
Resource Version: 221379
Self Link: /apis/config.openshift.io/v1/clusteroperators/service-catalog-apiserver
UID: efb57472-70de-4e7f-bcc8-c10ddddf21e7
Spec:
Status:
Conditions:
Last Transition Time: 2019-11-13T02:28:46Z
Reason: AsExpected
Status: False
Type: Degraded
Last Transition Time: 2019-11-13T02:47:18Z
Reason: AsExpected
Status: False
Type: Progressing
Last Transition Time: 2019-11-13T11:40:03Z
Message: Available: v1beta1.servicecatalog.k8s.io is not ready: 503
Reason: Available
Status: False
Type: Available
Last Transition Time: 2019-11-13T02:46:42Z
Reason: AsExpected
Status: True
Type: Upgradeable
Extension: <nil>
Related Objects:
Group:
Name: openshift-config
Resource: namespaces
Group:
Name: openshift-config-managed
Resource: namespaces
Group:
Name: openshift-service-catalog-apiserver-operator
Resource: namespaces
Group:
Name: openshift-service-catalog-apiserver
Resource: namespaces
Group: apiregistration.k8s.io
Name: v1beta1.servicecatalog.k8s.io
Resource: apiservices
Versions:
Name: operator
Version: 4.3.0-0.nightly-2019-11-12-185229
Name: service-catalog-apiserver
Version:
Events: <none>
The latest nightly build doesn't include the fix pr, will test when the nightly build is ready. test env: cv:4.3.0-0.nightly-2019-11-24-183610 test result: 1. oc new-project kaka 2. enable service-catalog-apiserver & service-catalog-controller-manager 3. oc delete ns kaka ns "kaka" is deleted successfully. 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:0062 |