From 7ad1afeb741d3273ef6e82fdbd5b263483396c99 Mon Sep 17 00:00:00 2001
From: Aurelien Lourot <aurelien.lourot@canonical.com>
Date: Tue, 6 Jul 2021 09:59:46 +0200
Subject: [PATCH] Fix Zaza deployment expectations

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

Change-Id: I932318afaf369a987d0ff0ac7a43d9665abc3757
---
 tests/tests.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tests/tests.yaml b/tests/tests.yaml
index ec89ca8e..c6b4ea75 100644
--- a/tests/tests.yaml
+++ b/tests/tests.yaml
@@ -43,6 +43,10 @@ configure_options:
 
 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