Comment 6 for bug 1325610

Hi

Re-open this bug as my customer is hitting same issue of below, which is reported a duplicate of this bug #1325610.

  https://bugs.launchpad.net/maas/+bug/1365035

The message in debug mode is as below

$ juju bootstrap maas maas-controller --bootstrap-constraints tags=bootstrap --debug
06:10:51 INFO cmd bootstrap.go:357 Starting new instance for initial controller
Launching controller instance(s) on maas...
06:10:53 DEBUG juju.cloudconfig.instancecfg instancecfg.go:832 Setting numa ctl preference to false
06:10:53 DEBUG juju.service discovery.go:63 discovered init system "systemd" from series "xenial"
06:10:53 DEBUG juju.provider.maas environ.go:1018 maas user data; 4200 bytes
06:10:56 DEBUG juju.provider.maas interfaces.go:265 interface "ens4" has no links
06:10:56 DEBUG juju.provider.maas interfaces.go:265 interface "ens3" has no links
06:10:56 DEBUG juju.provider.maas environ.go:1050 started instance "7ytpek"
- 7ytpek (arch=amd64 mem=16G cores=8)
06:10:56 INFO juju.environs.bootstrap bootstrap.go:606 newest version: 2.2.4
06:10:56 INFO juju.environs.bootstrap bootstrap.go:621 picked bootstrap agent binary version: 2.2.4
06:10:56 INFO juju.environs.bootstrap bootstrap.go:393 Installing Juju agent on bootstrap instance
06:11:01 INFO cmd bootstrap.go:485 Fetching Juju GUI 2.12.3
06:15:21 DEBUG juju.cloudconfig.instancecfg instancecfg.go:832 Setting numa ctl preference to false
Waiting for address
Attempting to connect to 210.252.76.51:22
06:15:22 DEBUG juju.provider.common bootstrap.go:497 connection attempt for 210.252.76.51 failed: /var/lib/juju/nonce.txt does not exist
06:15:27 DEBUG juju.provider.common bootstrap.go:497 connection attempt for 210.252.76.51 failed: /var/lib/juju/nonce.txt does not exist
06:15:32 DEBUG juju.provider.common bootstrap.go:497 connection attempt for 210.252.76.51 failed: /var/lib/juju/nonce.txt does not exist
06:15:38 INFO juju.cloudconfig userdatacfg_unix.go:410 Fetching agent: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/2.2.4/juju-2.2.4-ubuntu-amd64.tgz]>
Timeout, server 210.252.76.51 not responding.
06:17:38 ERROR juju.cmd.juju.commands bootstrap.go:496 failed to bootstrap model: subprocess encountered error code 255
06:17:38 DEBUG juju.cmd.juju.commands bootstrap.go:497 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:588: failed to bootstrap model} {subprocess encountered error code 255}])
06:17:38 DEBUG juju.cmd.juju.commands bootstrap.go:1095 cleaning up after failed bootstrap
06:17:38 INFO juju.provider.common destroy.go:20 destroying model "controller"
06:17:38 INFO juju.provider.common destroy.go:31 destroying instances
06:17:39 INFO juju.provider.common destroy.go:51 destroying storage
06:17:39 INFO cmd supercommand.go:465 command finished

We checked the network is working fine. And the version of juju and maas is as below

    juju: 2.2.4-0ubuntu0.16.04.1
    maas: 2.3.0-6434-gd354690-0ubuntu1~16.04.1

this issue can be reproduce in customer's environment,
but in my test lab(KVM) I don't have issue using same version of juju and maas.

It will be helpful if you can give me some advise or comment about this bug,
Please contact me if you need more detail information about the environment.

regards,

Wenhan