Bug 462229

Summary:	iSCSI disks do not show up after hitting 'Add iSCSI target' (and filling in the right entries)
Product:	[Fedora] Fedora	Reporter:	Konrad Rzeszutek Wilk <ketuzsezr>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	hdegoede
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:	2008-09-14 20:23:10 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 Konrad Rzeszutek Wilk 2008-09-14 15:48:40 UTC

Description of problem:

This works just fine under RHEL5.2 with the same exact machine so it is not a setup issue.

The issue is that the newly added SCSI disks does not show up in the disk view. It looks as if the routine that rescans for all the disks on the system is not called.

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


How reproducible:
Always

Steps to Reproduce:
1. Boot F9  install
2. Hit 'Add iSCSI target'
3. Fill in the entries with the right IP (and obviously have the IQN or the IP configured in the target).
4. See it says 'Initializaing iSCSI'
5. No disk shows up in the hard-disk view.
6. Switch to VC 4 and sure enough the SCSI disks is there.

 
If I do the manual iSCSI login before progressing in the graphical/VNC window the disk shows up. Those steps are obviously a hack:

#mkdir -p /etc/iscsi
#cat > /etc/iscsi/initiarname.iscsi
InitiatorName=iqn.2008.something:blah
#iscsiadm -m discovery -t st -p <IP>
#iscsiadm -m node -L all

And then go in the graphical view, and the iSCSI disk is there.

Expected results:

Step 5 should show the disk.

Additional info:

Comment 1 Hans de Goede 2008-09-14 20:23:10 UTC

Thanks for reporting!

This is a know issue with Fedora-9 which has been fixed in the F-10 alpha and the upcoming F-10 beta.