block-storage-relation-changed retrieves incorrect device location
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
storage (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1) Deploy three units for the one service, all with a storage subordinate
Expected result:
* All three units get storage assigned
Actual result:
* First unit gets storage assigned successfully
* Other units will (randomly - depends on ordering) be passed the device id (eg. /dev/vdb) of the first unit, which may not exist on the other units yet, and so they error with http://
The cause seems to be because hooks/storage-
{{{
device_path = common_
"block-
common_
}}}
which gets the block-device-path from *any* block-storage relation (ie. not necessarily one for this unit) and tries to mount it.