Bug 1118305

Summary: RFE: Ability to set iSCSI-Initiator-IQN for iSCSI connections
Product: [Community] Virtualization Tools Reporter: Raghu <rgs2k7>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: ptoscano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1118334 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1118334    
Bug Blocks:    
Attachments:
Description Flags
output of libguestfs-test-tool none

Description Raghu 2014-07-10 12:08:39 UTC
Created attachment 917050 [details]
output of libguestfs-test-tool

Description of problem:
libguestfs has no means to set an explicit initiator IQN for iSCSI connections.  A default intiator IQN  ( incase of LIBGUESTFS-BACKEND=direct ) or a random IQN ( in case of libvirt backend ) is used for iSCSI connections. 
This creates problems when storage systems expect a preconfigured initiator IQN to be used while establishing iSCSI connections.

The underlying QEMU command has an option (`-iscsi initiator-name=<initiator-iqn>' to set initiator IQN string explicitly. But currently libguestfs has no option to set this parameter and pass it on to QEMU.

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


How reproducible:

Use
guestfish -a iscsi://<target IQN> 
against a storage system which validates incoming connection against a preconfigured Initiator IQN


Steps to Reproduce:
1.
2.
3.

Actual results:
Error while connecting to iSCSI target

Expected results:
Should be able to establish iSCSI connection with any Initiator IQN


Additional info: