Bug 1478261 - Unable to mount gluster volumes to jboss pods
Unable to mount gluster volumes to jboss pods
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: kubernetes (Show other bugs)
3.0
Unspecified Unspecified
urgent Severity urgent
: ---
: ---
Assigned To: Humble Chirammal
Anoop
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-04 02:53 EDT by Jaspreet Kaur
Modified: 2017-08-07 02:51 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jaspreet Kaur 2017-08-04 02:53:49 EDT
Description of problem: when trying to mount gluster volumes to jboss pods it always fails to mount.

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

How reproducible: Followed link :

https://docs.openshift.com/container-platform/3.5/install_config/persistent_storage/persistent_storage_glusterfs.html

When using a pod.yaml to use the pvc directly it works however when trying to create jboss/jbpm pods with mysql templates it fails everytime.

 cat gluster-pv.yaml 
apiVersion: "v1"
kind: "PersistentVolume"
metadata:
  name: "gluster-default-volume"
spec:
  capacity:
    storage: "1Gi"
  accessModes:
    - "ReadWriteOnce"
  glusterfs:
    endpoints: "glusterfs-cluster"
    path: "jbpm"
    readOnly: false
  persistentVolumeReclaimPolicy: "Retain"


gluster volume info
 
Volume Name: jbpm
Type: Replicate
Volume ID: b2594a58-482c-4396-bb8e-4c628068e073
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: glu01:/brick04/b4
Brick2: glu02:/brick04/b4
Brick3: glu03:/brick04/b4
Options Reconfigured:
transport.address-family: inet
performance.readdir-ahead: on
nfs.disable: on





Tried to set glustervolume security but it fails. Below errors are seen :

  3m		3m		1	{default-scheduler }						Normal		Scheduled	Successfully assigned kie-app-mysql-10-6gnpt to vm253-38.gsslab.pnq2.redhat.com
  1m		1m		1	{kubelet vm253-38.gsslab.pnq2.redhat.com}			Warning		FailedMount	Unable to mount volumes for pod "kie-app-mysql-10-6gnpt_jbpm(44a3e3fd-7905-11e7-82df-001a4a1601e4)": timeout expired waiting for volumes to attach/mount for pod "jbpm"/"kie-app-mysql-10-6gnpt". list of unattached/unmounted volumes=[kie-app-mysql-pvol]
  1m		1m		1	{kubelet vm253-38.gsslab.pnq2.redhat.com}			Warning		FailedSync	Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "jbpm"/"kie-app-mysql-10-6gnpt". list of unattached/unmounted volumes=[kie-app-mysql-pvol]


Actual results: Fails each time to mount volumes.


Expected results: It should suceed without any manual interventions.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Note You need to log in before you can comment on or make changes to this bug.