Juju gives unhelpful error when azure out of resource groups
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Juju is frequently failing to bootstrap on Azure with messages like "ERROR cmd supercommand.go:448 failed to bootstrap model: creating controller resource group: creating virtual network: creating virtual network "juju-internal-
See here for examples:
http://
Not clear what the root cause is, but even if it's on the Azure side, we know it doesn't always happen, so there may be a way to mitigate it in Juju.
This is preventing builds from being blessed, so I am marking it critical blocker.
description: | updated |
Changed in juju-core: | |
importance: | High → Critical |
tags: | added: blocker |
Changed in juju-core: | |
status: | Incomplete → Invalid |
tags: | removed: blocker |
tags: | added: docs |
tags: | added: ui |
tags: | added: observability |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju: | |
importance: | High → Medium |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
tags: | added: helptext |
It's hard to tell because the logs disappear when the resource group is deleted by Juju, but I'm guessing this is due to quotas being hit. Your account has many resource groups hanging around, most probably on account of lp:1571687.