Bug 1357560

Summary:	Heketi-cli need to create PVs using Retain policy, not Recycle policy
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Luis Pabón <lpabon>
Component:	heketi	Assignee:	Luis Pabón <lpabon>
Status:	CLOSED ERRATA	QA Contact:	Neha <nerawat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	hchiramm, madam, mliyazud, nerawat, pprakash, rcyriac, sashinde, ssaha
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS Container Converged 1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 04:52:23 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:
Bug Depends On:
Bug Blocks:	1332128

Description Luis Pabón 2016-07-18 13:53:32 UTC

Description of problem:
Heketi-cli is currently using RECYCLE (see [1]).  I will create a bug to change it to RETAIN [2]

[1] https://github.com/heketi/heketi/blob/master/pkg/kubernetes/pv.go#L34
[2] https://github.com/kubernetes/kubernetes/blob/master/pkg/api/v1/types.go#L402

Comment 2 Luis Pabón 2016-07-18 14:00:57 UTC

https://github.com/heketi/heketi/issues/428

Comment 6 Neha 2016-07-25 12:48:39 UTC

PV json file with latest build:

 cat pv1.json 
{
  "kind": "PersistentVolume",
  "apiVersion": "v1",
  "metadata": {
    "name": "glusterfs-d2a1a246",
    "creationTimestamp": null
  },
  "spec": {
    "capacity": {
      "storage": "10Gi"
    },
    "glusterfs": {
      "endpoints": "glusterfs-cluster3",
      "path": "vol_d2a1a2468400d23d5ab1bf8cf9e371c5"
    },
    "accessModes": [
      "ReadWriteMany"
    ],
    "persistentVolumeReclaimPolicy": "Retain"
  },
  "status": {}
}


persistentVolumeReclaimPolicy is Retain. Moving it to verified.

Comment 8 errata-xmlrpc 2016-08-04 04:52:23 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://rhn.redhat.com/errata/RHBA-2016-1498.html