| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Some test have been unstable in Ubuntu Jammy because of the known
libvirt bug, and we have disabled these in functional jobs.
Let's disable the test case in grenade jobs, because these test cases
now cause frequent job failures.
Related-Bug: #1998274
Change-Id: I7038ce3ec2840b133e9ae5eb09a96dc8a5f3abc2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Heat upgrade script set the env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE
which are used to use the constraints during Tempest virtual env
installation. Those env var are set to non-master constraint when
we need to use non-master constraints but when we need to use the
master constraints we do not set/reset them point to master constraints.
This create the issue when this grenade script install the tempest with
stable constraints but with master Tempest and as there is mismatch of
constraints now with fasteners of stable branches. Below is failure
of heat greande job on stable/yoga
- https://zuul.opendev.org/t/openstack/build/3aaec4d59bb84068bb4d4428ea747cbd/log/controller/logs/grenade.sh_log.txt#3245
Similar way, role should set stable constraints only for the stable EM branch
not for all otherwise it fail when constraints/requirements are bumped.
- https://zuul.opendev.org/t/openstack/build/74f86b8097f44c35acaffdcfe41d9693
We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.
Closes-Bug: #2003993
Change-Id: I024cd134577338fc1075e7742df7f006dc914646
|
|
|
|
|
|
|
|
| |
stestr has removed whitelist / blacklist. This change updates the
devstack upgrade tests to ensure we use the new include-list instead.
https://github.com/mtreinish/stestr/commit/9ffeb470fb4eaed484152d35411668db19a64ace
Change-Id: Ia0df9b3468fee9382c42c8bd6a35b76ed7f2b4e5
|
|
|
|
|
|
|
| |
This change removes the cloud watch cleanup tasks
as part of general housecleaning.
Change-Id: Id8f678dfd504ff27d6fdb86011129d353a31f3cf
|
|
|
|
| |
Change-Id: I94075f261ce095c509635aab395df42878aceb1c
|
|
|
|
|
|
|
|
| |
As a followup for change I6a8cffdc86c895eebe4269c5cd37841325566c54
let's use branch specific upper constraints when running tests in
grenade.
Change-Id: I71f8398b6aa57b7c1910750b8e048825383e3d9a
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Setting RUN_HEAT_INTEGRATION_TESTS=False disables the Heat
integration tests which are normally executed by Grenade
after the deployment of the base environment and after the upgrade.
This is useful when Heat is used in a Grenade job of another
component, where the focus of the testing is not Heat itself,
thus shortening the run-time of the overall Grenade job.
The default behavior is unchanged.
Change-Id: I47b258fecd45ebc08c82df179625bcfb57a32894
|
|
|
|
| |
Change-Id: I25930a4af9b67e98c7705ad8801bfc6e5a7c0d72
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are updating all Python projects to publish artifacts to PyPI. The
name "heat" is already taken there by another project, and they have
rejected our request to claim the name. We therefore need to change the
dist name used to package heat. We have some other projects publishing
using an "openstack-" prefix, so I propose using the name
"openstack-heat". This will not change the imports or anything else
about how the code works, just how it is packaged.
Add a grenade plugin for upgrading between the packages with different
names so that we can clean up the old version of the code and avoid
discovering the heat plugins multiple times in different locations.
Change-Id: I59b55cffd9e648f842eb286b936f09c5b55a76db
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
|
|
|
|
|
|
| |
This patch defines the specified set of tests & runs these during
upgrade in grenade-multinode job.
Change-Id: I99fa1717f4bf46afc8dd989a3aae129e5c4ab9d7
|
|
|
|
|
|
|
|
| |
* Change transport_url to test Heat's upgrade strategy [1] in gate.
[1] https://review.openstack.org/475853/
Change-Id: I08770d2ae09891d7983345616186cff7c26df4ce
|
|
|
|
|
|
|
|
| |
Tempest has switched to stestr. Update the group_regex in
.stestr.conf
Change-Id: I6f12f95367748828977550ede5043d2f6b7e9970
Closes-Bug: #1750960
|
|\ |
|
| |
| |
| |
| |
| | |
Change-Id: Ie573f27d47e7e88cde27712a12aa8b40b5afda8b
Closes-Bug: #1720988
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: Ie18d80e8faaec984b127ab3abeeb66d6a3aa1b6c
|
|/
|
|
| |
Change-Id: I3a3744fa116a2d424b2afd95eb89058ad78d7f0b
|
|
|
|
| |
Change-Id: I0f5b7204c6dc3cf7bfe50acc5427590ee35d202f
Closes-Bug: #1711282
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Use domain ids along with domain names
It's possible that either the domain_id or domain_name
is set in the env.
- Adds an workaround for bug #1662911
- Fix shutdown script for apache
Change-Id: Ib9d3c14327d73d8cb0e0cddcc9d16191797ffffa
Closes-Bug: #1663105
|
|
|
|
|
|
|
|
|
| |
This reverts the workaround for the devstack plugin,
as now the gate jobs pass(with the plugin and no devstack
tree heat code) and make it only a devstack plugin.
Change-Id: Ia8d88eca2dec301b692bbef3e1d8988f00e1936a
Depends-On: I5b60422bf1f5fa78aa8f3383f7a222e0356d9e42
|
|
|
|
|
|
|
|
|
| |
Now that base and target releases are incremented in grenaderc,
we should run the integration tests using tempest plugin before
upgrade.
Change-Id: I39b7758798ff94401fda042ff6954de75821e8bb
Closes-Bug : #1627297
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We seem to be running quite a few neutron tests during
upgrade and it seems to result in neutron quotas for
resources being exceeded, when tests run in parallel.
We should avoid running them.
Change-Id: I0a88f509af05a98ddd4811ea920a81cc997a0c6a
Closes-Bug: #1618789
|
|/
|
|
|
|
|
|
| |
Now that we've the devstack plugin in-tree let's use
the functions from the plugin for upgrade, so that
we can remove the devstack tree heat code.
Change-Id: Ic392bcc24bc374ee8511a94f1d8f6ac23131c7e3
|
|
|
|
|
|
| |
completes blueprint tempest-plugin-support
Change-Id: I0109e68bb135cd257e2fff74e75575a7e2f91539
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Change-Id: I1a064648a2bee046e9b5afeafb40ede0ece748eb
Closes-Bug: #1561810
|
|
|
|
|
|
|
|
|
| |
Some echo message contain error or warning message which better be contain in
stderr. And futher more some error message already contain in stderr, but for
error message reader, the following information for that echo should be
contained as well.
Change-Id: I2aac631df19829218d446150c91cf6d50aa5e7e7
|
|
|
|
|
|
|
|
| |
This includes lib/apache from devstack as the devstack heat plugin now
requires it.
Change-Id: Ie48e417f2b36ce79c3485e559b6141a1499b6eb1
Closes-Bug: #1511369
|
|
|
|
|
|
|
|
| |
Due to some fix in devstack, using the old lib/heat library doesn't work
anymore, so let's replicate the stop_heat function.
Change-Id: I8e7c62962cef29e35c37ad98a1646630388fb4ab
Closes-Bug: #1506462
|
|
|
|
|
|
|
|
|
|
|
| |
Ceilometer services are now enabled and controlled via a plugin
with this change Ie3219a41a3d371d9ac21552e3d8b15775ea696f6. This
means we can remove all ceilometer specific manual config entries
in the grenade plugin.
Related-Bug: #1489436
Change-Id: I2fbff1fed38ac8acc8a7950024714abea049aeb8
|
|
|
|
|
|
|
|
|
|
| |
Only a few tests are run because these tests only verify the
sanity of the build rather than doing the upgrade tests itself.
Closes-Bug: #1482152
partial blueprint upgrade-tests
Change-Id: I8fed19bd25cc3a62c03c35afafe2b662551dbd4e
|
|
The following implements in tree support for grenade upgrade testing
for heat. It includes the expected directory structure to be used for
the external plugin.
For now, we create a simple OS::Heat::RandomString resource
and check whether the stack survives the upgrade.
We should add better tests for upgrades in the future.
Co-Authored-By: Steven Hardy <shardy@redhat.com>
Co-Authored-By: Sergey Kraynev <skraynev@mirantis.com>
Co-Authored-By: Emilien Macchi <emilien.macchi@enovance.com>
partial blueprint upgrade-tests
Change-Id: I0847004a8ac023a113cabaee46896abc823a01da
|