Re: 'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno
On 23/04/2015, Robert Day robert@metaswitch.com wrote: Martin, Mark, Thank you! That was indeed the problem - once I'd changed that entry to an IP address (and fixed a couple of similar problems with my metadata files not being accessible, where the error messages were much easier to diagnose from), everything started working, and I've now successfully got my charms working on my OpenStack environment. Great! I put up a branch last night to make the error handling when listing instances in the openstack provider saner, so this kind of thing should be easier to diagnose in future. Martin -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
RE: 'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno
Martin, Mark, Thank you! That was indeed the problem - once I'd changed that entry to an IP address (and fixed a couple of similar problems with my metadata files not being accessible, where the error messages were much easier to diagnose from), everything started working, and I've now successfully got my charms working on my OpenStack environment. Thanks again, Rob -Original Message- From: Martin Packman [mailto:martin.pack...@canonical.com] Sent: 22 April 2015 18:01 To: Robert Day Cc: juju@lists.ubuntu.com; Mark Wenning Subject: Re: 'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno On 16/04/2015, Robert Day robert@metaswitch.com wrote: I'm trying to set up Juju on my private OpenStack Juno cloud, but 'juju bootstrap' is consistently failing with 'ERROR juju.cmd supercommand.go:430 no instances found'. My juju-core package version is 1.22.1-0ubuntu1~12.04.1~juju1. Having looked at some logs kindly forwarded by Mark, I don't have a definitive diagnostic, but have got an educated guess. auth-url: http://obuenfvm1:5000/v2.0/ Can an instance within the cloud resolve this address? Once the state server is up, it also needs to be able to talk to the api endpoints, and that seems to be where it's failing. As the machine is still up after bootstrap fails, you should be able to ssh in and confirm if the routing works. Otherwise, look in /var/log/juju and check with upstart if jujud had issues starting up. We have a bug filed already about the final error message being unhelpful, that I've been meaning to get round to fixing for a while: https://bugs.launchpad.net/juju-core/+bug/1222413 Martin -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: 'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno
On 16/04/2015, Robert Day robert@metaswitch.com wrote: I'm trying to set up Juju on my private OpenStack Juno cloud, but 'juju bootstrap' is consistently failing with 'ERROR juju.cmd supercommand.go:430 no instances found'. My juju-core package version is 1.22.1-0ubuntu1~12.04.1~juju1. Having looked at some logs kindly forwarded by Mark, I don't have a definitive diagnostic, but have got an educated guess. auth-url: http://obuenfvm1:5000/v2.0/ Can an instance within the cloud resolve this address? Once the state server is up, it also needs to be able to talk to the api endpoints, and that seems to be where it's failing. As the machine is still up after bootstrap fails, you should be able to ssh in and confirm if the routing works. Otherwise, look in /var/log/juju and check with upstart if jujud had issues starting up. We have a bug filed already about the final error message being unhelpful, that I've been meaning to get round to fixing for a while: https://bugs.launchpad.net/juju-core/+bug/1222413 Martin -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno
Hi all, I'm trying to set up Juju on my private OpenStack Juno cloud, but 'juju bootstrap' is consistently failing with 'ERROR juju.cmd supercommand.go:430 no instances found'. My juju-core package version is 1.22.1-0ubuntu1~12.04.1~juju1. The relevant section of my environments.yaml file is: obuenfvm1: type: openstack use-floating-ip: true network: 410d9e32-5283-49eb-b837-c1d3b813d2a9 auth-url: http://obuenfvm1:5000/v2.0/ tenant-name: clearwater region: RegionOne auth-mode: userpass username: USER password: PASS and I've attached my metadata files (generated with 'juju metadata generate-image -i 572da09e-5759-47d0-8ede-5d2f42cf4a46 -e obuenfvm1 -d juju_obuenfvm1_metadata3'). The image 572da09e-5759-47d0-8ede-5d2f42cf4a46 is the standard 14.04 image from https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img. Juju-bootstrap then fails: $ juju bootstrap --metadata-source /home/vagrant/juju_obuenfvm1_metadata3 --upload-tools Bootstrapping environment obuenfvm1 Starting new instance for initial state server Launching instance - 88e45c3e-a0a1-45a6-92ca-9e5482695b1c Building tools to upload (1.22.1.1-trusty-amd64) Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 10.225.20.106:22 Attempting to connect to 192.168.0.8:22 [snip SSH warning] bash: warning: setlocale: LC_ALL: cannot change locale (en_US) sudo: unable to resolve host juju-obuenfvm1-machine-0 /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US) Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Running apt-get upgrade Installing package: curl Installing package: cpu-checker Installing package: bridge-utils Installing package: rsyslog-gnutls Installing package: cloud-utils Installing package: cloud-image-utils Bootstrapping Juju machine agent Cloud-init v. 0.7.5 running 'init-local' at Thu, 16 Apr 2015 11:20:25 +. Up 4.38 seconds. Cloud-init v. 0.7.5 running 'init' at Thu, 16 Apr 2015 11:20:28 +. Up 7.40 seconds. [snip standard boot/install messages] cloud-image-utils is already the newest version. cloud-image-utils set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 14a0a963edd043a0ee723f8d44c3c872361f6468b0694827f4528bc0aa6912df /var/lib/juju/tools/1.22.1.1-trusty-amd64/tools.tar.gz 2015-04-16 11:22:30 INFO juju.cmd supercommand.go:37 running jujud [1.22.1.1-trusty-amd64 gc] 2015-04-16 11:22:30 INFO juju.network network.go:117 setting prefer-ipv6 to false 2015-04-16 11:22:30 INFO juju.provider.openstack provider.go:249 opening environment obuenfvm1 2015-04-16 11:22:49 ERROR juju.cmd supercommand.go:430 no instances found ERROR failed to bootstrap environment: subprocess encountered error code 1 (I've attached the full output, in case any of my trimmed information is interesting). At this point, the 'initial state server' is running - I can SSH into it, for example - but juju status just silently does nothing (and juju status --v doesn't give any verbose output). Has anyone successfully got Juju working on OpenStack Juno, or have any suggestions on how to debug this further? Thanks, Rob $ juju bootstrap --metadata-source /home/vagrant/juju_obuenfvm1_metadata3 --upload-tools Bootstrapping environment obuenfvm1 Starting new instance for initial state server Launching instance - 88e45c3e-a0a1-45a6-92ca-9e5482695b1c Building tools to upload (1.22.1.1-trusty-amd64) Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 10.225.20.106:22 Attempting to connect to 192.168.0.8:22 @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is a9:fb:8f:3a:a4:31:f1:0c:c4:02:64:2c:78:68:4a:38. Please contact your system administrator. Add correct host key in /home/vagrant/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/vagrant/.ssh/known_hosts:162 remove with: ssh-keygen -f /home/vagrant/.ssh/known_hosts -R 10.225.20.106 Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Agent forwarding is disabled to avoid man-in-the-middle attacks. bash: warning: setlocale: LC_ALL: cannot change locale (en_US) sudo: unable to resolve host juju-obuenfvm1-machine-0 /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US) Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Running apt-get upgrade Installing package: curl Installing package: cpu-checker Installing package: bridge-utils Installing package: rsyslog-gnutls
