It seems we consider disabling the auto rollback to a "working" DC version when a rollout fails. We can do that by adding, "revisionHistoryLimit: 0" to all logging project DCs. The problem scenario is as follows: 1. DC version X depends on configmap "version" A 2. An upgrade is performed modifying the configmap to "version" B, and DC to version Y 3. Version of Y of the DC is rolled out, but fails for some reason 4. Because of the rollout failure, the DC rolls back to version X 5. Now DC version X fails because the corresponding configmap "version" A is no longer present
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/415fc54d7b44be4a1ee3cc63233c3bd8b031bdb2 bug 1519622. Disable rollback of ES DCs https://github.com/openshift/openshift-ansible/commit/7b4c6781a680175fa985edab92c73cb3fc662073 Merge pull request #6356 from jcantrill/1519622_disable_revision_history bug 1519622. Disable rollback of ES DCs
This fix is not merged to v3.7. and please move the bug to a installer errata too.
Please ignore comment 3, the fix is in openshift-ansible-3.7.22-1.git.0.a938a52.el7.noarch. The errata include both installer and package now.
The test is blocked by 1533313
Verified with openshift-ansible-3.7.23.
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:0113