Many thanks for fixing this! I filed bug 1567874 with a small leftover.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567440
Title:
debconf for bridge configuration is confusing and too
This bug was fixed in the package lxd - 2.0.0~rc9-0ubuntu3
---
lxd (2.0.0~rc9-0ubuntu3) xenial; urgency=medium
* More lxdbr0 tweaks:
- Generate a random IPv4 and IPv6 subnet and pre-fill the questions
with it at interactive configuration time. (LP: #1567440)
- Point
Ok, so just had a pretty good chat with Martin, conclusion is that we will:
- Make use of the debconf "seen" flag to check whether we are running
interactively or not
- If running interactively and no configuration was previously set, set both
IPv4 and IPv6 to "yes"
- Show a warning message
You are right that we don't actually have to ask the user to pre-fill
some random values. We should however show a warning explaining that
those values may conflict with their network and that they should take a
close look at them.
So basically the change I would do is: When selecting Yes to the
** Changed in: lxd (Ubuntu)
Importance: Undecided => High
** Changed in: lxd (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/1567440
Title:
debconf for
> with a pretty big warning that if you are somehow using those subnets,
this will break your network.
But the .config script can tell if there's an existing interface/network
with that subnet?
> That would mean two more questions though
Why two new ones? I think we should repurpose the current
We could add a "seed with default values" option for both IPv4 and IPv6
which sets everything to the suggested values with a pretty big warning
that if you are somehow using those subnets, this will break your
network.
--
You received this bug notification because you are a member of Ubuntu
That would mean two more questions though (one for IPv4, one for IPv6)
as we really should still show all the values to the user so they can
check that they are sane and have a chance to change them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> We also can't default on any subnet, that's the whole point of lxdbr0,
defaulting on a subnet has been breaking user network in the past
How is that, OOI? postinst/debconf/etc. should certainly check if
there's an existing 10.0.3.x network already, and not set up a default
lxdbr0 then (or use a
I'll try to find a way to get debconf to empty the bridge name when
switching from a LXD configured bridge to you providing one. The same
debconf variable is used for both which is why you saw lxdbr0 pre-seeded
in there, but I should be able to detect that case and have it emptied.
--
You
> We can't do what you suggest because LXD is pre-installed in a bunch
of images and picking a default subnet there is going to break
networking.
No, no, I don't mean on package install time, but at the time you run
"dpkg-reconfigure lxd" . I understand that/why we can't set up the
bridge by
Now that I read the initial debconf note three times I think I know what
the difference between "yes" and "no" is. But "Do you want LXD to setup
a network bridge for you?" does not encourage me to select "no", and the
default is "yes" too.
But "yes" leads you into this trap of having to specify
We can't do what you suggest because LXD is pre-installed in a bunch of
images and picking a default subnet there is going to break networking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567440
Hmm, the fact that you had lxcbr0 was probably a bug in a previous
migration script, it should have been lxdbr0.
We can't use lxcbr0 because on most systems lxc1 will be marked for
auto-removal after upgrading to the lxd version which brings lxdbr0, so
at configuration time the bridge would still
As for the first debconf question, it was a request from
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1566764 but it sounds
like you got the updated prompt already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
After installing current lxd (I purged it before, so any previous
- configuration should be done) the networking in the containers does not
+ configuration should be gone) the networking in the containers does not
work at all, not even with apt-get update (as it seems
It turns out that if I answer "no" to the first question, it only asks
me about using an existing bridge. I leave the default lxcbr0, then I
get networking back in containers.
So *if* lxcbr0 exists, I suggest using that by default in lxd -- I can't
imagine a situation where you would *not* want
17 matches
Mail list logo
