Bug 1609716
Summary: | etcd operator can't be deleted | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ge liu <geliu> |
Component: | Etcd | Assignee: | Sebastien Pahl <spahl> |
Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | dma, ecordell |
Target Milestone: | --- | ||
Target Release: | 3.11.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: | 2018-10-11 07:22:47 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
ge liu
2018-07-30 08:52:03 UTC
The etcd operator should not be deleted when the subscription is deleted. Deleting the etcd subscription is telling OLM "stop updating the etcd operator". To actually delete the etcd operator you can remove the ClusterServiceVersion for the etcd operator that was created by OLM due to the subscription. The etcd operator deployment has ownerreferences pointing to the ClusterServiceVersion and should be GC'd by openshift shortly after deleting the etcdoperator ClusterServiceVersion. @ecordell, yes, thanks for your kindly explanation, and I suppose these points will be recorded in doc later, because customer will puzzled about it also. and I tried to delete etcd-operator ClusterServiceVersion by command line, then the etcd operator pod really be deleted right now, but I tried to do this operation on admin console ui, it looks like there is not DELETE action in: Operators-->Cluster Service Versions-->Open Cloud Services-->etcd, there is only one action:Edit application Definition, I tried to delete etcd subscription successfully, but the etcd ClusterServiceVersion still exist, so is it a UI bug? 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-2018:2652 |