Bug 1678654
| Summary: | [marketplace] the default catalogsourceconfig and marketplace’s pod will be deleted automatically | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Fan Jia <jfan> |
| Component: | OLM | Assignee: | Aravindh Puthiyaparambil <aravindh> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fan Jia <jfan> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.1.0 | CC: | chezhang, dyan, jiazha, zitang |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.1.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: | 2019-02-20 21:04:17 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
Fan Jia
2019-02-19 10:27:30 UTC
(1. logs before the marketplace crash) The scenario here is the marketplace-operator pod crashed. There is nothing in the logs to indicate why this crash happened. (2.the logs for the first time reload of marketplace) Given that the marketplace-operator pod is part of a deployment, another instance is launched again. "User \"system:serviceaccount:openshift-marketplace:marketplace-operator\" cannot get resource \"customresourcedefinitions\" in API group \"apiextensions.k8s.io\" at the cluster scope" and "Failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:openshift-marketplace:marketplace-operator" cannot list resource "secrets" in API group "" in the namespace "openshift-marketplace" indicates that the "ClusterRole" or "ClusterRoleBindings" for the "marketplace-operator" have disappeared. One theory I have is that whatever entity that deleted "ClusterRole" or "ClusterRoleBinding", also deleted the Deployment. Then CVO recreated the Deployment first before recreating the "ClusterRole" or "ClusterRoleBinding" (3. the logs for the second time reload of marketplace) During this reload it looks like the "ClusterRole" or "ClusterRoleBinding" for the "marketplace-operator" has been created again, allowing it to successfully come up and recreate the resources required. So we need to figure out: 1. Why did the "marketplace-operator" crash in the first place? 2. Why did the "ClusterRole" or "ClusterRoleBindings" for the "marketplace-operator" disappear? As a side note, please be aware that the `CatalogSourceConfigs` and it child resources, associated with "OperatorSources" will be deleted and recreated to sync with Quay on very "marketplace-operator" restart. We plan to fix this bug soon but that is not related to this issue. All the resources (olm's packageserver, marketplace , all the pods) will remain stable after stopping the cluster-version-operator. The olm also has the same situation : lose resource like packageserver & serviceaccount ( https://bugzilla.redhat.com/show_bug.cgi?id=1678606 ) *** This bug has been marked as a duplicate of bug 1679309 *** |