Hide Forgot
Created attachment 513528 [details] fail to add dud to rhel5.3 via nfs Description of problem: my target system IBM system x 3650 m3 is in dhcp network enviroment. It has ripley 6gb ssd/sas raid card, in order to install rhel5.3, I have to add the driver update disk (dud) of mpt2sas, otherwise rhel5.3 can't be installed. I can succeed add the driver via http/ftp, but fail with nfs method. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.put the dud of mpt2sas and the kickstart file on the source server 2.when instal rhel5.3 on the target server, put args "ks=nfs:x.x.x.x:/rhel5.ks" 3.in rhel5.ks specify the dud args: "driverdisk --source=nfs:x.x.x.x:/home/dud-2.6.18-128-64.RHEL5.iso" Actual results: rhel installer anaconda report errors when to retrieve the dud "getFileFromNfs: no client ip infomation; unable to retrieve driver disk:nfs:x.x.x.x:/home/dud-2.6.18-128-64.RHEL5.iso", then break the installation Expected results: installer should load the driver disk of mpt2sas which contained in the dud-2.6.18-128-64.RHEL5.iso, and continue to install the os Additional info: to confirm the nfs address is accessible,I do the following action: a. I manually mount the nfs, it is successful. "mount -t nfs x.x.x.x:/home/ /mnt" b. use the same nfs server, I try to add the mpt2sas dud to suse linux on the target system, it's also successful. "linux dd dud=nfs://x.x.x.x/home/dud-2.6.18-128-64.RHEL5.iso"
I am a software engineer from IBM, and the issue is very urgent because it will impact our new feature in our deployment tools. Thanks.
(In reply to comment #0) > Created attachment 513528 [details] > fail to add dud to rhel5.3 via nfs > > Description of problem: > my target system IBM system x 3650 m3 is in dhcp network enviroment. It has > ripley 6gb ssd/sas raid card, in order to install rhel5.3, I have to add the > driver update disk (dud) of mpt2sas, otherwise rhel5.3 can't be installed. I > can succeed add the driver via http/ftp, but fail with nfs method. > > Version-Release number of selected component (if applicable): > > > How reproducible: > > > Steps to Reproduce: > 1.put the dud of mpt2sas and the kickstart file on the source server > 2.when instal rhel5.3 on the target server, put args "ks=nfs:x.x.x.x:/rhel5.ks" > 3.in rhel5.ks specify the dud args: "driverdisk > --source=nfs:x.x.x.x:/home/dud-2.6.18-128-64.RHEL5.iso" > > > > Actual results: > rhel installer anaconda report errors when to retrieve the dud "getFileFromNfs: > no client ip infomation; unable to retrieve driver > disk:nfs:x.x.x.x:/home/dud-2.6.18-128-64.RHEL5.iso", then break the > installation > > Expected results: > installer should load the driver disk of mpt2sas which contained in the > dud-2.6.18-128-64.RHEL5.iso, and continue to install the os > > Additional info: > to confirm the nfs address is accessible,I do the following action: > a. I manually mount the nfs, it is successful. "mount -t nfs x.x.x.x:/home/ > /mnt" > b. use the same nfs server, I try to add the mpt2sas dud to suse linux on the > target system, it's also successful. "linux dd > dud=nfs://x.x.x.x/home/dud-2.6.18-128-64.RHEL5.iso" This looks like anaconda issue to me, I added Martin sivak and Jon Masters to the CC/NEEDINFO. Also it might probably help them to see logs with loglevel=debug command line option. jirka
Hi, can you please test this with any recent RHEL5? (like 5.7 GA?) We do not respin installer for older releases, so the possible fixes could only be pushed into 5.8 or 5.9 anyway.
any feedback on this? I'll close this as WONTFIX in a week if I dont hear from you
closinf as WONTFIX due to no feedback, please reopen otherwise