Running juju commands via sudo result in a Terminated stderr output

[Diko Parvanov]

Testing multiple deployments on VMs on Azure (doing juju bootstrap and other juju commands via sudo) - some of them just exit with stderr Terminated and nothing else.

The workaround for this has been to do:

loginctl enable-linger root
loginctl enable-linger ubuntu

This happens 50% of the time of those commands, so not reproducible on every run, opening this so we can track down the problem.

This was also reported here: https://bugs.launchpad.net/juju/+bug/1921876, but was presumed it was MAAS that was causing this, however on Azure we have no maas. I am doing juju bootstrap manual/ubuntu@127.0.0.1 on the local machine.

I would gladly run deployments with suggested enabled debugging to capture the issues.

[Diko Parvanov (dparv)]

Generated an sosreport from a failed deployment.

[Diko Parvanov (dparv)]

The stderr is just this (from set -x on the script):

+ sudo -u ubuntu juju bootstrap manual/ubuntu@127.0.0.1 --debug --verbose
Terminated

[Ian Booth (wallyworld)]

Dumb question - why is sudo needed?

[Diko Parvanov (dparv)]

to not bootstrap with the root user and the custom scripts in Azure run with root

[Ian Booth (wallyworld)]

We'll need to look into it - it's not a scenario that's ever been tested or designed for as far as I know.