vSphere provider leaves behind virtual machines upon bootstrap failure
Bug #1510675 reported by
John George
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
High
|
Sergey Matyukevich | ||
Bug Description
After each failed bootstrap attempt I've had to log into the vSphere server and remove the virtual machine that was created.
Multiple attempts at bootstrapping runs the vSphere server out of resources.
Revision history for this message
| John George (jog) wrote | #1 |
| summary: |
- vSphere provider leaves behind virtual mchines upon bootstrap failure + vSphere provider leaves behind virtual machines upon bootstrap failure |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| John George (jog) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Sergey Matyukevich (s-matyukevich) |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Adding a second log, which gets past the CPU resource error. In this bootstrap something has gone wrong with cloud-init and ssh key setup. The virtual machine instance is left running in this case as well.