Refstack-client is dropping support of python2 and also all python3
versions above python3.8
Changes:
-requirements.txt - added license on python-subunit
-setup.cfg - removed python2 and python3 versions below python3.8
- added python3.10
-setup_env - removed all python2 mentions
- python3 min version set to 3.8.0
- added parameter l which will force installation of
python into ${WORKDIR}/.localpython
-tox.ini - removed py27 from envlist, added py38
Change-Id: I6500ed950cb9bc07d87370940b4752e686712c14
The commit updates tempest version and removes Ussuri and Train jobs
as those aren't supported by the community anymore.
The patch also updates old openstack.org links.
Depends-On: https://review.opendev.org/c/openinfra/ansible-role-refstack-client/+/854211
Change-Id: Idf69f02ba844bdeea21ec744ec41ca78bbd1907d
Add Python 3.9 to the list of supported Pythons and replace
dashes (which are deprecated) with underscores.
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I12cc6206ebfe06b7cf3a50ea59bf1b55a3ff7303
tox deprecated its whitelist_externals option in
3.18 release. The patch bumps the min version of tox
to 3.18 and renames the option from whitelist_externals
to allowlist_externals.
Change-Id: I06bf94861056e06722da839f7c5c8c60be2fc6ee
The commands used by constraints need at least tox 2.0.
Update to reflect reality, which should help with local running of
constraints targets.
Change-Id: I35e4facae2d35838a73cdb6100968e98b550ea43
The patch edits the code so that it complies with W605 rule
wherever it makes sense. W504 rule is added to a ignore list.
High version cap of pyflakes and flake8 packages is increased
as well.
Change-Id: I51558ee9c808e03b4164d0832fc525c5556dddd1
Interop repos are going under rename from
openstack namespace to osf namespace (Depends-On),
which need update the zuul job to start using the
new location.
Update .gitreview as well.
Disable py27 and py35 jobs, they don't work anymore as is.
Depends-On: https://review.opendev.org/#/c/734669/
Change-Id: Ib6871eaf0735e756f051d14513869fbe7cc6e826
The review:
* adds a python3 job in order to test the refstack-client with
python3 as well.
* adds a job which runs unit tests by python3.7
* changes default python3 (when -p 3 is specified) in setup_env script
to version 3.6.0
* converts downloaded list of tests from bytes to str in order to unify
the types used for python2 and python3 compatibility.
* edits -p argument in the setup_env script so that it also accepts a full
version of Python a user wants to run with, before there were 2 options:
* python2.7.8
* python3.6.0
* sets object-storage.operator_role to Member in tempest.conf in order to run
tempest.api.object_storage.test_container_services.ContainerTest tests
Change-Id: I961f0f093bd7d40fde7e448ea12ef9907c61d126
A month ago a flake8 3.6.0 version was released and it's been causing
pep8 check gate fail since then.
This patch
* removes flake8 dependency from tox.ini file, because otherwise
version defined in test-requirements.txt is not taken into account.
* flake8==2.0 version is too old so the version is bumped, however, it's
limited for versions < 3.6.0
* pyflakes version needs to be bumped too otherwise it doesn't work
with newer flake8 versions
Change-Id: I470d1e8ae69aff87dcc9bf9dfa988370efb2817d
Usage: $ refstack-client config --use-test-accounts <path to test
accounts file>
If not accounts.yaml is passed then:
$ refstack-client config
It will generate accounts.yaml and tempest.conf in etc folder
* It adds support for the above command
* Added zuul based devstack job to run the same
* let setup_env handles the installation of tempestconf
* updated git url for tempest
* It also generates accounts.yaml if no account file is
passed
* we can --overrides flag to overrides the tempest.conf
value.
* volume-feature-enabled.api_v2=True is added as default
in overrides as it is deprecated in Rocky cycle but needed
for interop tests.
Depends-On: https://review.openstack.org/589260
Story: 2001696
Task: 19758
Change-Id: I9cabfc52672e7a8a54792ca9d867c62babf12cb7
Implement optional cleanup to support the new PTI jobs
for documentation which won't use tox anymore.
Docs tox environment will still available for developers but
it is no loger used in the gate to construct the documentation.
See http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html
Change-Id: Ib26b711365389c59658f9d7f6cafd5acb736dfce
* Let tox auto handles the setting for LANG variables in order to
fix py35 tox venv creation and installation.
* Use OS_TEST_PATH in tox variables and re-use it
Change-Id: I534ed66d154b6b05a03a06eb0baa0ff23d851f4e
* As stestr is the successor of testr, it's time to switch to
stestr for running refstack unit tests.
Change-Id: I3b9c0e2b4363dec24bad43bf5cfbeef4ecc7a37c
Running py2* post py3* tests results in error. Add
'rm -f .testrepository/times.dbm' command in testenv to
resolve this.
Change-Id: I29d6247e11f1c9c207e9b89c0ae41f590141d281
Added feature to upload test results in to Refstack API signed with
your personal RSA key. Just do upload with key '-i PATH_TO_PRIVATE_KEY'.
You can use your general OpenSSH key ~/.ssh/id-rsa or
generate a new one with 'ssh-keygen -b 4096'.
Change-Id: Icce6d7146f0fa9de892d1f4785ef24f17fc9b286
Previously, after the run_tempest script, was run, all post-processing
was done only if the returncode was 0. If it was non-zero, an error message
was given. This was an oversight, as the run_tempest script will return a code
of 1 when any test case fails. This leaves the unintended side effect of refstack
not parsing the results or producing the output json when Tempest successfully
runs, but a test case fails.
Checking for the existence of the expected subunit file will at least validate
that the Tempest test was at least started successfully, and didn't fail to run
due to some misconfiguration in the environment.
Change-Id: I541b798db41b713525efeb8dedfb9347be780a3f
