Description of problem:
Since 4.12 TopoLVM (LVMS) D/S provisioner was renamed from "topolvm.cybozu.com" to "topolvm.io". For the old provisioner, we fixed this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2143268

Version-Release number of selected component (if applicable):
4.12, 4.13

How reproducible:
Always

Steps to Reproduce:
1. oc get storageprofile lvms-vg1 -oyaml

Actual results:
spec: {}
status:
  provisioner: topolvm.io
  storageClass: lvms-vg1

Expected results:
$ oc get storageprofile lvms-vg1 -oyaml
....
spec: {}
status:
  claimPropertySets:
  - accessModes:
    - ReadWriteOnce
    volumeMode: Block
  - accessModes:
    - ReadWriteOnce
    volumeMode: Filesystem
  - accessModes:
    - ReadWriteOncePod
    volumeMode: Block
  - accessModes:
    - ReadWriteOncePod
    volumeMode: Filesystem
  provisioner: topolvm.io
  storageClass: lvms-vg1


Additional info: 

This will impact the boot-source images feature when lvms-vg1 is the default storage class:

   $ oc describe dv -n openshift-virtualization-os-images centos-stream8-2f16c067b974
     ...
     Warning  ErrClaimNotValid  4m35s (x17 over 10m)  datavolume-controller  DataVolume.storage spec is missing accessMode and volumeMode, cannot get access mode from StorageProfile lvms-vg1


W/A: 
1. Patch the storageProfile manually: 

   oc patch storageprofile lvms-vg1 --type=merge -p '{"spec": {"claimPropertySets": [{"accessModes": ["ReadWriteOnce"], "volumeMode": "Block"}, {"accessModes": ["ReadWriteOnce"], "volumeMode": "Filesystem"}]}}'

2. Delete the DVs in openshift-virtualization-os-images namespace, they will be recreated and will grab the accessMode and volumeMode from the updated storageprofile.