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].
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I65a7403ec68d8be880e418bc4fca1b1fdffe6eb9
(cherry picked from commit 96750d85f0)
* 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: I0f28e1e28ee9cb5712ef5b7b007903d317a5f61a
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ied3c4d70fb5a7cf2556a4ca7d9c0aec551b63939
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: Ie41022bf94c69019799d87abf138228ff27dddb8
Without db_auto_create = False each barbican-worker attempts to run
alembic upgrades on the database whenever they start. This leads to
race conditions that can leave the sate of the database broken
(multiple alembic version that "overlap").
This change runs the barbican-manage db upgrade by the leader only
avoiding the race condition. charms.openstack also handles the
openstack upgrade process with a call to instance.db_sync.
Change-Id: I6b9498059c7057b73b1c3db0e355456c38b0510e
Closes-Bug: #1827690
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I69fab5d73305dfe1eb0563d5e570ef76b64e5d64
Also updates for testing period for 20.01 release.
All these changes are needed together in order to have passing
functional tests.
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: Ieff90482f0acfac735c1ed69fc0593bd44913bac
Closes-Bug: #1903725
The python-apt binary package is removed in Ubuntu Groovy.
Switch the charm to python3-apt.
Change-Id: Ib3da731b3e649bf99d63229c376eb8c8354a72d7
Closes-Bug: #1899680
* 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: Ic9b019feec791d33f45e71264f4649d60b75f958
So that users can have a control over the number of processes to be
spawend and database connections to be consumed.
Change-Id: I7ffdafb807a604d89381a2fecaba8300f00e9691
Closes-Bug: #1677543
Charmhelper sync to pick up the fix to the AMQP context.
Also remove jinja2 from wheelhouse.txt as is a duplicate
and due to improvements in charm build it now causes the
build to fail.
Change-Id: I1c41ccedfbe453180b4c7835b47028ff7604711a
Closes-Bug: #1796886
- 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: I51482cc30f21cb03710655f08b93171d6f3bf8d8
Fix regression in layer-basic which failed to unpack new dependencies
properly during the upgrade-charm hook.
Github Issue: #166
Closes Bug: #1875496
Change-Id: I193337bbf53d0f5d396eee6b630ccc5d692b33cd
Use default_update_peers which will publish admin, internal and public
addresses to peers.
Change-Id: Icf242fefbae99682aae2e666c246ac94edeb3f39
Closes-Bug: #1858132
The keystone charm no longer supports the use of the admin-token;
drop its use in the barbican charm functional test suite.
Lowercase domain names when matching to deal with 'Default' as
setup by the new keystone bootstrap process.
Change-Id: Iee2091941d614aa803366e6f5c04d00909f7b1b3
TODO: rewrite tests using Zaza
Add the stein/train/ussuri major package versions.
Drop the disco functional test now that disco is EOL.
Change-Id: I4b4ec23cfb698732df7a467dc88b79e3dd6e07b1
This patch also updates the smoke test to run train.
Change-Id: I3112cf697922237ba719d183f2d94b6f92237ebc
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
Previously the default ``certificates.available`` handler was
enabled without the charm authors intervention, this was changed
in I12f45236632b608e07fdd35d31b90b84ca92eb1f.
Change-Id: I85e82273f9a423ce0fe9d8462c82de608e3922f7
Alex Kavanagh