Update tox.ini to support the new TEST_CONSTRAINTS_FILE
Additionally pin netaddr in test-requirements.txt. The latest netaddr
1.2.1 release throws an error when passed None, which it previously
didn't. This causes MonContextTest.test_ctxt_missing_data to error out.
This should probably be fixed in charmhelpers later.
Change-Id: I5bf8900c426395421c73ec3d52ebd691cc5496f8
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: Ieb1ef7b7ab76775f5769621a6a7cbcfb18c40b7f
This patchset adds these 2 additional keys to the ceph.conf file,
which are used in multisite configurations when present.
Change-Id: I51ca46bbb3479cb73ec4d9966208ed794f0ed774
Closes-Bug: #1975857
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.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: If352ea32d18cd3d1d8bc5577a32c0397e1cb7e93
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I4346d715d47b77e862ecf75d6ab6f00e1dcab752
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I6c46959aa659454d28880e375e3488058227dca7
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I13a2e11b53e290316919efca90aaa513a1f40975
We need to unpin flake8 to allow linting on Python 3.8 systems.
Sync charms.ceph.
Depends-On: Idf2fea27b19cec47ffed9891b518ac7b5b75e405
Change-Id: I91a2133b6d7dc7e59d62dd80779cdc6e77206a20
This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again
Change-Id: I3f4b9ba3177a1262468d4222a9f9c4f3df078398
This change adds in zaza.openstack, as well as changing the
branch target of zaza to a branch with zaza.openstack
removed, allowing us to validate the new library
Change-Id: I72415540bee6eea1969432bb3e35a5573def9d49
Because we have charmhelpers in-tree, adding it via
test-requirements.txt means we have duplicate modules
Change-Id: I7109f96124b3b52fd25a41d3ac60c37e651eb43a
Drop amulet tests and create bundles for all target
Ubuntu/OpenStack series combinations inline with
current best practice.
Zaza tests are not a direct translation from the Amulet tests;
the new tests focus in Ceph RADOS Gateway and integration with
keystone rather than deploying compute, image and block
services (which do not make use of the ceph-radosgw charm).
Change-Id: I41914df024eb02e5a555bc0e44993e09d310933e
When the TC merged I2637dd714cbb6d38ef8b8dc1083e359207118284 we're
supposed to invoke stestr rather than testr so lets do that
Change-Id: I151eb37008936358bd4108a2510c924c261dba8e
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: Ia9a42cd4a76a6fa8a70e7092b9d61657816d2d65
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.
Rename amulet tests inline with gate-*, dev-* and dfs-*
naming standards.
Update README to refer to functional testing section of the charm
guide.
Change-Id: Id91a7281d98be3bb69d42257ea9213471bdefa69
The new release of charm-tools no longer ships the charm
command; update minimum version requirement and switch
to using charm-proof instead, unblocking current pep8
failures across all charms.
Also pin the version of requests to 2.6.0 until theblues
(indirect dependency of charm-tools) sort out its
requirements versioning.
Change-Id: I10271bfa64674a4789d1cc623a2a7250a154ec43
Trent Lloyd