I was able to reproduce this problem on R4E when working on USHIFT-148. The procedure below mimics partial stop/clean of resources required pre-rollback.

Latest build from the main branch

100%

for service in microshift microshift-etcd kubepods.slice ; do
   sudo systemctl stop --now   ${service} 2>/dev/null
   sudo systemctl reset-failed ${service} 2>/dev/null
done

sudo ovs-vsctl del-br br-int 2>/dev/null
for pname in conmon pause ovn-controller ovn-northd ovsdb-server ; do
   sudo pkill -9 --exact ${pname}
done

sudo systemctl start microshift

# sudo -i oc get pods -A
NAMESPACE                  NAME                                  READY   STATUS             RESTARTS         AGE
openshift-dns              dns-default-m6lsw                     1/2     Running            11 (61s ago)     168m
openshift-dns              node-resolver-gzxlf                   1/1     Running            5 (9m56s ago)    3h1m
openshift-ingress          router-default-5d4d6d9cf9-m9jzf       0/1     Completed          2                171m
openshift-ovn-kubernetes   ovnkube-master-tc9gv                  4/4     Running            20 (9m56s ago)   3h1m
openshift-ovn-kubernetes   ovnkube-node-hbvzk                    1/1     Running            7 (9m56s ago)    3h1m
openshift-service-ca       service-ca-66dc44968-cfbrg            0/1     CrashLoopBackOff   8 (85s ago)      172m
openshift-storage          topolvm-controller-78c647d9c9-gt4nv   3/4     CrashLoopBackOff   21 (76s ago)     166m
openshift-storage          topolvm-node-mgwbt                    3/4     CrashLoopBackOff   21 (79s ago)     165m

All pods up and running