neutron-lbaas has been deprecated since long. Let's remove the
service from gate jobs and skip the relevant tests.
Change-Id: I8eede46ed2ad014522e00d28b0b7c0b194a0b996
This patch defines the specified set of tests & runs these during
upgrade in grenade-multinode job.
Change-Id: I99fa1717f4bf46afc8dd989a3aae129e5c4ab9d7
Most jobs now run with apache+uwsgi, so the test has no significance.
Also we don't test it anymore.
Depends-On: I022077c92bc10e908c7fe549ed555ad0194e0704
Change-Id: I6d6e025f60867e5128704f54e5e793762f6c1b8a
This patch propose to use heat tempest plugin for Integration tests
(with no co-gating potential) and configuration tests.
Also we will remove test_autoscaling_lb from tempest plugin as well,
since it's no longer been used.
Remove senario base, since we now move all senario tests to plugin.
Change-Id: Ice6a0e1fe8ce2e1de5253c674d11949b0f8a6e31
This patch propose to use heat tempest plugin for potential
co-gating integration tests.
These tests are consider as potential co-gating. And we now
already maintain them in heat tempest plugin.
This also disables all except two of the gate/test jobs, to enable us to
land this series and stop the carnage. The jobs will be re-enabled once
all of the duplicated tests have been eliminated.
Change-Id: I55e204b72cd5a2876576852b10ad09f24d04beb4
Regression tests will be maintained in-tree. See categries list:
https://etherpad.openstack.org/p/heat-integration-test-categories
We will seperate tests to tempest plugin or in-tree base on conditions
of each tests. So we need to rework on framework for integration tests.
This patch propose following changes:
* This partially reverts commit fff6518e69
* Allow running heat tempest plugin and heat regression tests.
* iniset configs to both heat_integrationtests.conf and tempest.conf
Change-Id: Ief31dc961bc108e2863119598dfb16581a38e9cf
Depends-On: I5e9325766ce166e62c731330c462c030cb1e11fc
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
Note: We still have to change grenade jobs to use
the plugin, before removing the plugin from tree.
Change-Id: Ie63f25e724ed3fbd42adcf5bb2d625c2fec67df1
In change I84d2b34d65b3ce7d8d858de106dac531aff509b7, we changed to
call self._converge_create_or_update() in a sub-thread. However,
thread_group_mgr is not set for cancel_update (with rollback),
which in turn calls converge_stack.
This also enables test_cancel_update_server_with_port, as
bug #1607714 seems to be fixed now.
Change-Id: Ie674fd556418f6aa8e79654458cbe43648851db2
Closes-Bug: #1713952
This changes the test to use AodhGnocchiAggregationByMetricsAlarm
and add measures using gnocchi api.
Change-Id: I0b2fe154b93d9882b703e95a0b09f139697ceb9a
Closes-Bug: #1727637
It seems ceilometer api has been removed[1].
As part od zuulv3 transition we are moving jobs to project repo[2]
and change to enable gnocchi devstack plugin at the gate has to wait
till the movement is complete.
We probably have no other option but to disable the test for the
time being.
[1] https://review.openstack.org/#/c/512286/
[2] https://review.openstack.org/#/c/509098/
Change-Id: I547b26ea78ad70742ae6fcf9a0eae4cd4af60100
Related-Bug: #1727637
Add a "convergence_engine_enabled" configuration option to the functional
tests' Tempest plugin. The option is enabled by default, but can be
disabled by setting the DISABLE_CONVERGENCE environment variable to "true"
when running prepare_test_env.sh, so that if convergence is disabled in
devstack it will also be disabled in Tempest.
This will allow us to write functional tests for convergence-specific (or
non-convergence-specific) behaviours.
Change-Id: If3a37de75467d50af10582215e16611e59a4ad06
The integration jobs currently download images from a third party
mirror which can be slow at times or use up a lot of bandwidth.
This patch tries to automatically detect if nodepool mirrors are
active and uses them, falling back to the global round-robin mirror
of the Fedora project instead of a specific mirror.
Change-Id: Ie111c20b6dd0efe2e1cbfcac2a46b27ce6bc20c0
It seems for py35 job barbicanclient is installed from source.
Ib91e7049de007f4d4254abcd4c125b4dc7e03c55 has made some backward
incompatible changes.
This also changes to upload images using $IMAGE_URLS, so
the images are stored locally and then uploaded.
Change-Id: I9d3d9dabdfca0442bd17f93ce69ef9753049dc23
Closes-Bug: #1704725
This change ensures that api services deployed with apache+uwsgi
by default with devstack. User can still deploy apache+mod_wsgi
by setting WSGI_MODE=mod_wsgi in local.conf.
Using HEAT_USE_APACHE=False or HEAT_USE_MOD_WSGI=False
(for backward compatibility) would deploy the services
without apache.
Change-Id: Ia5e28e2987b4aeab6c049a3bde3a956204ddc5d9
Depends-On: I3b77aafc6104119503363e5db36b0379964daba5
Change Ica5f87614f5fb98f253d65cbd4355dcc7c6714eb adds it to the
list of scenario tests to skip, whereas it's a functional test.
Related-Bug: #1694371
Change-Id: I84e806bad284cffb32e68fef6b14dfff11dba846
Reverts I90e1d26a67a349f897d895f750d8e57fae98ec1f and
I116a96b20082d1c47068ddc64873200e9ae33a27 .
There have been a few changes that should enable these tests to
succeed on a regular basis, all related to edge cases around updating
a resource's atomic_key and metadata:
Corrected max secs for concurrent trans retries
e37d9fab8f
Don't set metadata for deleted resources
8d7e3e41e8
Allow retries when resource acquires lock
2ec2d5a973
Change-Id: I0fe508cf102bc1041a16c5ce1d9e384ecd591173
This test is failing very often with timeout, let's
skip it until the issue is resolved.
Change-Id: I116a96b20082d1c47068ddc64873200e9ae33a27
Related-Bug: #1651768
devstack has made keystone v3 the default, it seems
the env variables for domain names are not set.
Change-Id: Ief9314b81f8b7624ceb390c432d6487fce5b4a5e
Closes-Bug: #1646343
Skip test_cancel_update_server_with_port till bug 1607714 is
fixed in nova. Related tempest nova tests are skipped
currently[1].
[1] https://review.openstack.org/#/c/348955/
Change-Id: Id08866d5b428a64778423892455495c0182335af
Related-Bug: #1643268
Falling back to environment variable credentials is convenient for
development but could lead to unexpected credentials being used during
tests. Also this is not a known practice for tempest tests.
This change removes the env var defaults and explicitly sets the
credentials to use in prepare_test_env.sh.
Pre and post grenade tests also get their config from the conf file
rather than the environment.
blueprint tempest-plugin-support
Change-Id: Icf9fb4c58ed11483106c2b62d1e1093223f7dc51
In preperation for writing heat_integrationtests config to
tempest.conf instead.
blueprint tempest-plugin-support
Change-Id: I9aa75b0a0052754ede32752a6add93827283a0df
As a transition strategy to running heat_integrationtests as a
tempest plugin, this change puts the test config values in the
"heat_plugin" section. This will allow for either test runner
to be used during the transition.
blueprint tempest-plugin-support
Change-Id: I2eab50be92c998aeb1ee98011908a9828a7efe6c
When we run the integration tests, we download the test image that we
need and upload it on the fly. If the download is aborted because of
some network problem, the image is incorrect, but we still try to run
the tests and boot servers with it. We should fail early instead.
Change-Id: I8797440086206749c9098dcd42b84d95426fbf3e
Closes-Bug: #1534026
Heat integration test test_encryption_vol_type will not work in environments
where admin user is named differently or does not have the same password as
that of the demo user.
The admin credentials is now made available via heat_integrationtests.conf.
The tests which require admin privileges should be run only if admin
credentials are available and use the same.
Change-Id: I5f329be6d4c4249763e0aec8696fb87605a0812a
Closes-Bug: #1546993
Gate seems to be broken due to some recent change. Possibly
https://review.openstack.org/#/c/254755/. Disabling the test
till it's sorted.
Change-Id: Iaae3305b3844be8c20c0652f544abe6a4844fe00
Partial-Bug: #1529058