Add issues experienced during test upgrade #1822
Open
+91
−1
Conversation
This file contains hidden or 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
product-auto-label
bot
added
size: m
documentation
Alex-Welsh
requested changes
Aug 7, 2025
Comment on lines
+210
to
+214
| `Let's Encrypt TLS settings fix <https://review.opendev.org/c/openstack/kolla-ansible/+/925971>`__ | ||
| brought breaking change to Let’s Encrypt ansible role. Now users have to explictly set the target | ||
| Let’s Encrypt ACME server as a kolla ansible variable ``letsencrypt_external_cert_server``/ | ||
| ``letsencrypt_internal_cert_server`` if they were using Let’s Encrypt as a CA of their | ||
| external/internal TLS certificates. |
There was a problem hiding this comment.
Suggested change
| `Let's Encrypt TLS settings fix <https://review.opendev.org/c/openstack/kolla-ansible/+/925971>`__ | |
| brought breaking change to Let’s Encrypt ansible role. Now users have to explictly set the target | |
| Let’s Encrypt ACME server as a kolla ansible variable ``letsencrypt_external_cert_server``/ | |
| ``letsencrypt_internal_cert_server`` if they were using Let’s Encrypt as a CA of their | |
| external/internal TLS certificates. | |
| `Let's Encrypt TLS settings fix <https://review.opendev.org/c/openstack/kolla-ansible/+/925971>`__ | |
| brought a breaking change to Let’s Encrypt ansible role. Now users have to explicitly set the target | |
| Let’s Encrypt ACME server as a kolla ansible variable ``letsencrypt_external_cert_server``/ | |
| ``letsencrypt_internal_cert_server`` if they were using Let’s Encrypt as a CA of their | |
| external/internal TLS certificates. |
Comment on lines
+219
to
+224
| `Enhancement of Ceph integration of multiple clusters | ||
| <https://review.opendev.org/c/openstack/kolla-ansible/+/907166>`__ | ||
| made Cinder role now requires ``user`` and ``pool`` set to the each item of kolla dict | ||
| variable ``cinder_ceph_backends`` at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | ||
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) | ||
| For example, |
There was a problem hiding this comment.
Suggested change
| `Enhancement of Ceph integration of multiple clusters | |
| <https://review.opendev.org/c/openstack/kolla-ansible/+/907166>`__ | |
| made Cinder role now requires ``user`` and ``pool`` set to the each item of kolla dict | |
| variable ``cinder_ceph_backends`` at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | |
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) | |
| For example, | |
| `Enhancement of Ceph integration of multiple clusters | |
| <https://review.opendev.org/c/openstack/kolla-ansible/+/907166>`__ | |
| means the Cinder role now requires ``user`` and ``pool`` set to the each item of kolla dict | |
| variable ``cinder_ceph_backends`` at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | |
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) | |
| For example, |
| pool: volumes-hdd | ||
| enabled: true | ||
|
|
||
| You can find the name of pools from ``cephadm_pools`` in cephadm.yml. |
|
|
||
| You can find the name of pools from ``cephadm_pools`` in cephadm.yml. | ||
|
|
||
| The K-A upstream change `<https://review.opendev.org/c/openstack/kolla-ansible/+/909974>`__ |
There was a problem hiding this comment.
Would be best to shorten this
Suggested change
| The K-A upstream change `<https://review.opendev.org/c/openstack/kolla-ansible/+/909974>`__ | |
| The K-A upstream change `#909974 <https://review.opendev.org/c/openstack/kolla-ansible/+/909974>`__ |
| The K-A upstream change `<https://review.opendev.org/c/openstack/kolla-ansible/+/909974>`__ | ||
| requires users to manually set Cinder cluster name at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | ||
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments). | ||
| It should be matching with current cluster name. You can find the name from ``cinder.conf``. |
There was a problem hiding this comment.
I'm not 100% sure that this is the correct variable, but we should definitely include the variable name here.
Suggested change
| It should be matching with current cluster name. You can find the name from ``cinder.conf``. | |
| It should match the current cluster name. You can find the name from ``cinder.conf`` as ``rbd_cluster_name``. |
Comment on lines
+254
to
+257
| Elasticseach storage driver is no longer compatible with Opensearch storage backend. | ||
| Need to set CloudKitty storage backend to Opensearch if it was set to be Elasticseach before. | ||
| This can be set at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | ||
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) |
There was a problem hiding this comment.
Suggested change
| Elasticseach storage driver is no longer compatible with Opensearch storage backend. | |
| Need to set CloudKitty storage backend to Opensearch if it was set to be Elasticseach before. | |
| This can be set at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | |
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) | |
| The elasticsearch storage driver is no longer compatible with Opensearch storage backend. | |
| Set the CloudKitty storage backend to ``opensearch`` if it was ``elasticseach`` before. | |
| This can be set at ``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` | |
| (``$KAYOBE_CONFIG_PATH/environments/<env>/kolla/globals.yml`` if using environments) |
| From Dalmatian, `Kayobe no longer provides its own default driver & interfaces | ||
| <https://review.opendev.org/c/openstack/kayobe/+/836999>`__ | ||
| for Ironic and follows Ironic's default. | ||
| This can cause your Ironic configuration ``ironic.conf`` to have regression. |
There was a problem hiding this comment.
Suggested change
| This can cause your Ironic configuration ``ironic.conf`` to have regression. | |
| This can cause your Ironic configuration ``ironic.conf`` to regress. |
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.
From SMS Lab upgrade