storageprovider seems to be stuck in an infinite loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Cloned from GitHub for a user: https:/
I'm running juju 1.24.6-trusty-amd64 and my logs are filling up with these messages:
machine-113[552]: 2015-09-24 15:06:16 ERROR juju.worker runner.go:223 exited "storageprovisi
I think the problem is that I tried to deploy a charm that had storage requirements but I never allocated them.
I can't remove-service or destroy-machine --force to stop it.
This is still an issue in 1.25.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.25.5 |
tags: | added: storage |
Changed in juju-core: | |
milestone: | 1.25.5 → 1.25.6 |
Changed in juju-core: | |
milestone: | 1.25.6 → 1.25.7 |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0-rc1 |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
importance: | High → Undecided |
milestone: | 1.25.7 → none |
tags: | added: unit-tests |
Changed in juju: | |
milestone: | 2.0-rc1 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
We cannot reproduce this anymore.
The fix must have going in sometimes since the failure was first reported as a drive-by for another piece of work.
If you are still seeing an issue, please open a new report with newer logs.