Drop configuration key 'source' override in rabbitmq-server and
mysql-innodb-cluster applications.
Add bindep.txt to install package dependencies needed to run unit tests.
Related-Bug: #1991528
Change-Id: I345e3bb7be7492286daf9e5ab36506915f3daab9
This patch adds the service user rotation feature, which provides two
actions:
- list-service-usernames
- rotate-service-user-password
The first lists the possible usernames that can be rotated. The
second action rotates the service, and is tested via the func-test-pr.
Change-Id: Ia94ab3d54cd8a59e9ba5005b88d3ec1ff87019b1
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1029
This change reconfigures the bundles to use OpenStack yoga, they are the
last version that support Focal and Jammy.
Change-Id: Ia54bfacee6635c1e85a0c97e22bc2a5974bda7d1
Closes-Bug: #1991528
This reverts commit c0beec6fa2.
Reason for revert: I think this should be reverted as it removes focal support from the rabbitmq-server master, and thus this won't cherry-pick cleanly to the stable/jammy channel for the 3.9 track.
Change-Id: Iebab77fcc0cee31af66980c2d3be334fffe06222
* 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: I93da9ce52bed2b3e8a467491d2a61bfd2ed4ea7d
The nrpe charm doesn't support jammy yet, which is a problem because it
is a subordinate charm. Drop it from the test bundles for the time being
and when this is resolved, it will be added back in.
Change-Id: Id54c0d145fb111914a38e9ed5776712ec6a92f87
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: I3cb1f519e8f1d6765b41751994633be73e5bdea5
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: If003131e8a1bde58d90b1a3b1e47801bbb044335
The check_rabbitmq_queues nrpe check accesses the cron file created
for running collect stats job. This is done in order to determine if
the stats are too old and an alert should be raised. The nagios user
does not have access to read the cron job when running in a hardened
environment where /etc/cron.d is not readable.
This change refactors this logic to move the calculation of maximum
age for a stats file from the check_rabbitmq_queues script and into
the rabbit_utils code where it is generating the nrpe configuration.
A new (optional) parameter is added to the check_rabbitmq_queues
script to accept the maximum age in seconds a file can last be
modified.
This change also removes the trusty support in hooks/install and
hooks/upgrade-charm as the rabbit_utils.py file needs to import a
dependency which is installed by the scripts. It is cleaned up to make
sure the croniter package is always installed on install or upgrade.
Change-Id: If948fc921ee0b63682946c7cc879ac50e971e588
Closes-Bug: #1940495
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libraries sync.
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: I7c4e4bfed4b61dd19bcab06f39a2d54a1d74f237
Since rabbitmq-server is not usually in the cloud archive it does
not make sense to duplicate tests with different OpenStack releases.
Change-Id: I75a79fd24dd80a8340126f65e65bd9b7d0fa35d8
The patchset adds ussuri to bionic and focal-ussuri tests. This depends
on the linked patch below that adds initial focal support to the charm.
Depends-On: Ia239b7c2f0ed2383e220cf0fa4ade443149a3b32
Change-Id: Ib65896cd433a2108a154e18cae6f0089b5e3f44a
Add status inquiry list-unconsumed-queues action to allow operators to
determine which queues are not being consumed in each RMQ vhost. Useful for
troubleshooting message queue volume alerts.
Closes-Bug: 1767437
Change-Id: Icdd0b8c4db607701bc5e33d86e263b6a5f1bb7f5
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: I8d41b4c88ad35c7d3429885c406d0b24e0a908e3
During upgrade to a new cloud archive and a new rabbitmq-server
package, the package update will stop the rabbitmq service. If two or
more units do this near the same time the services will fail to restart.
This change adds the cluster_wait function before a package upgrade to
avoid collisions.
Fix relation_get for cluster_with causing extraneous hooks to execute.
Fix nagios stats collection logic.
Change-Id: I8d9aa38d917583fa45b5570eca9a78c813303e2b
Closes-Bug: #1778829
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: I6f24a3122c42149348c73661288fb0aba2b939dd
Enable the xenial/queens gate test; as the tests don't actually
query the OpenStack API's, no test changes are required.
Change-Id: Idb27ee82917dcda27bece03b42127745de61df62
Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.
Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.
Change-Id: If2923103254a4816e188407379307425020a931d
Felipe Reyes