Certs are root readable so we use a cron job to perform
the check and save state for an nrpe check to read and
send back to nagios.
Closes-Bug: #1979539
Change-Id: I7c7cd238ddf3fd9f92bfa5879d19d78c091cf2ac
* 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
Change-Id: If284bc3f7b3d55ba8a2b8849887a5a5c8ea5b68b
Remove pins.
Properly format passenv list.
Drop the outer tox.ini func-target hack.
Drop the incepted tox in src/test-requirements.txt.
Drop pip.sh script.
Fix undeterministic check in test_configure_deferred_restarts
The test checks output of a class property that provides a list
in undetermined order.
Mocking class properties is non-trivial so let's just sort the
result and expected list.
Closes-Bug: #2001893
Change-Id: I25dec5d1853a5aeb686df353d7c661f4a6eb5b69
Now that the use of system-files interface has been approved and the
prometheus-ovn-exporter snap with the relevant plugs has been released
to the store, devmode usage can be disabled and additional connections
can be made.
Change-Id: Ie90719e564f0e7b5b2b209c724267057e5538af9
* Add prometheus-scrape interface
* Install the prometheus-ovn-exporter snap if the relevant option is
set appropriately (to a valid channel rather than an empty string);
* Provide the endpoint details to the prometheus-k8s-operator
scrape_interface compatible relation (app and unit data);
* Remove the snap or ignore steps to install it if the option is set to
an empty string;
* Clear the relation data for individual jobs if the snap is removed.
Change-Id: Ic50ed032f91de36528cb0a93bfd9d52c9bee6e63
The current description erronously refers to 'focal-ovn-22.03' as
a valid value, while the correct value is 'cloud:focal-ovn-22.03'.
Closes-Bug: #1992592
Change-Id: Ia391dac80787ed5f271274abccca2c19b6d845c4
Charmcraft 2.1 provides the required functionality to build the
charm using the reactive plugin.
Add missing `kinetic` series in src/metadata.yaml.
Drop the `build-rective` target, old charm-tools environment
variables and redundant pins in tox.ini.
Fixup the bases configuration and make associated changes to test
bundles.
Change-Id: I46c9b035408d13474ddbf375434a6ec190653c22
Make use of the coordinator layer to ensure payload upgrades
happen at one unit at a time, starting with the charm leader.
Closes-Bug: #1902562
Change-Id: I6abc20651ba6f81172b0193d22fdde23e6d38ed0
Commit f049e91ea95 added support for using the UCA
focal-ovn-22.03 pocket by default for new deployments on Focal.
Unfortunately the change missed some required changes for this to
work end to end.
Ensure charm works on Focal without any UCA pocket with the
`openstack-release` package already installed. The behavior
of `charms.openstack` is quite different dependning on whether
that information is available or not.
Ensure charm is able to detect availability of and to perform
payload upgrade on change of source.
Ensure charm does not attempt payload upgrade on charm upgrade.
When upgrading from a charm that does not have the `ovn-source`
configuration option, the reactive automatic flag
`config.changed.ovn-source` will fire even though it has not
changed. Clear the flag in upgrade-charm hook.
Closes-Bug: #1991319
Change-Id: Ib7760bd6fc659ec8f2be65f1e00cac860f6943e6
Add `ovn-source` configuration option which should be used in
addition to the `source` configuration option.
The default of the `ovn-source` configuration option is
determined at runtime based on whether the end user has provided
config, whether its a fresh or upgraded charm deployment and which
series it is deployed on.
Change-Id: I54f2339a16bd958c29f877394209039f345e106e
* 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
* pin zipp to a version that does not require setuptools>=42 since this
is causing an issue when the install hook runs at the deployment time.
Change-Id: I2cb698f719106e54b06009f24ea47259419e9cad
The ovn-northd daemon has gained support for runtime reload of
certificate data [0] and is now on par with the other OVS/OVN
daemons.
Remove the workaround from the charm.
0: https://github.com/ovn-org/ovn/commit/8de4f8005f210
Closes-Bug: #1895303
Change-Id: I7f45b36e03b985ba2d170ead391615f9ef9dad8e
- charmcraft: build-on 20.04 -> run-on 20.04/22.04 [*archs]
- Refresh tox targets
- Drop impish bundles and OSCI testing
- Add jammy metadata
- Set default source config and update bundles to confirm it
works.
Drop NRPE from Jammy bundles as the charm is not updated to
support Python 3.10 yet.
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/742
Change-Id: If83897aa488a415ab2e3ae85190ef06cbbe17dc9
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: I9b41911cdc3f8e6c327d68df50007b5223aaed34
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
The certificate handler code does a bit of work and should not
run during the update-status hook.
Rebuild to pull in fix merged in layer-openstack.
Depends-On: I4a3aa544f98049c83db576f95de826038e8e1afc
Closes-Bug: #1954748
Change-Id: I2ee39f7a0dcd1f4a37051d8dc08e383522387f1f
* 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: Icf8351b1ecea0ae879d101e2fce7083b52e19da7
This is a boilerplate section that will eventually
be added to the README for every charm that supports
the deferred restart feature.
Change-Id: I1e53e2d47e81cbcfc80e8f5200f65481e6004769
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Add missing charm-build job.
Change-Id: I01017a66cd1a20d5e8e680ab3d812a55e39260c4
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ie3f9294a3d181f96e6841eaac767e1779a8dca78
When the OVN packages are upgraded they restart the ovn-central
and the ovn north and south DB services. However, the restart
of ovn-central after the upgrade does not trigger the DB
services to be restarted. To fix this ensure that when the action
is run to restart services the DB services are done too.
Closes-Bug: 1924750
Change-Id: Ic058a10f9534d35d6402b66f7e1d88a90c772f1f
* 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: Ib8720493e67c5395416b3af5a920711745c049a2
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ia0120000edf459b794e6f6f576de507d67111bbe
* 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: Ic9070ad185650647d23978d17d811579d388fca5
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: Ia016386d30afdc1af67162fbf87fc4c9fb574884
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: I881ff2c3b570b8c273ba18de74812225ec2fac67
* 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: I831f67cd799ef76830794d09c6153246996b2404
The `ovn-ctl` script uses the combination of presence of
`--db-*-cluster-local-addr` and non-presence of
`--db-*-cluster-remote-addr` to decide when to do certain actions. [0]
Update the charm to not render the `--db-*-cluster-remote-addr`
argument on the charm leader.
Note that once the clustered database file has been created and
peers have joined the OVSDB server processes uses the contents
of the database file to connect to their peers and not the
information provided as arguments to the `ovn-ctl` script.
0: 67e2f386cc
Change-Id: I88b4aba31c8c05dba6f3f4ade5a8951613483d64
Closes-Bug: #1907081