TopoLVM does not currently support hot reload of config file. This means, if the user adds/removes a device class from LVMCluster after the initial deployment, the change will not be reflected on the cluster until TopoLVM-Node Pod gets deleted and recreated. 

Always

1. Deploy an LVMCluster CR having one or more device classes
2. Wait until all the pods in openshift-storage get into Running state 
3. Edit LVMCluster to add a new device class
4. Create a pod and PVC using the storage class associated with the newly added device class

PV gets stuck in Pending state

PV is Bound

This will be solved by https://issues.redhat.com/browse/OCPVE-774 in the new releases. However, for the existing releases that is affected (4.13, 4.14, and 4.15), we should document the workaround which is removing the TopoLVM-Node pod so it will be recreated with the new config.