storage-get unable to access previously attached devices

[James Page]

Unit successfully attached and consumed osd-devices/{0-3} and osd-journal/{4,5} but when two more devices where presented on osd-devices, the charm was no longer able to access the original devices.

$ juju run --unit ceph-osd/0 "storage-list"
osd-devices/0
osd-devices/1
osd-devices/18
osd-devices/19
osd-devices/2
osd-devices/3
osd-journals/4
osd-journals/5
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/0location"
error: invalid value "osd-devices/0location" for flag -s: invalid storage ID "osd-devices/0location"
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/0 location"
error: invalid value "osd-devices/0" for flag -s: unknown storage ID
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/1 location"
error: invalid value "osd-devices/1" for flag -s: unknown storage ID
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/18 location"
/dev/vdi
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/19 location"
/dev/vdj
$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/2 location"
error: invalid value "osd-devices/2" for flag -s: unknown storage ID

$ juju run --unit ceph-osd/0 "storage-get -s osd-devices/3 location"
error: invalid value "osd-devices/3" for flag -s: unknown storage ID

This operation was performed on 3 units - the other 2 succeeded.

[Cheryl Jennings (cherylj)]

James, can you verify what level you're currently running, and attach machine-0.log?

[James Page (james-page)]

1.25.3

On Sat, 30 Jan 2016 at 03:50 Cheryl Jennings <email address hidden>
wrote:

> James, can you verify what level you're currently running, and attach
> machine-0.log?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1539684
>
> Title:
> storage-get unable to access previously attached devices
>
> Status in juju-core:
> New
>
> Bug description:
> Unit successfully attached and consumed osd-devices/{0-3} and osd-
> journal/{4,5} but when two more devices where presented on osd-
> devices, the charm was no longer able to access the original devices.
>
> $ juju run --unit ceph-osd/0 "storage-list"
> osd-devices/0
> osd-devices/1
> osd-devices/18
> osd-devices/19
> osd-devices/2
> osd-devices/3
> osd-journals/4
> osd-journals/5
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/0location"
> error: invalid value "osd-devices/0location" for flag -s: invalid
> storage ID "osd-devices/0location"
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/0 location"
> error: invalid value "osd-devices/0" for flag -s: unknown storage ID
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/1 location"
> error: invalid value "osd-devices/1" for flag -s: unknown storage ID
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/18 location"
> /dev/vdi
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/19 location"
> /dev/vdj
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/2 location"
> error: invalid value "osd-devices/2" for flag -s: unknown storage ID
>
> $ juju run --unit ceph-osd/0 "storage-get -s osd-devices/3 location"
> error: invalid value "osd-devices/3" for flag -s: unknown storage ID
>
> This operation was performed on 3 units - the other 2 succeeded.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1539684/+subscriptions
>

[JuanJo Ciarlante (jjo)]

I'm also seeing this under 1.25.3 for a local provider deployed environment,
created with:

$ juju deploy local:trusty/prometheus --storage metrics-filesystem=rootfs prometheus

$ juju run --unit=prometheus/0 'storage-get -s $(storage-list) location'
error: invalid value "metrics-filesystem/0" for flag -s: unknown storage ID

$ juju storage list
[Storage]
UNIT ID LOCATION STATUS MESSAGE
prometheus/0 metrics-filesystem/0 /srv/prometheus attached

$ juju version
1.25.3-trusty-amd64

$ juju status |egrep -o agent-version.*|sort -u
agent-version: 1.25.3.1

[Andrew Wilkins (axwalk)]

I cannot reproduce the issue on the 2.1 branch. The code that deals with storage in the uniter (i.e. to do with storage-list & storage-get) was overhauled in Juju 2.0. It's possible that this was fixed as a byproduct of those changes.

I'm going to mark this as Fix Committed, please reopen if this can be reproduced on 2.1 with steps to repro.