From ec55f4f0d55f77e43100a84a796715b2cb08463c Mon Sep 17 00:00:00 2001 From: Cody Hoag Date: Sat, 2 May 2020 20:51:10 -0400 Subject: [PATCH] BZ1830409 known issue for RNs --- release_notes/ocp-4-4-release-notes.adoc | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/release_notes/ocp-4-4-release-notes.adoc b/release_notes/ocp-4-4-release-notes.adoc index d34f0337a6..647dc3cf31 100644 --- a/release_notes/ocp-4-4-release-notes.adoc +++ b/release_notes/ocp-4-4-release-notes.adoc @@ -2110,7 +2110,27 @@ issue by deleting the Elasticsearch deployments in sequence. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1824006[*BZ#1824006*]) * {product-title} 4.4 is not shipping with a v.4.4 Metering Operator. Customers can install or continue to run the v.4.3 Metering Operator on {product-title} 4.4 clusters. -(link:https://bugzilla.redhat.com/show_bug.cgi?id=1829035[*BZ1829035*]) +(link:https://bugzilla.redhat.com/show_bug.cgi?id=1829035[*BZ#1829035*]) + +* When updating an {product-title} cluster from version 4.3 to 4.4, the etcd +Operator sometimes fails to upgrade because it is in a degraded state. +This is caused by an InstallerPod failure. As a workaround, you must force a new +revision on etcd to overcome the InstallerPod failure, which allows the etcd +Operator to recover: ++ +. Force a new revision on etcd: ++ +---- +$ oc patch etcd cluster -p='{"spec": {"forceRedeploymentReason": "recovery-'"$( date --rfc-3339=ns )"'"}}' --type=merge +---- ++ +. Verify the nodes are at the latest revision: ++ +---- +$ oc get etcd '-o=jsonpath={range .items[0].status.conditions[?(@.type=="NodeInstallerProgressing")]}{.reason}{"\n"}{.message}{"\n"}' +---- ++ +(link:https://bugzilla.redhat.com/show_bug.cgi?id=1830789[*BZ#1830789*]) [id="ocp-4-4-asynchronous-errata-updates"] == Asynchronous errata updates