Bug 1118305 - RFE: Ability to set iSCSI-Initiator-IQN for iSCSI connections
Summary: RFE: Ability to set iSCSI-Initiator-IQN for iSCSI connections
Keywords:
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libguestfs
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact:
URL:
Whiteboard:
Depends On: 1118334
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-10 12:08 UTC by Raghu
Modified: 2018-07-18 14:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1118334 (view as bug list)
Environment:
Last Closed:


Attachments (Terms of Use)
output of libguestfs-test-tool (45.89 KB, text/plain)
2014-07-10 12:08 UTC, Raghu
no flags Details

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:


Note You need to log in before you can comment on or make changes to this bug.