Comment 3 for bug 1814356

E. MAS (erwan-mas) wrote :

I dont have anymore the issue .

In my context , i use maas , and in this context , at this time , i need to reboot the server .

The server is deployed with the bogus package ( 2.37.1+18.04 ) , and after when juju install his agent , juju do the upgrade to 2.37.1.1 .
This already too late because the systemd path is already corrupted .

On the next reboot , snapd will not corrupt the systemd path .

I dont know when my maas server will install directly with the right version .

You can close , the problem is solved .