From owner-freebsd-bugs@freebsd.org  Thu Oct 29 15:59:39 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FEEAA214EE
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 29 Oct 2015 15:59:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8C95A1D85
 for <freebsd-bugs@FreeBSD.org>; Thu, 29 Oct 2015 15:59:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9TFxdsZ029462
 for <freebsd-bugs@FreeBSD.org>; Thu, 29 Oct 2015 15:59:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 204129] iscsictl doesn't list discovered targets
Date: Thu, 29 Oct 2015 15:59:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: amvandemore@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-204129-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2015 15:59:39 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204129

            Bug ID: 204129
           Summary: iscsictl doesn't list discovered targets
           Product: Base System
           Version: 10.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: misc
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: amvandemore@gmail.com

Currently there is no method to list out possible targets to connect to:

root@bhyve1:~ # iscsictl -d 10.0.0.2
iscsictl: -L and -d and mutually exclusive

I see others wanting this functionality, see [1].

And here where it's sort of replied to as "Works as intended", see [2].

I don't use Windows or VMware but XenServer allows you to choose when setting
up an SR.  VMware docs indicate this functionality is available though.  See
[3]

Bulk connecting to all is not just undesirable, it's bad.

Unfortunately, iscontrol(which has the functionality) can't be used as a work
around:

root@bhyve1:~ # kldload iscsi_initiator
kldload: an error occurred while loading the module. Please check dmesg(8) for
more details.

[1] https://forums.freebsd.org/threads/iscsictl-discovery-only.52099/
[2] https://lists.freebsd.org/pipermail/freebsd-scsi/2015-February/006580.html
[3]
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc%2Fcli_manage_iscsi_storage.7.7.html

-- 
You are receiving this mail because:
You are the assignee for the bug.