touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #131448
[Bug 1537136] Re: ISST-LTE: no network after install due to interface order change
** Description changed:
== Comment: #0 - Chanh H. Nguyen <chnguyen@xxxxxxxxxx> - 2015-12-10 20:32:29 ==
We use the network to install Ubuntu 14.04.4 version. The installation is successful but then there is no network after system reboot in post install. Checking the network and I saw the order of interface are changed. This is causing no network at all.
There is 2 cards (Houston 4ports & Mellanox 2 ports). We are using the Mellanox interface for this installation.
At the installation menu, we select this interface eth2 (mellanox card)
??????????????????????? [!!] Configure the network ????????????????????????
? ?
? Your system has multiple network interfaces. Choose the one to use as ?
? the primary network interface during the installation. If possible, ?
? the first connected network interface found has been selected. ?
? ?
? Primary network interface: ?
? ?
? eth0: Emulex Corporation OneConnect NIC (Lancer) ?
? eth1: Emulex Corporation OneConnect NIC (Lancer) ?
? eth2: Mellanox Technologies MT27500 Family [ConnectX-3] ?
? eth3: Mellanox Technologies MT27500 Family [ConnectX-3] ?
? eth4: Emulex Corporation OneConnect NIC (Lancer) ?
? eth5: Emulex Corporation OneConnect NIC (Lancer) ?
? ?
? <Go Back> ?
? ?
???????????????????????????????????????????????????????????????????????????
After install,
root@monklp3:~# ifconfig
eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2368 (2.3 KB) TX bytes:2368 (2.3 KB)
root@monklp3:~# ifconfig -a|grep eth
eth0 Link encap:Ethernet HWaddr 00:00:c9:d1:be:26
eth1 Link encap:Ethernet HWaddr 00:00:c9:d1:be:27
eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28
eth3 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b0
eth4 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b1
eth5 Link encap:Ethernet HWaddr 00:00:c9:d1:be:29
root@monklp3:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth2
iface eth2 inet dhcp
root@monklp3:~# dmesg |grep "eth"
[ 0.950725] ibmveth: IBM Power Virtual Ethernet Driver 1.05
[ 0.950735] ehea: IBM eHEA ethernet device driver (Release EHEA_0107)
[ 9.810472] mlx4_en: eth3: Link Up
[ 40.554271] be2net 0001:80:00.2 eth2: Link is Down
[ 40.560738] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
root@monklp3:~#
The mellanox inteface is now on eth3 but on the /etc/network/interface
file, it is set on eth2.
-
SRU TEST CASE:
--------------
- * Do a netboot install in a VM or machine with more than one NIC. If you use a VM, take care to not use the default MAC addresses as they are blacklisted from the persistent net generator. E. g. use "-net nic,model=virtio,macaddr=A2:A2:A2:12:34:XX" with QEMU.
- * In the d-i environment, switch to a console with Alt+F2 after the base system got installed.
- * With current trusty, there is no /etc/udev/rules.d/70-persistent-net.rules and thus it also does not exist in /target/.
- * With the proposed update, /etc/udev/rules.d/70-persistent-net.rules should exist and be copied to /target/etc/udev/rules.d/ as well.
+ * Do a netboot install in a VM or machine with more than one NIC. If you use a VM, take care to not use the default MAC addresses as they are blacklisted from the persistent net generator. E. g. use "-net nic,model=virtio,macaddr=A4:4E:31:12:34:XX" with QEMU.
+ * In the d-i environment, switch to a console with Alt+F2 after the base system got installed.
+ * With current trusty, there is no /etc/udev/rules.d/70-persistent-net.rules and thus it also does not exist in /target/.
+ * With the proposed update, /etc/udev/rules.d/70-persistent-net.rules should exist and be copied to /target/etc/udev/rules.d/ as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1537136
Title:
ISST-LTE: no network after install due to interface order change
Status in debian-installer package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in debian-installer source package in Trusty:
Fix Committed
Status in systemd source package in Trusty:
Fix Committed
Bug description:
== Comment: #0 - Chanh H. Nguyen <chnguyen@xxxxxxxxxx> - 2015-12-10 20:32:29 ==
We use the network to install Ubuntu 14.04.4 version. The installation is successful but then there is no network after system reboot in post install. Checking the network and I saw the order of interface are changed. This is causing no network at all.
There is 2 cards (Houston 4ports & Mellanox 2 ports). We are using the Mellanox interface for this installation.
At the installation menu, we select this interface eth2 (mellanox card)
??????????????????????? [!!] Configure the network ????????????????????????
? ?
? Your system has multiple network interfaces. Choose the one to use as ?
? the primary network interface during the installation. If possible, ?
? the first connected network interface found has been selected. ?
? ?
? Primary network interface: ?
? ?
? eth0: Emulex Corporation OneConnect NIC (Lancer) ?
? eth1: Emulex Corporation OneConnect NIC (Lancer) ?
? eth2: Mellanox Technologies MT27500 Family [ConnectX-3] ?
? eth3: Mellanox Technologies MT27500 Family [ConnectX-3] ?
? eth4: Emulex Corporation OneConnect NIC (Lancer) ?
? eth5: Emulex Corporation OneConnect NIC (Lancer) ?
? ?
? <Go Back> ?
? ?
???????????????????????????????????????????????????????????????????????????
After install,
root@monklp3:~# ifconfig
eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2368 (2.3 KB) TX bytes:2368 (2.3 KB)
root@monklp3:~# ifconfig -a|grep eth
eth0 Link encap:Ethernet HWaddr 00:00:c9:d1:be:26
eth1 Link encap:Ethernet HWaddr 00:00:c9:d1:be:27
eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28
eth3 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b0
eth4 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b1
eth5 Link encap:Ethernet HWaddr 00:00:c9:d1:be:29
root@monklp3:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth2
iface eth2 inet dhcp
root@monklp3:~# dmesg |grep "eth"
[ 0.950725] ibmveth: IBM Power Virtual Ethernet Driver 1.05
[ 0.950735] ehea: IBM eHEA ethernet device driver (Release EHEA_0107)
[ 9.810472] mlx4_en: eth3: Link Up
[ 40.554271] be2net 0001:80:00.2 eth2: Link is Down
[ 40.560738] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
root@monklp3:~#
The mellanox inteface is now on eth3 but on the /etc/network/interface
file, it is set on eth2.
SRU TEST CASE:
--------------
* Do a netboot install in a VM or machine with more than one NIC. If you use a VM, take care to not use the default MAC addresses as they are blacklisted from the persistent net generator. E. g. use "-net nic,model=virtio,macaddr=A4:4E:31:12:34:XX" with QEMU.
* In the d-i environment, switch to a console with Alt+F2 after the base system got installed.
* With current trusty, there is no /etc/udev/rules.d/70-persistent-net.rules and thus it also does not exist in /target/.
* With the proposed update, /etc/udev/rules.d/70-persistent-net.rules should exist and be copied to /target/etc/udev/rules.d/ as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1537136/+subscriptions
