It feels to me, that this bug isn't related to MAAS itself, or the fact
that it's a snap. MAAS is a confined snap, so upgrading the postgres
package on the host system shouldn't have any effect at all. If it does
indeed has an affect, we'd need to involve the snapd team. But I don't
think that's actually what's happening here.
If feels like this is related to the postgres server only. The error
message in MAAS is a bit weird, but I suspect it actually the error it
gets from the server.
Nobuto seems to confirm that suspicion. I also suspect that you would
get the same behavior if you would install MAAS in a different node, and
would access the DB purely remotely.
** Changed in: maas (Ubuntu)
Status: New => Invalid
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939898
Title:
Unnatended postgresql-12 upgrade caused MAAS internal error
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1939898/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
