Subordinate charm dies when deployed with --storage option

Bug #1595617 reported by Jacek Nykis
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Andrew Wilkins

Bug Description

I wrote a subordinate charm with the following storage in metadata.yaml:
storage:
  srv:
    type: filesystem
    description: Srv storage
    location: /srv
    multiple:
      range: 0-1

If I deploy like this everything works:
juju deploy --repository=. local:trusty/my-charm
juju add-relation apache2 my-charm

But of course with the above storage is not used.

When I try to use storage:
juju deploy --repository=. --storage srv=1G local:trusty/my-charm

The service deploys then I add relation:
juju add-relation apache2 my-charm

And agents end ups up in the lost state:

apache2/0 unknown idle 1.25.5.1 1 10.0.3.144
  my-charm/0 unknown lost 1.25.5.1 10.0.3.144 agent is lost, sorry! See 'juju status-history my-charm/0'

And logs on the unit show this:
2016-06-23 15:22:17 ERROR juju.worker.uniter.filter filter.go:137 tomb: dying
2016-06-23 15:22:21 ERROR juju.worker.uniter.filter filter.go:137 tomb: dying
2016-06-23 15:22:24 ERROR juju.worker.uniter.filter filter.go:137 tomb: dying

juju 1.25.5-trusty-amd64

Tags: storage
Revision history for this message
Cheryl Jennings (cherylj) wrote :

Can you please attach the following?

1 - /var/log/juju/machine-0.log from the state server

2 - The unit log for the primary and subordinate charm?

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Jacek Nykis (jacekn) wrote :

I uploaded logs here:
https://private-fileshare.canonical.com/~jacek/lp1595617.tgz

Please don't share outside of the company.

Changed in juju-core:
status: Incomplete → New
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: storage
Revision history for this message
Ryan Beisner (1chb1n) wrote :

I am experiencing death of subordinates with 1.25.6-trusty-amd64, but without use of the --storage option:

2016-07-20 16:23:47 ERROR juju.worker.uniter.filter filter.go:137 tomb: dying

cinder/4 blocked idle 1.25.6 32 8776/tcp 10.5.2.171 Services not running that should be: cinder-backup
  cinder-backup/4 unknown failed 1.25.6 10.5.2.171 Waiting for agent initialization to finish

To date, I've only observed this on Xenial deployments.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0.0
no longer affects: juju-core
Revision history for this message
Andrew Wilkins (axwalk) wrote :

In 2.0-rc1 I see what I believe is the same issue, but the error message is different:

    2016-09-27 00:31:24 ERROR juju.worker.dependency engine.go:539 "uniter" manifold worker returned unexpected error: watching storage attachment: getting storage filesystem: filesystem for storage instance "filesystem/1" not found

Andrew Wilkins (axwalk)
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Revision history for this message
Andrew Wilkins (axwalk) wrote :
Andrew Wilkins (axwalk)
Changed in juju:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju:
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.