Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Missing calls to parse_constraints in model.py #36
Comments
|
Fixing this should be as simple as finding instances of the string "constraints" in model.py, and replacing where appropriate with parse_constraints(constraints). |
|
Working on this now. It looks like it's not as simple as naively adding parse_constraints -- I get errors on the core side, and may have to make the logic in parse_constraints more sophisticated. :-/ |
|
This bug has unveiled a whole tangle of fun issues:
|
|
Update: I've addressed point 4, from the previous comment, in a branch, but I'm now getting a failure getting haproxy up. Either there's a bug in 3 (Placement objects aren't making lxd containers correctly), or we're missing something that haproxy needs (it looks like it's complaining about missing a config value). Will continue to work on this ... |
|
A lot of this issue was fixed in #37 The remaining issue is open in launchpad here: https://bugs.launchpad.net/juju-core/+bug/1651260 Will open a new issue here if we need to do more work after addressing the launchpad bug. |
petevg commentedDec 14, 2016
Looks like we missed some places where we need to parse constraints that we get back from the planner in in model.py.
To reproduce: