Bindings configuration doesn't work with juju 2.2

Bug #1696765 reported by David Lawson
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-deployer
Confirmed
Low
Unassigned

Bug Description

I can only confirm this behavior with juju 2.2 but I was never able to get bindings to work with that version, no matter what format I tried specifying them in. I ended up getting past this by expressing bindings as constraints, which works fine. I suspect that this is a quoting issue, juju 2.2 expects bindings as --bindings "default-binding endpoint=other-binding" and it doesn't look like the code will result in the correct quoting, but that's just a guess.

As an aside, if there were an easy way to get the juju command lines that deployer is running out of deployer, with some kind of extra verbose debugging option, that would have made diagnosing this issue immensely easier.

tags: added: 4010
Revision history for this message
Alvaro Uria (aluria) wrote :

On diff from bzr210 and bzr212, "--bind" uses "=" when it should use ":"

See diff: http://pastebin.ubuntu.com/24957168/
See docs: https://jujucharms.com/docs/2.1/charms-deploying#deploying-to-spaces

We will test such a change, and confirm.
"""
bindings_list.append("{}:{}".format(key, value))
"""

Revision history for this message
David Lawson (deej) wrote :

--bind actually uses =, the docs are wrong, see https://github.com/juju/docs/issues/1931

Alvaro Uria (aluria)
tags: added: canonical-bootstack
Michał Ajduk (majduk)
tags: removed: 4010
Tom Haddon (mthaddon)
Changed in juju-deployer:
status: New → Confirmed
importance: Undecided → Low
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.