One of UA customer runs into this issue at 20.04.
The customer is not using PXE boot to install server. The customer is using a
customized ISO to install the server, so the comment #18 is not applicable.
For example, the preseed is like
d-i netcfg/choose_interface select auto
d-i netcfg/disable
Is there any plan/timetable fixing this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg/choose_interface=auto fails to find the right interface
To manage notifications abo
netcfg/choose_interface=auto does work in 22.04 installers. When setting
to manual, any WiFi configuration is ignored (even after selecting the
appropriate entry), but auto and a valid config does indeed connect to
the predefined network.
--
You received this bug notification because you are a me
How to add IPAPPEND 2 into /var/lib/tftpboot/grub/grub.cfg ? What option
for http://archive.ubuntu.com/ubuntu/dists/bionic-
updates/main/uefi/grub2-amd64/current/grubnetx64.efi.signed ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
The IPAPPEND solution is only useful if netbooting. What about if you
are not netbooting, netcfg picks enp10s0 instead of enp7s0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg/c
I can confirm that adding "IPAPPEND 2" in my pxe config has fixed the
issue for me on Ubuntu 18.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg/choose_interface=auto fails to
Ubuntu 16.04.x must add these two companions to the APPEND option
only netcfg/choose_interface=auto is not work , must be added IPAPPEND 2
成功的tftp/default
DEFAULT ubuntu16.04
LABEL ubuntu16.04
KERNEL http://xxx.com/linux
APPEND initrd=http://xxx.com/initrd.gz auto=true priority=critical
netcfg
I can also confirm this bug is still happening with the Ubuntu 18.04.2
installer. Using BOOTIF and "netcfg/choose_interface=auto" the installer
defaults to using eno1 (first interface in the list). These machines all
have an external network card they use the PXE boot.
I see the following messages
I can also confirm this is a bug. We are using Cobbler to netboot
systems (RedHat and Ubuntu). The RedHat systems have no problem using
PXE or iPXE with multiple NICs. Ubuntu 16.04 *seems* to work with PXE,
but fails during DHCP with iPXE chainloading.
I believe the issue is that the standard PXE
following script gives a working workaround for ubuntu 16 and debian 9:
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/56679/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Titl
Did not wrote - also affects Ubuntu 16.04 LTS, same as Debian 9 - no
preseeding possible with multiple NICs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg/choose_interface=auto f
I can confirm that this Bug is again present in Debian 9.
Motherboard is Asus AB350 Gaming K4 P2.60
Internal NIC is detected as enp10s0 (nr. 2 in list by `ip address show`) (no
wire plugged)
External NIC is detected as enp7s0 (nr. 3 in list by `ip address show`) (wire
plugged)
Debian 9 tries to
How has this issue been going on since 2011 with no fix to make
`interface=auto` work? Does anyone know where the code is that
implements this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Tit
This bug made a lots of pain for me, but I've found workaround.
As cloudbuilders told option "netcfg/choose_interface=auto" still not working,
and unfortunately BOOTIF=01-${mac-with-hyphens} is not working too.
There is undocumented feature in netcfg package. Option
"netcfg/choose_interface" acce
@operations-8, We had the same issue with Ubuntu 14.04.0, now that I'm
using Ubuntu 14.04.5 I don't have these issues anymore. HTH.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg
I'm having the same problem. We have a farm of 2000+ boxes, and
everytime I try to re-install a box, we need to check whether it will
boot from eth0 or eth1, to manually add that to txt.cfg.
The option: "netcfg/choose_interface=auto" it's not working. It will
only try dhclient on one interface onl
For anyone else stuck on this, the workaround is to pass
"netcfg/choose_interface=auto" to your kernel.
If you're using cobbler, just `cobbler distro edit --name=
--kopts="netcfg/choose_interface"`
This bug should still be fixed though.
--
You received this bug notification because you are a me
Confirming that this is still a bug.
Also chiming in to say that specifying the interface isn't a viable
solution for everyone, especially for massive automated installs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Colin, with all the respect, but I think it rather should be treated
with some higher priority. I am currently trying to deploy a batch of
new servers and because of this issue, the process cannot be fully
automated - it keeps asking me to choose networking interface, no matter
what value is assign
I'm told out of band that the fix for bug 56679 should be sufficient to
resolve this in practice. The link detection bug hasn't gone away, so
I'm going to leave this bug open, but I'm unassigning it since it
doesn't sound as though it needs to be treated with any particular
priority. Leave a comm
BTW, the debian bug to address the solution proposed in the bug above
(with a patch provided) is http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=615600.
** Bug watch added: Debian Bug tracker #615600
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615600
--
You received this bug notificat
I'm thinking if netcfg properly supported mac address designation, then
we wouldn't need to hack the "=auto" approach to handle nics that don't
report link status. Would the workaround in
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/56679 help until
we resolve this?
--
You received this
** Changed in: netcfg (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713385
Title:
netcfg/choose_interface=
Natty doesn't seem to work any better, unfortunately.
This is on a Dell PowerEdge 2950 with two BCM5708 onboard NICs and a
dual-port Intel 82571EB expansion card. PCI IDs of the network
controllers:
~ # lspci -n | grep ' 0200:'
05:00.0 0200: 14e4:164c (rev 11)
09:00.0 0200: 14e4:164c (rev 11)
0c
24 matches
Mail list logo
