[juju-go + hpcloud] Anyone have this bootstrap error before?

[Nick Veitch]

I've been happily running juju-go on hpcloud for a week or so now, but
last night, it stopped working.

>From a completely clean environment:
* connects to cloud fine
* bootstrap runs, but fails (see below)
* The bootstrap node is actually created and running, just the value
returned for the instance is bonkers (1.027581e+06!), hence nothing else
will work
* it is the same version of juju, and the same environments.yaml that
worked fine on Friday, btw


here is the output:

evilnick at ubuntu-juju:~$ juju bootstrap -v
2013/03/26 12:35:00 JUJU environs/openstack: opening environment "hpcloud"
2013/03/26 12:35:00 JUJU environs/openstack: bootstrapping environment "hpcloud"
2013/03/26 12:35:10 JUJU environs: searching for tools compatible with version: 1.9.11-precise-amd64
2013/03/26 12:35:11 JUJU environs/openstack: starting machine 0 in "hpcloud" running tools version "1.9.11-precise-amd64" from "https://region-a.geo-1.objects.hpcloudsvc.com:443/v1/49578719334052/juju-dist/tools/juju-1.9.11-precise-amd64.tgz"
2013/03/26 12:35:18 JUJU juju bootstrap command failed: cannot start bootstrap instance: cannot get started instance: failed to get details for serverId: 1.027581e+06, caused by: Resource at https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/88246674274378/servers/1.027581e+06 not found, caused by: request (https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/88246674274378/servers/1.027581e+06) returned unexpected status: 404; error info: {"itemNotFound": {"message": "The resource could not be found.", "code": 404}}
error: cannot start bootstrap instance: cannot get started instance: failed to get details for serverId: 1.027581e+06, caused by: Resource at https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/88246674274378/servers/1.027581e+06 not found, caused by: request (https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/88246674274378/servers/1.027581e+06) returned unexpected status: 404; error info: {"itemNotFound": {"message": "The resource could not be found.", "code": 404}}

Any clues?

Nick

-- 
Nick Veitch,
Technical Writer, Cloud Engineering, Canonical
https://launchpad.net/~evilnick