no need to run integration tests in upgrade
the purpose of upgrade script is to upgrade service, and heat shouldn't run any jobs inside of that. moreover there is no benefit in executing these tests after upgrade because it doesn't test anything related to upgrades: if heat is correctly configured after upgrade it will be ready to run tests (but this can be covered by usual integration job). heat should be testing specific things like updating stacks after migration to the new openstack code, deleting stacks and so on. Co-authored-by: Vitaly Gridnev <vgridnev@mirantis.com> Change-Id: Ie600dfc09db0ffa91609f92be4b9ef27259b5314
This commit is contained in:
parent
0f9a18555c
commit
3cf288bc8c
|
@ -83,12 +83,6 @@ start_heat
|
|||
# Don't succeed unless the services come up
|
||||
ensure_services_started heat-api heat-engine heat-api-cloudwatch heat-api-cfn
|
||||
|
||||
# run heat_integrationtests instead of tempest smoke after upgrade
|
||||
pushd $TARGET_DEVSTACK_DIR/../heat
|
||||
source $TARGET_DEVSTACK_DIR/openrc demo demo
|
||||
tox -eintegration heat_integrationtests.functional.test_create_update
|
||||
popd
|
||||
|
||||
set +o xtrace
|
||||
echo "*********************************************************************"
|
||||
echo "SUCCESS: End $0"
|
||||
|
|
Loading…
Reference in New Issue