Bug 700104

Summary: Beaker system that installs on 6.0 fails installation on 6.1.
Product: Red Hat Enterprise Linux 6 Reporter: Barry Donahue <bdonahue>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: rvykydal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-31 20:32:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
tar file of the files in /tmp
none
sys.log none

Description Barry Donahue 2011-04-27 13:33:47 UTC
Description of problem: The system (storageqe-02.rhts.eng.bos.redhat.com) is a system with 2 NICs on the motherboard and an Emulex 10Gb PCI adapter with 2 ports. On 6.1 the install stops and asks you to identify which NIC to use. It shouldn't be asking because we specify which NIC to use at install time.

ksdevice=00:23:7D:E6:0A:78 

I specify using eth0 but once anaconda starts up, eth0 is bumped to eth2 and anaconda can't find it. Or at least the install fails.

Looking for installation images on CD device /dev/sr0Running anaconda 13.21.104, the Red Hat Enterprise Linux system installer - please wait.
Examining storage devices
The following error was found while parsing the kickstart configuration file:

The following problem occurred on line 10 of the kickstart file:

The provided network interface eth2 does not exist



Version-Release number of selected component (if applicable):

   Any 6.1 release.

How reproducible:

   Every time.




Additional info:

Comment 2 Radek Vykydal 2011-04-27 13:59:41 UTC
Please attach the kickstart file, /tmp/syslog, /tmp/anaconda.log, and /tmp/ifcfg.log if existing.

The reason for eth2 device specified in kickstart not being found might be the new biosdevname feature (renaming devices to emX and pciXpY). As far as I know, the feature can be turned on/off by biosdevname=[0,1] boot flag, and it is on by default on machines where SMBIOS >= 2.6 is found.

Comment 3 Barry Donahue 2011-04-27 21:10:03 UTC
It dies so early in the process that beaker doesn't collect any files. I'll try a manual install tomorrow.

Comment 4 RHEL Program Management 2011-04-28 06:02:05 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Barry Donahue 2011-04-28 16:55:03 UTC
Created attachment 495604 [details]
tar file of the files in /tmp

I did the install manually and this a tar ball of the files.

Comment 6 Radek Vykydal 2011-04-29 12:34:35 UTC
Thanks for the logs, /tmp/syslog is missing but I think in this case I can tell what is happening here.

Anaconda detects two network devices - eth0 and eth1, while in your kickstart file you specify eth2 which anaconda can't find and therefore asks in UI to choose one of detected files. In 6.0 network wouldn't be reconfigured with values from kickstart network commands file once the network had been activated to obtain the kickstart file. This was a regression wrt rhel 5 which was fixed rhel 6.1.

So in your case you need to fix the device name of this line in kickstart file:

network --device eth2 --bootproto dhcp --onboot yes

Another question is whether eth2 should be detected and why it was not, for that I'd need to see /tmp/syslog but I'd guess that it was not detected in rhel 6.0 either.

Comment 7 Radek Vykydal 2011-05-24 09:05:40 UTC
Are my abductions from comment #6 correct? Or should eth2 be detected? If so, could you please attach /tmp/syslog?

Comment 8 Barry Donahue 2011-05-24 13:18:46 UTC
   I'll rerun the test and get the syslog. This system contains the 2 NICs on the mother board and an Intel Niantic 10Gb, dual port CNA. How they are discovered seems to change release to release.

Comment 9 Radek Vykydal 2011-05-25 10:46:40 UTC
Setting needinfo until the syslog arrives.

Comment 10 Barry Donahue 2011-05-25 19:33:14 UTC
Created attachment 500927 [details]
sys.log

Here is the sys.log from Beaker job #89239

Comment 11 Radek Vykydal 2011-05-27 07:33:25 UTC
According to syslog only eth0 and eth1 devices are initialized by kernel, therefore anaconda is correct complaining about eth2 specified in kickstart not found.

Kernel failing to initialize the Emulex card (snipped from comment #10):

12:27:18,126 INFO kernel:be2net 0000:0e:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
12:27:18,126 DEBUG kernel:be2net 0000:0e:00.0: setting latency timer to 64
12:27:18,249 DEBUG kernel:  alloc irq_desc for 32 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 32 for MSI/MSI-X
12:27:18,249 DEBUG kernel:  alloc irq_desc for 33 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 33 for MSI/MSI-X
12:27:18,249 DEBUG kernel:  alloc irq_desc for 34 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 34 for MSI/MSI-X
12:27:18,249 DEBUG kernel:  alloc irq_desc for 35 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 35 for MSI/MSI-X
12:27:18,249 DEBUG kernel:  alloc irq_desc for 36 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 36 for MSI/MSI-X
12:27:18,249 DEBUG kernel:  alloc irq_desc for 37 on node -1
12:27:18,249 DEBUG kernel:  alloc kstat_irqs on node -1
12:27:18,249 DEBUG kernel:be2net 0000:0e:00.0: irq 37 for MSI/MSI-X
12:27:18,503 WARNING kernel:be2net 0000:0e:00.0: Error in cmd completion - opcode 90, compl 2, extd 30
12:27:18,901 INFO kernel:be2net 0000:0e:00.0: PCI INT A disabled
12:27:18,901 ERR kernel:be2net 0000:0e:00.0: Emulex OneConnect 10Gbps NIC initialization failed
12:27:18,901 WARNING kernel:be2net: probe of 0000:0e:00.0 failed with error -1
12:27:18,901 INFO kernel:be2net 0000:0e:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
12:27:18,901 DEBUG kernel:be2net 0000:0e:00.1: setting latency timer to 64
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 32 for MSI/MSI-X
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 33 for MSI/MSI-X
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 34 for MSI/MSI-X
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 35 for MSI/MSI-X
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 36 for MSI/MSI-X
12:27:18,975 DEBUG kernel:be2net 0000:0e:00.1: irq 37 for MSI/MSI-X
12:27:19,227 WARNING kernel:be2net 0000:0e:00.1: Error in cmd completion - opcode 90, compl 2, extd 30
12:27:19,631 INFO kernel:be2net 0000:0e:00.1: PCI INT B disabled
12:27:19,631 ERR kernel:be2net 0000:0e:00.1: Emulex OneConnect 10Gbps NIC initialization failed
12:27:19,631 WARNING kernel:be2net: probe of 0000:0e:00.1 failed with error -1

Comment 12 David Cantrell 2011-05-31 20:32:39 UTC
Closing as NOTABUG per comment #11.