Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2094669

Summary:	Heat stack update failure due to comparison between resource's 'updated_at' fields
Product:	Red Hat OpenStack	Reporter:	Randy Rubins <rrubins>
Component:	openstack-heat	Assignee:	Rabi Mishra <ramishra>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	cjeanner, fpiccion, ggrimaux, ldavidde, ramishra, spower
Target Milestone:	z4	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-heat-13.1.1-2.20220804174850.e69a96d.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-07 19:23:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Randy Rubins 2022-06-08 07:08:15 UTC

Description of problem:
Heat stack updates fail with the following error:

UPDATE_FAILED  '<' not supported between instances of 'datetime.datetime' and 'NoneType'


Version-Release number of selected component (if applicable):

Release: RHOSP 16.2.2
Container: rhosp16/openstack-heat-engine(16.2.2-14)
RPM: openstack-heat-engine-13.1.1-2.20211014110014.05708d9.el8ost.noarch

How reproducible:


Steps to Reproduce:
1. Deploy OSP13 cloud and deploy heat stack in tenant environment
2. Upgrade OSP to 16.2
3. Run stack update on the tenant heat stack and observe the error described above.

Actual results:
Heat stack update fails


Expected results:
Heat stack update succeeds


Additional info:
https://storyboard.openstack.org/#!/story/2009653
https://review.opendev.org/c/openstack/heat/+/815967

Comment 1 Luca Davidde 2022-06-09 12:07:47 UTC

Heat db dump attached to the case:

|   IDX |  PRFX  | FILENAME                     |   SIZE (KB) | DATE                 | SOURCE   |   CACHED |
|-------|--------|------------------------------|-------------|----------------------|----------|----------|
|     1 |  0010  | heat-2022-06-09-09:46:40.sql |    16018.22 | 2022-06-09 10:10 UTC | S3       |      No  |

Comment 15 David Rosenfeld 2022-10-31 17:37:34 UTC

Created a tenant stack with quota limit of two cores and a nova instance that used two cores

Attempted a stack update to add a second nova instance:
| stack_status_reason   | Resource CREATE failed: Forbidden: resources.my_instance2: Quota exceeded for cores: Requested 2, but already used 2 of 2 cores (HTTP 403) (Request-ID: req-532247e4-ef75-4319-85f7-d8ee1fabcd14) |

Repeated stack update attempt two more times. Saw above error each time.

Did a stack update that did not exceed the core quota and it was successful.

Comment 22 errata-xmlrpc 2022-12-07 19:23:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.4), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8794