Chapter 4. Updating operating systems

Confirm the node and pod selectors configured on the service’s daemonset.

oc get daemonset -n <project_name> -o wide

$ oc get daemonset -n <project_name> -o wide

These selectors are found under NODE-SELECTOR and SELECTOR, respectively. The example commands below will use glusterfs=storage-host and glusterfs=storage-pod, respectively.

Given the daemonset’s node selector, confirm which hosts have the label, and hence are running pods from the daemonset:

oc get nodes --selector=glusterfs=storage-host

$ oc get nodes --selector=glusterfs=storage-host

Chose a node which will have its operating system upgraded.

Remove the daemonset label from the node:

oc label node <node_name> glusterfs-

$ oc label node <node_name> glusterfs-

This will cause the OpenShift Container Storage pod to terminate on that node.

To restart an OpenShift Container Storage pod on the node, relabel the node with the daemonset label:

oc label node <node_name> glusterfs=storage-host

$ oc label node <node_name> glusterfs=storage-host

Given the daemonset’s pod selector, determine the name of the newly spawned pod by searching for a pod running on the node whose OS you upgraded:

oc get pod -n <project_name> --selector=glusterfs=storage-pod -o wide

$ oc get pod -n <project_name> --selector=glusterfs=storage-pod -o wide

oc rsh into the gluster pod to check the volume heal:

oc rsh <pod_name>
for vol in `gluster volume list`; do gluster volume heal $vol info; done
exit

$ oc rsh <pod_name>
$ for vol in `gluster volume list`; do gluster volume heal $vol info; done
$ exit

Ensure all of the volumes are healed and there are no outstanding tasks. The heal info command lists all pending entries for a given volume’s heal process. A volume is considered healed when Number of entries for that volume is 0. Use gluster volume status <volume_name> for additional details about the volume. The Online state should be marked Y for all bricks.