Good morning, I just wanted to update this thread and report back that we successfully upgraded our production cloud from Antelope to Caracal two days ago. There were a few obstacles we already knew from upgrading our test environment, but we faced an additional challenge during the production upgrade. The cinder db sync failed with this error message: CRITICAL cinder [-] Unhandled error: oslo_db.exception.DBDataError: (pymysql.err.DataError) (1265, "Data truncated for column 'use_quota' at row 2") It took us around two hours to clean up our cinder database (grown since Kilo or Liberty) to get past this, I'll spare you the details. We're still dealing with some aftermath, but it's not entirely clear if it's related to the OpenStack upgrade or something else in our environment. Regards, Eugen Zitat von Allison Price <allison@openinfra.dev>:
Hi everyone,
We have now published two case studies from OpenStack users who have implemented and are benefiting from the SLURP upgrade process[1]: Cleura[2] and Indiana University[3]
I wanted to follow up to see if there are other organizations who have implemented the SLURP upgrade process who would like to tell your story? If we can get a few more, I would love to schedule an OpenInfra Live to deep dive into the improvements made around OpenStack upgrades and what users stuck on older releases should know.
If you are interested, please let me know. And even if you’re not but you’re still using OpenStack—please remember to take the OpenStack User Survey[4] so we can learn more!
Thanks! Allison
[1] https://docs.openstack.org/project-team-guide/release-cadence-adjustment.htm... [2]https://superuser.openinfra.org/articles/streamlining-openstack-upgrades-man... [3] https://superuser.openinfra.org/articles/streamlining-openstack-upgrades-a-c... [4] https://www.openstack.org/user-survey