From what we're seeing it seems that when the PV is automatically created for a PVC with a very long name the generated name for the PV can be too long, breaking the pv creation.

What's the latest status here?

To summarize, you should not face this issue with oc build which is >= 3.11.43, It should allow successful volume creation.

Zitang,

Could you help to provide support to try to confirm this problem with >= 3.11.43 ? Thx.

In v3.11.104,
I think this is fixed.
pvc created successfully.

[root@ip-172-18-7-57 ~]# oc get pod
NAME                                                      READY     STATUS    RESTARTS   AGE
postgresql-9fef1d35-5c24-11e9-b749-0a580a800006-1-mgz6f   1/1       Running   0          9m
[root@ip-172-18-7-57 ~]# oc get pvc
NAME                                              STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
postgresql-9fef1d35-5c24-11e9-b749-0a580a800006   Bound     pvc-d02c0c32-5c24-11e9-bd52-0e715c043546   1Gi        RWO            glusterfs-storage   9m

(In reply to Zihan Tang from comment #10)
> In v3.11.104,
> I think this is fixed.
> pvc created successfully.
> 
> [root@ip-172-18-7-57 ~]# oc get pod
> NAME                                                      READY     STATUS  
> RESTARTS   AGE
> postgresql-9fef1d35-5c24-11e9-b749-0a580a800006-1-mgz6f   1/1       Running 
> 0          9m
> [root@ip-172-18-7-57 ~]# oc get pvc
> NAME                                              STATUS    VOLUME          
> CAPACITY   ACCESS MODES   STORAGECLASS        AGE
> postgresql-9fef1d35-5c24-11e9-b749-0a580a800006   Bound    
> pvc-d02c0c32-5c24-11e9-bd52-0e715c043546   1Gi        RWO           
> glusterfs-storage   9m



Awesome!! Thanks Zihan Tang for verifying the fix. 

I am closing this bug as "FIXED IN CURRENT RELEASE" !