[SRU] 2024.1 stable point releases

Hello James, or anyone else affected,

Accepted neutron into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:24.1.0-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted python-oslo.service into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-oslo.service/3.4.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted nova into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/3:29.2.0-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted heat into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/heat/1:22.0.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted magnum into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/magnum/18.0.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted glance into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glance/2:28.1.0-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello James, or anyone else affected,

Accepted cinder into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cinder/2:24.2.0-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted python-oslo.service (3.4.1-0ubuntu1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

watcher/2:12.0.0-0ubuntu1 (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#python-oslo.service

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello James, or anyone else affected,

Accepted cinder into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted glance into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted heat into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted magnum into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted neutron into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted nova into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello James, or anyone else affected,

Accepted python-oslo.service into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:caracal-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verification done on noble

Hello, I've done the necessary verification on Noble. I have deployed a core openstack services + heat + magnum and run the tempest tools to functionally test these services.

I have attached the script I used to perform the whole verification and the resulting logs.

Verified versions:
magnum 18.0.1-0ubuntu1
glance 2:28.1.0-0ubuntu1
nova 3:29.2.0-0ubuntu1
neutron 2:24.1.0-0ubuntu1
heat 1:22.0.1-0ubuntu1
cinder 2:24.2.0-0ubuntu1
python-oslo.service 3.4.1-0ubuntu1

To reproduce my verification:

Verification done on jammy-caracal

Hello, I've done the necessary verification on Jammy Caracal. I have a deployed a core openstack services + heat + magnum and run the tempest tools to functionally test these services.

I have attached the script I used to perform the whole verification and the resulting logs.

Please note that in the case of jammy-caracal, I've had to backport the versions from noble-caracal for both tempest and magnum-tempest-plugin.

tempest: 29.0.0-3 -> 36.0.0-2
magnum-tempest-plugin: 1.5.0 -> 2.1.0

PPA holding these 2 backports: https://launchpad.net/~gboutry/+archive/ubuntu/jammy-caracal-backports/+packages

Tempest is the functional testing tool for OpenStack services. I don't think having to backport tempest to match the release versions is an issue to consider these functional tests as valid. (tempest 36.0.0 is the version for Caracal but is not backported into the Ubuntu Cloud Archive for jammy-caracal)

Verified versions:
magnum 18.0.1-0ubuntu1~cloud0
glance 2:28.1.0-0ubuntu1~cloud0
nova 3:29.2.0-0ubuntu1~cloud0
neutron 2:24.1.0-0ubuntu1~cloud0
heat 1:22.0.1-0ubuntu1~cloud0
cinder 2:24.2.0-0ubuntu1~cloud0
python-oslo.service 3.4.1-0ubuntu1~cloud0

This bug was fixed in the package cinder - 2:24.2.0-0ubuntu1

---------------
cinder (2:24.2.0-0ubuntu1) noble; urgency=medium

  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * New upstream release for OpenStack Caracal (LP: #2097425).
  * d/p/CVE-2024-32498.patch: Drop, included in release.
  * d/p/lp1823445.patch: Refresh.

 -- James Page <email address hidden> Wed, 05 Feb 2025 10:01:53 +0000

The verification of the Stable Release Update for cinder has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glance - 2:28.1.0-0ubuntu1

---------------
glance (2:28.1.0-0ubuntu1) noble; urgency=medium

  * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
    caracal.
  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * New upstream release for OpenStack Caracal (LP: #2097425):
    - d/p/CVE-2024-32498*.patch: Drop, included in release.

 -- James Page <email address hidden> Wed, 05 Feb 2025 09:49:29 +0000

This bug was fixed in the package heat - 1:22.0.1-0ubuntu1

---------------
heat (1:22.0.1-0ubuntu1) noble; urgency=medium

  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * New upstream release for OpenStack Caracal (LP: #2097425).

 -- James Page <email address hidden> Wed, 05 Feb 2025 10:57:11 +0000

This bug was fixed in the package magnum - 18.0.1-0ubuntu1

---------------
magnum (18.0.1-0ubuntu1) noble; urgency=medium

  [ James Page ]
  * d/gbp.conf: Create stable/2024.1 branch.
  * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
    caracal.
  * d/gbp.conf: Set upstream branch to upstream-caracal.

  [ Guillaume Boutry ]
  * New upstream stable release for OpenStack Caracal (LP: #2097425).

 -- Guillaume Boutry <email address hidden> Wed, 05 Feb 2025 10:07:46 +0000

This bug was fixed in the package neutron - 2:24.1.0-0ubuntu1

---------------
neutron (2:24.1.0-0ubuntu1) noble; urgency=medium

  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * d/gbp.conf: Set debian branch to stable/2024.1.
  * New upstream release for OpenStack Caracal (LP: #2097425).
  * d/p/lp2072154_port_status.patch: Drop, included in release.
  * d/control: Bump oslo.service >= 3.4.1 to pickup associated fix to
    ensure predicatable order to signal handling.

 -- James Page <email address hidden> Wed, 05 Feb 2025 12:01:01 +0000

This bug was fixed in the package nova - 3:29.2.0-0ubuntu1

---------------
nova (3:29.2.0-0ubuntu1) noble; urgency=medium

  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * New upstream release for OpenStack Caracal (LP: #2097425).
  * d/p/CVE-2024-{32498,40767}*.patch: Drop, included in release.

 -- James Page <email address hidden> Wed, 05 Feb 2025 10:22:54 +0000

This bug was fixed in the package python-oslo.service - 3.4.1-0ubuntu1

---------------
python-oslo.service (3.4.1-0ubuntu1) noble; urgency=medium

  * d/gbp.conf: Create stable/2024.1 branch.
  * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
    caracal.
  * d/gbp.conf: Set upstream branch to upstream-caracal.
  * New upstream release for OpenStack Caracal (LP: #2097425).

 -- James Page <email address hidden> Wed, 05 Feb 2025 12:00:27 +0000

The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package cinder - 2:24.2.0-0ubuntu1~cloud0
---------------

 cinder (2:24.2.0-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 cinder (2:24.2.0-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * New upstream release for OpenStack Caracal (LP: #2097425).
   * d/p/CVE-2024-32498.patch: Drop, included in release.
   * d/p/lp1823445.patch: Refresh.
 .
 cinder (2:24.0.0-0ubuntu1.4) noble; urgency=medium
 .
   [ James Page ]
   * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
     caracal.
 .
   [ Rodrigo Barbieri ]
   * d/p/lp1823445.patch: Fix "signature_verified" volume metadata
     from propagating to images and causing errors later when
     creating volumes from such images (LP: #1823445).

The verification of the Stable Release Update for glance has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glance - 2:28.1.0-0ubuntu1~cloud0
---------------

 glance (2:28.1.0-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 glance (2:28.1.0-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
     caracal.
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * New upstream release for OpenStack Caracal (LP: #2097425):
     - d/p/CVE-2024-32498*.patch: Drop, included in release.

The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package heat - 1:22.0.1-0ubuntu1~cloud0
---------------

 heat (1:22.0.1-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 heat (1:22.0.1-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * New upstream release for OpenStack Caracal (LP: #2097425).

The verification of the Stable Release Update for magnum has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package magnum - 18.0.1-0ubuntu1~cloud0
---------------

 magnum (18.0.1-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 magnum (18.0.1-0ubuntu1) noble; urgency=medium
 .
   [ James Page ]
   * d/gbp.conf: Create stable/2024.1 branch.
   * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
     caracal.
   * d/gbp.conf: Set upstream branch to upstream-caracal.
 .
   [ Guillaume Boutry ]
   * New upstream stable release for OpenStack Caracal (LP: #2097425).

The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package neutron - 2:24.1.0-0ubuntu1~cloud0
---------------

 neutron (2:24.1.0-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 neutron (2:24.1.0-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * d/gbp.conf: Set debian branch to stable/2024.1.
   * New upstream release for OpenStack Caracal (LP: #2097425).
   * d/p/lp2072154_port_status.patch: Drop, included in release.
   * d/control: Bump oslo.service >= 3.4.1 to pickup associated fix to
     ensure predicatable order to signal handling.

The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package nova - 3:29.2.0-0ubuntu1~cloud0
---------------

 nova (3:29.2.0-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 nova (3:29.2.0-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * New upstream release for OpenStack Caracal (LP: #2097425).
   * d/p/CVE-2024-{32498,40767}*.patch: Drop, included in release.

The verification of the Stable Release Update for python-oslo.service has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package python-oslo.service - 3.4.1-0ubuntu1~cloud0
---------------

 python-oslo.service (3.4.1-0ubuntu1~cloud0) jammy-caracal; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 python-oslo.service (3.4.1-0ubuntu1) noble; urgency=medium
 .
   * d/gbp.conf: Create stable/2024.1 branch.
   * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
     caracal.
   * d/gbp.conf: Set upstream branch to upstream-caracal.
   * New upstream release for OpenStack Caracal (LP: #2097425).