[Bug 1305135] Re: FFE: Provide ssh access to Qemu testbed for easier test debugging

[Martin Pitt]

I synced the package into unapproved. Feel free to reject if you think
that it's unappropriate at this time.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1305135

Title:
  FFE: Provide ssh access to Qemu testbed for easier test debugging

Status in “autopkgtest” package in Ubuntu:
  New

Bug description:
  I just uploaded autopkgtest 2.14.1 to Debian and I'd like to get it
  into trusty. Annotated changelog:

  autopkgtest (2.14.1) unstable; urgency=medium

    * tools/adt-buildvm-ubuntu-cloud: Enable ssh login with passwords.

  That's
  http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=3a424e7ac
  and really should be treated as a bug fix. cloud-init disables ssh
  password login by default, this enables it again. These are just local
  test VMs which are totally open for outside root access, so limiting
  ssh logins isn't any security issue. But it prevents easy ssh login
  for debugging test failures.

  autopkgtest (2.14) unstable; urgency=medium

    * lxc: Greatly simplify bind mounting of shared tmp dir using the
      lxc-start -s option.

  I originally had a rather complicated approach to do this with poking
  in LXC's directories directly:
  http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=5fbbe3f05
  . In bug 1304309 Stéphane showed me how to do this properly, so this
  change simplifies and robustifies this a lot again:

  http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=70af21afa417f

  This is covered by automatic tests.

    * adt-virt-qemu: Forward VM's ssh port 22 to the first free localhost port
      starting from 10022. When finding one, suggest connecting to the VM with
      an appropriate ssh command on --shell.

  This is
  http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=9a193eb76
  and a new feature. I tested this extensively, and IMHO it is low risk.
  Logging into the testbed with ssh is much more comfortable than with
  nc or even minicom, as the latters have relatively limited terminal
  capabilities (e. g. byobu doesn't work). Also, it's rare to find
  minicom on production machines that host autopkgtests, but ssh is
  available pretty much everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1305135/+subscriptions