openstack/vitrage
Code Issues Proposed changes

fix typos

Browse Source 
Change-Id: I1bc4458d655d12b5c9dfa5af983718993b4be815
This commit is contained in:
sunqingliang6 2018-06-20 20:42:42 +08:00
parent 902f472451
commit 61dc024f31
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
vitrage/tests/functional/evaluator/test_scenario_evaluator.py
View File

@ -692,12 +692,12 @@ class TestScenarioEvaluator(TestFunctionalBase, TestConfiguration):
def test_complex_not_operator_deduced_alarm(self): def test_complex_not_operator_deduced_alarm(self):
"""Handles a complex not operator use case """Handles a complex not operator use case
We have created the following template: if there is a openstack.cluster We have created the following template: if there is an
that has a nova.zone which is connected to a neutron.network and also openstack.cluster that has a nova.zone which is connected to a
there is no nagios alarm of vitrage_type CLUSTER_PROBLEM on the cluster neutron.network and also there is no nagios alarm of vitrage_type
and no nagios alarm of vitrage_type NETWORK_PROBLEM on the CLUSTER_PROBLEM on the cluster and no nagios alarm of vitrage_type
neutron.network, then raise a deduced alarm on the nova.zone called NETWORK_PROBLEM on the neutron.network, then raise a deduced alarm
complex_zone_deduced_alarm. on the nova.zone called complex_zone_deduced_alarm.
The test has 3 steps in it: The test has 3 steps in it:
1. create a neutron.network and connect it to a zone, and check that 1. create a neutron.network and connect it to a zone, and check that
the complex_zone_deduced_alarm is raised on the nova.zone because it the complex_zone_deduced_alarm is raised on the nova.zone because it