Document URL: 

In 
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html/deployment_guide/chap-upgrade-glusterfs-registry-namespace#idm140154256621984

we seem to mention wrong image for gluster block: 

6.1.3. Upgrading if existing version deployed by using Ansible
   Depending on the OCP version, edit the glusterblock-provisioner template to change the IMAGE_NAME, IMAGE_VERSION and NAMESPACE. 

~~~~
# oc edit template glusterblock-provisioner

    - displayName: glusterblock provisioner container image name
    name: IMAGE_NAME
    required: true
    value: registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7   --------------------------->  egistry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7
    - displayName: glusterblock provisioner container image version
    name: IMAGE_VERSION
    required: true
    value: v3.11.2
    - description: The namespace in which these resources are being created
    displayName: glusterblock provisioner namespace
    name: NAMESPACE
    required: true
    value: glusterfs
    - description: A unique name to identify which heketi service manages this cluster,
      useful for running multiple heketi instances
    displayName: GlusterFS cluster name
    name: CLUSTER_NAME
    value: storage
~~~~

~~~~
# oc edit template glusterblock-provisioner

    - displayName: glusterblock provisioner container image name
    name: IMAGE_NAME
    required: true
    value: registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7:v3.11.1   --------------------------->  registry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7:v3.11.2
    - description: The namespace in which these resources are being created
    displayName: glusterblock provisioner namespace
    name: NAMESPACE
    required: true
    value: glusterfs
    - description: A unique name to identify which heketi service manages this cluster,
      useful for running multiple heketi instances
    displayName: GlusterFS cluster name
    name: CLUSTER_NAME
    value: storage
~~~~
------------------------------------------------------------

6.2.3. Upgrading if existing version deployed by using Ansible
 Depending on the OCP version, edit the glusterblock-provisioner template to change the IMAGE_NAME, IMAGE_VERSION and NAMESPACE. 

~~~~
# oc edit template glusterblock-provisioner

- displayName: glusterblock provisioner container image name
  name: IMAGE_NAME
  required: true
  value: registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7    ---------------------------> egistry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7
- displayName: glusterblock provisioner container image version
  name: IMAGE_VERSION
  required: true
  value: v3.11.2
- description: The namespace in which these resources are being created
  displayName: glusterblock provisioner namespace
  name: NAMESPACE
  required: true
  value: glusterfs-registry
- description: A unique name to identify which heketi service manages this cluster,
    useful for running multiple heketi instances
  displayName: GlusterFS cluster name
  name: CLUSTER_NAME
  value: registry
~~~~

~~~
# oc edit template glusterblock-provisioner

- displayName: glusterblock provisioner container image name
name: IMAGE_NAME
required: true
value: registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7:v3.11.2   ---------------------------> egistry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7:v3.11.2
- description: The namespace in which these resources are being created
displayName: glusterblock provisioner namespace
name: NAMESPACE
required: true
value: glusterfs-registry
- description: A unique name to identify which heketi service manages this cluster,
useful for running multiple heketi instances
displayName: GlusterFS cluster name
name: CLUSTER_NAME
value: registry
~~~







apart from referring still 3.11.1 I thing the gluster block image should be rhgs-gluster-block-prov-rhel7  NOT rhgs-volmanager-rhel7:v3.11.x


at least when I do this I do get :
# oc logs -f glusterblock-storage-provisioner-dc-1-pgf9g
/usr/sbin/heketi-start.sh: line 7: /var/lib/heketi/container.log: Permission denied
/usr/sbin/heketi-start.sh: line 8: /var/lib/heketi/container.log: Permission denied
/usr/sbin/heketi-start.sh: line 9: /var/lib/heketi/container.log: Permission denied
/usr/sbin/heketi-start.sh: line 23: /var/lib/heketi/container.log: Permission denied
/usr/sbin/heketi-start.sh: line 24: /var/lib/heketi/container.log: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied
flock: cannot open lock file /var/lib/heketi/heketi.db: Permission denied

using rhgs-gluster-block-prov-rhel7 brings this back to work


and the pods keeps crashing