create a machine job for machines/environments that provide local storage
Bug #1229507 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
The local provider, and now the null provider, manage local storage at the bootstrap node. Currently jujud is hard-coded to check if the provider is null or local, and machine-id is "0", and then enable the local-storage worker. We should add a new job to handle this like any other capability.
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
| tags: | added: local-provider |
| tags: | added: manual-provider |
| tags: |
added: ssh-provider removed: manual-provider |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| status: | In Progress → Triaged |
| importance: | High → Low |
| tags: |
added: manual-provider removed: ssh-provider |
| Changed in juju-core: | |
| assignee: | Andrew Wilkins (axwalk) → nobody |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #2 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Dependent on better upgrade story as we need to modify jobs on existing environments.