Juju agent stuck in pending if charm storage's minimum-size exceeds available disk space on machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
High
|
Unassigned | ||
1.25 |
Won't Fix
|
High
|
Unassigned |
Bug Description
Version(s) affected: Juju 1.25.5, 2.0 beta 6
I've hit a repeatable issue where I can put the juju agent into an infinite loop while allocating, and no combination of destroy-environment (1.25.5), destroy-model, destroy-controller, destroy-model (2.0 beta6) will complete.
Scenario:
Deploy charm with storage requirement that exceeds the default machine constraints.
Steps to recreate:
juju bootstrap
juju deploy cs:~3-bruno/
The quobyte-registry charm has a minimum storage requirement of 10G. This exceeds the default machine constraints. The juju agent attempts to install but can't because the storage loopback file creation has run the disk out of space. The unit agent remains in a pending state forever.
I've attempted every command to destroy the environment, model, and controller to no avail. `destroy-
Changed in juju-core: | |
milestone: | none → 2.0-beta8 |
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: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
tags: | added: 2.0 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Won't Fix |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
You can force kill-controller to go through the provider by first manually taking down the controller through your provider and running juju kill-controller.
We still need to address the situation which caused the machine to get stuck in pending.