Bug 1651901 - PVC not getting Bound using SC created as part of OCS ansible-deployment
Summary: PVC not getting Bound using SC created as part of OCS ansible-deployment
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: CNS-deployment
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Michael Adam
QA Contact: Ashmitha Ambastha
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-21 07:12 UTC by Ashmitha Ambastha
Modified: 2019-03-19 07:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-03-19 07:22:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ashmitha Ambastha 2018-11-21 07:12:38 UTC
Description of problem:
After deploying OCP 3.11 and OCS 3.11.1 successfully, the PVC created with the storage class that got created as part of the ansible deployment, glusterfs-storage, is not getting Bound.

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

How reproducible: Always

Steps to Reproduce:
1. Successfully deploy OCP 3.11 and OCS 3.11.1 (latest available builds).
2. Check for storage classes that get created via the ansible deployment.
# oc get sc
NAME                       PROVISIONER                AGE
glusterfs-registry-block   gluster.org/glusterblock   1d
glusterfs-storage          kubernetes.io/glusterfs    1d
3. Try creating a pvc using the storage class glusterfs-storage. The pvc created is not getting Bound. 

Actual results: The pvc is not getting Bound. 

Expected results: The pvc should get Bound.

Comment 3 Humble Chirammal 2018-11-21 12:43:45 UTC
Check heketi pod status and curl command output of heketi service  from master.

Comment 8 Ashmitha Ambastha 2019-03-19 07:22:04 UTC

We've have tried this as part of OCS 3.11.2 testing efforts and the issue mentioned is not seen. Closing this bug.

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