Invalid storage returned by storage-list causing charm breakage

Bug #1518482 reported by Ian Booth
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Won't Fix
Low
Unassigned

Bug Description

When adding storage that is invalid (over size limits), charms can break.

For example:

juju switch amazon
juju bootstrap
juju deploy cs:~chris.macnaughton/trusty/ceph-osd --storage "osd-devices=ebs,2T,1"
juju destroy-service ceph-osd

storage-list will return the invalid attachments, causing :

storage_ids = storage_list('osd-devices')
devices.extend((storage_get('location', s) for s in storage_ids))

to break within a charm environment.

Revision history for this message
Andrew Wilkins (axwalk) wrote :

can you please provide the error text? what version of juju are you using?

Revision history for this message
Andrew Wilkins (axwalk) wrote :

I think this is solved when lp:1501709 is fixed

Changed in juju-core:
milestone: 1.26-beta1 → 2.0-alpha2
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

The only time I've seen this happen is when adding a LOT of storage devices to the ceph charm with storage hooks. The charm iterates through the results of storage-list instead of just adding the device currently in the hook. What this seems to cause is the last device not being attached with the first device's attaching hook fires.

Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
tags: added: 2.0-count
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Changed in juju:
status: Triaged → Won't Fix
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.