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: I1d277dfe9b80d550b83eb9e4814cf43b4e55bf30
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: I54312c4216337a4e16340ec2b7f1bc6095137337
Add the 'docs' key and point it at a Discourse topic previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: I8ce65b31e286ee9b081a1dc5b7f27bde8a2ba5d2
Before the update-status hook would run handlers that are expected to
run when the configuration changes or relations added/removed.
The update-status hook doesn't hold the machine lock which makes
concurrent hook executions possible and seen in the gate where for
example multiple "apt-get" executions trying to acquire dpkg's lock.
Closes-Bug: #2016893
Change-Id: I63bfd9903057cbea2db8de4f1b612601aacb568d
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
* Add libpython3-dev to allow the charm to be built. This
fixes a missing dependency with Cython
Change-Id: I90a8235e29b42d6cd445ead387ae531988b578e6
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml
Change-Id: Ibaf707048e9acad8f6a900c821744b1901a3bb3b
* 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
- 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
Change-Id: Id47bea856f31c318f8e3f0c8c678fb7e11b826f4
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: I2780ed9642105a4491df14dcf35c6be1cd481898
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I3a717050803c897395e37e3093be6cb9dc73ef45
* 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: I3c7ce7e7254cabb72a7455f9ecdf71ed9293afb3
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: I1ee4a15c2ac3b9d1644ed52a2654b3018cd68b50
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I738f6b48d939a4437d815229a7e5e9de556992a9
* 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
* lock oslo.i18n < 4.0.0 if python_version < 3.6 as version 4.0.0 drops
py35 support.
Change-Id: I9af5639d69bfcea1353a80e0e01b81dfea00abb0
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I7e7ade5b85fbc379f49877227ac4288f2725d998
* 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: If18376ad944096289fa4899596d73d456425ef56
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: Ib8c80f78cf03740e9789ebcd1d8f85fee034bd90
Ensures that haproxy.cfg is written with the correct
space address for peer backends.
Related-Bug: #1912505
Change-Id: I594d20e11aa45d3a1da330f3ce18fa5fe551ca10
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: Ib76b797a0f09fca5c9881d442e3057c30916ca9d
* 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: I8f131a50ba3084ea61d59eccab0e9ae37d9f84b7
At the moment, if you only add relations for shared-db and
identity-service then the charm will come out of blocked to ready.
However, there is still no placement (to nova-cloud-controller) and so
the cloud will not work.
This patch makes the charm complain if it has no placement relation
made to prompt the operator to add the relation, or indicate if it has
been missed out of the bundle.
Change-Id: I3d34e6ec413220e2359198583975385bc98db563
If the charm switches the service from http to https (or vice versa)
and the default identity-service handler has already run during this
hook execution then keystone is not informed of the change until a
subsequant hook execution. This subsequant hook could be
update-status as the charm currently does not disable any of its
methods during update-status hooks.
Change-Id: I5f11c2439b74f893b757951cab3da4d49888375c
* 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: Id87dd403aafbfec18b9a463468e9712ef607ceab
If the certificates interface is present then it should be passed
to configure_tls otherwise it is ignored.
Change-Id: I3ba5432d3fd4f9481dadb49586a7bab938a0c4ff
Closes-Bug: 1896227
Alex Kavanagh