Created attachment 320293 [details] 5.3-anaconda-logs.tgz Description of problem: Attempts to add an iSCSI volume in text-mode fail Version-Release number of selected component (if applicable): TREE - RHEL5.3-Server-20081014.nightly ANACONDA - anaconda-11.1.2.140-1.i386 How reproducible: 100% Steps to Reproduce: 1. Boot into the installer for RHEL5.3-Server-20081014.nightly (add "text" boot prompt) 2. At disk partitioning, press <F2> to add a iSCSI drive 3. Select iSCSI 4. Enter IP=192.168.33.219 and initiator name:iqn.ibft0 Actual results: An error prompt that says "Need more than 3 values to unpack" Expected results: Adding the iSCSI volume Additional info: Works fine in graphical mode
Created attachment 320294 [details] Failure Screenshot
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Testing with updates=http://clumens.fedorapeople.org/updates.img resolves this reported issue in text-mode.
This will be fixed in anaconda-11.1.2.142. I'll move that updates image to http://clumens.fedorapeople.org/466902.img so people can continue to use it while I work on other stuff.
I was able to add the iSCSI drive but then partitioning failed with: | vgcreate failed for VolGroup00 | | | | The installer will now exit... will try graphical and see if it works.
(In reply to comment #9) > I was able to add the iSCSI drive but then partitioning failed with: > > | vgcreate failed for VolGroup00 | > | | > | The installer will now exit... > > will try graphical and see if it works. That is a different issue then reported in this bug, if the error prompt that says "Need more than 3 values to unpack" is fixed please note so here so this bug can be marked as verified and open a new bug for the issue you are seeing now. Also when you file a new bug please be much much more verbose about what you are seeing, the description of the problem you've given above is not very useful. When you file a new bug, please include atleast the following: -Which version where you using (which RHEL-5.3 nightly?) -Which choices did you make leading up to the error (what kind of partitioning scheme did you use, is this an install or an update, etc.) -What did you do before the error happened (on which screen where you, and which button did you push). Also in the future, with any issues you want to report: 1) please don't tag unrelated issues onto existing bug reports 2) be much much more verbose both in the initial report and in any comments you add
Alexander, could it be that what you are seeing is the same as bug 466902 ?
Alexander, sorry this is bug 466902, I meant the same as bug 469700 ?
Hans, sounds possible that I hit bug #469700. The iSCSI drive I used has been previously used for other installs.
(In reply to comment #15) > Hans, > sounds possible that I hit bug #469700. The iSCSI drive I used has been > previously used for other installs. Could you try wiping the first and last MB of that disk using dd, and then try again?
(In reply to comment #15) > Hans, > sounds possible that I hit bug #469700. The iSCSI drive I used has been > previously used for other installs. Alexander, can you please try again with this updates.img: http://rvykydal.fedorapeople.org/updates.wipelvm.149.img That fixes bug #469700, and most likely the issue you are seeing here.
install with snap #2 and iscsi details form comment #0 resulted in: 1) the error in comment #0 was not seen 2) using updates.img from comment #18 the error from comment #9 didn't occur I'm moving this one to VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0164.html