no Peter, I have 100G of disk space and didn't have any firewall rule. I created the new controller using this command: juju bootstrap --bootstrap-series=bionic --bootstrap-constraints "tags=new-juju" maas_cloud new_maas_cloud_controller
then upgraded agent version from 2.7.6 to 2.7.8 to be on the same version as the original controller.
And then did a migration with this command: juju migrate default new_maas_cloud_controller
no Peter, I have 100G of disk space and didn't have any firewall rule. I created the new controller using this command: juju bootstrap --bootstrap- series= bionic --bootstrap- constraints "tags=new-juju" maas_cloud new_maas_ cloud_controlle r cloud_controlle r
then upgraded agent version from 2.7.6 to 2.7.8 to be on the same version as the original controller.
And then did a migration with this command: juju migrate default new_maas_
I also tested the workaround in this bug: https:/ /bugs.launchpad .net/juju/ +bug/1882827
but had the same issue