For the time being this is being addressed with "net.ifnames=0" in the
Wily and Xenial images.
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Package changed: ubuntu => cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483457
Title:
non-virtio devices get named with systemd "predictable network
interface names"
To m
Thanks Martin.
On Fri, Aug 21, 2015 at 10:39 AM, Martin Pitt
wrote:
> > Is it true that net.ifnames is now set to 1 by default in wily?
>
> Yes, see https://lists.ubuntu.com/archives/ubuntu-
> devel/2015-June/038786.html and /usr/share/doc/udev/NEWS.Debian.gz and
> /usr/share/doc/udev/README.Deb
> Is it true that net.ifnames is now set to 1 by default in wily?
Yes, see https://lists.ubuntu.com/archives/ubuntu-
devel/2015-June/038786.html and /usr/share/doc/udev/NEWS.Debian.gz and
/usr/share/doc/udev/README.Debian.gz .
A nd where is that value set? in systemd/udev binary?
It's the defaul
Martin, can you comment on this in particular?
> net.ifnames should be set to 0 by default IIUC[1]. It appears that
it's not set in the wily kernel used in this image. I don't know where
we configure/control the default value.
Is it true that net.ifnames is now set to 1 by default in wily? And
wh
Wrt. correctly handling multiple interfaces we should IMHO keep the
default net.ifnames. After all, providing stable names for cloud
instances and virtual machines with multiple interfaces was one of the
reasons why we switched to net.ifnames in the first place -- before, the
old udev rules had bla
It looks like this is only an issue when a non-virtual nic is presented,
i.e. e1000 vs virtio/hyper-v/xenbus/etc. My gut tells me tat
'net.ifnames=0' is the obvious choice as it would maintain ethX
regardless of the virtual hardware. But with out some guidance from the
foundations team, I am littl
Pitti, can you weigh in on the correct course of action here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483457
Title:
non-virtio devices get named with systemd "predictable network
interface
net.ifnames should be set to 0 by default IIUC[1]. It appears that it's
not set in the wily kernel used in this image. I don't know where we
configure/control the default value.
We don't see this issue with virtio-net nics because systemd considers
virtio numbers to be unstable[2] and doesn't ha
Lets get some input from pitti and foundations on how we really shoudl fix this.
At first it looks like "disable that new behavior", but I just want to think
that through as we dont want to fight indefinitely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Changed in: ubuntu
Assignee: (unassigned) => Ben Howard (utlemming)
** Changed in: ubuntu
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483457
Title:
n
12 matches
Mail list logo
