Comment 4 for bug 1486615

Revision history for this message
Daniel Manrique (roadmr) wrote :

Once I pinned the revno, I get another error:

https://ci.admin.canonical.com/view/live-ols-jobs/job/live-pes-capomastro/142/console

2015-08-20 22:25:25 ERROR juju-log block-storage:3: Error: Multiple volumes are associated with postgresql/0 prodstack-zone-1 volume. Cannot get_volume_id.
2015-08-20 22:25:25 ERROR juju.worker.uniter.operation runhook.go:86 hook "block-storage-relation-changed" failed: exit status 1
This is the table of volumes in that environment:

https://pastebin.canonical.com/138112/

The get_volume_id method in the block_storage_broker charm tries to determine which volume needs to be associated, but does so with a simple "A in B" statement. In the table, there are two entries which contain what we want ("postgresql/0 prodstack-zone-1 volume"): the other one is "spi-postgresql/0 prodstack-zone-1 volume".

I notice that other volumes are prefixed (spi-, grafana-, blah-), I'll try to figure out how to do something similar with capomastro so the volume matching works.