Back to bug 1301763
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Zane Bitter | 2016-01-25 23:16:46 UTC | Link ID | Launchpad 1537857 | |
| Zane Bitter | 2016-01-25 23:17:15 UTC | Link ID | OpenStack gerrit 272213 | |
| Angus Thomas | 2016-01-26 17:54:46 UTC | Status | NEW | ASSIGNED |
| CC | athomas | |||
| Assignee | rhos-maint | brad | ||
| Jaromir Coufal | 2016-01-26 23:25:35 UTC | CC | jcoufal | |
| Mike Burns | 2016-01-27 14:49:08 UTC | Status | ASSIGNED | ON_DEV |
| John Skeoch | 2016-02-01 02:40:59 UTC | CC | calfonso | hbrock |
| James Slagle | 2016-02-03 14:35:21 UTC | CC | bcrochet | |
| Flags | needinfo?(bcrochet) | |||
| James Slagle | 2016-02-03 20:45:07 UTC | Status | ON_DEV | POST |
| Flags | needinfo?(bcrochet) | |||
| James Slagle | 2016-02-04 08:08:08 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-tripleo-common-0.0.1.dev6-6.git49b57eb.el7ost | |||
| Mike Burns | 2016-02-05 17:01:56 UTC | CC | yeylon | |
| Component | python-tripleoclient | openstack-tripleo | ||
| Lon Hohberger | 2016-02-05 20:09:16 UTC | CC | slinaber | |
| Component | openstack-tripleo | openstack-tripleo-common | ||
| QA Contact | yeylon | sasha | ||
| errata-xmlrpc | 2016-02-10 20:55:25 UTC | Status | MODIFIED | ON_QA |
| Omri Hochman | 2016-02-11 19:03:27 UTC | Status | ON_QA | VERIFIED |
| CC | ohochman | |||
| Dan Macpherson | 2016-02-15 04:35:41 UTC | CC | dmacpher | |
| Doc Text | For Overcloud stack updates, the director had issues determining whether a resources existed or whether an existing resource did not have any events. The director returned a 404 error for both. This fix adds an exception to determine if a resource exists but has no events. Now the director sets the event list to an empty list if no events exist. | |||
| Zane Bitter | 2016-02-15 14:27:45 UTC | Doc Text | For Overcloud stack updates, the director had issues determining whether a resources existed or whether an existing resource did not have any events. The director returned a 404 error for both. This fix adds an exception to determine if a resource exists but has no events. Now the director sets the event list to an empty list if no events exist. | When listing events for a resource, the Heat API does not distinguish between resources that do not exist and those that have no events associated. The "openstack overcloud update" command retrieves a list of events for any extant resources. If a previous update had ended after a resource had been added to the stack but before it had any events associated with it - as would happen, for example, if the resource was waiting at a breakpoint at the time the update ended - Heat would report that the resource was not found when the client tried to list its events. This was unexpected, since the client was only looking up events for resources that did, in fact, exist, and as a result the client exited when encountering this situation. This has been resolved by having the client correctly handle the error. |
| Dan Macpherson | 2016-02-15 15:26:47 UTC | Doc Text | When listing events for a resource, the Heat API does not distinguish between resources that do not exist and those that have no events associated. The "openstack overcloud update" command retrieves a list of events for any extant resources. If a previous update had ended after a resource had been added to the stack but before it had any events associated with it - as would happen, for example, if the resource was waiting at a breakpoint at the time the update ended - Heat would report that the resource was not found when the client tried to list its events. This was unexpected, since the client was only looking up events for resources that did, in fact, exist, and as a result the client exited when encountering this situation. This has been resolved by having the client correctly handle the error. | 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. |
| errata-xmlrpc | 2016-02-18 15:46:45 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-02-18 16:51:50 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-18 11:51:50 UTC |
Back to bug 1301763