Cause: We weren't preserving the storage type for ES dcs when upgrading/rerunning
Consequence: The existing storage type would be overwritten.
Fix: We now use preserve the storage type as a default (will use an inventory variable if specified).
Result: We see the configured storage values preserved when not specifying a storage type during upgrade.
Description of problem:
if we use local storage for ES storage folowing , the hostpath  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:
Steps to Reproduce:
1. use local storage for ES storage following . 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
The hostPath are deleted.
The storage configure values are perserved.
https://docs.openshift.com/container-platform/3.5/install_config/aggregate_logging.html-> Persistent Elasticsearch Storage.
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?
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.