Bug 1698463

Summary:	Volume creation should be successful if the pvc name is > 63 chars.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Humble Chirammal <hchiramm>
Component:	kubernetes	Assignee:	Humble Chirammal <hchiramm>
Status:	CLOSED ERRATA	QA Contact:	Aditya Ramteke <aramteke>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	asriram, jmulligan, knarra, rhs-bugs, rtalur
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 4
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, due to a limitation of glusterfs driver, an OpenShift developer/user was not able to create a persistent volume claim with a name of more than 63 characters. With this fix, users will be able to create PVCs with >63 character names.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 12:50:47 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 Humble Chirammal 2019-04-10 12:16:45 UTC

Description of problem:

At present if PVC name is more than 63 chars, the volume creation fail for glusterfs. 

For ex:  the error message looks like below:


....failed to create volume: failed to create endpoint/service namespace/glusterfs-dynamic-mysamplevol-1d665b23-ba1e-11e8-a345-0a580a800006: error creating service: Service "glusterfs-dynamic-mysamplevol-1d665b23-ba1e-11e8-a345-0a580a800006" is invalid: metadata.name: Invalid value: "glusterfs-dynamic-mysamplevol-1d665b23-ba1e-11e8-a345-0a580a800006": must be no more than 63 characters”




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

OCS <= 3.11.x

How reproducible:

Create a PVC with name >63 chars.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Humble Chirammal 2019-04-10 12:19:21 UTC

https://github.com/kubernetes/kubernetes/pull/76184

Comment 4 RamaKasturi 2019-04-27 18:20:58 UTC

Hello John,

   We cannot definitely take this in for BU3 testing but if the patch is available we can propose it for testing it for the next batch update and based on the content for that release we can take a call. Does that sound okay ?

Thanks
kasturi

Comment 6 Humble Chirammal 2019-05-06 08:08:05 UTC

(In reply to RamaKasturi from comment #4)
> Hello John,
> 
>    We cannot definitely take this in for BU3 testing but if the patch is
> available we can propose it for testing it for the next batch update and
> based on the content for that release we can take a call. Does that sound
> okay ?
> 


Kasturi, iiuc, you are saying eventhough the content is not going 
in OCS 3.11.3 , we can do the qualification at OCS 3.11.3 timeframe. Is that you meant?

Comment 21 errata-xmlrpc 2019-10-30 12:50:47 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-2019:3262