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: Icff1cd3f9176ffeacc2b96338662d08b51d8553b
Sync charm-helpers to pick up fix for openstack_upgrade_available
that enables successful payload upgrades. This will need backporting
to stable/wallaby.
https://github.com/openstack-charmers/zaza/pull/619
Closes-Bug: #2040606
Change-Id: Ib1586a486a7a01023bd59bfa70016481ad5f89dc
The package-upgrade action performs package upgrades for the current
OpenStack release.
The code path used is similar to the openstack-upgrade action, with the
difference being that package-upgrade will not execute if an openstack
upgrade is available (based on the openstack-origin setting).
This change includes a charm-helpers sync.
Change-Id: I0c7184bba29731354e52dc28e3a4dd6f282fa843
* 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
Depends-On: https://review.opendev.org/c/openstack/charm-swift-proxy/+/847513
As per the bug report, the xfs-inode-size default value is in contradiction with the current upstream advice.
This patch removes the default value and accept the filesystem defaults for mkfs.xfs inode sizes.
Closes-Bug: #1879423
Change-Id: I9effc6052524ead9817454912284e3c48ce55901
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
- charmhelpers sync
Change-Id: Ie37826e7803659f2f40eaac5f8d539cce5ef145b
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: Id5ec1154770c87e18bb2a4244b22354c9d0edfc0
* 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: I4e72dafd2ab198846cb376097dd8a2b7438dedd9
The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().
Change-Id: Icfa65b0e02060e63fa90a57cd95da1dcac729c06
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I4a1e9239e40d27d48e48b9e5241240eff9689a3d
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: Ic9c930a58afa9e1e849e61581b9cca588cc48529
* 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: I28bc6125b817c2f1608157509c27d54dab9541a5
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: Ifac4b14907328345f1fc8f645a61a4812519670c
This is to enable other charms to pass there enable-focal patchsets.
The pre-enable is simply to sync in charmhelpers with py38 support so
that this charm can participate in swift-proxy's focal enablement.
Change-Id: Ic94761fd65e9f442fa08315bbbdc377d7d0a97c9
The referenced bug is essentially: make vault:secrets relation to vault
but keep the 'encrypt' option as False. In this case, the Context
handling code in charm-helpers is expecting python3-hvac to be
available, but it is only installed if the encrypt option is set to
True. Hence the charm crashes. This resolves that crash.
Note the related charm-helpers fix [1].
[1]: https://github.com/juju/charm-helpers/pull/431
Change-Id: I92773b7c1f48d456091062751e69581fabe4c5f3
Closes-bug: #1862085
Also gate checking vault context completing on whether
dependencies are installed.
Change-Id: Ib424abe608081da21207db262fb82362f23fe6ca
Closes-Bug: #1849323
Ensure that charmhelpers directory is up to date.
Change-Id: Ib1c419a0c9710b4489777471226ccd680408f8fe
Needed-By: If621587a02746876ee6c35d7af2e878dbc2ac8ef
Partial-Bug: 1826552
apt.version_compare changed behaviour to return >= 1 in the event
that a newer package version is detected.
Resync charmhelpers code to pickup fixes for openstack upgrade
detection.
Change-Id: Iacf8db9bbacca782646584a4982b265937b63b9e
Closes-Bug: 1817384
Using the new version of the sync tool which removes the charmhelpers
directory before syncing, run charm helpers sync to find any unexpected
missing dependencies.
Change-Id: I8e046f8816fd91920ba2c15f8c960b74442eb7bd
PY3 bug in loopback_devices caused the related bug. This patch syncs
just the relevant file to fix the bug into charmhelpers.
Change-Id: I5aacd16c2bd4957c49210e867dc76efa1a315ab4
Closes-Bug: #1804128
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: I785071825f7ef96cdb15fcd5bbab9963d7f2631a