adam got in touch (thnaks) and we got sudo snap run --shell maas -c 'maas-region shell' That drops me in "another" python shell but I couldn't get anything more useful from it.
Their theory actually matches mine closely which is around stored procedures which maas seems to use heavily. That could explain why only maas triggers it so far. Chances are that the server never loaded the plpgsql.so. IIRC postgresql will dlopen that once needed. But if it never has done so until an upgrade it will - if triggered later - try to load the new binary which fails to load into the non-restarted server. I'll set up a stored procedure on the host to verify that which would eliminate maas/snap as planned. It still would be an "if not managed by the services/postinst you have to take care yourself - case" but I'd want to be sure of the root cause. -- 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
