Files
746fde810878d21edd4fef90a5d4a5ee81f7f97c
puppet-openstack-integration /run_tests.sh

362 lines
13 KiB
Bash
Raw Normal View History

#!/bin/bash -ex
# Copyright 2015 Red Hat, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
export SCRIPT_DIR=$(cd `dirname 0ドル` && pwd -P)
source ${SCRIPT_DIR}/functions
export WORKSPACE=${WORKSPACE:-/tmp}
export PUPPET_URL_SUFFIX=
export PUPPET_MAJ_VERSION=${PUPPET_MAJ_VERSION:-4}
export SCENARIO=${SCENARIO:-scenario001}
export MANAGE_PUPPET_MODULES=${MANAGE_PUPPET_MODULES:-true}
export MANAGE_REPOS=${MANAGE_REPOS:-true}
Align the stars to bring our CI back 1) Add 2GB swap by default Add some swap when running CI jobs, so we can reduce the number of failures in CI related to missing memory. By default 2GB, can be disabled or increased/decreased with parameters. 2) Promote RDO repository to have Oslo DB from master python-oslo-db 4.13.x releases are known to break Gnocchi. https://review.openstack.org/367221 will fix it, but it is not yet in any release, so RDO unpinned oslo.db until that happens. 3) Disable Ironic testing on Ubuntu. Packages are broken in recent Newton upgrade. They are working on it. 4) Enable br_netfilter kernel module on Ubuntu. See https://bugs.launchpad.net/cloud-archive/+bug/1621651 Even if it's not critical, it's a nice-to-have because it removed the ERROR that we had in neutron logs. We'll see how the bug report evolve and maybe remove this workaround. 5) Export lsmod in logs, easier for us to debug later. 6) Disable linuxbridge on scenario003 for Ubuntu Also see https://bugs.launchpad.net/cloud-archive/+bug/1621651 7) Pin Puppetlabs release package. Context: https://tickets.puppetlabs.com/browse/CPR-378 Change-Id: I732ef375a681f03af751ebb6ebd5b12df55a0ecc
2016年09月08日 13:43:30 -04:00
export ADD_SWAP=${ADD_SWAP:-true}
2017年05月23日 13:14:08 +02:00
export SWAP_SIZE_GB=${SWAP_SIZE_GB:-4}
export HIERA_CONFIG=${HIERA_CONFIG:-${SCRIPT_DIR}/hiera/hiera.yaml}
export MANAGE_HIERA=${MANAGE_HIERA:-true}
export PUPPET_ARGS="${PUPPET_ARGS} --detailed-exitcodes --color=false --test --summarize --trace --hiera_config ${HIERA_CONFIG} --logdest ${WORKSPACE}/puppet.log"
Support of Ubuntu 16.04 LTS Xenial deployments Add support for Xenial deployments. * Disable SSL on Ubuntu Xenial deployments. * Pin puppetlabs-mysql to a recent commit (until they produce a new tag). * Disable Ceph on Ubuntu Xenial deployments, neither Hammer or Jewel currently work out of the box with puppet-ceph on Xenial. * Disable Horizon on Ubuntu Xenial deployments: not working yet. * Do not deploy UCA on Xenial, since we currently deploy Mitaka. * On Xenial, deploy Puppet using distro packaging, not puppetlabs.com. * Cleanup /etc/default/puppet on Xenial / Puppet4 runs (workaround) until we figure what is installing this file on Xenial nodepool image. All issues are documented here: See https://etherpad.openstack.org/p/puppet-openstack-xenial Change-Id: Ifc8c7e241add830c88b84c1f01770e5e15df1653
2016年04月20日 14:54:36 -04:00
export DISTRO=$(lsb_release -c -s)
# If openstack/tempest is broken on master, we can pin the repository to a specific commit
# by using the following line:
# export TEMPEST_VERSION=${TEMPEST_VERSION:-'382a2065f3364a36c110bfcc6275a0f8f6894773'}
export TEMPEST_VERSION=${TEMPEST_VERSION:-'master'}
# For installing Tempest from RPM keep TEMPEST_FROM_SOURCE to false
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
export TEMPEST_FROM_SOURCE=${TEMPEST_FROM_SOURCE:-false}
# Cirros Image directory
export IMG_DIR=${IMG_DIR:-'/tmp/openstack/image'}
# if we're running the tests we don't need to write out the facts to facter
# so we can disable it.
export WRITE_FACTS=false
source ${SCRIPT_DIR}/configure_facts.sh
if [ $PUPPET_MAJ_VERSION == 4 ]; then
export PATH=${PATH}:/opt/puppetlabs/bin:/opt/puppetlabs/puppet/bin
export PUPPET_RELEASE_FILE=puppetlabs-release-pc1
export PUPPET_BASE_PATH=/etc/puppetlabs/code
export PUPPET_PKG=${PUPPET_PKG:-puppet-agent}
elif [ $PUPPET_MAJ_VERSION == 5 ]; then
export PATH=${PATH}:/opt/puppetlabs/bin:/opt/puppetlabs/puppet/bin
export PUPPET_RELEASE_FILE=puppet5-nightly-release
export PUPPET_BASE_PATH=/etc/puppetlabs/code
export PUPPET_PKG=${PUPPET_PKG:-puppet-agent}
if is_fedora; then
PUPPET_URL_SUFFIX='puppet5-nightly/'
fi
fi
print_header 'Start (run_tests.sh)'
if [ ! -f fixtures/${SCENARIO}.pp ]; then
echo "fixtures/${SCENARIO}.pp file does not exist. Please define a valid scenario."
exit 1
fi
if [ $(id -u) != 0 ]; then
# preserve environment so we can have ZUUL_* params
export SUDO='sudo -E'
fi
Align the stars to bring our CI back 1) Add 2GB swap by default Add some swap when running CI jobs, so we can reduce the number of failures in CI related to missing memory. By default 2GB, can be disabled or increased/decreased with parameters. 2) Promote RDO repository to have Oslo DB from master python-oslo-db 4.13.x releases are known to break Gnocchi. https://review.openstack.org/367221 will fix it, but it is not yet in any release, so RDO unpinned oslo.db until that happens. 3) Disable Ironic testing on Ubuntu. Packages are broken in recent Newton upgrade. They are working on it. 4) Enable br_netfilter kernel module on Ubuntu. See https://bugs.launchpad.net/cloud-archive/+bug/1621651 Even if it's not critical, it's a nice-to-have because it removed the ERROR that we had in neutron logs. We'll see how the bug report evolve and maybe remove this workaround. 5) Export lsmod in logs, easier for us to debug later. 6) Disable linuxbridge on scenario003 for Ubuntu Also see https://bugs.launchpad.net/cloud-archive/+bug/1621651 7) Pin Puppetlabs release package. Context: https://tickets.puppetlabs.com/browse/CPR-378 Change-Id: I732ef375a681f03af751ebb6ebd5b12df55a0ecc
2016年09月08日 13:43:30 -04:00
if [ "${ADD_SWAP}" = true ]; then
print_header "Create $SWAP_SIZE_GB GB swapfile"
set +e
$SUDO swapon -s |grep -q '/swapfile'
RESULT=$?
set -e
if [ $RESULT -eq 0 ]; then
$SUDO swapoff /swapfile && $SUDO rm -f /swapfile
fi
Align the stars to bring our CI back 1) Add 2GB swap by default Add some swap when running CI jobs, so we can reduce the number of failures in CI related to missing memory. By default 2GB, can be disabled or increased/decreased with parameters. 2) Promote RDO repository to have Oslo DB from master python-oslo-db 4.13.x releases are known to break Gnocchi. https://review.openstack.org/367221 will fix it, but it is not yet in any release, so RDO unpinned oslo.db until that happens. 3) Disable Ironic testing on Ubuntu. Packages are broken in recent Newton upgrade. They are working on it. 4) Enable br_netfilter kernel module on Ubuntu. See https://bugs.launchpad.net/cloud-archive/+bug/1621651 Even if it's not critical, it's a nice-to-have because it removed the ERROR that we had in neutron logs. We'll see how the bug report evolve and maybe remove this workaround. 5) Export lsmod in logs, easier for us to debug later. 6) Disable linuxbridge on scenario003 for Ubuntu Also see https://bugs.launchpad.net/cloud-archive/+bug/1621651 7) Pin Puppetlabs release package. Context: https://tickets.puppetlabs.com/browse/CPR-378 Change-Id: I732ef375a681f03af751ebb6ebd5b12df55a0ecc
2016年09月08日 13:43:30 -04:00
$SUDO dd if=/dev/zero of=/swapfile count=${SWAP_SIZE_GB}k bs=1M
$SUDO chmod 0600 /swapfile
$SUDO mkswap /swapfile
$SUDO swapon /swapfile
fi
# We install some gems as root so to take benefit of
# OpenStack Infra mirrors.
if [ -f ~/.gemrc ]; then
cat ~/.gemrc | $SUDO tee /root/.gemrc
fi
print_header 'Clone Tempest, plugins & pre-cache CirrOS'
# TODO(pabelanger): Move this into tools/install_tempest.sh and add logic so we
# can clone tempest outside of the gate. Also, tempest should be sandboxed into
# the local directory but works needs to be added into puppet to properly find
# the path.
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
# If it's running in tempest gate, we need to deploy it from source to test the
# patch.
if [[ "${ZUUL_PROJECT}" = "openstack/tempest" ]]; then
TEMPEST_FROM_SOURCE=true
fi
if [ -e /usr/zuul-env/bin/zuul-cloner ] ; then
# For ubuntu we always need to deploy tempest-horizon from source
if uses_debs; then
/usr/zuul-env/bin/zuul-cloner --workspace /tmp --cache-dir /opt/git \
git://git.openstack.org openstack/tempest-horizon
fi
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
if [ "${TEMPEST_FROM_SOURCE}" = true ]; then
/usr/zuul-env/bin/zuul-cloner --workspace /tmp --cache-dir /opt/git \
git://git.openstack.org openstack/tempest
# Pin Tempest to TEMPEST_VERSION unless we're running inside the
# openstack/tempest gate.
if [[ "${ZUUL_PROJECT}" != "openstack/tempest" ]]; then
pushd /tmp/openstack/tempest
git reset --hard $TEMPEST_VERSION
popd
fi
fi
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
else
# For ubuntu we always need to deploy tempest-horizon from source
if uses_debs; then
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
$SUDO rm -rf /tmp/openstack/tempest-horizon
git clone git://git.openstack.org/openstack/tempest-horizon /tmp/openstack/tempest-horizon
fi
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
if [ "${TEMPEST_FROM_SOURCE}" = true ]; then
$SUDO rm -rf /tmp/openstack/tempest
git clone git://git.openstack.org/openstack/tempest /tmp/openstack/tempest
pushd /tmp/openstack/tempest
git reset --hard origin/$TEMPEST_VERSION
popd
fi
fi
# NOTE(pabelanger): We cache cirros images on our jenkins slaves, check if it
# exists.
if [[ ! -e $IMG_DIR ]]; then
mkdir -p $IMG_DIR
fi
if [ -f ~/cache/files/cirros-0.4.0-x86_64-disk.img ]; then
# Create a symlink for tempest.
if ! [ -h /tmp/openstack/image/cirros-0.4.0-x86_64-disk.img ] ; then
ln -s ~/cache/files/cirros-0.4.0-x86_64-disk.img $IMG_DIR
fi
else
wget http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img -P $IMG_DIR
fi
install_puppet
PUPPET_FULL_PATH=$(which puppet)
if [ "${MANAGE_HIERA}" = true ]; then
configure_hiera
fi
if uses_debs; then
$SUDO apt-get install -y dstat ebtables iotop sysstat
elif is_fedora; then
$SUDO $YUM install -y dstat setools setroubleshoot audit iotop sysstat
$SUDO service auditd start
# SElinux in permissive mode so later we can catch alerts
$SUDO selinuxenabled && $SUDO setenforce 0
fi
# use dstat to monitor system activity during integration testing
if type "dstat" 2>/dev/null; then
print_header 'Start dstat'
$SUDO dstat -tcmndrylpg --top-cpu-adv --top-io-adv --nocolor | $SUDO tee --append /var/log/dstat.log > /dev/null &
fi
if type "iostat" 2>/dev/null; then
print_header 'Start iostat'
$SUDO iostat -x -k -d -t 4 | $SUDO tee --append /var/log/iostat.log > /dev/null &
fi
if [ -f "/usr/sbin/iotop" ]; then
print_header 'Start iotop'
$SUDO /usr/sbin/iotop --kilobytes --only --batch --time --delay=2 --processes --quiet | $SUDO tee --append /var/log/iotop.log > /dev/null &
fi
if [ "${MANAGE_PUPPET_MODULES}" = true ]; then
$SUDO ./install_modules.sh
fi
# Added tempest specific values to common.yaml
if [ "${TEMPEST_FROM_SOURCE}" = false ]; then
echo "tempest::install_from_source: false" >> ${SCRIPT_DIR}/hiera/common.yaml
fi
# Run puppet and assert something changes.
set +e
if [ "${MANAGE_REPOS}" = true ]; then
print_header 'Install repos'
$SUDO $PUPPET_FULL_PATH apply $PUPPET_ARGS -e "include ::openstack_integration::repos"
RESULT=$?
if [ $RESULT -ne 0 ] && [ $RESULT -ne 2 ]; then
print_header 'Puppet failed to install repositories.'
exit 1
fi
if is_fedora; then
print_header 'Updating packages'
$SUDO $YUM update -y
if [ $? -ne 0 ]; then
print_header 'Error updating packages'
exit 1
fi
fi
fi
print_header "Running Puppet Scenario: ${SCENARIO} (1st time)"
run_puppet $SCENARIO
RESULT=$?
set -e
if [ $RESULT -ne 0 ] && [ $RESULT -ne 2 ]; then
print_header 'First Puppet run contains errors in catalog.'
catch_puppet_failures
print_header 'SELinux Alerts (1st time)'
catch_selinux_alerts
exit 1
fi
timestamp_puppet_log
# Run puppet a second time and assert nothing changes.
set +e
print_header "Running Puppet Scenario: ${SCENARIO} (2nd time)"
run_puppet $SCENARIO
RESULT=$?
set -e
if [ $RESULT -ne 0 ]; then
print_header 'Second Puppet run is not idempotent.'
catch_puppet_failures
print_header 'SELinux Alerts (2nd time)'
catch_selinux_alerts
exit 1
fi
timestamp_puppet_log
print_header 'Prepare Tempest'
# FIXME: Since tempest create tempest workspace which is owned by root user.
# We need to fix it in puppet-tempest, as a workaround we are changing the mode
# of tempest workspace and run tempest command using root.
$SUDO touch /tmp/openstack/tempest/test-whitelist.txt
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
$SUDO chown -R "$(id -u):$(id -g)" /tmp/openstack/tempest/
# install from source now on ubuntu until packaged
if uses_debs; then
cd /tmp/openstack/tempest-horizon;
if [ $(lsb_release --id -s) = "Debian" ] ; then
$SUDO apt-get install -y tempest python3-stestr python3-os-testr python3-tempest python3-tempest-horizon
else
$SUDO python setup.py install
$SUDO pip install -U stestr os-testr
fi
fi
set +e
# Select what to test:
# Smoke suite
echo "smoke" > /tmp/openstack/tempest/test-whitelist.txt
# Horizon
echo "dashboard" >> /tmp/openstack/tempest/test-whitelist.txt
# Aodh
echo "TelemetryAlarming" >> /tmp/openstack/tempest/test-whitelist.txt
# Gnocchi
echo "telemetry_tempest_plugin.gnocchi" >> /tmp/openstack/tempest/test-whitelist.txt
# Vitrage
echo "TestEvents" >> /tmp/openstack/tempest/test-whitelist.txt
# Test Autoscaling with Telemetry (need panko, ubuntu doesn't ship it)
uses_debs || echo "test_telemetry_integration" >> /tmp/openstack/tempest/test-whitelist.txt
# Ironic
# Note: running all Ironic tests under SSL is not working
# https://bugs.launchpad.net/ironic/+bug/1554237
echo "ironic_tempest_plugin.tests.api.admin.test_drivers" >> /tmp/openstack/tempest/test-whitelist.txt
2016年02月17日 15:30:37 -05:00
# Zaqar
echo "v2.test_queues.TestManageQueue" >> /tmp/openstack/tempest/test-whitelist.txt
# ec2api
# VPN tests require VPNaaS, which doesn't work yet in puppet-tempest.
# As soon as enabling neutron_vpnaas_available works there, the VPN tests can
# be included.
echo "ec2api_tempest_plugin.api.*test_create_delete(?!.*_vpn_connection)" >> /tmp/openstack/tempest/test-whitelist.txt
# Cinder Backup
echo "VolumesBackupsAdminV2Test" >> /tmp/openstack/tempest/test-whitelist.txt
# Cinder encrypted volumes
echo "TestEncryptedCinderVolumes" >> /tmp/openstack/tempest/test-whitelist.txt
# Mistral
# We have to ignore a smoke test because of:
# https://bugs.launchpad.net/mistral/+bug/1654555
echo "test_create_and_delete_workflow" >> /tmp/openstack/tempest/test-whitelist.txt
# BGPVPN
echo "test_create_bgpvpn" >> /tmp/openstack/tempest/test-whitelist.txt
# L2GW
echo "test_create_show_list_update_delete_l2gateway" >> /tmp/openstack/tempest/test-whitelist.txt
if uses_debs; then
Switch tempest to use RPM by default and disable trove 1) Switch tempest to be installed from RPM instead of source Currently, tempest is deployed from source by default. This is problematic as some changes in master trunk can be incompatible with packages in promoted repo. This patch switchs p-o-i to deploy tempest from the rpm package used in the promoted repo, what should fix this kind of scenarios. 2) Disable trove until integration with keystone v3 is fixed upstream Currently, trove doesn't work fine with keystone API v3. It's being worked in https://review.openstack.org/#/c/507087/ in upstream project. 3) Disable tempest tests for object_storage when running with ubuntu as they are failing with the current version of tempest in the uca repo. Until it's fixed, let's disable it from p-o-i to unblock promotion. Change-Id: I385e2f34dd925bdc2fdbc1553d49dce104f566f2
2017年10月10日 19:05:08 +02:00
# TODO (amoralej) tempest tests for object_storage are not working in master with current version of tempest in uca (16.1.0).
EXCLUDES="--regex=^(?!mistral_tempest_tests.tests.api.v2.test_executions.ExecutionTestsV2.test_get_list_executions.*$)(?!ceilometer.tests.tempest.api.test_telemetry_notification_api.TelemetryNotificationAPITest.test_check_glance_v2_notifications.*$)(?!tempest.api.object_storage.*$).*"
else
# https://review.openstack.org/#/c/504345/ has changed the behavior of tempest when running with --regex and --whitelist-file
# and now operator between them is OR when filtering tests (which is how it was documented, btw). In order to promote
# we need to remove this regex option and implement https://review.openstack.org/#/c/547278 when ready.
# Note these tests were disabled in https://review.openstack.org/#/c/461969/ and hopefully it's more stable now and allows
# us to run it until we can implement --blacklist-file in a stable way.
#EXCLUDES="--regex=^(?!tempest.scenario.gnocchi.test.live_assert_vcpus_metric_is_really_expurged.test_request.*$)(?!tempest.scenario.gnocchi.test.live_assert_no_delete_metrics_have_the_gabbilive_policy.test_request.*$).*"
EXCLUDES=""
fi
print_header 'Running Tempest'
cd /tmp/openstack/tempest
if [ "${TEMPEST_FROM_SOURCE}" = true ]; then
virtualenv --system-site-packages run_tempest
run_tempest/bin/pip install -c https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt -U -r requirements.txt
run_tempest/bin/python setup.py install
export tempest_binary="run_tempest/bin/tempest"
else
export tempest_binary="/usr/bin/tempest"
fi
# List tempest plugins
$tempest_binary list-plugins
# list tempest workspace
$tempest_binary workspace list
# list tempest tests before running tempest
$tempest_binary run -l --whitelist_file=/tmp/openstack/tempest/test-whitelist.txt
# Run tempest commands
$tempest_binary run --whitelist_file=/tmp/openstack/tempest/test-whitelist.txt --concurrency=2 $EXCLUDES
RESULT=$?
set -e
if [ -d .testrepository ]; then
testr last --subunit > /tmp/openstack/tempest/testrepository.subunit
elif [ -d .stestr ]; then
stestr last --subunit > /tmp/openstack/tempest/testrepository.subunit
fi
subunit2html /tmp/openstack/tempest/testrepository.subunit /tmp/openstack/tempest/testr_results.html
print_header 'SELinux Alerts (Tempest)'
catch_selinux_alerts
print_header 'Done (run_tests.sh)'
exit $RESULT