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:
https://github.com/kubernetes/kubernetes/pull/76184
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
(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?
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