These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: If3fd48454e7959fdd6e2e1708b80a97c76576063
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: I18f3112b7fca0e6af35aa4f6231b9ca9a5414a3e
* 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: Idf4a6cd1e0888576f890b00aa5b343936900d6dd
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: Ia2f3bcba500de242a93d9f0bf073a9c5c3aad89a
* drop xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I6b5b33d17450361f9f11bbc21e0651c2e2d3c0cf
- add non-voting focal-xena bundle
- add non-voting impish-xena bundle
- charm-helpers sync for new charm-helpers changes
- update tox/pip.sh to ensure setuptools<50.0.0
- Note that this depends on I7f17acb4cc4a83fc15655bf6e15c8ff3b3fe92ff
to be able to land this as glance needs xena support to run in this
charms functional tests.
Change-Id: Ieaed39e06a7454f71b1422c46c4fccd72fbe04af
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Sync libraries
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: Id837ffa7bdc3ed4ed739824785d658522dc9e328
Sharing the admin password with peers over the 'cluster' relation
was needed in case the leader would die and the next leader would
then need that information. This was implemented years ago when
the leader DB didn't exist.
This led to a race condition described in the mentioned bug and
can now be safely removed.
Validated by deploying several keystone and glance units, then
removing the keystone leader, then adding a glance unit and
checking that this new unit gets its service credentials.
Also added useful traces, made linter happy and increased fernet
token expiration to avoid spurious test failures.
Closes-Bug: #1818113
Change-Id: I004903e50f51e190467d71691982de26518d7149
This brings it into line with the other charms that are part of the the
enable-focal topic. This makes it easier to add a new bundle just by
changing a couple of variables.
Change-Id: If45c350bb782b5e3367e97153379f2706f8fe4c9
This patch adds a focal-ussuri and bionic-ussuri bundles to the tests
for the charm. Note that this requires a modified zaza (to use the
force_deploy option).
The patchset includes a charm-helpers sync to bring in Py3.8 compatible
charm-helpers for focal support.
It also requires Py3.8 compatible versions of hacluster and glance
charms. See:
- https://review.opendev.org/#/c/711616/ - charm-glance
- https://review.opendev.org/#/c/711617/ - charm-hacluster
Change-Id: I78569b8c51626177164084e4d1f5e18d40f4c3d8
Switch to using get_managed_services_and_ports from charmhelpers.
Charmhelper sync included to bring in required
get_managed_services_and_ports method.
Change-Id: Ib2b1f3dead1dbb613591bdf3903ed56e8c14f45c
This patch also updates the smoke test to run train.
Change-Id: I8cbc3d890e1fbeb05e2eef0354cdb60d849f20b4
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
This patchset implements policy overrides for keystone. It uses the
code in charmhelpers.
Closed-Bug: #1741723
Change-Id: I187f4493392178d87ef7dbd67de841bbeae0c65d
The bundle disco-stein was in the dev_bundles because
a bug with the Python 3.7 syntax prevented the success of
the deployment of HA clusters. This bug is fixed, we can
reintegrate disco-stein in the gate_bundles.
Other minor adds:
- Changing naming convention for vip: 'Amulet' is deprecated.
- Passing OS env vars
LP Related-Bug: #1823719
Change-Id: I787248ad2983858c6db2e5a838270a128dae717a
This charm adds the general ownership audits, as well
as keystone specific security checklist audits.
Change-Id: Iee093b36c54081f14a07c95e677ea08c72d72ca4
Currently the keystone zaza tests deploy multiple instances of keystone,
however, without hacluster.
The recent LP Bug #1801754 would have been caught if the tests ran a
true HA environment with hacluster.
This change adds hacluster and a VIP for keystone.
Change-Id: I7ebd7cd5c1961329080c9ddd7d7e574f925872ae
Switch package install to Python 3 for OpenStack Rocky or later.
When upgrading, remove any python-* packages that were explicitly
installated and then autoremove --purge any dependencies that are
no longer required.
Also drop the python2 shebang from hooks/manager.py in favor of
specifying the interpreter on the subprocess call. The python
interpreter version must match the python version of the OpenStack
payload due to the keystoneclient library imports.
Depends-On: I18996e15d2d08b1dacf0533132eae880cbb9aa32
Change-Id: If973ebc2be3b32ee3ff2122b5874dad96cda9fec
Give machine deployed for database unit more RAM.
Make sure machine used for database unit is deployed first.
Change-Id: I3a2f09396629fda52f9b72284d90756da9cc2536
Starting OpenStack Rocky the currently used `uuid` token format
is no longer supported and we need to change to use `fernet` tokens.
This change provides basic functionalty to initialize fernet token
repository and distribute keys to non-leader units.
A configuration option is also added allowing change of token format
in a controlled manner prior to upgrading to OpenStack Rocky.
Further work is required to implement key rotation, actions etc. and
these topics will be addressed in separate commits.
The commit also fixes a instance of missing release check for writing
of `policy.json`, and a few places where writing of `policy.json`
previously was omitted.
Change-Id: I1d0ff22a5f091b02f5700412745572c246103e9e
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I7fc1db909aa2059f039a09b694c1058322883f4a
There was a mid-air collision with charm helpers syncs. The critical
piece is the removal of a second stats socket line from the haproxy
templates which breaks on trusty.
All other amulet tests that include keystone will fail on trusty until
this is landed.
Change-Id: Ide3b7cbda238b9a7b93f0625c21d43335bc10e81
When keystone is deployed with multiple units but without hacluster one
off scenarios occur where one non-leader unit will fail to update its
client relations.
This change runs all identity client relations when the database
relation is complete thus guaranteeing all keystone units update there
identity relation data with clients.
Small timing fix to amulet tests.
Closes-Bug: #1761562
Change-Id: I338e500dbc155b75c75b9261a9b5b471bd73088a
Openstack PKI token support was dropped in the Pike release.
The following update ensures that PKI token validation is
only run if the release is supported when the sync leader
broadcasts any service credentials to its peers.
In this case; if the release is <= pike. then we can sync
token certs and ensure the pki permissions are valid.
Otherwise this action will be skipped.
Closes-Bug: 1759403
Change-Id: I3d8ba6d3cac3a3505a3722a5082c3a6933a9ef67
For Queens keystone v2 has been dropped. V3 is the only valid API
version. The charm has already made this change. This change is to
bring the amulet test up to match by creating a separate class.
Charm-helpers sync
Enlarging the amulet timeout value.
Change-Id: I822624bdf45bfb060dd75ba3b10e71984bc10e48