From 1cc3eba140116c80443c024ebfd09358b98f395a Mon Sep 17 00:00:00 2001
From: Aurelien Lourot <aurelien.lourot@canonical.com>
Date: Mon, 5 Jul 2021 11:22:49 +0200
Subject: [PATCH] Fix Zaza deployment expectations

Fix Zaza's expected application status after
https://github.com/openstack-charmers/zaza/pull/451

Change-Id: I1a6f1316817a444d9cb82a4bc7e57d832a921eae
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/598
---
 tests/tests.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tests/tests.yaml b/tests/tests.yaml
index 3f369228..efc805df 100644
--- a/tests/tests.yaml
+++ b/tests/tests.yaml
@@ -29,6 +29,10 @@ dev_bundles:
 
 target_deploy_status:
   neutron-api-plugin-ovn:
+    # NOTE(lourot): at first we deploy a bundle in which this subordinate charm
+    # isn't related to anything, so it has no unit. It will become related and
+    # receive units later as part of OVSOVNMigrationTest.
+    num-expected-units: 0
     workload-status: waiting
   ovn-chassis:
     workload-status: maintenance