Doesn't seem like a 4.7 blocker
Verified on 4.5.0-0.nightly-2021-02-04-193735, and passed.
$ ./openshift-install destroy cluster --dir ipi_test --log-level debug
DEBUG OpenShift Installer 4.5.0-0.nightly-2021-02-04-193735
DEBUG Built from commit e30ca92797532d9f0e0c56aac20aad27e594ab43
DEBUG find attached objects on tag
DEBUG find VirtualMachine objects
DEBUG delete VirtualMachines
INFO Destroyed VirtualMachine=jima0205-sq62j-rhcos
DEBUG Powered off VirtualMachine=jima0205-sq62j-master-0
INFO Destroyed VirtualMachine=jima0205-sq62j-master-0
DEBUG Powered off VirtualMachine=jima0205-sq62j-master-2
INFO Destroyed VirtualMachine=jima0205-sq62j-master-2
DEBUG Powered off VirtualMachine=jima0205-sq62j-master-1
INFO Destroyed VirtualMachine=jima0205-sq62j-master-1
DEBUG Powered off VirtualMachine=jima0205-sq62j-worker-w4w4q
INFO Destroyed VirtualMachine=jima0205-sq62j-worker-w4w4q
DEBUG Powered off VirtualMachine=jima0205-sq62j-worker-hppjb
INFO Destroyed VirtualMachine=jima0205-sq62j-worker-hppjb
DEBUG Powered off VirtualMachine=jima0205-sq62j-worker-vj4fg
INFO Destroyed VirtualMachine=jima0205-sq62j-worker-vj4fg
DEBUG find Folder objects
DEBUG delete Folder
INFO Destroyed Folder=jima0205-sq62j
Also could not find tag category "openshift-jima0205-sq62j"on vsphere client any more.
$ govc tags.category.ls | grep jima0205-sq62j
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: OpenShift Container Platform 4.5.33 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.