Add the stable/squid-jammy branch #32
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change-Id: I314fef8551e896ab35678bc78f0233cb42030413
For better stability use LTS series for rabbitmq and mysql when testing instead of interim releases. Also remove xena (non-lts) from tests and yoga as a source default Change-Id: Ie443c55dc4cc1b7f63eacfee79b28f210f1277e4
When ceph doing the version upgrade, it will check the previous ceph from the `source` config variable which store in persistent file. But the persistent file update is broken. It is because we use hookenv.Config from ops framework, but the hookenv._run_atexit, which save the change to file, is not been called. Partial-Bug: #2007976 Change-Id: Ibf12a2b87736cb1d32788672fb390e027f15b936 func-test-pr: openstack-charmers/zaza-openstack-tests#1047
Due to a Grafana bug[0] installing zip plugins has issues. We are also not testing plugins, therefore removing plugin installation from functest. [0] https://bugs.launchpad.net/charm-grafana/+bug/2017810 Change-Id: I4de5e911754cc5d99cdf94e394c81a70269c50e8
This option is required for server-side encryption to be allowed if radosgw is behind a reverse proxy, such as here when certificates are configured and apache2 is running. ref. https://docs.ceph.com/en/latest/radosgw/encryption/ It is safe to always enable when https is configured in the charm, because it will be securely behind the reverse proxy in the unit. This option must not be enabled when https is not configured in the charm, because this would allow clients to spoof headers. Closes-Bug: #2021560 Change-Id: I940f9b2f424a3d98936b5f185bf8f87b71091317
- update bundles to include UCA pocket tests - update test configuration - update metadata to include kinetic and lunar - update snapcraft to allow run-on for kinetic and lunar Change-Id: I72ab8b2ec96cf78df8a84e0686a33229a6270fb3
Auth for getting pool details can fail initially if we set up a rbd mirror relation at cloud bootstrap. Add some retry to give it another chance Change-Id: I2f5ac561120b1abe52ea0621bb472bc78495fa97 Partial-Bug: #2021967
After Octopus, the reporting about image states fails because of a permission issue in Ceph. This change disables that status reporting to allow a deployment to be healthy even when some tools cannot query status. Also modernize build and func testing: remove python 3.9 and xena from tests Related-Bug: #1879749 func-test-pr: openstack-charmers/zaza-openstack-tests#1063 Change-Id: Id86fc043495b89609cf6873ec58aee1e2e388578
* 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 * fix poetry-core addition in wheelhouse Change-Id: Ia2ad44152cf620e9812bfbd58276735a7491949c
Change-Id: Id3f21f8ab68fb88529b6cbd78217e27772c2739c
- update bundles to include UCA pocket tests - update test configuration - update metadata to include kinetic and lunar - update snapcraft to allow run-on for kinetic and lunar Change-Id: Ic9c1aef2b8c81bf53be3a18ca2806c69ce618f90 func-test-pr: openstack-charmers/zaza-openstack-tests#1074 Change-Id: Ie39cef6965c30f2adb78b4be568ced17a140115b
The charm can now set osd_memory_target, but it's not per device class or type by the nature of how the charm works. Resetting osd_memory_target always when osd_memory_target is not passed over the relation is a bit risky behavior since operators may have set osd_memory_target by hand with `ceph config` command out side of the charm. Let's be less disruptive on the charm upgrade. Closes-Bug: #1934143 Change-Id: I34dd33e54193a9ebdbc9571d153aa6206c85a067
This unpinning is meant to solve the issues with tox 4.x breaking all the virtualenv dependencies. Change-Id: Idd02728e33be4931c7729c218629b7a8430d0f41
Change-Id: I0053f28aaaecc6b9d60dfbccbb7c308c929cb046
Summary of changes: - Drop 'source' override in mysql-innodb-cluster and rabbitmq-server - Fix 'openstack-origin' Change-Id: I19faecbcfebdaf5dcf0d0346c5d0b0eed02866aa
Extend ceph-proxy to implement ceph-mds interface, this allows the ceph-fs to be related. The testing is made reusing the CephFSTests testing class. Usage example: juju add-relation ceph-proxy:mds ceph-fs:ceph-mds Co-Authored-By: Felipe Reyes <felipe.reyes@canonical.com> Closes-Bug: #1922195 Func-Test-PR: openstack-charmers/zaza-openstack-tests#558 Change-Id: I437dbac9fe018eb2d0ffb87052d61a08aa014473
Change-Id: Id74fa86d80e6e7bf16ee048bb6277f082705e8d7 Signed-off-by: utkarshbhatthere <utkarsh.bhatt@canonical.com>
Also set channels Change-Id: I21d7865c41898551f3f1b1859388139b4cff2bd1
Non leader units will skip the event handling if Ceph dashboard is not enabled by the leader yet. Some test bundle fixes. Partial-Bug: #1952282 Change-Id: I743e50663ee85c91af4962d7d100e2fd48efa48c
When broker-request caching was added, it broke functionality that ensured that clients were updated on charm-upgrade, this change enables a bypass of that cache functionality and uses it to re-process broker requests in the upgrade-charm hook. Depends-On: https://review.opendev.org/c/openstack/charms.ceph/+/848311 Func-Test-Pr: openstack-charmers/zaza-openstack-tests#1066 Closes-Bug: #1968369 Change-Id: Ibdad1fd5976fdf2d5f3384f1b120b0d5dda34947
This PR makes some small changes in the upgrade path logic by providing a fallback method of fetching the current ceph-mon version and adding additional checks to see if the upgrade can be done in a sane way. Closes-Bug: #2024253 Change-Id: I1ca4316aaf4f0b855a12aa582a8188c88e926fa6
Avoid the unintuitive situation where users are deploying from channel=quincy but get an older ceph due to deploying series=focal by explicitly setting source=quincy which is what most users want anyway; those that do not can still explicitly set source. Change-Id: I9428e93ba6107ba5e2ebcc667995b3d88eb03d27
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: I173cadb5a8208283883e1119dbfc5d661809cc5f
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: I0fb5e14bd2e58d4abdcce6e230d5c4c1a1d00af7
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: Id759ee81cea83fe9b18671ce5bc19a31db319a77
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: Ia36919df21c55bfc40497f7c174ba5919f44a394
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: I4c9f607213138adff0af434a417048c9d40af2a4
Series and UCA pockets were off. Also deploy supporting charms for lunar on jammy for stability Change-Id: I805b28bf625d69626fcf663530ac93073d298732
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
sabaini
force-pushed
the
stable/squid-jammy
branch
from
5fd4d3d to
b999b43
Compare
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
sabaini
force-pushed
the
stable/squid-jammy
branch
from
4aa25fe to
b3e1766
Compare
Signed-off-by: Peter Sabaini <peter.sabaini@canonical.com>
sabaini
force-pushed
the
stable/squid-jammy
branch
from
b3e1766 to
f33b1d8
Compare
|
Note the failing tests are expected:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.