azure: units fail to attach block storage

Bug #1498746 reported by Andrew Wilkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Andrew Wilkins
1.25
Fix Released
High
Andrew Wilkins

Bug Description

I've just deployed a charm with block storage to azure, and the unit never initialises. Looking at the unit logs, I see:

    2015-09-23 05:10:18 ERROR juju.worker.uniter.remotestate watcher.go:81 remote state watcher exited: processing initial storage attachment change: refreshing storage details: cannot determine device path: no serial or persistent device name

Looks like we're not combining information from volume sources and block devices properly.

Andrew Wilkins (axwalk)
Changed in juju-core:
assignee: nobody → Andrew Wilkins (axwalk)
Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → In Progress
Andrew Wilkins (axwalk)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
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.