From fd707058649e161d538f7144601ad702ff76401b Mon Sep 17 00:00:00 2001 From: Brian Rosmaita Date: Wed, 5 Apr 2017 14:28:19 -0400 Subject: [PATCH] Add release note for bug 1670409 Bug 1670409 affected the experimental zero-downtime database migration process introduced in Ocata. It's worth pointing out that there was a bug and that it was fixed for those deployers who tried the experimental upgrade and were uncertain about why exactly it failed. Change-Id: I4f6d246d0cf860bc7e6b0588db0b3295a4f54e16 --- releasenotes/notes/exp-emc-mig-fix-a7e28d547ac38f9e.yaml | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 releasenotes/notes/exp-emc-mig-fix-a7e28d547ac38f9e.yaml diff --git a/releasenotes/notes/exp-emc-mig-fix-a7e28d547ac38f9e.yaml b/releasenotes/notes/exp-emc-mig-fix-a7e28d547ac38f9e.yaml new file mode 100644 index 0000000000..f090499462 --- /dev/null +++ b/releasenotes/notes/exp-emc-mig-fix-a7e28d547ac38f9e.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + There was a bug in the **experimental** zero-downtime database upgrade + path introduced in the Ocata release that prevented the **experimental** + upgrade from working. This has been fixed in the Pike release. The + bug did not affect the the normal database upgrade operation.