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: Id88fe1d5e3b177099966c659d11b96e6d1fb4c4f
* 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: I46c1bb4a5c751d12435b6a42a59dd90413937d49
* 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: I2cb698f719106e54b06009f24ea47259419e9cad
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: Ifdf20eb653bf5a828a03e120018fa447310f043c
* 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: Ie287d7462b5e2cfcb1f91f25117eb61d93f59a1f
When the local overlay is enabled, Zaza ends up deploying
a 0-unit openstack-dashboard into the Vault model, which
breaks the waiting for status as, generally, it is not
desired to have a 0-unit openstack-dashboard. We can
disable this local overlay with a key in the bundle in
question.
Closes-Bug: #1945786
Change-Id: Id11d0d00e45f2d332debdc9119ad4f5150e46a51
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libraries sync
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: Iea8564df7d5f1236864bc9bcbc719350384df1e7
When the certificates relation is ready before the
HA relation is clustered, the VIP symlinks will not
be created pointing at the correct certificates. This
change updates the HA handlers to ensure that the
certificate relation is handled after clustering,
if there are any certificate relations.
There was no functional test coverage for HA and TLS
deployments so this change also add a test for
those and CMR too. Having said that, the test
initialises vault once the deployments are
complete so is unlikely to trigger #1886077 the tests
to check there is no regression of exising
functionality.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/389
Change-Id: I7c9c81318dbbcea618ac3781b8f19e8159e56bcb
Closes-Bug: #1886077
Add bionic-ussuri and focal-ussuri (with mysql8 support) bundles.
Also, for focal, switch the install and upgrade-charm hooks to install
python3 modules rather than python2 modules.
Change-Id: I75dbf72eb4c2d7d2986730e0ada9a6c359f825d3
The core issue is that the plugin had no way to signal to the
principal charm what packages needed to be installed, and crucially,
which conflicted with the packages that the plugin needs to operate.
The referenced bug exhibits this issue in that, on install, a package
is removed by the plugin, but the principal charm "doesn't know". Then
on upgrade, the principal charm re-installs the package, and breaks
the plugin.
This patch allows the plugin to signal which packages it requires to
operate via the dashboard-plugin interface. This ensures that when
the openstack-dashboard charm upgrades it already "knows" what a
plugin needs and acts accordingly. Equally, plugins can change their
requirements and this patch allows them to update/remove/install
packages as needed.
The local_settings.py is already controlled by the principal, and this
just shifts absolute control over packaging to the principal as well.
The plugin charm's purpose is to indicate packages and config to the
principal.
Note. There should be no backwards compatibility issues with this
change. If a plugin doesn't notify the principal of any packages then it
won't take any action. This does mean that the openstack-charm should
be upgrade prior to any plugins that gain this feature.
Also disable disco test as disco is EOL.
Change-Id: Ib3fc0b0525dabf70f45fd050af2ed05ba31129b9
Related-Bug: #1853851
When resuming services exclude those managed by hacluster, in
this case haproxy. If pacemaker lacks quorum it may shut haproxy
down which will cause this charm to error.
Charmhelper sync included to bring in required
get_managed_services_and_ports method.
Change-Id: I6f997df31922b6090e5b4b1daeec342a044be5c3
This patch also updates the smoke test to run train.
Depends-On: https://review.opendev.org/#/c/681927/
Change-Id: I1b6fb659ae3c655609bdbc360a2bf09f30577d0b
This patchset adds the stein gate check and the changes necessary in
basic_deployment.py to get the auth to pass, as the app has changed
slightly since rocky.
Change-Id: I2dfde541ebcceb7b29a055fd75cd783e845839b5
This change upgrades the charm to PY3 only mode.
Note the changes to charm-helpers has also been made to support
Apache auditing code in PY3.
Change-Id: Idd347de5818ec57cb05f38170fe0d6536157a0da
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: I7c775abf0172bb17e047542c8b1fc728c56bdfe5
Adds a setting custom-theme which operats similar to ubuntu-theme and
default-theme. The provided resource is placed in the themes folder and
apache is setup to serve static content for the theme. This leaves the
default theme untouched allowing the custom theme to override files
based on the built in horizon theme capabilities. For details on theming
capabilities see:
https://docs.openstack.org/horizon/latest/configuration/themes.html
gnuoy: retry logic for unrelated test updated after a number of CI
failures.
Closes-Bug: #1778284
Change-Id: I91ad19e8aad5c0e0773d42fa4f085cbcecb82458
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I1e0b7d0d0994fd229c15cf8c456b2b82bc4041e8
`syncdb` subcommand was deprecated in django 1.7
and subsequently removed in 1.9.
Use `subprocess.check_call()` so we catch errors.
Add `shared-db` relation and enable debug logging in deployment
used in functional test. Add functional test that authenticates
through the dashboard.
Update unit tests.
Change-Id: I567461e57ec431fc470d7a2a31d3f16e9dc50e8b
Closes-Bug: #1777358
There is a eluding issue that currently makes the
first request to the OpenStack Dashboard error out
with 500 Internal Server Error in CI. Temporarilly
add retry logic to unwedge the gate. This issue
should be revisited and root caused properly when time
allows.
Change-Id: Id828082416c7cbdd88247d9b6750c0f77467bc26
The comparison of bytes vs string of the CA certificate produces a
false negative. This leads to rewriting certificates and affecting
connectivity to services.
Read in the certificate as bytes as well for a bytes vs bytes
comparison.
Change-Id: I3b233a79689858db0962bafe71eba0a0667c2bf0
Closes-Bug: #1762431
Alex Kavanagh