Description of problem: During 3.5 to 3.6 upgrade, playbook aborts with "field is immutable after creation" Version-Release number of selected component (if applicable): 3.6 How reproducible: 100% Steps to Reproduce: 1. ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-logging.yml 2. 3. Actual results: The PersistentVolumeClaim "logging-es-0" is invalid: \n* spec: Forbidden: field is immutable after creation\n* metadata.annotations.volume.beta.kubernetes.io/storage-class: Invalid value: "": field is immutable\n', u'stdout': u''} Expected results: Upgraded ELK stack Additional info: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/installation_and_configuration/#deploying-the-efk-stack Section 30.4 Workaround: oc delete pvc -n logging logging-es-0
@Eric haven't we seen this before recently?
Please verify per comment#2
I can reproduced with ose-ansible:v3.5. 1. Reproduce with ose-ansible:v3.5 MSG: {u'cmd': u'/usr/bin/oc replace -f /tmp/openshift-logging-ansible-jlyAPh/templates/logging-logging-es-0-pvc.yaml -n logging', u'returncode': 1, u'results': {}, u'stderr': u'The PersistentVolumeClaim "logging-es-0" is invalid: spec: Forbidden: field is immutable after creation\n', u'stdout': u''} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-logging.retry PLAY RECAP ******************************************************************************************************************************************************************************************************** localhost : ok=10 changed=0 unreachable=0 failed=0 openshift-208.lab.eng.nay.redhat.com : ok=1 changed=0 unreachable=0 failed=0 openshift-225.lab.eng.nay.redhat.com : ok=170 changed=18 unreachable=0 failed=1 2. No such issue with ose-ansible:3.6.173.0.30
To clarify https://bugzilla.redhat.com/show_bug.cgi?id=1485969#c3, should be addressed in https://access.redhat.com/errata/RHBA-2017:2639 Testing now...
Not seeing the issue in openshift-ansible-3.6.173.0.21-2.git.0.44a4038.el7 but the system is already upgraded
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