Back to bug 1041084

Who When What Removed Added
RHOS Integration 2013-12-12 13:36:02 UTC Keywords FutureFeature
Whiteboard upstream_milestone_next upstream_status_needs-code-review
Red Hat Bugzilla 2013-12-12 13:36:02 UTC Doc Type Bug Fix Enhancement
RHEL Program Management 2013-12-12 17:33:42 UTC Target Release --- 5.0
Stephen Gordon 2013-12-18 06:24:57 UTC Target Release 5.0 ---
John Skeoch 2014-01-13 01:09:38 UTC CC hateya
RHOS Integration 2014-02-19 21:44:38 UTC Whiteboard upstream_milestone_next upstream_status_needs-code-review upstream_milestone_next upstream_status_needs-code-review upstream_definition_approved
RHOS Integration 2014-03-14 04:11:31 UTC Whiteboard upstream_milestone_next upstream_status_needs-code-review upstream_definition_approved upstream_milestone_next upstream_status_implemented upstream_definition_approved
RHOS Integration 2014-03-21 04:03:52 UTC Status NEW POST
Target Release --- 5.0
Whiteboard upstream_milestone_next upstream_status_implemented upstream_definition_approved upstream_milestone_icehouse-rc1 upstream_status_implemented upstream_definition_approved
Severity unspecified low
Stephen Gordon 2014-04-06 20:33:47 UTC Priority unspecified medium
CC ndipanov, rbryant, sgordon
Component RFEs openstack-nova
QA Contact ajeain
Summer Long 2014-04-07 10:48:46 UTC CC slong
RHOS Integration 2014-04-09 13:03:18 UTC Target Milestone --- rc
Vladan Popovic 2014-05-29 16:31:00 UTC Status POST MODIFIED
CC vpopovic
Fixed In Version openstack-nova-2014.1-3.el7ost
Stephen Gordon 2014-06-09 14:57:12 UTC Status MODIFIED ON_QA
Vladan Popovic 2014-06-24 20:19:36 UTC Doc Text Feature:
Automatic recovery from transient db connection failures

Reason:
There are a variety of circumstances which can cause a transient failure in database connections, for example: restart / upgrade of the database, migration of VIP between HA pair, or just a network failure.

Result (if any):
Nova is catching these "db-has-gone-away" errors and automatically reconnects and retries the last operation, in such a way that the caller is able to continue what ever operation was in process. It is not necessary to abort long-running operations (such as nova boot or glance image-create) just because of a momentary interruption in db connectivity.
Lon Hohberger 2014-06-25 16:21:18 UTC Status ON_QA MODIFIED
errata-xmlrpc 2014-06-25 16:34:07 UTC Status MODIFIED ON_QA
Summer Long 2014-06-30 02:12:15 UTC Doc Text Feature:
Automatic recovery from transient db connection failures

Reason:
There are a variety of circumstances which can cause a transient failure in database connections, for example: restart / upgrade of the database, migration of VIP between HA pair, or just a network failure.

Result (if any):
Nova is catching these "db-has-gone-away" errors and automatically reconnects and retries the last operation, in such a way that the caller is able to continue what ever operation was in process. It is not necessary to abort long-running operations (such as nova boot or glance image-create) just because of a momentary interruption in db connectivity.
Transient database-connection failures are now recovered automatically. There are a variety of circumstances which can cause a transient failure in database connection (for example, the restart or upgrade of the database, migration of VIP between an HA pair, or a network failure). Compute now catches these "db-has-gone-away" errors by automatically reconnecting and retrying the last operation in such a way that the caller is able to continue whatever operation was in progress. The user no longer has to abort long-running operations (such as 'nova boot' or 'glance image-create') just because of a momentary interruption in database connectivity.
errata-xmlrpc 2014-07-07 12:03:17 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2014-07-08 15:27:16 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-07-08 11:27:16 UTC
Russell Bryant 2019-09-09 14:46:09 UTC CC rbryant

Back to bug 1041084