Rebasing microshift to use latest 4.13 ovnk image and cluster fails to start with the following err in ovnkube-master container:

I0302 10:55:18.547069  107024 network_controller_manager.go:212] Won leader election; in active mode
I0302 10:55:18.547077  107024 network_controller_manager.go:213] Starting cluster master
panic: duplicate metrics collector registration attempted

goroutine 234 [running]:
github.com/prometheus/client_golang/prometheus.(*Registry).MustRegister(0x1e1a662?, {0xc000e35620?, 0x1, 0x15?})
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/vendor/github.com/prometheus/client_golang/prometheus/registry.go:403 +0x7f
github.com/prometheus/client_golang/prometheus.MustRegister(...)
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/vendor/github.com/prometheus/client_golang/prometheus/registry.go:178
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/metrics.RegisterMasterFunctional()
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/metrics/master.go:385 +0x6b8
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/network-controller-manager.(*networkControllerManager).configureMetrics(0xc0003f61e0, 0x48fe77?)
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/network-controller-manager/network_controller_manager.go:359 +0x36
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/network-controller-manager.(*networkControllerManager).Init(0xc0003f61e0)
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/network-controller-manager/network_controller_manager.go:298 +0x25
github.com/ovn-org/ovn-kubernetes/go-controller/pkg/network-controller-manager.(*networkControllerManager).Start.func1({0x214bc88, 0xc000e5c1c0})
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/pkg/network-controller-manager/network_controller_manager.go:220 +0x14f
created by k8s.io/client-go/tools/leaderelection.(*LeaderElector).Run
	/go/src/github.com/openshift/ovn-kubernetes/go-controller/vendor/k8s.io/client-go/tools/leaderelection/leaderelection.go:211 +0x11b

4.13

100%

1. use latest ovnk image url from nightly release payload
2. start microshift
3. check the log of ovnkube-master container in ovnkube-master-xxxx pod

panic