Bug 463156

Summary:	using "iscsi ...." from ks without preceding iscsiname fails silently
Product:	[Fedora] Fedora	Reporter:	Hans de Goede <hdegoede>
Component:	anaconda	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-13 08:04:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hans de Goede 2008-09-22 11:49:58 UTC

When using a kickstart file for an iscsi install, if you put just an
iscsi --ipaddr=<foo>

Line in kickstart, anaconda won't pick up the iscsi volumes at ip-addr foo, because no initiator name is configured. But instead of complaining about this it continues silently until you try to use the iscsi disk and goes boom then.

It should ofcourse go boom as soon as it fails to successfully execute the iscsi command, or just choose a random initiator name as is done in interactive mode.

This is related to bug 461830, basicly we do not seem to throw an error if something goes wrong with iscsi ever, bad, very bad.

Comment 1 Hans de Goede 2008-09-22 11:50:34 UTC

Re-assigning to myself.

Comment 2 Bug Zapper 2008-11-26 03:10:48 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Hans de Goede 2009-02-13 08:04:01 UTC

This is fixed in anaconda-11.5.0.17, which is now in rawhide, closing.