Bootstrap timeout on private cloud should give a explicit msg

[Nicolas Thomas]

Following up from this: https://bugs.launchpad.net/juju-core/+bug/1591488

I then tried with providing a url for metadata:
juju bootstrap openstack openstack --config image-metadata-url=http://192.168.16.5/juju/images/ --config network=private --upload-tools --debug -v

It gets much further .. bootstrapping a node etc .. verifying metadata get read pass .. (before bootstrap agent only).

I did capture the cloud-init log/output during the process and attach them.

Can reproduce with 2.0 or 1.25 (similar behaviour)..

Checked nova cmds works from the jumphost..

[Cheryl Jennings (cherylj)]

Looks like this is the same issue as bug #1591488 as I see the following in the cloud init output:

2016-06-11 11:08:00 ERROR cmd supercommand.go:448 cannot set initial model constraints: index file has no data for cloud {RegionOne http://172.27.60.36:35357/v2.0/} not found

[Nicolas Thomas (thomnico)]

In my opinion they are different.

In the 1591488 juju does not even try to create a vm to bootstrap on.

On this one juju start the VM (hence can find the UUID of the image)
but fails once trying to bootstrap the agent on the VM.

My 2 cents..

On Sun, Jun 12, 2016 at 10:16 PM, Cheryl Jennings
<email address hidden> wrote:
> *** This bug is a duplicate of bug 1591488 ***
> https://bugs.launchpad.net/bugs/1591488
>
> Looks like this is the same issue as bug #1591488 as I see the following
> in the cloud init output:
>
> 2016-06-11 11:08:00 ERROR cmd supercommand.go:448 cannot set initial
> model constraints: index file has no data for cloud {RegionOne
> http://172.27.60.36:35357/v2.0/} not found
>
> ** This bug has been marked a duplicate of bug 1591488
> Can not bootstrap on private openstack juju 1.25 or 2.0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1591499
>
> Title:
> Bootstrap timeout and fail on private cloud
>
> Status in juju-core:
> New
>
> Bug description:
> Following up from this: https://bugs.launchpad.net/juju-
> core/+bug/1591488
>
> I then tried with providing a url for metadata:
> juju bootstrap openstack openstack --config image-metadata-url=http://192.168.16.5/juju/images/ --config network=private --upload-tools --debug -v
>
> It gets much further .. bootstrapping a node etc .. verifying
> metadata get read pass .. (before bootstrap agent only).
>
> I did capture the cloud-init log/output during the process and attach
> them.
>
> Can reproduce with 2.0 or 1.25 (similar behaviour)..
>
> Checked nova cmds works from the jumphost..
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1591499/+subscriptions

--
Best Regards,
       Nicolas Thomas
http://insights.ubuntu.com/?p=889
EMEA Solution Architect Canonical
GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9

[Nicolas Thomas (thomnico)]

Here are cloud-inits with trace on (hopefully) ..

I do see the file are touched by juju bootstrap client but the controller seems to simply ignore it and time out.

The cli is :
export JUJU_LOGGING_CONFIG="<root>=DEBUG;juju.environs.simplestreams=TRACE"

juju bootstrap openstack openstack --config image-metadata-url=http://$my_ip/juju-meta/images/ --config network=private --upload-tools --keep-broken --logging-config="<root>=DEBUG;juju.environs.simplestreams=TRACE"

ubuntu@jumpserver2:~$ echo $my_ip
192.168.16.3

[Anastasia (anastasia-macmood)]

Nicolas,

Do you have the directory structure for your images metadata @ http://192.168.16.5/juju/images/? The contents of the files in there would be very useful too.

The logs seems to indicate that we have seen that you've specified images metadata location but we have skipped over it and fell threw to cloud-images.ubuntu.com (which, of course, is not going to have your desired images metadata). This may happen if the provider requires metadata files to be signed.

Please clarify if the files that contain image metadata are signed.

Also, despite the attempt at setting logs at TRACE level, I am not seeing any trace level messages. Is it possible for you to set up TRACE for root (<root>=TRACE) just for this deploy attempt and provide generated logs?

[Nicolas Thomas (thomnico)]

The root cause was the Openstack setup filtering port 80 between bootstrap and the jumpserver.

Meanwhile the msgs from juju telling it can not find the ids on the official meta data stream is confusing ... a "timeout reaching http://my-ip" would have avoid a lot of this :)

Thanks for the help

As far as trace I was following instructions from discussion on freenode #juju-dev

[Nicolas Thomas (thomnico)]

I succeed to bootstrap using swift which is a much better way for
first time user to see things going..

Where can I contribute to the doc on this please ?

On Tue, Jun 14, 2016 at 5:38 PM, Anastasia
<email address hidden> wrote:
> ** Changed in: juju-core
> Status: Incomplete => Triaged
>
> ** Changed in: juju-core
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1591499
>
> Title:
> Bootstrap timeout on private cloud should give a explicit msg
>
> Status in juju-core:
> Triaged
>
> Bug description:
> Following up from this: https://bugs.launchpad.net/juju-
> core/+bug/1591488
>
> I then tried with providing a url for metadata:
> juju bootstrap openstack openstack --config image-metadata-url=http://192.168.16.5/juju/images/ --config network=private --upload-tools --debug -v
>
> It gets much further .. bootstrapping a node etc .. verifying
> metadata get read pass .. (before bootstrap agent only).
>
> I did capture the cloud-init log/output during the process and attach
> them.
>
> Can reproduce with 2.0 or 1.25 (similar behaviour)..
>
> Checked nova cmds works from the jumphost..
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1591499/+subscriptions

--
Best Regards,
       Nicolas Thomas
http://insights.ubuntu.com/?p=889
EMEA Solution Architect Canonical
GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.