[Bug 2019175] Please test proposed package
Corey Bryant
2019175 at bugs.launchpad.net
Thu May 25 12:38:29 UTC 2023
Hello Andreas, or anyone else affected,
Accepted heat into victoria-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:victoria-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-victoria-needed to verification-victoria-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-victoria-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!
** Changed in: cloud-archive/victoria
Status: In Progress => Fix Committed
** Tags added: verification-victoria-needed
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to heat in Ubuntu.
https://bugs.launchpad.net/bugs/2019175
Title:
[SRU] Fix None comparision when sorting by `updated_at`
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive ussuri series:
In Progress
Status in Ubuntu Cloud Archive victoria series:
Fix Committed
Status in Ubuntu Cloud Archive wallaby series:
Fix Released
Status in Ubuntu Cloud Archive xena series:
Fix Committed
Status in Ubuntu Cloud Archive yoga series:
Fix Released
Status in Ubuntu Cloud Archive zed series:
Fix Released
Status in heat package in Ubuntu:
Fix Released
Bug description:
StoryBoard link: https://storyboard.openstack.org/#!/story/2009653
[Impact]
If resource candidates were never updated before then their `updated_at` value in the db remain `None`.
This prevents future resource updates when any of of the resources in db has been replaced without being updated before.
[Test Plan]
A. Reproducer steps:
1. create a project and nova instances using > 1 vcpus in that project
2. create a stack with a OS::Nova::Quota resource managing the project's quotas
3. change the vcpu quota to an invalid value (i.e. 0) and update the stack three times
4. set a valid quota and update the stack again
B. Install the package with fix
C. Re-run the reproducer steps again
D. Confirm that resource updates (can repeat several times as well) is either successful or fails with a different message for another reason
[Where problems could occur]
If the `created_at` value happens to `None` as well for some reason then this will end up failing in the same manner.
Newer OpenStack versions already contain this fix and released packages (Wallaby, Yoga, and Zed) work as expected.
[Other info]
The fix was backported to Ussuri after the last release of Heat (14.2).
Upstream PR: https://review.opendev.org/c/openstack/heat/+/837697
This was impacting a user who is using Ussuri. Latest releases already contain the fix in the following packages:
Wallaby: heat_16.1.0-0ubuntu1~cloud0
Yoga: heat_18.0.0-0ubuntu1.2~cloud0
Zed: heat_19.0.0-0ubuntu1.2~cloud0
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2019175/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list