Browse code

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

Matt Riedemann authored on 2018/09/05 05:51:45
Showing 1 changed files
... ...
@@ -1442,6 +1442,12 @@ if is_service_enabled n-api; then
1442 1442
         # environment is up.
1443 1443
         echo_summary "SKIPPING Cell setup because n-cpu is not enabled. You will have to do this manually before you have a working environment."
1444 1444
     fi
1445
+    # Run the nova-status upgrade check command which can also be used
1446
+    # to verify the base install. Note that this is good enough in a
1447
+    # single node deployment, but in a multi-node setup it won't verify
1448
+    # any subnodes - that would have to be driven from whatever tooling
1449
+    # is deploying the subnodes, e.g. the zuul v3 devstack-multinode job.
1450
+    $NOVA_BIN_DIR/nova-status --config-file $NOVA_CONF upgrade check
1445 1451
 fi
1446 1452
 
1447 1453
 # Run local script