Description of problem:
When registry storage backend is using pvc, make some changes in image-registry, the new created registry pods cannot be running for no available pvc with below errors:
Events:
  Type     Reason              Age    From                     Message
  ----     ------              ----   ----                     -------
  Normal   Scheduled           3m15s  default-scheduler        Successfully assigned openshift-image-registry/image-registry-f6d697586-46vpv to compute-0
  Warning  FailedAttachVolume  3m15s  attachdetach-controller  Multi-Attach error for volume "pvc-d9e871b6-601a-11e9-861f-0050569bf97a" Volume is already used by pod(s) image-registry-5bdc5cdb79-hj62t
  Warning  FailedMount         72s    kubelet, compute-0       Unable to mount volumes for pod "image-registry-f6d697586-46vpv_openshift-image-registry(11020e55-6028-11e9-8891-0050569b0d3c)": timeout expired waiting for volumes to attach or mount for pod "openshift-image-registry"/"image-registry-f6d697586-46vpv". list of unmounted volumes=[registry-storage]. list of unattached volumes=[registry-storage registry-tls registry-certificates registry-token-rj8q7]


Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-04-10-182914

How reproducible:
Always

Steps to Reproduce:
1.Config registry storage to PVC
2.Make some changes in image-registry config to make a new deployment triggered
3.Check new created pod

Actual results:
Pod is in ContainerCreating state:
$ oc get pods
NAME                                               READY   STATUS              RESTARTS   AGE
cluster-image-registry-operator-7d8ddc5d64-qz2t6   1/1     Running             0          27h
image-registry-5bdc5cdb79-hj62t                    1/1     Running             0          83m
image-registry-f6d697586-46vpv                     0/1     ContainerCreating   0          5m31s


Expected results:
Pod should be running

Additional info: