cmd/juju/storage: "add" fails to dynamically add filesystem for storage
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
High
|
Anastasia | ||
| | 1.24 |
High
|
Anastasia | ||
Bug Description
There seems to be a problem with juju storage add. I've got a charm with a filesystem-type store, and I've deployed using EBS. So it's a filesystem backed by EBS.
I then did "juju storage add <unit> filesystem=ebs,1G" to get another instance. That doesn't error, but if I then run "juju storage list" I get:
$ juju storage list
getting attachments for storage filesystem/1: getting storage attachment info: getting filesystem: filesystem for storage instance "filesystem/1" not found
[Storage]
UNIT ID LOCATION STATUS PERSISTENT
storagetest/0 filesystem/0 /var/lib/
| Changed in juju-core: | |
| status: | Triaged → New |
| importance: | High → Undecided |
| Andrew Wilkins (axwalk) wrote : | #1 |
| Anastasia (anastasia-macmood) wrote : | #2 |
| Anastasia (anastasia-macmood) wrote : | #3 |
Whilst dynamic storage creates storage instances and attachments, it does not create filesystems/volumes and related attachments. Fixing this now :D
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.25.0 |
| Changed in juju-core: | |
| assignee: | nobody → Anastasia (anastasia-macmood) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
I wrote a unit test to reproduce your sequence of events. I am using testing charm that declares filesystem store as per your configuration.
The storage is added dynamically as instance count is increased by 1 from before to after.
However, storage list does not seem to reflect this. Looking into storage list now.