loopback storage provider not completing successfully

Bug #1498081 reported by Charles Butler on 2015-09-21
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
High
Unassigned

Bug Description

I am in correspondance with a CPP developer, and they are having problems using the loopback storage provider with Juju. The following excerpt is from their correspondence:

1. How to create block device on node? I've read https://jujucharms.com/docs/stable/storage topic, but I can't create devices on new node.
   metadata.yaml
   ...
   storage:
     data:
       type: block
       multiple:
         range: 2

   juju deploy --repository=. local:trusty/nedge-node

    but in log file:
    machine-1[4789]: 2015-09-18 14:38:21 ERROR juju.worker runner.go:223 exited "storageprovisioner-machine": processing pending volume attachments: creating volume attachments: attaching volumes from source "loop": attaching volume 1/0: attaching loop device: /var/lib/juju/storage/loop/volume-1-0: No such file or directory: exit status 1

    anton@JUJU:~/charms$ juju storage volume list
    MACHINE UNIT STORAGE DEVICE VOLUME ID SIZE
    1 nedge-node/0 data/0 1/0 volume-1-0 1.0GiB
    1 nedge-node/0 data/1 1/1 volume-1-1 1.0GiB

    anton@JUJU:~/charms$ juju storage list
    [Storage]
    UNIT ID LOCATION STATUS PERSISTENT
    nedge-node/0 data/0 pending false
    nedge-node/0 data/1 pending false

tags: added: storage
Aaron Bentley (abentley) on 2015-09-21
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.26-alpha1
Andrew Wilkins (axwalk) wrote :

@lazypower, what version of Juju is in use? Assuming 1.24, there are some bugs that may not have been fixed. 1.25 is in a much better state.

Charles Butler (lazypower) wrote :

Thanks for the follow up Andrew

The Juju version is 1.24.5-trusty-amd64

Andrew Wilkins (axwalk) wrote :

@lazypower: if it's possible, please recommend that they use 1.25 (beta1) when it's available. If not, we can look at back-porting fixes. Storage is only really stable as of 1.25; there were many bugs that required drastic changes.

Curtis Hovey (sinzui) on 2015-11-03
Changed in juju-core:
milestone: 1.26-alpha1 → 1.26-alpha2
Changed in juju-core:
milestone: 1.26-alpha2 → 1.26-beta1
Changed in juju-core:
milestone: 1.26-beta1 → 2.0-alpha2
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Cheryl Jennings (cherylj) wrote :

Marking as incomplete unless the problem can be reproduced on 1.25 or higher, based on Andrew's comments above.

Changed in juju-core:
status: Triaged → Incomplete
milestone: 2.0-beta4 → none
Launchpad Janitor (janitor) wrote :

[Expired for juju-core because there has been no activity for 60 days.]

Changed in juju-core:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers