search

canonical / maas-ansible-playbook

An Ansible playbook for installing and configuring MAAS
Apache License 2.0
48 stars 36 forks source link

playbook forces ssh keys import and fails (admin_id) #137

Closed patriziobassi closed 1 year ago

patriziobassi commented 1 year ago

SSH import should be conditional while it's hardcoded

in: https://github.com/maas/maas-ansible-playbook/blob/main/roles/maas_region_controller/tasks/install_maas.yaml#L100 and https://github.com/maas/maas-ansible-playbook/blob/main/roles/maas_region_controller/tasks/install_maas.yaml#L82

ElineMaaikedeWeerd commented 1 year ago

Hi @patriziobassi thank you for raising this issue. Can you provide a bit more information about your setup and the error messages you're seeing? The admin_id is in principle assigned a default (admin, as in the readme), and this does not cause an error in my setup, so more information would be helpful for me to reproduce the failure you're seeing. Thank you!

patriziobassi commented 1 year ago

if you try in a airgapped enviroment it will fail. i had to patch those line removing the --ssh-import={{ admin_id }} call.

the default i had was: "lp:admin" so it was going to launchpad.net

Anyhow i think the ssh keys import it should be a conditional

SK1Y101 commented 1 year ago

Hey @patriziobassi. I've just done some testing on my end: to simulate the airgapped environment while still installing all of the packages needed, I disconnected from my local network after MAAS Region: Install Chrony and reconnected during MAAS Firewall: Install persistent iptables package so that the region would be entirely separated during initialisation.

Using the standard deploy command I also hit an issue where I couldn't connect to launchpad and the playbooks failed there. Trying a second time with a new host but Including the variable admin_id='' in the command, I was able to fully initialise MAAS and continue onwards. Seems like this could be a way to do this until importing ssh keys is optional.