Description of problem: Deleting the clusterlogging CR removes the deployments for kibana and fluentd and terminates all pods. It also deletes the elasticsearch CR, but deleting the elasticsearch CR does not delete the elasticsearch-clientdatamaster Version-Release number of selected component (if applicable): Latest operators built by ART: registry.reg-aws.openshift.com:443/openshift/ose-cluster-logging-operator v4.0 d30f397c70ae 33 hours ago 273 MB registry.reg-aws.openshift.com:443/openshift/ose-elasticsearch-operator v4.0 b35c5b1efb46 33 hours ago 261 MB How reproducible: Always Steps to Reproduce: 1. Create an clusterlogging CR from the hack/cr.yaml 2. Verify ES, fluentd and kibana are running successfully 3. oc delete clusterlogging example Actual results: elasticsearches/elasticsearch CR is deleted, but the deployment and pod remain: [fedora@ip-172-31-53-199 ~]$ oc delete elasticsearch/elasticsearch clusterlogging/example elasticsearch.logging.openshift.io "elasticsearch" deleted clusterlogging.logging.openshift.io "example" deleted [fedora@ip-172-31-53-199 ~]$ oc get pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-959d488b8-vtlsq 1/1 Running 0 16h elasticsearch-clientdatamaster-0-1-d4ddc458f-lr67g 1/1 Running 0 16h elasticsearch-operator-566cf5bb5c-wnh75 1/1 Running 0 16h [fedora@ip-172-31-53-199 ~]$ oc get deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE cluster-logging-operator 1 1 1 1 16h elasticsearch-clientdatamaster-0-1 1 1 1 1 16h elasticsearch-operator 1 1 1 1 16h Expected results: All resources related to the clusterlogging CR are cleaned up upon deletion Additional info: Operator pod logs will be attached
Created attachment 1521516 [details] CLO and ES operator logs after CR deletion
https://github.com/openshift/elasticsearch-operator/pull/62
Verified with upstream - waiting for official OCP images.
Verified on 4.0.0-0.nightly-2019-02-11-045151. Deleting the clusterlogging cr cascades to the elasticsearch cr
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