This patch updates some featureset configuration files that are
defining 'tempest_tempestconf_profile' with overrides set to
'tempest_tempest_conf_overrides'. Since [1], a new var was added
to hold tempestconf profile overrides. This patch combines
both 'tempest_tempestconf_profile_overrides' and
'tempest_tempest_conf_overrides' to define tempestconf profile
overrides, since lots of jobs definitions still use
'tempest_tempest_conf_overrides'.
This fix is needed since these configuration files are currently
defining 'tempest_tempestconf_profile', see [2].
[1] 1003438006
[2] 1003438006/defaults/main.yml (L319-L325)
Change-Id: I86289df6d6480405b7b6e0ee7028978f6c9a4ab7
Signed-off-by: Douglas Viroel <dviroel@redhat.com>
Current config assumed deployments to be based
on single-nic, update minimal featureset to support
deployment with multiple-nics-vlans network_isolation.
Not changing any defaults with that patch, user
who want to deploy with multi-nics-vlans can
pass -e network_isolation_type=multiple-nics-vlans
to quickstart deployment command.
Required networks will be auto created and attached
to overcloud and undercloud vms to support multi-nic-vlans.
By default 6 networks will be created with this config
each for ctlplane, Internal, Storage, StorageMgmt,
Tenant and External.
If want to created different number of networks or
with different name can be done by passing
extra_networks var like:-
extra_networks:
- name: data
bridge: br-data
- name: tenant
bridge: br-tenant
- name: ovcexternal
bridge: br-external
Need to use seperate name as used by default_networks.
Depends-On: I82013d33c1729619e47b633bddd1580e9efe0b55
Change-Id: Ife4d31ecd9912b424a178cc4bbc0d6de7216e512
We changed the minimal featureset to use baremetal
provisioning like other featuresets for ussuri.
We need to add --disable-validations for it.
Change-Id: Icb1fbcf6e5f88c6e7dbccb02d2906d72dfcbba22
This featuresets still deploy installed heat, Converting
it to use ephermal heat.
Test was failing master jobs in ci.centos.
Change-Id: Ibbe125c2825cba36270f5f46ebbec4e7150a3464
Related-Bug: #1944217
The deaployment args were showing up as:
--disable-validations--disable-protected-resource-types
This review removes th e yaml dashes to add the required
spacing in the args.
Change-Id: I0cc787837d304e7d1d67864ca75c88efcf225311
This patch removes:
* legacy tripleo-validations config boolean, since now the role
is in tripleo-validations repos and is enabling by another
configuration in the zuul config directly
* documentation, because its now outdated and a new one should
be moved under tripleo-validations repos
Change-Id: Ibc5e1aec08643d53760953ebb1c026e99689a2b6
Since we are working in process of removing tempest container
from wallaby release and all the tempest run is switched to
os_tempest for all supported release in tripleo-ci.
This change is not going to affect any periodic jobs also.
It also removes run_tempest and tempest_format var.
Related-Bug: #1916875
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I3d046047833044fd2d75ba399f784be5d992fbef
Adding the vars:
run_tripleo_validations: false
run_tripleo_validations_negative_tests: fasle
to the config/general_config/minimal.yml, and fixed the error
due to the lack of value.
Closes-bug: #1915265
Change-Id: I6d44ba89ea067c3dc474dcd7c35184b66483a32c
This configuration should not be used in featureset, because it would
never be overwriten, it should be in the playbooks/tempest.yml in
tripleo-quickstart-extras
Change-Id: I06480c30e0c671c3f97361c8bdc06c5fc28dfb94
Removes the redundant undercloud mapping from featuresets.
We've the default mapping in environments/undercloud.yaml.
Also this CI specific environment is redundant.
Change-Id: I72e41fb8cdebff12aab9704c2a9c4e368410c1ad
* Since tempest is runned using tempest container so
undercloud_enable_tempest is set to be true so that it will enable
tempest in undercloud.conf and pull tempest container on undercloud
registry and reuse it from there while running it.
Change-Id: Ibe7e873f204679f25c09ea51b3818f7eed3b53e5
Closes-Bug: #1800682
Tempest container is available and built when we deploy
containerized undercloud.
Since undercloud is containerized from rocky and ongoing, this patch
enable containerized tempest when undercloud is running as container.
Also, moved all tempest related configuration to the end of file to
avoid overwritten options
Depends-On: https://review.openstack.org/#/c/580384/
Change-Id: Icdb0f2b033ad0d1ba2548c591fa32dc649fff319
config/general_config/minimal.yml tests Ironic provisioning
of VMs, therefore it requires eth1 to be included into br-ctlplane
bridge. T-h-t default net-config-undercloud.yaml provides that
functionality, while the one from
ci/common/net-config-simple-bridge.yaml does not.
Closes-Bug: #1782267
Change-Id: I460b2e0e47be737dfdfd84bbace81f7ee2f4f733
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
We have ntp_args which include ntp_server variable. Don't set it
in extra agrs so we can overwrite it.
Change-Id: Ib6a30b4581f095b89f0a128232c165c53a716a48
The minimal configuration for libvirt based
deployments was slightly out of date
Closes-Bug: #1781541
Change-Id: Iee97dcf6968504c1bf9d4d3f2094be2602401500
Bug was introduced in https://review.openstack.org/#/c/566527/
Set default value for tempest_format in logs collection role
when it publishes docs.
Closes-Bug: #1776164
Change-Id: I25a73bbd3804cf013f38627ca3d742e3a6a2f5d1
Now that config-download is the default across tripleoclient and
tripleo-heat-templates, we can update all the CI jobs to remove the
explicit --config-download and -e
environments/config-download-environment.yaml.
Note that --deployed-server didn't actually trigger any needed behaviors
with --config-download, so where it was used, it has now been removed as
well.
Change-Id: Ic5c5df350a7eb5291d45cf8e229af575fe9bed57
* https://review.openstack.org/551441 introduced test_black_regex
in order to skip test directly from featureset files. In order
to avoid confusion between test_regex and test_black_regex, we
are renaming test_regex to test_white_regex.
* It will fix all the featuresets.
Depends-On: https://review.openstack.org/560006
Change-Id: If66225c2e2f8c571cc85aebacee01431e4f64dcc
Running ping test depends on Heat and ovb-ha.yaml doesn't have it, go back to
ping test only for old releases.
Change-Id: I1390d74800221ba28dcf966e6c89d99d25b90152
The minimal config is only used outside of the upstream CI
system. We cover both ping and tempest upstream but not
across all the releases. Let's use minimal.yml as the
config that should work across rleases to verify that
both ping and tempest are working correctly from a
CI standpoint.
Change-Id: I23cb01a5f753214897a0e59b4adc45e910fb3cf3
There are several configurations that are no longer
very well tested due to limitation in ci.centos.
Consolidating on configurations that are tested in upstream
and rdo.
The patch rebases minimal and pacemaker configs to be
exactly like fs001 w/ single-nic-vlans instead of
multiple nics
Related-Bug: #1737602
Change-Id: Id26eb558800b8fccc5e5f2c2f9684545e445bc6d
We should install tempest plugins via the tempest role.
This is done at run time and is more transparent to the
user.
In this review we are also enabling tempest and
disabling ping test in order to test the consistency
in ci.centos.
Related-To: 1736252
Depends-On: I58a955943191045324956bd61da0652076984e8c
Change-Id: I04635ed37c4f40a7310d311539138ab0d64c0c97
This patch allows us to run tripleo-validations tests through the
Mistral framework and running negative tests from Ansible directly.
Depends-On: Iec07a18322252af2d484bc3f06a59dbd1b08f537
Change-Id: I2e0831fc8b7bdf6acca1d0f99bf41adcad94f688
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
This patch adds blank newline for each [yaml|sh] files if they
don't end with one. This will allows us getting linters happy and avoid us
having git adding "\ No newline at end of file" in diffs when pushing
a new patch.
In other way, you can configure Git to properly handle line endings in
typing:
$ git config --global core.autocrlf input
Change-Id: I8a113541b3eae6a36ed32995822dedbbd2d9666e
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
This change takes the overcloud_nodes variable and defines that
under config/nodes/foo.yml. This depend on the change
to quickstart-extras where a definition of topology (nodes)
will be created. Pass the topology in an explicit variable vs.
using extra_args.
The original configuration files in config/general_config/ will
continue to work but are now deprecated.
The featureset files that define standard set of feature to test are
also added, and should correspond to test configuration for jobs that
are typically found upstream
Change-Id: Id6dd3f71b33f76a0401fe8a84080fe80de0dbb69
Co-Authored-By: Gabriele Cerami <gcerami@redhat.com>
We introduced a few network isolation types support in
patch https://review.openstack.org/#/c/437437.
Now it's required to set type of network isolation.
Set centos.ci network isolation type by default to single nic
with vlans which was used always by quickstart before.
Change-Id: If3ad22a2db0cb9420264745620aa57841da5f1dd
Currently introspection with virtualbmc is failing with following
problems:
https://bugs.launchpad.net/tripleo/+bug/1651719https://bugs.launchpad.net/tripleo/+bug/1651704
Until this is fixed and as a temporary workaround to allow promotion
in rdo-ci i'm proposing to disable introspection in minimal job. Note
that it's tested in periodical job in upstream TripleO CI.
Change-Id: I23727e6ab709bd030177a915c47fdaca8f80f414
This patch is replacing the usage of the pxe_ssh driver in Ironic in
favor of pxe_ipmitool + VirtualBMC*. The main reason for this patch is
because the pxe_ssh driver is already marked as unsupported and will be
removed from Ironic upstream at the end of the Ocata release.
Older releases: Liberty, Mitaka and Newton will continue to rely on the
pxe_ssh driver.
* VirtualBMC is a proxy that converts IPMI commands to libvirt calls
Partial-Bug: #1645733
Change-Id: Iaaa9fc1fd593cbce045456f4341c461a8eea82ad
Review https://review.openstack.org/#/c/397312/ has removed
some options in tripleoclient.
Specifically, --neutron-network-type and --neutron-tunnel-types
are being used in tripleo-quickstart. This patch removes them
from extra_args.
This parameters are being passed via environment files or using
vxlan by default so i think it doesn't need any other adjustment.
Change-Id: I8f9b52e7a0e78266fab0717e20a9710be264f5aa
The main place we test tripleo-quickstart (ci.centos.org), struggles
to provide consistent results running tempest. The hardware there is
heterogeneous, specifically three of the four chassis there have
slower CPU. When a job that runs tempest is scheduled to one of these
nodes, the deployed cloud can not handle the load and fails random
tests. This is problematic because it gives us a 75% false negative
rate for jobs that run tempest.
There is some new hardware being purchased for ci.centos.org that
will be put in a pool that can be specifically scheduled to. In the
worst case, we can re-enable tempest jobs at that time.
There is also some possibility of tuning the performance on the
underperforming CI nodes in order to drop the false negative rate.
Change-Id: I6302d20f869dfcf9517965468752d483c8acafbb
This reverts commit 6f818ea426.
Also reduce the tempest_workers to achieve stable tempest results.
Depends-On: Id7269556526d0240d145877d163c6afc78d37761@gerrithub
Change-Id: I9a4491d260062d29a1050741a9bbf6e0d8df9c94
Unfortunately, the CI infrastructure is not able to handle running
tempest on top of our virtual cloud. We need the minimal job to
have a very low rate of false negatives, and right now it is at
100 percent. As such, we should return to using the ping test until
tempest can be proven to work on quickstart deployed on the
ci.centos infrastructure.
Change-Id: I6f8c41b30d2b6d38d84711de6d73418959ccd580
Ghanshyam Mann
yatinkarel