SSH exception does not provides enough basic information

[Attila Fazekas]

http://logs.openstack.org/78/98178/1/check/check-tempest-dsvm-neutron/fbea859/console.html.gz

I cannot see the console log of the instance:
- I cannot see was it able to boot
- I cannot see was it able to get dhcp information

I do not see the the ovs bridge statuses:
 replaying the ovs commands in head is not easy..

[Mauro S M Rodrigues (maurorodrigues)]

Correct me if I'm wrong, but it end up successfully connecting by this piece of log
http://logs.openstack.org/78/98178/1/check/check-tempest-dsvm-neutron/fbea859/console.html.gz#_2014-06-06_05_10_02_782

specifically:
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,467 Switch to new keys ...
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,489 Adding ssh-rsa host key for 172.24.4.66: 17cce79c182d59163b133b267abd7251
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,490 Trying SSH key c96108c64ee6f45dfd36f8389ac7e32c
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,493 userauth is OK
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,609 Authentication (publickey) successful!
2014-06-06 05:10:02.782 | 2014-06-06 05:05:37,622 ssh connection to cirros@172.24.4.66 successfuly created

I know it sounds weird, and I do not think this behaved fine, but might justify why we're missing console log

[Launchpad Janitor (janitor)]

[Expired for tempest because there has been no activity for 60 days.]