Subordinate charm dies when deployed with --storage option
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/
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/
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.
2016-06-23 15:22:21 ERROR juju.worker.
2016-06-23 15:22:24 ERROR juju.worker.
juju 1.25.5-trusty-amd64
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: storage |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0.0 |
no longer affects: | juju-core |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
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?