From: maurosr@linux.vnet.ibm.com (Mauro S. M. Rodrigues)
Subject: [PATCH 1/3] nvmetcli: Fix Port and Host operations in shell
Date: Mon, 27 Mar 2017 14:46:43 -0300 [thread overview]
Message-ID: <1490636805-13688-1-git-send-email-maurosr@linux.vnet.ibm.com> (raw)
Operations against Port and Host entities are broken. When performing
operations like the follow:
/ports> create 1
/hosts> create 1
nvmetcli fails, saying the object doesn't have the attribute we're
trying to access, for instance:
'module' object has no attribute 'Port'
This patch fixes this issue by importing the classes Port and Host in
nvmet/__init__.py which was forgotten during the follow change:
a21ebd54f0 ("nvmetcli: Fix nvmet import").
Tested-by: Guilherme G. Piccoli <gpiccoli at linux.vnet.ibm.com>
Signed-off-by: Mauro S. M. Rodrigues <maurosr at linux.vnet.ibm.com>
---
nvmet/__init__.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/nvmet/__init__.py b/nvmet/__init__.py
index a084151..9a0b51d 100644
--- a/nvmet/__init__.py
+++ b/nvmet/__init__.py
@@ -1 +1 @@
-from .nvme import Root, Subsystem, Namespace
+from .nvme import Root, Subsystem, Namespace, Port, Host
--
2.7.4
next reply other threads:[~2017-03-27 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 17:46 Mauro S. M. Rodrigues [this message]
2017-03-27 17:46 ` [PATCH 2/3] nvmetcli: Fix Referral operation in shell Mauro S. M. Rodrigues
2017-03-28 10:41 ` Sagi Grimberg
2017-03-30 8:27 ` Christoph Hellwig
2017-03-27 17:46 ` [PATCH 3/3] nvmetcli: Install nvmetcli executable in $PATH Mauro S. M. Rodrigues
2017-03-28 10:41 ` Sagi Grimberg
2017-03-30 8:28 ` Christoph Hellwig
2017-04-05 23:56 ` Mauro Rodrigues
2017-04-06 7:20 ` Christoph Hellwig
2017-03-28 10:40 ` [PATCH 1/3] nvmetcli: Fix Port and Host operations in shell Sagi Grimberg
2017-03-30 8:27 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490636805-13688-1-git-send-email-maurosr@linux.vnet.ibm.com \
--to=maurosr@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).