Override the layer_ovn method used to check if services
are running so that we can use SSL connections instead
of netcat since the latter causes problems with
ovsdb-server due to connections not being closed
properly.
Closes-Bug: #1920770
Change-Id: I6b2c09c643c6fddfb48dc15d6272e58303fae265
(cherry picked from commit fafa6d418afe04d9b79326a621091d9d6c5f74f4)
(cherry picked from commit 05722e0fbc9474c98c373a589c4f86116cdd9b23)
(cherry picked from commit 0a7904fba22b196a9f2484f4d55bc6f98b5a71fb)
(cherry picked from commit 202684c9f70373bb3531653e134fcfababebb9fb)
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: Ie72ba89c3afe22f977efe35c56c7796b272e07cd
(cherry picked from commit 171c39b1e2edebffbce1fbc20d41514c80f7e660)
Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.
Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.
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.
