Description of problem: centos-7-image-cron was expected to be centos7-image-cron to match existing naming against datasources How reproducible: 100% Steps to Reproduce: 1. $ oc get dataimportcron -n openshift-virtualization-os-images Actual results: centos-7-image-cron Expected results: centos7-image-cron Additional info: $ oc get datasources -n openshift-virtualization-os-images NAME AGE centos-stream8 4d15h centos-stream9 4d22h centos7 4d22h fedora 4d22h rhel6 4d22h rhel7 4d22h rhel8 4d22h rhel9 4d22h win10 4d22h win2k12r2 4d22h win2k16 4d22h win2k19 4d22h $ oc get dataimportcron -n openshift-virtualization-os-images NAME AGE centos-7-image-cron 4d15h centos-stream8-image-cron 4d15h centos-stream9-image-cron 4d15h fedora-image-cron 4d15h rhel8-image-cron 4d15h rhel9-image-cron 4d15h
@sbennert - I don't think it's a blocker. We can rename the DIC and it should create a new one *instead of* the existing one. Since the managedDataSource is the same, it should work with no problems. The only issue is that the old DVs won't be garbage collected, because they'll have the old DIC annotation. For that reason, I'm not sure we should fix the DIC for wrong name, because the outcome is worse. @
@
@stirabos - WDYT?
I tend to think that is not such a serious issue, for instance centos-7-image-cron and centos-stream8-image-cron sounds coherents to me and I agree that a fix can be worse than the issue introducing leftovers that need explicit deletion. Personally I'm for closing this as WONTFIX, please feel free to reopen if you see some other technical aspect that I'm missing.