From 9e3b3bf5244e0b62cd4ab9914c622e81ba08f4c8 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Tue, 4 Sep 2018 16:51:45 -0400 Subject: [PATCH] Add nova-status upgrade check call post-deploy Once nova is setup and n-cpu on the host is reporting a service record and discovered (the host is mapping in the API DB), we should run the nova-status upgrade check to verify the deployment. Change-Id: I9683bf94233ebacb3057ce159cb3dc53aa55a2f4 Related-Bug: #1790721 --- stack.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/stack.sh b/stack.sh index 4f6e5b6da1..b06f7bdcc1 100755 --- a/stack.sh +++ b/stack.sh @@ -1442,6 +1442,12 @@ if is_service_enabled n-api; then # environment is up. echo_summary "SKIPPING Cell setup because n-cpu is not enabled. You will have to do this manually before you have a working environment." fi + # Run the nova-status upgrade check command which can also be used + # to verify the base install. Note that this is good enough in a + # single node deployment, but in a multi-node setup it won't verify + # any subnodes - that would have to be driven from whatever tooling + # is deploying the subnodes, e.g. the zuul v3 devstack-multinode job. + $NOVA_BIN_DIR/nova-status --config-file $NOVA_CONF upgrade check fi # Run local script