This patchset implements key rotation for managers only. The user
can specified either the full entity name (i.e: 'mgr.XXXX') or
simply 'mgr', which stands for the local manager.
After the entity's directory is located, a new pending key is
generated, the keyring file is mutated to include the new key and
then replaced in situ. Lastly, the manager service is restarted.
Note that Ceph only has one active manager at a certain point,
so it only makes sense to call this action on _every_ mon unit.
Change-Id: Ie24b3f30922fa5be6641e37635440891614539d5
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1195
During cluster deployment a situation can arise where there are
already osd relations but osds are not yet fully added to the cluster.
This can make version retrieval fail for osds. Retry version retrieval
to give the cluster a chance to settle.
Also update tests to install OpenStack from latest/edge
Change-Id: I12a1bcd32be2ed8a8e5ee0e304f716f5a190bd57
When ceph doing the version upgrade, it will check the previous ceph
from the `source` config variable which store in persistent file.
But the persistent file update is broken. It is because we use hookenv.Config
from ops framework, but the hookenv._run_atexit, which
save the change to file, is not been called.
Partial-Bug: #2007976
Change-Id: Ibf12a2b87736cb1d32788672fb390e027f15b936
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1047
For better stability use LTS series for rabbitmq and mysql when
testing instead of interim releases.
Also remove xena (non-lts) from tests and yoga as a source default
Change-Id: Ie443c55dc4cc1b7f63eacfee79b28f210f1277e4
- update bundles to include UCA pocket tests
- update test configuration
- update metadata to include kinetic and lunar
- update snapcraft to allow run-on for kinetic and lunar
Change-Id: I6b229b502dd4ee9f1d219240b86f7826abf0c25d
In addition to trivial changes (passing `event` into
the `copy_pool` function), this change introduces an
update to the actions/__init__.py that allows succinct
import and use from the main charm.py.
An apparently unrelated change is the removal of
charm-proof from the lint job, as it fails with the
removal of actions/copy-pool.
Change-Id: I66a5590ddf0f0bb5ca073a91b451f8c78598609a
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/866
This patchset implements the first rewrite of the charm using the
operator framework by simply calling into the hooks.
This change also includes functional validation about charm upgrades
from the previous stable to the locally built charm.
Fix tempest breakage for python < 3.8
Co-authored-by: Chris MacNaughton <chris.macnaughton@canonical.com>
Change-Id: I61308bb2900134ea163d9e92444066a3cb0de43d
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/849
This patchset rearranges the tests so that the upgrade path is
properly tested, with the tests that aren't in main moved into
a different class.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/849
Change-Id: I5ca38134115f82ac6dff5f559757df68a6c0cd24
Update the channel for quincy channels; the channels were specified as
stable/yoga which causes Juju to pick the stable charm. Fix this and
point it at the right track and channel - quincy/edge in this case.
Change-Id: I5d68c0c15f3a7ab5ff80ddda0d376d9031cbdb13
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: I546438f1af6b3f779aa01e9ddd8c8ae7c3b7d063
Groovy Gorilla (20.10) is now EOL, and functional tests will fail
due to it not being supported anymore. This will move the bundle
to the force section, allowing tests to be run.
Change-Id: I71e69346c288bcae492bb66be8b67feb4892012c
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
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
Sync charm-helpers
Also pin prometheus2 charm in bundles to focal series as it does not
support groovy or hirsute.
Change-Id: I75602720f8e30be647aa8a1227d565c692ff8170
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This change adds a bundle that configures erasure coded pools
for glance, cinder-ceph and nova. To verify that the pools are
using EC it also adds a test which verifies the pool type.
To verify that the nova pool is configured correctly in all
scenarious all the bundles have been updated to set
libvirt-image-backend to rbd which triggers the nova pool
creation.
During testing the Prometheus tests were failing which is
down to a known bug *1 in the prometheus charm. The
bundles have been updated to pin the prometheus2 charm
to an earlier version to get round the bug.
*1 https://bugs.launchpad.net/charm-prometheus2/+bug/1891942
Change-Id: I7d29aec3ba9924d5677be25137907b1465401f9c
The test specification doesn't need the 'cinder' spec as part of the osd
devices, and this patchset brings it in line with the other bundles.
Change-Id: If13f38eea33f3d83133396e01eff0b36eb90e82a
use btrfs-progs instead of btrfs-tools for eoan and later
update bionic-train zaza test bundle to include placement
Closes-Bug: #1850181
Change-Id: Ic8e46dda154c19edadf0e6810701233c3db88e04
Revert the removal of the fsid charm configuration option.
This is required for the in-place migration of an existing Ceph
deployment into a Charm managed deployment.
This reverts commit 54c3f21221.
Change-Id: I260b3eef85465293cc7ec554913dc66d9a4b7ee4
Closes-Bug: 1846337
This patch also provides a fix from the last charms.ceph sync to fix
random issue with ceph >= 14.
Change-Id: I8aa03e073442c2eaa1c979562f68c435c229db16
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
Drop service check for ``glance-registry``. The service is
removed as of Stein, and it really is not the ``charm-ceph-mon``
functional tests job of checking this anyway. Any such detail
should be deferred to the ``charm-glance`` functional tests.
Change-Id: I85dd396b55e3d1582da18c6d8248ba1cced3e89f
Luciano Lo Giudice