GCE bootstraps but fails to provision
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Cheryl Jennings |
Bug Description
I just set up a 'free trial' with GCE, and I was able to enable the Google Compute Engine.
After doing so, I did "juju add-credential google" and passed in the JSON file credentials. I was then able to do "juju bootstrap ... google" just fine. The machine came up as expected.
However, I then did "juju switch controller; juju enable-ha" because I wanted to test it. I can see that there are 2 machines up and running in the GCE dashboard, but there are not *3* machines. Further if I do: "juju status" it reports that 1 machine is running, but 2 machines are still "pending".
There is no /var/lib/juju on the second machine, though cloud-init-
I *can* SSH to the second machine that was started, though there is no 3rd machine, and I don't see a jujud running.
Mark also noted the same problem (bootstrap works, provisioning new machines does not).
Changed in juju-core: | |
milestone: | 2.0-beta8 → 2.0-beta9 |
Changed in juju-core: | |
milestone: | 2.0-beta9 → 2.0-beta10 |
Changed in juju-core: | |
milestone: | 2.0-beta10 → 2.0-beta11 |
Changed in juju-core: | |
milestone: | 2.0-beta11 → 2.0-beta12 |
Changed in juju-core: | |
importance: | Critical → High |
assignee: | nobody → Cheryl Jennings (cherylj) |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta12 → none |
milestone: | none → 2.0-beta12 |
I checked, and I can manually start 3 instances via the web API. I don't know if they are a different CPU level, or some other difference, but it is possible to create more than 2 instances.