Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fix not_networks for MAAS 1.9 #6528
Conversation
added some commits
Nov 1, 2016
voidspace
changed the base branch from
staging
to
develop
Nov 2, 2016
|
!!build!! |
voidspace
commented
Nov 2, 2016
|
!!build!! |
|
LGTM and QA OK on MAAS Version 1.9.4+bzr4592-0ubuntu1 (14.04.1) - observed in /var/log/maas/maas.log during juju bootstrap with 2 negative spaces constraints:
|
voidspace
commented
Nov 3, 2016
|
!!build!! |
voidspace
commented
Nov 3, 2016
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit ac4cbf5
into
juju:develop
Nov 3, 2016
1 check failed
github-check-merge-juju
Built PR, ran unit tests, and tested LXD deploy.
Details
voidspace
referenced this pull request
Nov 3, 2016
Merged
Fix not_networks parameter (negative space constraints) for MAAS 1.9 #6541
added a commit
that referenced
this pull request
Nov 4, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
voidspace commentedNov 2, 2016
With MAAS 1.9 the not_networks parameter (for negative space constraints) should be specified as multiple values, not a comma separated list.
Fixes bug #1636969
There is a separate PR (against gomaasapi) to fix the same issue for MAAS 2.x where "not_networks" becomes "not_subnets".
QA
Bootstrap specifying negative space constraints. Juju must honour those constraints in the machine it picks.