[OpenShift]Cannot deploy cluster with GlusterFS and CRI-O using 3.11.43

Solution In Progress - Updated -


  • After upgrading to 3.11.43, unable to provision clusters with GlusterFS using CRI-O.
# oc describe pod glusterfs-storage-j6xvn -n glusterfs
Name:               glusterfs-storage-j6xvn
Namespace:          glusterfs
Priority:           0
PriorityClassName:  <none>
Node:               node.example.com/10.xx.xx.xx
Status:             Running
  Type     Reason     Age   From                                     Message
  ----     ------     ----  ----                                     -------
  Normal   Pulling    10m   kubelet, node.example.com  pulling image "example.registry.com/rhgs3/rhgs-server-rhel7:latest"
  Normal   Pulled     10m   kubelet, node.example.com  Successfully pulled image "example.registry.com/rhgs3/rhgs-server-rhel7:latest"
  Normal   Created    10m   kubelet, node.example.com  Created container
  Normal   Started    10m   kubelet, node.example.com  Started container
  Warning  Unhealthy  9m    kubelet, node.example.com  Readiness probe errored: rpc error: code = Unknown desc = command error: time="2018-12-12T12:39:59Z" level=error msg="open /dev/null: permission denied" open /dev/null: permission denied exec failed: container_linux.go:336: starting container process caused "read init-p: connection reset by peer", stdout: , stderr: , exit code -1
  Warning  Unhealthy  9m  kubelet, node.example.com  Liveness probe errored: rpc error: code = Unknown desc = command error: time="2018-12-12T12:40:15Z" level=error msg="open /dev/null: permission denied"


  • OpenShift Container Platform 3.11
  • CRI-O
  • GlusterFs

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content