"Relation not found" when running relation-list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Critical
|
Jim Baker | ||
juju (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Quantal |
Fix Released
|
Critical
|
Unassigned |
Bug Description
When attempting to query all relationships during hook execution, I receive the following error from relation-list. The error for all relation ids *except* the current one (as specified by the JUJU_RELATION:
2012-09-20 15:55:49,546 unit:parent/0: twisted ERROR: Unhandled Error
Traceback (most recent call last):
File "/usr/lib/
result = f(*args, **kw)
File "/usr/lib/
return maybeDeferred(
File "/usr/lib/
result = f(*args, **kw)
File "/usr/lib/
return _inlineCallback
--- <exception caught here> ---
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
get_
File "/usr/lib/
raise RelationStateNo
juju.state.
For example, during foo-relation-
# relation-ids foo
foo:1
foo:2
# relation-list -r foo:1
myunit/0
# relation-list -r foo:2
<error occurs here>
This behavior can be reproduced using lp:~mew/+junk/debug-charm:
juju bootstrap
juju deploy --repository=. local:precise/
juju deploy --repository=. local:precise/
juju deploy --repository=. local:precise/
juju add-relation parent:child child1:parent
juju add-relation parent:child child2:parent
I'm running juju locally under LXC. I've reproduced the issue on Quantal and Precise hosts.
Related branches
- Clint Byrum (community): Approve
-
Diff: 456 lines (+292/-33)4 files modifiedjuju/hooks/commands.py (+36/-10)
juju/hooks/invoker.py (+6/-2)
juju/hooks/protocol.py (+11/-6)
juju/hooks/tests/test_invoker.py (+239/-15)
Changed in juju: | |
importance: | Undecided → Critical |
Changed in juju: | |
status: | New → Confirmed |
Changed in juju (Ubuntu Quantal): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in juju (Ubuntu Quantal): | |
importance: | High → Critical |
Changed in juju: | |
milestone: | none → 0.6 |
Changed in juju (Ubuntu Quantal): | |
milestone: | none → ubuntu-12.10 |
Changed in juju: | |
assignee: | nobody → Jim Baker (jimbaker) |
Changed in juju: | |
status: | Confirmed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju (Ubuntu Quantal): | |
status: | Confirmed → Fix Released |
After talking this through with a few folks, it looks like this may be fixed in some version of juju. Adding "juju-origin: ppa" to environments.yaml makes the problem go away.
The issue remains in the stock version of juju for precise.