The EC2-API project was marked inactive, because of lack of appropriate
maintenance effort[1] and the project was excluded from Caracal
deliverables. This removes testing with the puppet-ec2api module
because we are also retiring this module for the unmaintained project.
[1] https://review.opendev.org/c/openstack/governance/+/902625
Change-Id: Ic8c89e096e9b3acd5a71ec0be1bff20936977bcf
The sahara project was marked inactive, because of lack of appropriate
maintenance effort[1] and the project was excluded from Caracal
deliverables. This removes testing with the puppet-sahara module
because we are also retiring this module for the unmaintained project.
[1] https://review.opendev.org/c/openstack/governance/+/899986
Change-Id: Icb639d2724df41035af53e67de7d24558832adb6
This enables the Tap-as-a-Service plugin in neutron to test the
deployment support we recently added to puppet-neutron.
Depends-on: https://review.opendev.org/906016
Change-Id: I1bed97477fa737733d5b59b7de085e61494c69f9
The puppet-neutron module supports the neutron-vpnaas plugin.
This enables the plugin in scenario 004 job so that we can test
the implementation.
Depends-on: https://review.opendev.org/c/openstack/puppet-neutron/+/900704
Change-Id: Id36ed62e64776b0a7895a3735b13180f708fdfb5
We have occasionally seen tempest failures caused by http timeout in
CI. This extends the timeout to lower down the failure late.
Depends-on: https://review.opendev.org/880120
Change-Id: Ic13252e9adb58de3485375bb17a65c355d322afe
We do not really run in-tree tests from neutron repo but we use only
tempest and neutron-tempest-plugin. Because the required packages are
now installed within virtualenv we don't have to install these packages
additionally.
Change-Id: I9f57a2b81d705731f7edc2711bc528dfe5185d92
This fixes the skipped bgpvpn tempest tests so that the functionality
is tested in the integration jobs.
Change-Id: I2de028ddac3bd8683b092f9b59f0b7bc13be87a3
The metering-agent service is an optional service to gather metrics in
Telemetry(ceilometer + gnocchi), thus is usually disabled if Telemetry
is disabled.
This change disables the service in the scenarios without Telemetry so
that we can validate deployments without this optional service.
Change-Id: I6f1bb575b891318ac83e26450d7b0699a1911b66
This enables the basic API test of Magnum so that we can ensure API and
the conductor services are running.
Also, recent magnum packages require python-werkzeug[1] and we don't
have to install the package additionally. This removes the outdated
(and unused) workaround.
[1] bafe87ce31
Change-Id: I5eb150def6744fb52043ef8413e72514d13f9c2e
Previously EC2 API is always deployed with IPv4. This fixes that and
ensure the appropriate IP version is used. This also fixes the wrong
endpoint urls (we have never enabled ssl for EC2 API).
Depends-on: https://review.opendev.org/872369
Change-Id: I9cf64609c4f2095ae0456388d3b05dd3a512b41f
Currently tempest in Ubuntu integration jobs are consistently failing
because ssh does never succeeds. This change switches from RSA key to
ECDSA key in Ubuntu jobs as well as CentOS jobs, to fix it.
Change-Id: I5d53eea3434be8fa425467b2346da368cd046473
This enables cinder backend in Glance in scenario 005 job so that we
can test the deployment architecture as part of integration jobs.
Depends-on: https://review.opendev.org/844813
Change-Id: I22d48bc7616caf66157110d6f3f5d66d943aee43
Currently there is no test to check functionality of Horizon, and
because of this missing test coverage we didn't notice a syntax error.
This change attempts to re-enable the dashboard scenario test to ensure
horizon configurations can be loaded without error.
Related-Bug: #1965970
Change-Id: I30dd59631cc8a8ae5345c537058d8e08ed827ad3
This is follow-up of 6f090cc74d0eaa6ae835864ff70856bd1e812efc and fixes
the api extension list for neutron which was unexpectedly removed from
tempest.conf.
Change-Id: Ic9ea7ab5429a60b232f90722f6ee7f2871f0c857
This introduces a new scenario (005) to integration tests to cover
ml2+ovn, because ml2+ovn is now the default plugin/mechanism driver
used by Neutron.
Change-Id: I15b52f34c6bff9aa68e9abbecc261af50d59e393
... as rsa key no longer works with the latest openssl in CentOS 9
Stream repo.
Closes-Bug: #1962507
Depends-on: https://review.opendev.org/831336
Change-Id: I7a9a35a263d510301e437e84f7f7c56961977cf5
This change enables Octavia in scenario004 integration job so that we
can validate deployment of Octavia by puppet-octavia.
Because of limited resource in CI, noop driver is used and all of
backend operations like amphora instance management are disabled. This
is the same method as is used in a CI job in Octavia itself.
Depends-on: https://review.opendev.org/828063
Change-Id: I627872dd81d5ca576ea33ecf4755bf8de43df76a
While evaluating new versions of a base
operating system it is handy to have a very
minimal deployment.
* configure_[images,networks] turned off
* tempest api tests only for keystone
Match TripleO's scenario000 deployment:
https://bit.ly/3tBNBor
Change-Id: Ie7ebee89b1ca00ca2fc50b7d1cbd2d8364daca46
We already have OpenStack Victoria releae available in cloud archive
so let's switch our master tests to that latest version.
Since Victoria release is only available in Focal this change also
switch base Ubuntu version from Bionic to Focal.
Change-Id: Ie78b6ef1c3f09fbbc3bc584ac99d2a0acfc5d9d9
We are hitting random timeout issues when intances trying to get
metadata. This version includes a fix for this [1].
[1] e40bcd2964
Change-Id: I7ee221be2a01b0e8b22b51902a81fe29bb624db3
The option is deprecated for more than 4 years already and it will
be removed soon, see the change in Tempest [1].
Starting Tempest 25.0.0 release, CONF.scenario.img_file need
a full path for the image. CONF.scenario.img_dir was deprecated
and will be removed in the next release. Till Tempest 25.0.0,
old behavior is maintained and keep working but starting
Tempest 26.0.0, you need to specify the full path in
CONF.scenario.img_file config option.
This patch does analogically the same change as was done in Tempest,
in order to give users of the plugin some time for removing img_dir.
[1] https://review.opendev.org/#/c/710996
Related-Bug: #1393881
Change-Id: I6f1377e5eb9e81c484795fc80341ca87d7b9ed04
FWaaS is being retired upstream during Victoria release, so we need to
remove it.
[1] https://review.opendev.org/#/c/735829/
Change-Id: I2a8fe7352ea0a6c99ac29455f86eedccff7c9772
In Puppet 3 there was a need to use absolute
names to prevent issues. Since Puppet 4 everything
is absolute by default which makes this not needed.
We need to change this everywhere so that we can
revert the pin in [1] that now prevents us from
using the latest version of the puppet-lint check
puppet-lint-absolute_classname_check that properly
checks that we dont use absolute names.
[1] https://review.opendev.org/#/c/697742/
Change-Id: I78b74fbeb08be7234189e4d266412fb7fb7a73c0
Removes from upstream Neutron in Train release and will be
removed from puppet-neutron in this [1] commit.
[1] https://review.opendev.org/#/c/658801/
Change-Id: Ica68eacc724dad6207b9f085198f921db0279ef6
Adds testing for the bgp-dragent that is
shipped by neutron-dynamic-routing in
scenario004.
Depends-On: https://review.openstack.org/#/c/586462/
Change-Id: I8998a1a0f0a8e944cd5f836b3cbe568aa99fcedb
keystone is creating default roles for member since [1]. This
is "member" and it's not configurable so we need to switch it
in p-o-i too to avoid conflicting names errors (keystone is not
case sensitive in object names).
[1] https://review.openstack.org/#/c/572243/
Depends-On: Icd91bd27d0c0f375d2e99e9c018d3971fc49ce18
Change-Id: Id838d69e4ace9b2ea6c2a9cc6f8fd079d2115dd6
