[ https://issues.jboss.org/browse/ISPN-8611?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-8611: -------------------------------- Description: The default name for the application is "caching-service-app" and "shared-memory-service-app" respectively. The persistent volume claim (for StatefulSets) is called {code}${APPLICATION_NAME}-data{code} Now when I use e.g. GlusterFS for persistent volumes and deploy this application, a new service is created called "glusterfs-dynamic-caching-service-app-data-caching-service-app-0" (or "glusterfs-dynamic-shared-memory-service-app-data-shared-memory-service-app-0" However, the maximum length of service name is 63 chars. And the persistent volume claim fails with: {code}Failed to provision volume with StorageClass "gluster-container": glusterfs: create volume err: failed to create endpoint/service <nil>.{code} When the name whole name gets under 63 characters the volume claim is created successfully. was: The default name for the application is "caching-service-app" and "shared-memory-service-app" respectively. The persistent volume claim (for StatefulSets) is called ${APPLICATION_NAME}-data. Now when I use e.g. GlusterFS for persistent volumes and deploy this application, a new service is created called "glusterfs-dynamic-caching-service-app-data-caching-service-app-0" (or "glusterfs-dynamic-shared-memory-service-app-data-shared-memory-service-app-0" However, the maximum length of service name is 63 chars. And the persistent volume claim fails with: {code}Failed to provision volume with StorageClass "gluster-container": glusterfs: create volume err: failed to create endpoint/service <nil>.{code} When the name whole name gets under 63 characters the volume claim is created successfully. -- This message was sent by Atlassian JIRA (v7.5.0#75005)