We are affected by this bug when upgrading from MAAS 3.1 to 3.2 or 3.3
The workaround for us is to use 3.1/stable
We are affected by this bug when upgrading from MAAS 3.1 to 3.2 or 3.3
The workaround for us is to use 3.1/stable