With the recent introduction of an improved set_link
interface (see 4ada095f8bd3a3435d6f51db0b4164c7d1122070
and a9ef23f9ed66ca5892f8a3c784b33093d6b5ced4),
update the set_link test with it and resolve
issue #18.
Signed-off-by: Lucas Meneghel Rodrigues <l...@redhat.com>
---
client/tests/kvm/tests/set_link.py | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/client/tests/kvm/tests/set_link.py
b/client/tests/kvm/tests/set_link.py
index ef34c71..f50dc93 100644
--- a/client/tests/kvm/tests/set_link.py
+++ b/client/tests/kvm/tests/set_link.py
@@ -29,13 +29,13 @@ def run_set_link(test, params, env):
"""
ip = vm.get_address(0)
- vm.monitor.cmd("set_link %s down" % linkid)
+ vm.set_link(linkid, up=False)
s, o = virt_test_utils.ping(ip, count=10, timeout=20)
if virt_test_utils.get_loss_ratio(o) != 100:
raise error.TestFail("Still can ping the %s after down %s" %
(ip, linkid))
- vm.monitor.cmd("set_link %s up" % linkid)
+ vm.set_link(linkid, up=True)
s, o = virt_test_utils.ping(ip, count=10, timeout=20)
# we use 100% here as the notification of link status changed may be
# delayed in guest driver
--
1.7.7.5
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
