Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1466703

Summary: [trello nEOGoTet] Not able to deploy logging with dynamic pv + ops cluster enabled
Product: OpenShift Container Platform Reporter: Xia Zhao <xiazhao>
Component: InstallerAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Xia Zhao <xiazhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
This bug was introduced with refactoring changes made for 3.6; fixing it prevents a regression.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-10 05:29:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the inventory file when dynamic pv + ops cluster enabled --> the failed deployment
none
ansible execution log
none
the inventory file when dynamic pv + ops cluster disabled --> the succeeded deployment none

Description Xia Zhao 2017-06-30 09:43:55 UTC
Created attachment 1293172 [details]
the inventory file when dynamic pv + ops cluster enabled --> the failed deployment

Description of problem:
Not able to deploy logging with dynamic pv + ops cluster enabled, meet this error: 

MSG:
{u'returncode': 1, u'cmd': u'/usr/bin/oc replace -f /tmp/openshift-logging-ansible-aLJDxB/templates/logging-es-pvc.yml -n logging', u'results': {}, u'stderr': u'The PersistentVolumeClaim "logging-es-0" is invalid: spec: Forbidden: field is immutable after creation\n', u'stdout': u''}

The correcponding deployment with dynamic pv + ops cluster DISABLED can be successful on the same env.


Version-Release number of selected component (if applicable):
openshift-ansible-playbooks-3.6.126.4-1.git.0.d25d828.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging with the attached inventory file (dynamic pv + ops cluster enabled)

Actual results:
deployment failed

Expected results:
deployment should succeed

Additional info:
full ansible execution log attached
both the inventory file attached:
dynamic pv + ops cluster enabled --> the failed deployment
dynamic pv + ops cluster disabled --> the succeeded deployment

Comment 1 Xia Zhao 2017-06-30 09:46:33 UTC
The error message seemed to be related with this trello card in 3.6:  https://trello.com/c/XbNceey9/154-make-pvc-storageclass-annotation-immutable

Storage team members told that they have a recent change in 3.6 to prevent patch update pvc annotations.

Comment 2 Xia Zhao 2017-06-30 09:57:03 UTC
Created attachment 1293178 [details]
ansible execution log

Comment 3 Xia Zhao 2017-06-30 09:57:42 UTC
Created attachment 1293179 [details]
the inventory file when dynamic pv + ops cluster disabled --> the succeeded deployment

Comment 4 Scott Dodson 2017-06-30 14:52:58 UTC
Already fixed in https://github.com/openshift/openshift-ansible/pull/4651

Comment 6 Xia Zhao 2017-07-05 06:41:57 UTC
Issue fixed well, logging deployment can succeed with this bug fix.

ansible version tested with:

# rpm -qa | grep ansible
openshift-ansible-callback-plugins-3.6.133-1.git.0.950bb48.el7.noarch
openshift-ansible-docs-3.6.133-1.git.0.950bb48.el7.noarch
openshift-ansible-lookup-plugins-3.6.133-1.git.0.950bb48.el7.noarch
openshift-ansible-filter-plugins-3.6.133-1.git.0.950bb48.el7.noarch
openshift-ansible-playbooks-3.6.133-1.git.0.950bb48.el7.noarch
ansible-2.2.3.0-1.el7.noarch
openshift-ansible-3.6.133-1.git.0.950bb48.el7.noarch
openshift-ansible-roles-3.6.133-1.git.0.950bb48.el7.noarch


$ oc describe $es_pod:
...
  elasticsearch-storage:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	logging-es-0
    ReadOnly:	false

Comment 8 errata-xmlrpc 2017-08-10 05:29:50 UTC
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/RHEA-2017:1716