Bug 1617939

Summary: [APB] mariadb-apb can not sync data to pv when using prod plan
Product: OpenShift Container Platform Reporter: Zihan Tang <zitang>
Component: Service BrokerAssignee: Jason Montleon <jmontleo>
Status: CLOSED ERRATA QA Contact: Zihan Tang <zitang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.10.0CC: aos-bugs, chezhang, jmontleo
Target Milestone: ---   
Target Release: 3.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-31 06:18:11 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:

Description Zihan Tang 2018-08-16 08:05:49 UTC 
Description of problem:
when provision mariadb-apb in prod plan, the data doesn't sync to pv.

This is copied from bug: https://bugzilla.redhat.com/show_bug.cgi?id=1593183#c40

Version-Release number of selected component (if applicable):


How reproducible:
aways

Steps to Reproduce:
1. build a docker runtime env
2. provision mariadb-apb in prod plan, it will succeed.
3. check data in mariardb pod
4. check data in pv node

Actual results:
step 4: 
# oc get pvc
NAME                                           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
mariadb-c21f54d8-9c82-11e8-a0ff-0a580a8000bb   Bound     pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417   1Gi        RWO            standard       13m

# oc get pod -o wide
NAME                                                   READY     STATUS    RESTARTS   AGE       IP            NODE                   NOMINATED NODE
mariadb-c21f54d8-9c82-11e8-a0ff-0a580a8000bb-2-pd648   1/1       Running   0          8m        10.129.0.67   qe-zitang-810-node-1   <none>

# ssh to the qe-zitang-810-node-1
go to pv mount file
# mount | grep pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417
/dev/vdb on /var/lib/origin/openshift.local.volumes/pods/7deef55a-9c83-11e8-bc1b-fa163eebd417/volumes/kubernetes.io~cinder/pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417 type xfs (rw,relatime,seclabel,attr2,inode64,noquota)

[root@qe-zitang-810-node-1 ~]# cd /var/lib/origin/openshift.local.volumes/pods/7deef55a-9c83-11e8-bc1b-fa163eebd417/volumes/kubernetes.io~cinder/pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417
[root@qe-zitang-810-node-1 pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417]# ll
total 0
drwxr-sr-x. 2 root       1000440000 6 8月  10 05:55 data
srwxrwxrwx. 1 1000440000 1000440000 0 8月  10 05:55 mysql.sock

[root@qe-zitang-810-node-1 pvc-e9cc5630-9c82-11e8-bc1b-fa163eebd417]# ll data
total 0

data not synced to pv.

Expected results:
data synced to pv.

Additional info:
if changing dc mountPath to '/var/lib/mysql/data', the data in mariadb pod can 
sync with pv
Comment 1 Jason Montleon 2018-08-16 14:59:22 UTC 
https://github.com/ansibleplaybookbundle/mariadb-apb/pull/45
Comment 3 Zihan Tang 2018-08-21 07:30:37 UTC 
PR is merged in mariadb-apb-role-1.2.6
the latest is mariadb-apb-role-1.2.5 in v3.10.28, so change it to MODIFIED.
Comment 4 Zihan Tang 2018-08-22 05:43:29 UTC 
image is ready ,change it to ON_QA
Comment 5 Zihan Tang 2018-08-22 05:50:07 UTC 
Verified.
image: v3.10.34, mariadb-apb-role-1.2.6-1
Comment 7 errata-xmlrpc 2018-08-31 06:18:11 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/RHBA-2018:2376