After a failed attempt to create an LVMCluster (due to a dirty disk), removing the LVMCluster and attempting to recreate it with forceWipeDevicesAndDestroyAllData selected results in the topolvm-node pod stuck in ContainerCreating with:

Warning  FailedMount  6s (x6 over 21s)  kubelet            MountVolume.SetUp failed for volume "lvmd-config-dir" : configmap "lvmd-config" not found

Verified the configmap does not exist.

This problem does not occur if the first creation of the LVMCluster includes the option to wipe the device - I have only seen it on subsequent creation attempts.

    4.15.0.rc0 and latest lvms

    Always

    1. AWS SNO cluster, attach a dirty EBS volume (pre-existing LVM data, pre-existing FS)
    2. Install LVMS 4.15.0 operator
    3. Create an LVMCluster by path /dev/disk/by-id, do not select forceWipeDevicesAndDestroyAllData
    4. Creation fails (expected) due to existing vg data
    5. oc delete lvmcluster test-lvmcluster
    6. Create the lvmcluster again but do specify the option to wipe the device.
    

    topolvm-node pod is stuck in ContainerCreating and oc describe on it shows this event.

Warning  FailedMount  6s (x6 over 21s)  kubelet            MountVolume.SetUp failed for volume "lvmd-config-dir" : configmap "lvmd-config" not found

I haven't found a way around this.  Subsequent attempts to delete/recreate the lvmcluster hit the same problem.   

    lvmcluster created successfully on subsequent attempts if the wipe device option is specified.   If the option is specified on the initial attempt, the lvmcluster is created successfully.