** Changed in: maas
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications
[Expired for MAAS because there has been no activity for 60 days.]
** Changed in: maas
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start
I think we need to solve this somehow.
I'm thinking that we could re-use the 'allow_dns' flag on subnets. If
it's False, we shouldn't listen on an address in that subnet.
I think it should be safe, since AFAIK, allow_dns is only used to
determine whether the address should be returned in the DHCP
Could you please confirm if commands provided by Adam in #10 work for
you?
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cann
** Changed in: bind9 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage no
Can you `lxc network set lxdbr0 dns.mode=none` adjusting for the name of
your bridge.
This will tell LXD to not manage DNS on the bridge, as per
https://github.com/lxc/lxd/blob/master/doc/networks.md.
Note you might also want to disable DHCP: `lxc network set lxdbr0
ipv4.dhcp=false` and `lxc netw
subbing to field high,
the workaround for a new snapped install MaaS seems to be to install Maas into
a container, but existing installs upgrading to Focal will run into this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This workaround doesnt seem to work for snapped maas applying the fix to
/var/snap/maas/current/bind/named.conf.options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service wh
MAAS is installing bind9 and configuring it for its own purposes - it
provides other config for bind, and it's perfectly reasonable to expect
maas to configure it to only listen on interfaces MAAS wants to provide
DNS services on.
** Changed in: maas
Status: Invalid => New
** Tags added: c
to add floating ip too as:
listen-on { 185.168.3.1; 185.168.3.5; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage
It seems not works on my side ( 18.04 ARM64). I have to add the
listening IP explicitly.
ubuntu@infra1:/etc/bind$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
ubuntu@infra1:/etc/bind$ uname -a
Linux infra1 4.15.0-4
Correction to my last comment (listen-on, not listen):
listen-on { !10.224.138.0/24; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is man
Adding these two lines (specifically the second line) to
/etc/bind/named.conf.options and restarting bind, should solve this for
you:
listen-on-v6 { none; };
listen { !10.224.138.0/24; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications about this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cann
This is actually a bug in the bind9 package, from what I understand. I
think LaMont is already giving it some thought.
** Also affects: bind
Importance: Undecided
Status: New
** No longer affects: bind
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Chan
17 matches
Mail list logo
