[Bug 1644566] Re: juju bootstrap hangs forever at "Attempting to connect to 10.0.4.130:22"

[Stéphane Graber]

Rebuilding LXD with shlibs disabled but still using the in-archive
source packages fixes the issue. So this is yet-another Go shared
library regression with 1.7 I suspect.

Closing lxd and juju tasks, adding golang-go task and assigning to
mwhudson.

** Changed in: juju-core
       Status: New => Invalid

** Changed in: juju-core (Ubuntu)
       Status: New => Invalid

** Changed in: lxd (Ubuntu)
       Status: New => Invalid

** Also affects: golang (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: golang (Ubuntu)
     Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)

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

Title:
  juju bootstrap hangs forever at "Attempting to connect to
  10.0.4.130:22"

Status in juju-core:
  Invalid
Status in golang package in Ubuntu:
  New
Status in juju-core package in Ubuntu:
  Invalid
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  In current zesty, "juju-2.0 bootstrap lxd localhost" does:

  Creating Juju controller "lxd" on localhost/localhost
  Looking for packaged Juju agent version 2.0-rc3 for amd64
  Launching controller instance(s) on localhost/localhost...
   - juju-5fc6db-0
  Fetching Juju GUI 2.2.3
  Waiting for address
  Attempting to connect to 10.0.4.130:22

  and then hangs forever. It does create the container:

  | juju-5fc6db-0 | RUNNING | 10.0.4.130 (eth0) |      | PERSISTENT | 0
  |

  and it runs:

  $ lxc exec juju-5fc6db-0 systemctl is-active ssh
  active

  but ssh into it does not work:

  Warning: Permanently added '10.0.4.130' (ECDSA) to the list of known hosts.
  Permission denied (publickey).

  Indeed it does not install an ssh key:

  $ lxc exec juju-5fc6db-0 -- ls -l /home/ubuntu/.ssh
  total 0
  -rw------- 1 ubuntu ubuntu 0 Nov 24 14:04 authorized_keys

  I guess it's supposed to, as apparently password authentication is
  disabled.

  I didn't find a --debug switch or log file or anything similar -- can
  you reproduce this? If not, what can I do to provide further
  debugging?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: juju-2.0 2.0~rc3-0ubuntu4.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-29.31~lp1626436ProposedWithTwoPatches-generic 4.8.8
  Uname: Linux 4.8.0-29-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: i3
  Date: Thu Nov 24 15:01:52 2016
  EcryptfsInUse: Yes
  SourcePackage: juju-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1644566/+subscriptions