Bug 1301763 - HTTPNotFound exception when updating an overcloud
HTTPNotFound exception when updating an overcloud
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity high
: y3
: 7.0 (Kilo)
Assigned To: Brad P. Crochet
Alexander Chuzhoy
Depends On:
  Show dependency treegraph
Reported: 2016-01-25 18:16 EST by Zane Bitter
Modified: 2016-02-18 11:51 EST (History)
11 users (show)

See Also:
Fixed In Version: openstack-tripleo-common-0.0.1.dev6-6.git49b57eb.el7ost
Doc Type: Bug Fix
Doc Text:
The 'openstack overcloud update' command sought a list of events for each resource. When listing events for a resource, the Heat API returned a HTTP 404 error (Not Found) for resources with no events. The resource was considered as non-existent (due to the 404 error) and the client would fail. This occurred in situations where a previous update would end after adding a resource to the stack but before any events occur, such as a resource waiting at a breakpoint at the time the update ended. This fix adds error handling to the client, which resolves issues with the 404 error.
Story Points: ---
Clone Of:
Last Closed: 2016-02-18 11:51:50 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1537857 None None None 2016-01-25 18:16 EST
OpenStack gerrit 272213 None None None 2016-01-25 18:17 EST
Red Hat Product Errata RHBA-2016:0264 normal SHIPPED_LIVE Red Hat Enterprise Linux OSP 7 director Bug Fix Advisory 2016-02-18 16:41:29 EST

  None (edit)
Description Zane Bitter 2016-01-25 18:16:18 EST
In tripleo-common's StackUpdateManager._resources_by_state() method, we attempt to retrieve the event list for each resource in a stack. However, if there are no events for a given resource, Heat returns a 404 error. (This is probably unwise, since it should be possible to distinguish between a resource that does not exist and one that has no events, but nevertheless that's what it does). We need to catch this error, otherwise we cannot update the overcloud in the cases where one or more resources have no associated events.
Comment 1 James Slagle 2016-02-03 09:35:21 EST
Brad, if you're done with this patch, can you merge it downstream?
Comment 2 James Slagle 2016-02-03 15:45:07 EST
patch is merged now
Comment 4 Zane Bitter 2016-02-11 13:55:59 EST
This would be really hard to reproduce if you were trying. I think the way to do it might be:

- Do a stack update that adds a new resource, with a breakpoint set on that resource
- Restart heat-engine without clearing the breakpoint
- Do an overcloud update
Comment 5 Omri Hochman 2016-02-11 14:03:27 EST
Unable to reproduce. when updates from 7.x to 7.3:
Comment 7 errata-xmlrpc 2016-02-18 11:51:50 EST
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, and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.