This change reconfigures the bundles to use OpenStack yoga, the last
version that supports Focal and Jammy.
Change-Id: I8975f04ef03a7a1ff445771bacdb0fc6ed9d8267
Closes-Bug: #1991528
This reverts commit 527261db5c.
Reason for revert: I'm not sure that this should have been merged; it removes support for focal, and that's needed on the 2.4 branch; thus this couldn't be a clean cherry-pick to the stable/jammy branch.
Change-Id: I5b53d552961d39bda91ef97f425123c1bab7e349
* 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: I1a250a0591c15971840bbd6130c7cff3822eed4f
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: I4ebaac856ddda643804454288961924c1c256aa9
* drop trusty/xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I51ed5c7fdb98dcbea72298da956a66b411fed03f
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libaries 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: I84c6210e0db2596cb4ba12ba641b56b6e73b5419
Add an `update-ring` action for that purpose.
Also print more on various pacemaker failures.
Also removed some dead code.
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/369
Change-Id: I35c0c9ce67fd459b9c3099346705d43d76bbdfe4
Closes-Bug: #1400481
Related-Bug: #1874719
Co-Authored-By: Aurelien Lourot <aurelien.lourot@canonical.com>
Co-Authored-By: Felipe Reyes <felipe.reyes@canonical.com>
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).
Note that the func-test change below is to fix the zaza test that
assumes that all subordinates are hacluster; in focal, there is also a
mysql-router subordinate.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/241
Change-Id: I17b9617917a4e0e14817c97023a4676db57937c0
Stop HA services accross all units of an application when doing a
series upgrade to avoid the situation where the cluster has some
nodes on LTS N-1 and some on LTS N.
1) In the 'pre-series-upgrade' send a notification to peers informing
them that the unit is doing a series upgrade and to which Ubuntu
version.
2) Peers receive notification. If they are on a later Ubuntu version
than the one in the notification then they do nothing. Otherwise
they shutdown corosync and pacemaker and add an entry to the local
kv store with waiting-unit-upgrade=True.
3) In the 'post-series-upgrade' hook the notification is removed from
the peer relation. waiting-unit-upgrade is set to False and
corosync and pacemaker are started.
The result of this is that when the first unit in the cluster starts
a series upgrade all cluster services are shutdown across all units.
They then rejoin the cluster one at a time when they have been
upgraded to the new version.
I added the waiting-unit-upgrade key to deal with the situation where
the first node clears the notification after it has successfully
upgraded, with out the waiting-unit-upgrade the peers would not know
they were in a mixed Ubuntu version cluster.
Change-Id: Id9167534e8933312c561a6acba40399bca437706
Closes-Bug: 1859150
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 small additions:
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
LP Related-Bug: #1823718
Change-Id: Icc28a2fcecc41b7479d62fd6e3bed8e53d89299b
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: I5949c9620fb775b0c11cd13b51b7f94a8a010bea
pacemaker no longer Recommends crmsh so explicitly install it
for all Ubuntu series as its required for charm operation.
Also enable bionic amulet test as part of a full gate recheck.
Change-Id: I06e0dcfec0a787f85655c89bf36e18253c75de2e
* Fix up amulet tests to use keystone v3 clients.
* Remove admin_* and auth_* for Queens l3_agent and metadata
config files as they no longer appears to be used.
* charm helper sync
Change-Id: I880b7f710fa6b5ba480fb41d4095871fd9dabed7
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: I71a05a94d98f92b38744988e0a77702c554ef936
This config option allows syadmins to set pacemaker in maintenance mode
which will stop monitoring on the configured resources, so services
can be stopped/restarted and pacemaker won't start them again or
migrating resources (e.g. virtual IPs).
Change-Id: I232a043e6d9d45f2cf833d4f7c4d89b079f258bb
Partial-Bug: 1698926
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: Ibe6fffd7f615e43342b73258bde870dee9dcc5ad
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
Change-Id: Ib42a1e976c05a164f134ea54e4bd390b7d79d55c
Related-Bug: #1659575
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve trusty amulet test failures.
Change-Id: Ie191a57b33dd6b349e190686cb5b8a9a5b3075d1