Disable SubsRemoveDHCP test while failure investigataed
Change-Id: Ic0dc0c1ac68bef02a544236f5aadad3dc251d3e0
diff --git a/Makefile b/Makefile
index 48d9dd5..6aee2ea 100644
--- a/Makefile
+++ b/Makefile
@@ -82,6 +82,9 @@
system-scale-test: ROBOT_CONFIG_FILE := $(ROBOT_SANITY_SINGLE_PON_FILE)
system-scale-test: k8s-system-test
+voltha-test: ROBOT_MISC_ARGS += -e notready
+k8s-system-test: ROBOT_MISC_ARGS += -e notready
+
# virtualenv for the robot tools
vst_venv:
virtualenv $@ ;\
diff --git a/tests/functional/Voltha_PODTests.robot b/tests/functional/Voltha_PODTests.robot
index 272f201..d733129 100644
--- a/tests/functional/Voltha_PODTests.robot
+++ b/tests/functional/Voltha_PODTests.robot
@@ -133,7 +133,7 @@
[Documentation] Validates when removed subscriber access, DHCP attempt, ping fails and
... when again added subscriber access, DHCP attempt, ping succeeds
... Assuming that test1 or sanity test was executed where all the ONUs are authenticated/DHCP/pingable
- [Tags] functional SubsRemoveDHCP
+ [Tags] functional SubsRemoveDHCP notready
[Setup] None
#[Teardown] None