Description of problem: if we use local storage for ES storage folowing [1], the hostpath [2] will be added to deploymentconfig. For the upgrade playbook remove the hostpath , the user has to add it back mannuly. that is an extend request as https://bugzilla.redhat.com/show_bug.cgi?id=1478771 to persist ES storage configuration in deploymentconfig Version-Release number of the following components: openshift-ansible How reproducible: always Steps to Reproduce: 1. use local storage for ES storage following [1]. and save the deploymentconfig file oc get dc logging-es-data-master-xxxxx1 -o yaml > config.save1 2. upgrade logging and save the deploymentconfig file oc get dc logging-es-data-master-xxxxx2 -o yaml > config.save2 3. diff config.save1 config.save2 Actual results: The hostPath[2] are deleted. Expected results: The storage configure values are perserved. Additional info: [1]https://docs.openshift.com/container-platform/3.5/install_config/aggregate_logging.html-> Persistent Elasticsearch Storage. [2]- hostPath: path: /usr/local/es-storage name: elasticsearch-storage
@Eric, The work you did to preserve settings from DC's, does that include storage? I thought we had logic to preserve host storage
Do you have specific source and target version for us to investigate?
https://github.com/openshift/openshift-ansible/pull/6895
Verified and pass with openshift-ansible-3.9.0-0.41.0.git.0.8290c01.el7.noarch
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:0489