1.13.0 has been pushed to the Openshift marketplace stable channel and it autoupdates without checking if the new configmap exists #456
Description
as per title, this just broke production, after the operator self upgraded from 1.12.5 to 1.13.0 and found no configmap with the custom configuration we assume it reverted to the default behaviour, in our case our hosts are connected via fiber channel, the csi tried to use nvme as the deafult behaviour, which is not even available in our hardware, and this completely broke production, all hosts have been set to offline on the san and all storage attachment was lost on the cluster, the nodes multipath is broken and storage is not accessible.
We do believe that pushing what effectively works out as a breaking change to the openshift operator marketplace stable channel is bad practice.
there are tickets with both IBM and RedHat being handled right now, if this channel is faster to work out how to get back to a working situation please advice.