I managed to reproduce the errors. In order to reproduce this we have to go back to MAAS 1.9, where the migrations were applied by South. In MAAS 2.0 the team ported the migrations to the new builtin tool provided by django and apparently South and Django were treating the default column value in a different way.
I managed to reproduce the errors. In order to reproduce this we have to go back to MAAS 1.9, where the migrations were applied by South. In MAAS 2.0 the team ported the migrations to the new builtin tool provided by django and apparently South and Django were treating the default column value in a different way.