metal3-dev-env: Redeployment with metal3-dev-env fails

After successfully deploying Metal3 using metal3-dev-env, if we do a make clean and then redeploy using make, the deployment fails. This seems to be due to recreating device ironicendpoint already existing from previous deployment, maybe a cleanup issue ? Here is a snapshot of the error :

[user@hostname] $ make
...
...
! This VM is having trouble accessing https://k8s.gcr.io
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
* Preparing Kubernetes v1.18.3 on Docker 19.03.12 ...
* Verifying Kubernetes components...
* Enabled addons: default-storageclass, storage-provisioner
* Done! kubectl is now configured to use "minikube"
+ [[ -n '' ]]
+ [[ false == \t\r\u\e ]]
+ sudo su -l -c 'minikube ssh sudo brctl addbr ironicendpoint' metal
device ironicendpoint already exists; can't create bridge with the same name
ssh: Process exited with status 1
make: *** [Makefile:10: launch_mgmt_cluster] Error 1