That was before a maas 1.8 user reported #1531868, wherein maas tries to reload DNS for changes, and fails utterly to do so, because the named.conf is invalid.
I think that this bugfix warrants reconsideration since it's breaking maas 1.8 users in the field.
That was before a maas 1.8 user reported #1531868, wherein maas tries to reload DNS for changes, and fails utterly to do so, because the named.conf is invalid.
I think that this bugfix warrants reconsideration since it's breaking maas 1.8 users in the field.