Activity log for bug #1567440

Date Who What changed Old value New value Message
2016-04-07 13:08:11 Martin Pitt bug added bug
2016-04-07 13:19:03 Martin Pitt description After installing current lxd (I purged it before, so any previous configuration should be done) the networking in the containers does not work at all, not even with apt-get update (as it seems it can't even reach the default Debian mirror). So I went with "dpkg-reconfigure lxd" as advertised on the postinst note. The first question is ambiguous: "Choosing this option will let you configure the default LXD bridge to your liking. If you would rather not have LXD do this for you, then you will be asked whether you want to use an existing bridge or just do everything manually." The default is "yes", so I picked that as I indeed want some default LXD bridge. Now it asks me for "a valid network interface name", defaulting to lxcbr0. This might be because I have lxc1 still installed, or this is an upgrade or so, but either way, using lxcbr0 seems totally fine -- that's what is already preconfigured and has worked well for a long time and allows me to connect lxc and lxd containers. So I go with "lxcbr0", but now it asks me a gazillion questions about IP addresses, masks, ask me to come up with a valid IPv6 address (how do I do that, and pick one that's valid, private, and not overlapping with something else?) None of these questions have defaults. Moreover, lxcbr0 is already configured, so if I would put in different values then lxc and lxd probably just stomp on each other's feet? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxd 2.0.0~rc8-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: i3 Date: Thu Apr 7 15:01:25 2016 EcryptfsInUse: Yes SourcePackage: lxd UpgradeStatus: No upgrade log present (probably fresh install) After installing current lxd (I purged it before, so any previous configuration should be gone) the networking in the containers does not work at all, not even with apt-get update (as it seems it can't even reach the default Debian mirror). So I went with "dpkg-reconfigure lxd" as advertised on the postinst note. The first question is ambiguous: "Choosing this option will let you configure the default LXD bridge to your liking. If you would rather not have LXD do this for you, then you will be asked whether you want to use an existing bridge or just do everything manually." The default is "yes", so I picked that as I indeed want some default LXD bridge. Now it asks me for "a valid network interface name", defaulting to lxcbr0. This might be because I have lxc1 still installed, or this is an upgrade or so, but either way, using lxcbr0 seems totally fine -- that's what is already preconfigured and has worked well for a long time and allows me to connect lxc and lxd containers. So I go with "lxcbr0", but now it asks me a gazillion questions about IP addresses, masks, ask me to come up with a valid IPv6 address (how do I do that, and pick one that's valid, private, and not overlapping with something else?) None of these questions have defaults. Moreover, lxcbr0 is already configured, so if I would put in different values then lxc and lxd probably just stomp on each other's feet? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxd 2.0.0~rc8-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: i3 Date: Thu Apr 7 15:01:25 2016 EcryptfsInUse: Yes SourcePackage: lxd UpgradeStatus: No upgrade log present (probably fresh install)
2016-04-07 14:11:53 Dustin Kirkland  lxd (Ubuntu): importance Undecided High
2016-04-07 14:11:55 Dustin Kirkland  lxd (Ubuntu): status New Confirmed
2016-04-07 23:51:56 Launchpad Janitor lxd (Ubuntu): status Confirmed Fix Released