Bug 1466620
Summary: | logging services were not deleted after undeploying logging via ansible | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.6.0 | CC: | aos-bugs, nhosoi, rmeggins |
Target Milestone: | --- | ||
Target Release: | 3.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-25 13:02:19 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
Junqi Zhao
2017-06-30 05:21:30 UTC
@Janqi, Sorry for my ignorance... Could you put the command line(s?) for this step? 1. Undeploy logging 3.6.0. Thanks! (In reply to Noriko Hosoi from comment #1) > @Janqi, Sorry for my ignorance... Could you put the command line(s?) for > this step? > 1. Undeploy logging 3.6.0. > Thanks! Use the inventory file in Comment 0 to undeploy logging, openshift_logging_install_logging=false means to undeploy logging # cd /usr/share/ansible/openshift-ansible/ # ansible-playbook -vvv -i ${INVENTORY_FILE} playbooks/byo/openshift-cluster/openshift-logging.yml Using code from HEAD on master of openshift-ansible unable to reproduce. Issue is fixed, logging services are deleted after undeploying logging via ansible. Testing environment: # openshift version openshift v3.6.173.0.19 kubernetes v1.6.1+5115d708d7 etcd 3.2.1 Logging images: logging-kibana:v3.6.173.0.19-1 logging-elasticsearch:v3.6.173.0.19-1 logging-fluentd:v3.6.173.0.19-1 logging-auth-proxy:v3.6.173.0.19-1 logging-curator:v3.6.173.0.19-1 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-2017:3049 |