openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Merge pull request #21756 from codyhoag/rn-bz-addition

Browse Source 
etcd Operator upgrade issue for 4.4 RNs
This commit is contained in:
Cody Hoag
2020-05-03 20:37:28 -04:00
committed by GitHub
parent 3631369436 ec55f4f0d5
commit 3933244b2d
1 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
release_notes/ocp-4-4-release-notes.adoc
View File

@@ -2113,7 +2113,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