Azure-arm leaves machine-0 from the admin model behind
Bug #1571687 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Juju CI is finding many 10's of resource groups left behind each week in Azure. On Monday 2016-04-18, Azure had 26 resource groups/instances running from 1 or more days ago. Most instances were from April 15. A few were older from April 13 and some were from April 16. All but two were machine-0 from the admin model.
Changed in juju-core: | |
milestone: | 2.0-beta5 → 2.0-rc1 |
Changed in juju-core: | |
milestone: | 2.0-beta6 → 2.0-beta7 |
Changed in juju-core: | |
milestone: | 2.0-beta7 → 2.0-beta8 |
Changed in juju-core: | |
milestone: | 2.0-beta8 → none |
Changed in juju-core: | |
importance: | High → Undecided |
affects: | juju-core → juju |
Changed in juju: | |
status: | Incomplete → Fix Released |
To post a comment you must log in.
That would be because CI is timing out on kill-controller: data.vapour. ws/juju- ci/products/ version- 3914/native- deploy- landscape- azure/build- 51/consoleText
http://
I've found deleting VMs in Azure to be considerably slower than on other clouds. Resource group deletion is also very slow, and this is necessary to destroy a model.
I do think we should stop trying to be "friendly" in kill-controller, and just talk directly to the cloud API like we used to with --force. That would probably speed things up a bit, because then we'd just delete everything at once by deleting the resource group.