The doc about "Configuring a storage class for custom boot source updates" needs to be re-worked:
https://docs.openshift.com/container-platform/4.16/virt/storage/virt-automatic-bootsource-updates.html#virt-configuring-storage-class-bootsource-update_virt-automatic-bootsource-updates

Key points: 
- either add the storage class in the HCO CR
- or change the virt-default storage class
- or change the default storage class (explain the difference)
Re-import the images:
- need to disable the featuregate first? - needs to be decided by the Storage team
- delete the old boot source (DataSource, DataVolume/PVC, VolumeSnapshot)
- delete the DataImportCrons so that they'll recreate? - needs to be decided by the Storage team

    4.17, 4.16, 4.15

    Always

    No accurate and clear steps

    Clear steps for the user

    Storage team needs to describe the accurate steps of the process and hand it to the Docs team