Bindings configuration doesn't work with juju 2.2
Bug #1696765 reported by
David Lawson
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=
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 |
tags: | added: canonical-bootstack |
tags: | removed: 4010 |
Changed in juju-deployer: | |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
On diff from bzr210 and bzr212, "--bind" uses "=" when it should use ":"
See diff: http:// pastebin. ubuntu. com/24957168/ /jujucharms. com/docs/ 2.1/charms- deploying# deploying- to-spaces
See docs: https:/
We will test such a change, and confirm. list.append( "{}:{}" .format( key, value))
"""
bindings_
"""