Comment 2 for bug 1513775

I've been looking at the CI logs here:

/job/maas-trusty-trunk-manual/802/artifact/results/artifacts/maas-logs/var/log/

Is it possible that a version of MAAS without the patch was installed on this machine before it was upgraded to the current version?

I found this in the logs:

Nov 6 13:56:15 autopkgtest named[11375]: loading configuration from '/etc/bind/named.conf'
Nov 6 13:56:15 autopkgtest named[11375]: /etc/bind/maas/named.conf.options.inside.maas:2: 'dnssec-validation' redefined near 'dnssec-validation'
Nov 6 13:56:15 autopkgtest named[11375]: loading configuration: already exists

...

Nov 6 13:58:32 autopkgtest named[12695]: loading configuration from '/etc/bind/named.conf'
Nov 6 13:58:32 autopkgtest named[12695]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Nov 6 13:58:32 autopkgtest named[12695]: using default UDP/IPv4 port range: [1024, 65535]
Nov 6 13:58:32 autopkgtest named[12695]: using default UDP/IPv6 port range: [1024, 65535]
Nov 6 13:58:32 autopkgtest named[12695]: listening on IPv6 interfaces, port 53
Nov 6 13:58:32 autopkgtest named[12695]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 6 13:58:32 autopkgtest named[12695]: listening on IPv4 interface eth1, 10.245.136.6#53

To me, this seems to be a temporary condition which resolved itself in a couple of minutes. (possibly a version of MAAS without this fix was on the server, then it was upgraded?)