Back to bug 1395081

Who When What Removed Added
Devan Goodwin 2016-11-15 13:41:05 UTC CC dgoodwin
Assignee jdetiber dgoodwin
Devan Goodwin 2016-11-16 13:15:44 UTC Status NEW ASSIGNED
Devan Goodwin 2016-11-16 18:59:08 UTC CC jiajliu
Flags needinfo?(jiajliu)
Mike Barrett 2016-11-17 06:47:34 UTC CC mbarrett
Devan Goodwin 2016-11-17 12:20:54 UTC Keywords UpcomingRelease
liujia 2016-11-17 13:57:20 UTC Flags needinfo?(jiajliu)
Dan McPherson 2016-12-09 19:59:53 UTC Keywords UpcomingRelease
Devan Goodwin 2017-01-16 14:40:07 UTC Status ASSIGNED NEW
liujia 2017-01-24 05:10:15 UTC QA Contact anli jiajliu
Scott Dodson 2017-02-10 03:00:48 UTC Status NEW MODIFIED
Target Release --- 3.5.0
errata-xmlrpc 2017-02-10 03:02:42 UTC Status MODIFIED ON_QA
liujia 2017-02-10 11:29:08 UTC Status ON_QA VERIFIED
Devan Goodwin 2017-02-15 13:28:57 UTC Assignee dgoodwin sdodson
Doc Text Cause: In some situations node upgrade could terminate a running pod that was upgrading the router/registry.

Consequence: Router/registry would fail to upgrade.

Fix: Router/registry upgrade re-ordered to follow node upgrade when performing a full cluster in-place upgrade.

Result: Nodes no longer taken offline for upgrade while the router/registry is still running.
Doc Type If docs needed, set a value Bug Fix
errata-xmlrpc 2017-04-12 08:24:29 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-04-12 18:48:19 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-04-12 14:48:19 UTC
Eric Paris 2017-07-24 14:11:24 UTC Target Release 3.5.0

Back to bug 1395081