Bug 717842

Summary: can't install blade with RHEL5.7_snap 5 over network
Product: Red Hat Enterprise Linux 5 Reporter: IBM Bug Proxy <bugproxy>
Component: anacondaAssignee: Ales Kozumplik <akozumpl>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 5.7CC: akozumpl, jkachuck, jzeleny, mbanas
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-30 14:08:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 684940    
Attachments:
Description Flags
The screen shot and /tmp/anaconda.log and /tmp/syslog on ahi09(7998-61X) none

Description IBM Bug Proxy 2011-06-30 07:01:44 UTC 
---Problem Description---
P6 Blade JS22(7998-61X)  Installing RHEL5.7_Snap5 after the choose English menu.
choose HTTP install type:
Unable to find any devices of the type needed for this installation type.  Would you like to manually select your driver or use a driver disk.

This has not happened on previous snap version from what I am researching from my teammates:

---uname output---
I can't get that far.
 
Machine Type = 7998-61X- 
 
---Steps to Reproduce---
 bladecenter is http://xxx.ibm.com
in a dos prompt telnet to ahi.upt  run env -T blade[9]     console -o

reboot machine 
catch in SMS menu
select 5. boot options
    network
        port 2
            select 2 for normal install

At boot prompt select tab then type in rhel5-u7  then press enter
watch the bootp packets come across the screen.
   English
        http
             then you will see the message about the ethernet  device driver not being found

 
---Installation and Packaging Component Data--- 
Install disk info: didn't get that far
 
Install method: http  fails for ftp and nfs also
 
Install ISO Information: 2.6.18-269.el5 	/images/r5u7/Snap5/RHEL5.7-Server-20110622.0-ppc-DVD.iso 
 
I even tried to select the IBM HEA driver but that didn't work
I even tried to select Power5 Virtual Ethernet (ibmveth) and that didn't work

== Comment: #1 - Hua Chen Li <lihuach.com> - 2011.06.30 02:21:37 ==
HTTP/NFS/FTP methods all fails to install. And we have another three blades listed as follows to hit this bug with Snap5. So now upgrading this bug to ship issue...

ahi10 (7891-73X)   
papa08b (7778-63X)
fold13 (7778-23X)

Architecture Details : 

1. Server architecture(s) (please list all effected) (x86/POWER6/Z/etc.):PPC64

2. Server type (9117-MMA/HS20/s390/etc.): P6 Blade JS22(7998-61X)  

3. Other components involved (ixgbe/java/emulex/etc.): Anaconda 

4. Does the server have the latest GA firmware? Yes

5. Has the problem been shown to occur on more than one system ? Yes 

6. What is the latest official distro build on which this bug has been seen ? RHEL5.7-Server-20110622.0-ppc-DVD.iso 

7. Steps to reproduce. Mentioned in bug description 

8. Business justification. 

        Not able to install RHEL5.7 snap5 on JS22 blade series. If we won't fix customer will not be able to use rhel5.7 on these blades.
Comment 1 IBM Bug Proxy 2011-06-30 07:30:45 UTC 
Created attachment 510590 [details]
The screen shot and /tmp/anaconda.log and /tmp/syslog on ahi09(7998-61X)


------- Comment on attachment From lihuach.com 2011-06-30 03:28 EDT-------


The logs in this attachment was saved when I saw the message about the ethernet device driver not being found on ahi09(7998-61X) blade system.
Comment 4 Ales Kozumplik 2011-06-30 09:46:34 UTC 
Reporter,

1) Is it possible that an incorrect ramdisk image/vmlinuz was used, namely one for snap4 ? When I extract the snap5 images I have available, the kernel version is kernel-2.6.18-269.el5.ppc64.rpm, but anaconda in your log files is looking for the modules in 2.6.18-268.el5/ppc64

2) Please attach md5sum of the vmlinuz and ramdisk.image.gz you used.

3) Please attach the output of uname -a (after the installation stalls press ctrl-z, then 'uname -a')

Thank you.
Comment 5 IBM Bug Proxy 2011-06-30 13:20:32 UTC 
------- Comment From vahegde1.ibm.com 2011-06-30 09:18 EDT-------
Hello Red Hat ,
(In reply to comment #8)
> Reporter,
>
> 1) Is it possible that an incorrect ramdisk image/vmlinuz was used, namely one
> for snap4 ? When I extract the snap5 images I have available, the kernel
> version is kernel-2.6.18-269.el5.ppc64.rpm, but anaconda in your log files is
> looking for the modules in 2.6.18-268.el5/ppc64
>
You are right. It was vmlinuz was pointing to snap4 vmlinuz. Hence installation was failing. after updating to snap5 vmlinuz, installation is working.

We can close this bug.

Thanks for your support.
Comment 6 Ales Kozumplik 2011-06-30 14:08:25 UTC 
closed per comment 5.