UbuntuIRC / 2020 /12 /23 /#maas.txt
niansa
Initial commit
4aa5fce
[10:35] <Hybrid512> Hi
[10:36] <Hybrid512> Just encountered an issue after upgrading MaaS to 2.9
[10:36] <Hybrid512> I can't commission my machines anymore
[10:36] <Hybrid512> it keeps failing at the maas-kernel-cmdline script
[10:36] <Hybrid512> machines are in failed state and can't be provisionned anymore
[10:37] <Hybrid512> any idea on how to fix that ? MaaS is unusable anow
[12:35] <peeejayz> Hey all, got an issue with apparmor on a fresh 2.9 install. Anyone else had it Deny /etc/gss/mech.d/ in snap.maas.supervisor?
[13:55] <Hybrid512> Hi
[13:55] <Hybrid512> Just encountered an issue after upgrading MaaS to 2.9
[13:55] <Hybrid512> I can't commission my machines anymore
[13:55] <Hybrid512> it keeps failing at the maas-kernel-cmdline script
[13:55] <Hybrid512> machines are in failed state and can't be provisionned anymore
[13:55] <Hybrid512> any idea on how to fix that ? MaaS is unusable anow
[14:35] <Hybrid512> ha ! Found the fix
[14:36] <Hybrid512> Damn, I should read upgrade procedures more carefully ... I upgraded region server then rack servers ... I should have done the contrary (rack then region), I had to delete rack controllers and reinstall/reregister them to fix the issue