Bridge not created if bind9 is on
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Triaged
|
Medium
|
LaMont Jones | ||
lxc (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
lxd (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates the bridge.
Expected result: LXC will create the bridge, even if bind9 is on.
---
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2013-06-29 (110 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
Package: lxc
PackageArchitec
ProcCmdline: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
bind9utils 1:9.9.2.
apparmor 2.8.0-0ubuntu11
Tags: raring
Uname: Linux 3.8.0-31-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.
mtime.conffile.
tags: | added: landscape |
Changed in lxd (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in bind9 (Ubuntu): | |
milestone: | none → xenial-updates |
assignee: | nobody → LaMont Jones (lamont) |
Changed in lxd (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in lxc (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in bind9 (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in lxc (Ubuntu): | |
status: | Triaged → Won't Fix |
Thanks for reporting this bug.
Note that another workaround should be to put 'listen-on { ! 10.0.3.1 };' in the named.conf.
However, when I tried to reproduce this in saucy I could not, so I wonder if there is something specific in your configuration customizations which caused this.
Could you please re-enable bind and then run 'apport-collect 1240757'? Hopefully apport will report customizations.