[Bug 1667790] Re: PXE Installation Failure - Ubuntu14.04.5

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: debian-installer (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1667790

Title:
  PXE Installation Failure - Ubuntu14.04.5

Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  Steps to Reproduce: 
  1.Boot to BIOS setup menu to change to UEFI mode.   
  2.Boot form PXE of NIC. 
  3.Select Ubuntu 14.04.5 for the installing. 
  4.then, there's an error message appeared, as in the attachment (/Error_Messages)

  When symptom occurs(network configuration failure during
  installation), our NIC’s network function still works, i.e., it still
  can ping to PXE server.

  Logs and trace in the attachment.
            /BB_100G:  failed  case 
                      Install: system installation logs. “syslog” contains more detailed debug message.
                      bb.pcapng: network trace. 
                      dmesg.txt: output of system #dmesg
                      ip_address.txt: output of #ip address show
            /Intel_1G: pass case
                      dmesg.txt
                      ip_address.txt
                      intel.zip: zipped network trace.

  Quick summary for the test  setup:  
  	General PXE server can be used. I referred this page to setup ubuntu 14.04 PXE installation( http://www.tecmint.com/add-ubuntu-to-pxe-network-boot/ )
  	Add below entry into PXE installation menu “default” file(/var/lib/tftpboot/pxelinux.cfg/default)

       label  linux
                  menu label ^Install Ubuntu 14.04 x64
                 kernel ubuntu-14.04/ubuntu-installer/amd64/linux
                  append ks=http://192.168.10.100/linux/ks.cfg vga=normal initrd=ubuntu-14.04/ubuntu-installer/amd64/initrd.gz ramdisk_size=16432 root=/dev/rd/0 rw netcfg/choose_interface=p4p1 –

  	The highlighted texts in red need to be changed according to your server. 
  	Change p4p1 to the interface name shown on your DUT during installation, in my case p4p1 is used.  

         Copy all files on Ubuntu 14.04.05 CD to
  /var/www/html/Ubuntu1404_x64 for http installation

         Put the kickstart configuration “ks.cfg” to
  /var/www/html/linux

  	Put the initrd.gz into /var/lib/tftpboot/ubutu-14.04/Ubuntu-installer/amd64 
  	Please note that the initrd.gz had been injected with our qed.ko and qede.ko. 
  	The Ubuntu 14.04 netboot I am using is downloaded from  http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-amd64/current/images/xenial-netboot/ , where amd64 xenial’s 4.4 HWE kernel is used in my setup.  
  	I refereed the below pages to inject our drivers.
  http://tomoconnor.eu/blogish/hacking-initrdgz-ubuntu-netboot-installer/#.WLAHUctPo5s 
  https://ubuntuforums.org/showthread.php?t=1843448 

  We see a bunch of failures in syslogs. could they be causing this ? [We have seen these failures could cause installation issues on some Ubuntu bugs]
  There are no failures specific to driver logs – link etc. also shows connected for driver interface.

  We saw wire shark traces of BB_100G and saw lot of TFTP [Trivial file transfer protocol ] packets which looks quite same as intel traces.
  Is this issue always reproducible or it got passed ever ? 

  Feb 24 06:31:39 netcfg[3724]: WARNING **: Couldn't read Wpasupplicant pid file, not trying to kill.
  Feb 24 06:31:39 netcfg[3724]: DEBUG: Flushing addresses and routes on interface: p4p1
  Feb 24 06:31:39 netcfg[3724]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline

  Feb 24 06:31:48 netcfg[3724]: DEBUG: rdisc6 line: Soliciting ff02::2 (ff02::2) on p4p1...
  Feb 24 06:31:48 netcfg[3724]: DEBUG: rdisc6 line: Timed out.
  Feb 24 06:31:48 netcfg[3724]: DEBUG: rdisc6 line: No response.
  Feb 24 06:31:48 netcfg[3724]: DEBUG: rdisc6 parsing finished
  Feb 24 06:31:48 netcfg[3724]: DEBUG: Stopping rdnssd, PID 3747
  Feb 24 06:31:48 netcfg[3724]: DEBUG: No RA received; attempting IPv4 autoconfig
  Feb 24 06:31:48 netcfg[3724]: WARNING **: Started DHCP client; PID is 3787

  Feb 24 06:31:51 netcfg[3724]: DEBUG: Network config complete
  Feb 24 06:31:51 netcfg[3724]: DEBUG: No interface given; clearing /etc/network/interfaces
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Writing informative header
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Success!
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Writing loopback interface
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Success!
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Writing DHCP stanza for p4p1
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Writing wireless options for p4p1
  Feb 24 06:31:51 netcfg[3724]: DEBUG: Success!
  Feb 24 06:31:52 main-menu[2545]: WARNING **: Configuring 'netcfg' failed with error code 139
  Feb 24 06:31:52 main-menu[2545]: WARNING **: Menu item 'netcfg' failed.
  Feb 24 06:31:52 kernel: [   62.915859] netcfg[3724]: segfault at 0 ip 00007f1ab154e34f sp 00007ffc781aec78 error 4 in libc.so.6[7f1ab14b1000+1ba000]

  
  It look like the network configuration failure.
  But, We’d tried other vendors’ NICs(Intel and Broadcom), their NICs don’t have this failure under the same PXE environment... 
  The major difference is these NICs have had inbox drivers in Ubuntu netboot(initrd.gz).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1667790/+subscriptions