Description of problem: Logging stacks' upgrade from 3.4.1 to 3.5.0 failed when replacing curator dc, the ansible log: failed: [host-8-174-59.host.centralci.eng.rdu2.redhat.com] (item=logging-curator) => { "failed": true, "invocation": { "module_args": { "debug": false, "kind": "dc", "kubeconfig": "/etc/origin/master/admin.kubeconfig", "name": "logging-curator", "namespace": "logging", "replicas": 0, "state": "present" }, "module_name": "oc_scale" }, "object": "logging-curator" } MSG: {u'cmd': u'/usr/bin/oc replace -f /tmp/logging-curator-Gy41SY -n logging', u'returncode': 1, u'results': {}, u'stderr': u'Error from server (Conflict): error when replacing "/tmp/logging-curator-Gy41SY": Operation cannot be fulfilled on deploymentconfigs "logging-curator": the object has been modified; please apply your changes to the latest version and try again\n', u'stdout': u''} RUNNING HANDLER [openshift_logging : restart master] *************************** to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/openshift_logging.retry PLAY RECAP ********************************************************************* host-8-174-59.host.centralci.eng.rdu2.redhat.com : ok=254 changed=52 unreachable=0 failed=1 Version-Release number of selected component (if applicable): openshift-ansible-3.5.41-1.git.0.e33897c.el7.noarch How reproducible: Always Steps to Reproduce: 1. Install logging 3.4.1 stacks on a OCP 3.5.0 master, attach elasticsearch with the HostPath PV 2. Visit kibana route before upgrade 3. Upgrade logging stacks to 3.5.0 by using ansible scripts (inventory file attached) Actual results: 2. Kibana route accessible with log entries 3. Ansible script failed when relacing curator dc Expected results: 3. Should upgrade successfully Additional info:
Issue was reproduced with the latest playbooks from https://github.com/openshift/openshift-ansible -b release-1.5 head commit: e33897ca1d71a7c5817c9cff5ce6cdb632d63ddd
I'm removing keyword "regression" since confirmed with my colleague that it hadn't been tested upgrading from 3.4.1 to 3.5.0 with hostPathPV attached, so this may not really be a regression.
*** This bug has been marked as a duplicate of bug 1435144 ***