Fix Zaza deployment expectations
Fix Zaza's expected application status after https://github.com/openstack-charmers/zaza/pull/451 Change-Id: I932318afaf369a987d0ff0ac7a43d9665abc3757
This commit is contained in:
parent
3fc68108af
commit
7ad1afeb74
@ -43,6 +43,10 @@ configure_options:
|
|||||||
|
|
||||||
target_deploy_status:
|
target_deploy_status:
|
||||||
neutron-api-plugin-ovn:
|
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
|
workload-status: waiting
|
||||||
ovn-chassis:
|
ovn-chassis:
|
||||||
workload-status: maintenance
|
workload-status: maintenance
|
||||||
|
Loading…
Reference in New Issue
Block a user