openstack/trove
Code Issues Proposed changes

Disable wait for force-delete

Browse Source 
In the scenario tests, sometimes the force-delete command doesn't end up
deleting the instance. This seems to be a timing issue in that it
doesn't occur during every run (and therefore might be hard to track
down). It's not terribly critical as you can run the command again and
it will probably work the second time, but until it's fixed the test
has been disabled.

Change-Id: Id5b041cb4d5276c5015921784526423e766d032c
Related-Bug: 1656422
This commit is contained in:
Peter Stachowski 2017-01-13 21:48:16 +00:00
parent 6a917bab58
commit 57e4602420
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
trove/tests/scenario/runners/__init__.py
View File

@ -2,3 +2,4 @@ BUG_EJECT_VALID_MASTER = 1622014
BUG_WRONG_API_VALIDATION = 1498573
BUG_STOP_DB_IN_CLUSTER = 1645096
BUG_UNAUTH_TEST_WRONG = 1653614
BUG_FORCE_DELETE_FAILS = 1656422

7
trove/tests/scenario/runners/instance_force_delete_runners.py
View File

@ -15,6 +15,8 @@
from proboscis import SkipTest
from trove.tests.scenario import runners
from trove.tests.scenario.runners.test_runners import SkipKnownBug
from trove.tests.scenario.runners.test_runners import TestRunner
@ -52,5 +54,6 @@ class InstanceForceDeleteRunner(TestRunner):
self.assert_client_code(client, expected_http_code)
def run_wait_for_force_delete(self):
if self.build_inst_id:
self.assert_all_gone([self.build_inst_id], ['SHUTDOWN'])
raise SkipKnownBug(runners.BUG_FORCE_DELETE_FAILS)
# if self.build_inst_id:
# self.assert_all_gone([self.build_inst_id], ['SHUTDOWN'])