Hum, it's weird that Juju was able to SSH into the machine while it was deploying. AFAIK, Juju's SSH key is part of the user data that gets pulled by the machine *after* it's installed. It goes like this:
- Client deploys a machine
- MAAS starts machine
- Machine gets into the ephemeral environment and runs the Curtin install (only the SSH keys registered inside MAAS for the user are actually installed on the machine at this stage)
- Once the install is done, the machine reboots
- The Juju user data is pulled from MAAS by cloud init
- Juju can now connect to the machine
Hum, it's weird that Juju was able to SSH into the machine while it was deploying. AFAIK, Juju's SSH key is part of the user data that gets pulled by the machine *after* it's installed. It goes like this:
- Client deploys a machine
- MAAS starts machine
- Machine gets into the ephemeral environment and runs the Curtin install (only the SSH keys registered inside MAAS for the user are actually installed on the machine at this stage)
- Once the install is done, the machine reboots
- The Juju user data is pulled from MAAS by cloud init
- Juju can now connect to the machine