According [1] the dataclasses is already included in python 3.7 and
foward versions. Attempt to install it fails because the package
doesn't exist. This patch fix the test-requirements.txt to only
install it when python version is lower than 3.7.
1 - https://github.com/ericvsmith/dataclasses
Closes-Bug: #1960603
Change-Id: Iab540e69b698205cbb9c75061313aad9d9c2d3c4
In order to prevent future bugs with new molecule and its deps
versions set strict versions in requirements.
Change-Id: I92d6f34817789c9352a4b3513a14467acc2a7621
Install ansible which contains all required collections, since
it failed with new ansible-compat module.
Closes-Bug: #1957116
Change-Id: Id8b24b24e9540f2aa20128e2ce40837e4e525bd2
tripleo-tox-molecule started failing with the new releases
of ansible-compat-1.0.0 and identify-2.4.3.
This patch locks to previous versions to avoid
the failures until addressed.
Change-Id: I0de852f389979f0e33b9506cdf17712ca4883522
Related-Bug: #1957116
Remove for now "containers" driver and use "docker", since it
conflicts with podman.
Closes-Bug: #1952618
Change-Id: Iaed4f3f74d34e7fc7cd1dd424f551ad090601019
- upgrade ansible-lint and fix reported issues
- allow us to test code using newer versions of ansible
- `yaml` callback was removed
- ini_file module is no longer shipped with code
Change-Id: I899fc736da88de337fd4ee62535755e70d61d63c
With pytest-molecule==1.3.1, openstack-tox-molecule
tests fail with:
ImportError: cannot import name 'ansible_version'
Locking the pytest-molecule until the version bug is
addressed.
Add ansible for test-requirements.tx and install
molecule>=3.0,<3.1 so that all work toegther.
Closes-Bug: #1900033
Change-Id: I0eaf402066f1bb0257ea404926db6bc98ad268b9
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
pprint is a python standard library shipped with the python
itself. There is no package available on pypi and not used
within tripleo-ci codebase. So removing it.
If third party deps is using it, it will be consumed from
Python3 standard library.
Closes-Bug: #1891971
Change-Id: I245a4dba477b42aedce419e45e726dec817cd572
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Iba639e105ef6d8d9223967863ec6ac5d971be58f
- assure we test triple-jobs-gerrit.py file
- fix division by zero bug with above file
- simplified tox.ini file
- prevent accidental regression on CI by checking number of passed tests
- removed test_molecule.py file which was the precursor of what later
become pytest-molecule
Change-Id: Id6ffb9df88a376bcd3c8a0d77b2d378fca8da115
- reverted previours workarounds
- assures we run ansible-lint on our files
- bumped linters
- fixed new problems found by the linters
Change-Id: I7812fcfd17569b0c438f58bec73ab0f4b07e625c
Improve readability of pytest executions by producing html reports
which are also advertised by zuul, saving user time.
Change-Id: I306ad28c855c59f3d575da7a6132782ce02966d7
* Fixes ocassionally pre-commit linting was broken after a merge (-a)
By always running on all files we avoid this rare case from happening.
As seen on https://review.openstack.org/#/c/636160/55
* Fix minor bashare identation error that slipped in due to previous
issue fix.
* Adds .eggs/ to ignore
* Moves whitelist_externals at top level to simplify tox.ini file
* Adds missing file patterns for tox py27/py35 job
* Avoids repetition of file patterns between py27/py37 jobs.
* removed pyflakes as this is included in flake8
* Running just "tox" now works even if developer has alternative python
versions like py36/py37 instead of py35. No impact on CI where job
is forcing use of specific interpreter.
* Remove bindep tox env and include bindep run as part of unittest
environments. This will assure it runs on CI, as it previously din't.
Change-Id: Ia8f98fc0fda18203be3c17d4fdb93d33ca244dc4
Follows the same configuration that was used on
tripleo-quickstart-extras and documented use on tripleo-docs.
Change-Id: Iba8a2db92137f9f6ad28f498627eb1b87039d99f
Story: https://tree.taiga.io/project/tripleo-ci-board/task/381
This adds a CLI interface with the following options:
--stable-release
--featureset-file
--output-file
--log-file
This also adds the code and tests for the YAML file
parsing. I tried adding a specific error case for
when the YAML file fails to parse vs the more generic
case when the file just cannot be opened. However,
mock would not behave for testing the specific case.
We log and raise the exception in both cases though,
and the tests cover both as well.
Change-Id: I0834a0e9b3193c664b377ae7e066fe15239bbfb1
Currently, we do this in a combination of bash in this
repo and the release files themselves. However, as we begin
to support more different upgrade scenarios, this has proven
to be difficult to maintain.
Instead, we will use this python script to create a dictionary
of releases which describes which release will be used at each
point in the deploy: undercloud_install, undercloud_upgrade,
overcloud_deploy, and overcloud_upgrade.
This commit only provides an intial skeleton to work from.
Follow-up commits will provide:
1. The ability to get a DLRN hash for each of the above breakpoints
2. A CLI for the tool so it can be called from the TOCI scripts
3. The ability to parse a featureset config for upgrade variables
4. The ability to output the dictionary for consumption by TOCI scripts
Change-Id: Ibf61d7d12230f6714eb7dad91169aa043f5f8417
This patch adds files so that tripleo-ci can run
pep8 tests, and also be capable of running the
CI status report in a tox environment.
Pep8 tests are currently failing... those will be fixed
in a follow up patch.
Change-Id: Ifdfb0a8f3db0d53097b871408203448266145d50
Ghanshyam Mann