[2.1] Can't SSH to machine in Rescue mode

[Brendan Donegan]

After deploying a machine and putting it into Rescue mode, I am unable to SSH to that machine. After exiting Rescue mode I am then able to SSH in again.

There do seem to be some cloud-init failures in the rsyslog, which I have attached.

[Brendan Donegan (brendan-donegan)]

I also got what's at http://192.168.122.97:5240/MAAS/metadata/latest/by-id/b43hb4/?op=get_preseed:

http://paste.ubuntu.com/23185922/

[Andres Rodriguez (andreserl)]

I can't reproduce this bug. I have tested with trusty and xenial. Maybe issue is related to kernel bug ?

[Brendan Donegan (brendan-donegan)]

I re-bootstrapped my environment, I'm using a MAAS server in rack+region configuration running Xenial, created using uvt-kvm (i.e. an Ubuntu cloud image). I'm deploying a virsh node, then sending it to rescue mode and trying to ssh to it with the same IP that I used to ssh to it (succesfully) when it was deployed. I still can't reach it - I get:

brendand@brendand-T450:~/src/qa-lab-tests/maas-image-ci$ ssh -vvvn ubuntu@192.168.122.2
OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g-fips 1 Mar 2016
debug1: Reading configuration data /home/brendand/.ssh/config
debug1: /home/brendand/.ssh/config line 6: Deprecated option "useroaming"
debug1: /home/brendand/.ssh/config line 7: Applying options for *
debug3: kex names ok: [<email address hidden>,ecdh-sha2-nistp521,ecdh-sha2-nistp256,ecdh-sha2-nistp384,diffie-hellman-group-exchange-sha256]
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
Pseudo-terminal will not be allocated because stdin is not a terminal.
debug2: resolving "192.168.122.2" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.122.2 [192.168.122.2] port 22.
debug1: connect to address 192.168.122.2 port 22: No route to host