Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Update requirements, no need for python_version anymore
Drop rocky and queens jobs, those jobs are py27 and are not
supported here anymore.
Change-Id: I2e797d325c9427264ef3dbba7aca15936eb65cd1
By default python-tempestconf will set the same role for octavia
as was set in auth.tempest_roles. In case of more roles set in
auth.tempest_roles, the first one will be used.
Story: 2007471
Task: 39159
Change-Id: I9067a27eab04e6ff8a86f15ee71699321992e95e
Tempest Mistrial tests are skipping in undercloud deployment.
Mistrial service type 'workflowv2' was missing.
In tempest.conf mistrial_service available is set to false
and mistrial tests got skipped.
Adding it fixes the issue.
Closes-Bug: #1867332
Story: 2007428
Task: 39055
Change-Id: Iaa4719ef935cb5ded9d85c7aeb853d46d90b7260
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
ConfigParser only accept strings, these two opptions were setting to
boolean python value, and failing with TypeEror exception option values
must be strings
Closes-Bug: #1866687
Change-Id: Ia37ad9e14b51132f7ffd234e8010188e086a6ddf
Avoid dangerous file parsing and object serialization libraries.
yaml.load is the obvious function to use but it is dangerous[1]
Bandit flags yaml.load() as security risk so replace all occurrences
with yaml.safe_load().
[1]https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html
Story: 1634265
Task: 38963
Change-Id: Ie5baf64696e6214e3dd01f6e06ede8fd8432cbb8
centos7 packstack jobs are not compatible with python3 plus it seems
python-tempestconf is the only project which uses packstack-allinone
job.
The change replaces packstack-allinone by packstack-centos8 job and
makes packstack jobs voting again.
Change-Id: I81f700f739fd212f57fc6f4121e6a25f48163103
The patch set all back-end storage pools that are
known to the scheduler service for share and volume
services.
Change-Id: I9abb849cd28b8c4c7874919fb271d6506cb7a255
Add support to discover Barbican service, so that we can set
service_available/barbican automatically.
Change-Id: I96800a95f844ce7675d266e456e01620e63e347a
Since nova network feature is deprecated long time ago and was used
when neutron service is not enabled then nova lists the network and
set the compute.fixed_network_name in tempest.conf.
Since now networking is taken care by neutron, so it is no longer
needed.
nova network related client code is also removed.
Change-Id: I47c791e9257e262f6ac17fffaa2b4af6273a168e
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
In nova less deployment, nova service is not there, so there will
be no compute section in the tempest.conf byut when heat service
got detected, it tries to update the compute section which does
not exists leading to no section error.
It fixes the same.
Closes-Bug: #1860017
Change-Id: Id793975b2cc30038638275fe9f381ae21e6369bc
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
json in python3.5 requires that json object must be a string, not
byte object. In python2.7 or 3.6 it doesn't matter, it accepts both.
Depends-On: https://review.opendev.org/#/c/702448/
Change-Id: I10a2805b599767cbd1f5553c1640f68c25e85522
Currently tempestconf calls create_tempest_networks method
without checking neutron service is available or not which
leads to 'NoneType' object has no attribute
'create_tempest_networks'.
Making it conditional fixes the issue where we explicitly disables
the neutron service.
create_tempest_networks also contains the logic for creating
nova network and earlier it was called only when has_neutron
is false. nova network support is deprecated long time ago
and this change already pushes network creation part to
conditional then it will be never called.
Change-Id: I10f282e2a813060419e213dd25641078774a852d
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
tripleo-ci-centos-7-standalone-os-tempest was added while porting
tripleo ci jobs to os_tempest and now the porting is done.
tripleo-ci-centos-7-standalone-os-tempest and
tripleo-ci-centos-7-standalone are the same job, It replaces the
existing os_tempest job to plain tripleo standalone job to keep
consistency at all places.
Change-Id: Ia4491e375117e8cdb4b4c16db632f745ae3714c7
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Add train devstack jobs.
The packstack master jobs are failing on time out issues when spawning
a server. In order to unblock the gates let's make them non voting until
the issues are resolved.
Change-Id: I97c7cf2b808195acf0a5a08b318af522abe03216
The options are used in ec2api-tempest-plugin [1] and based on their usage
in the plugin they should be under [aws] section, not [boto] one.
[1] https://opendev.org/openstack/ec2api-tempest-plugin
Story: 2006906
Task: 37548
Change-Id: I6f787e140162bafce0eca85ebf96b0bfc5f48903
Currently in packstack deployment, we are collecting logs
once the deployment finishes and then we run tempest tests and
collect tempest related logs.
If the tempest tests fails, we have no openstack services logs
with tempest api calls in service logs, it is very hard to find
out what is causing the failure.
Copying the openstack services logs just after tempest runs
finishes will more info about the failure.
It also disables the copy log operation once packstack
deployment finishes.
Change-Id: I5ab038a49eeabe564650894f50c3b51e33e93fd2
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Configure compute/min_compute_nodes to have the number of the compute
nodes, to enable migration related tests in the env where we have
multiple compute nodes.
Change-Id: I646e355c5c8e46cc1f057c26fe61e5068a6d00f9
Add support to discover Designate service, so that we can set
service_available/designate automatically.
Change-Id: Ie4c092fc0b9d007b0ffdbf41d32d35679ed1b7f3
Let's download cirros image using https because http is slower and may
results in timeout issues. Also using https is a better practice.
Change-Id: I57a3e078932d1ef69f2eafdc589a9d4d17918483
Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
Change-Id: I4a4c07ffaacb65e9ee919fb7a0d25de3c0840e12
The TripleO undercloud will soon have no nova or glance due to
blueprint nova-less-deploy, however it is still required to run
tempest tests via a discover-tempest-config generated config.
Currently this fails due to always attempting to list existing flavors
and images.
This change only runs flavor and image code if those endpoints are
available.
Change-Id: Icffce84638e0db099626d5a86a84f44472943a69
Story: 2006527
Task: 36573
Because openstacksdk superseded os-client-config module, it is
recommended to use this module instead.
Story: 2002021
Task: 19662
Change-Id: I6f225416ff4791a00b04655614eb8f24bed8ae7b
Make sure that python-tempestconf will not fail due to a missing
value when heat-tempest-plugin is configured.
There has been a situation when python-tempestconf failed when it
was configuring [heat_plugin] section for a user whom intention
wasn't run the heat tests. Therefore the patch adds just a log
message there to inform about the missing value only users who
are going to run the heat-tempest-plugin.
Story: 2006277
Task: 35978
Change-Id: I2d10a03e444f29d3ffc4500e27be2e1688fa664b
Mocked request() was returning MagicMock object, which caused
test_do_get() to fail. This was caused by what seems to be
inconsistent behaviour of MagicMock object on different
platforms in Python 2.7 [1].
Ubuntu 18.04, Python 2.7.5, mock 3.0.5:
MagicMock() >= 400 -> True
CentOS-7, Python 2.7.5, mock 3.0.5:
MagicMock() >= 400 -> False
Story: 2001245
Task: 36038
[1] https://github.com/testing-cabal/mock/issues/196
Change-Id: I7d41ec9abd87b4c799f4c7797d76da5350ca90bd
When downloading of new file fails due to short and temporary network
issue then wait a few seconds and retry to download the file again.
There were situations when small network issues caused python-tempestconf
to end with an error.
Story: 2006231
Task: 35832
Change-Id: Ie3f1d8b412dccecac2b05f6b5f540e36824777a4
The review fixes permission denied issues while either tempest.conf
is copied to /opt/stack/tempest location or a tempest plugins are
installed there.
Change-Id: I16bbc2faccb31af04867757aa4357d55ee4de572
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Iaab467617fcc7775b425518c1378b907ec7e9003
The patch removes setting compute_feature_enabled.api_extensions
from tempest.conf as the extensions have been deprecated since
Tempest 14.0.
Story: 2005794
Task: 33521
Change-Id: I118c4ac1eac43db6b99605e830467b386be7c0b3
The current code led to a situation when volume-feature-enabled.backup
option in generated tempest.conf was supposed to be False, but
python-tempestconf left there the tempest default value (True).
The patch fixes that.
Story: 2005820
Task: 33575
Change-Id: Iec08dfe1a9bb9c3fa573b5132ecc55f634a6cc07
The current code mixes service type and service name based on
the context. Service type should be service type allways. The
same applies on service name. The patch clears the difference
between these two different variables.
Story: 2005820
Task: 33577
Change-Id: Ifdeaa2b854dfa2dcfda1491b522e4e67b822fc4f