juju drops ssh keys from maas user

[Ryan Beisner]

When deploying machines with Juju (2.1.0) against MAAS (2.1.4), the MAAS user's ssh keys are dropped. This prevents the user from being able to ssh directly into the machine.

When deploying machines with just MAAS, the user's ssh keys survive, and the user can ssh directly into the machine.

Confirmed by looking at the content of /home/ubuntu/.ssh/authorized_keys in the two scenarios above.

[Anastasia (anastasia-macmood)]

Putting on the Wishlist, as this is a current behavior and you are requesting a change.

[Ryan Beisner (1chb1n)]

Actually, this is a regression. With Juju 1.25.10 + MAAS 1.9.4, the ssh keys of the MAAS user do survive to exist on the Juju unit.

[Anastasia (anastasia-macmood)]

I am re-triaging this since Juju 2.0 and 2.1 exhibit this behavior. It is not a regression for Juju 2 nor for 2.2.

While we decide when and how we address this bug, the workaround would be to add ssh key using 'juju add-ssh-key'

[Anastasia (anastasia-macmood)]

Marking this report as Won't Fix for 2.0 and 2.1 series as we are not planning any further releases 2.0x/2.1x releases.

[John A Meinel (jameinel)]

Juju 2.0 has support for directly registering user's ssh keys which it will apply to all machines. (you can add keys, remove them, etc.)
It is possible that we should be looking up a user's set of keys from MAAS at some point, but the set-of-keys that can access the machine are intentionally controlled by Juju. (multi-user, etc means the set of keys that can access a machine could be entirely separate from the set of keys that deployed the machine.)

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.