Bug 1405415 - Output of a PV created for a statically provisioned volume with a GID doesn't show the value of the allocated GID
Summary: Output of a PV created for a statically provisioned volume with a GID doesn't...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: cns-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michael Adam
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: OCS-3.11.1-devel-triage-done
TreeView+ depends on / blocked
 
Reported: 2016-12-16 13:08 UTC by Prasanth
Modified: 2019-04-15 22:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-15 22:41:17 UTC
Embargoed:

Attachments (Terms of Use)

Description Prasanth 2016-12-16 13:08:09 UTC 
Description of problem:

Output of a PV created for a statically provisioned volume with a GID doesn't show the value of the allocated GID

Version-Release number of selected component (if applicable):
heketi-client-3.1.0-5.el7rhgs.x86_64

How reproducible: Always


Steps to Reproduce:
1. heketi-cli volume create --size=100 --persistent-volume-file=pv001.json --gid=590
2. Analyse the PV file (pv001.json) created
3.

Actual results: It doesn't show the value of GID that has been set for that PV


Expected results: It should show the GID value as well for validation


Additional info: Let me know if you need more details on this BZ
Comment 1 Humble Chirammal 2016-12-16 13:13:18 UTC 
Can you paste #cat pv001.json file ?
Comment 2 Humble Chirammal 2016-12-16 13:15:13 UTC 
(In reply to Humble Chirammal from comment #1)
> Can you paste #cat pv001.json file ?

Also #oc describe pv ( after creating the PV)
Comment 3 Prasanth 2016-12-16 13:19:19 UTC 
(In reply to Humble Chirammal from comment #1)
> Can you paste #cat pv001.json file ?

# cat pv001.json
{
  "kind": "PersistentVolume",
  "apiVersion": "v1",
  "metadata": {
    "name": "glusterfs-8862b17b",
    "creationTimestamp": null
  },
  "spec": {
    "capacity": {
      "storage": "100Gi"
    },
    "glusterfs": {
      "endpoints": "glusterfs-cluster",
      "path": "vol_8862b17b46b482faf85bb1bdd78debdc"
    },
    "accessModes": [
      "ReadWriteMany"
    ],
    "persistentVolumeReclaimPolicy": "Retain"
  },
  "status": {}
}
Comment 4 Humble Chirammal 2016-12-23 06:53:01 UTC 
(In reply to Prasanth from comment #3)
> (In reply to Humble Chirammal from comment #1)
> > Can you paste #cat pv001.json file ?
> 
> # cat pv001.json
> {
>   "kind": "PersistentVolume",
>   "apiVersion": "v1",
>   "metadata": {
>     "name": "glusterfs-8862b17b",
>     "creationTimestamp": null
>   },
>   "spec": {
>     "capacity": {
>       "storage": "100Gi"
>     },
>     "glusterfs": {
>       "endpoints": "glusterfs-cluster",
>       "path": "vol_8862b17b46b482faf85bb1bdd78debdc"
>     },
>     "accessModes": [
>       "ReadWriteMany"
>     ],
>     "persistentVolumeReclaimPolicy": "Retain"
>   },
>   "status": {}
> }

Can you please provide the output requested in  c#2. I would like to double confirm something here.
Comment 5 Prasanth 2016-12-27 11:06:27 UTC 
(In reply to Humble Chirammal from comment #4)

> 
> Can you please provide the output requested in  c#2. I would like to double
> confirm something here.

I've scrapped the setup that I've used for testing this and so I don't have this output handy now. But I'll provide the requested info once I re-test the same in a new setup.
Comment 6 Humble Chirammal 2018-04-26 10:05:38 UTC 
(In reply to Prasanth from comment #5)
> (In reply to Humble Chirammal from comment #4)
> 
> > 
> > Can you please provide the output requested in  c#2. I would like to double
> > confirm something here.
> 
> I've scrapped the setup that I've used for testing this and so I don't have
> this output handy now. But I'll provide the requested info once I re-test
> the same in a new setup.

Prasanth, I dont think this is important to be fixed in CNS 3.10 release, I am moving this bug out of this release.
Note You need to log in before you can comment on or make changes to this bug.