diff --git a/blocked-edges/4.2.0.yaml b/blocked-edges/4.2.0.yaml index 86dbe5b39..32f6b3fb0 100644 --- a/blocked-edges/4.2.0.yaml +++ b/blocked-edges/4.2.0.yaml @@ -1,2 +1,3 @@ to: 4.2.0 -from: 4\.1\.20 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.1.yaml b/blocked-edges/4.2.1.yaml index 92c687d3b..80192eb8a 100644 --- a/blocked-edges/4.2.1.yaml +++ b/blocked-edges/4.2.1.yaml @@ -1,2 +1,4 @@ to: 4.2.1 from: .* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# Not sure why we're blocking 4.2 -> 4.2.1. diff --git a/blocked-edges/4.2.10.yaml b/blocked-edges/4.2.10.yaml new file mode 100644 index 000000000..578e0c79f --- /dev/null +++ b/blocked-edges/4.2.10.yaml @@ -0,0 +1,3 @@ +to: 4.2.10 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.11-s390x.yaml b/blocked-edges/4.2.11-s390x.yaml index 4a0787d64..4975b95a2 100644 --- a/blocked-edges/4.2.11-s390x.yaml +++ b/blocked-edges/4.2.11-s390x.yaml @@ -1,2 +1,4 @@ to: 4.2.11-s390x from: .* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# Not sure why we're blocking 4.2 -> 4.2.11 on s390x. diff --git a/blocked-edges/4.2.11.yaml b/blocked-edges/4.2.11.yaml index b0aef6284..3090fbad6 100644 --- a/blocked-edges/4.2.11.yaml +++ b/blocked-edges/4.2.11.yaml @@ -1,2 +1,4 @@ to: 4.2.11 from: .* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# Not sure why we're blocking 4.2 -> 4.2.11. diff --git a/blocked-edges/4.2.12-s390x.yaml b/blocked-edges/4.2.12-s390x.yaml new file mode 100644 index 000000000..f3e43651e --- /dev/null +++ b/blocked-edges/4.2.12-s390x.yaml @@ -0,0 +1,3 @@ +to: 4.2.12-s390x +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.12.yaml b/blocked-edges/4.2.12.yaml new file mode 100644 index 000000000..f4fe0048c --- /dev/null +++ b/blocked-edges/4.2.12.yaml @@ -0,0 +1,3 @@ +to: 4.2.12 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.13-s390x.yaml b/blocked-edges/4.2.13-s390x.yaml index 3d7efb29e..5767f5336 100644 --- a/blocked-edges/4.2.13-s390x.yaml +++ b/blocked-edges/4.2.13-s390x.yaml @@ -1,3 +1,4 @@ -# Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1789260 to: 4.2.13-s390x from: .* +# 4.2.13 cpuinfo panic in node-exporter on s390x, fixed in 4.2.16, https://bugzilla.redhat.com/show_bug.cgi?id=1789260 +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.13.yaml b/blocked-edges/4.2.13.yaml new file mode 100644 index 000000000..da9f96ba9 --- /dev/null +++ b/blocked-edges/4.2.13.yaml @@ -0,0 +1,3 @@ +to: 4.2.13 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.14.yaml b/blocked-edges/4.2.14.yaml new file mode 100644 index 000000000..9e88b64ce --- /dev/null +++ b/blocked-edges/4.2.14.yaml @@ -0,0 +1,3 @@ +to: 4.2.14 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.16.yaml b/blocked-edges/4.2.16.yaml new file mode 100644 index 000000000..f6fc39a2c --- /dev/null +++ b/blocked-edges/4.2.16.yaml @@ -0,0 +1,3 @@ +to: 4.2.16 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.18.yaml b/blocked-edges/4.2.18.yaml new file mode 100644 index 000000000..2a230024d --- /dev/null +++ b/blocked-edges/4.2.18.yaml @@ -0,0 +1,3 @@ +to: 4.2.18 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.19.yaml b/blocked-edges/4.2.19.yaml new file mode 100644 index 000000000..ddfd1b79b --- /dev/null +++ b/blocked-edges/4.2.19.yaml @@ -0,0 +1,3 @@ +to: 4.2.19 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.2.yaml b/blocked-edges/4.2.2.yaml new file mode 100644 index 000000000..5c1e376b2 --- /dev/null +++ b/blocked-edges/4.2.2.yaml @@ -0,0 +1,3 @@ +to: 4.2.2 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.20.yaml b/blocked-edges/4.2.20.yaml new file mode 100644 index 000000000..f1947b5e8 --- /dev/null +++ b/blocked-edges/4.2.20.yaml @@ -0,0 +1,3 @@ +to: 4.2.20 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.4.yaml b/blocked-edges/4.2.4.yaml new file mode 100644 index 000000000..d99e4fbff --- /dev/null +++ b/blocked-edges/4.2.4.yaml @@ -0,0 +1,3 @@ +to: 4.2.4 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.7.yaml b/blocked-edges/4.2.7.yaml new file mode 100644 index 000000000..f1a00e137 --- /dev/null +++ b/blocked-edges/4.2.7.yaml @@ -0,0 +1,3 @@ +to: 4.2.7 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.8.yaml b/blocked-edges/4.2.8.yaml new file mode 100644 index 000000000..fdb9a5512 --- /dev/null +++ b/blocked-edges/4.2.8.yaml @@ -0,0 +1,3 @@ +to: 4.2.8 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.2.9.yaml b/blocked-edges/4.2.9.yaml new file mode 100644 index 000000000..9165b2299 --- /dev/null +++ b/blocked-edges/4.2.9.yaml @@ -0,0 +1,3 @@ +to: 4.2.9 +from: 4\.1\..* +# 4.1 -> 4.2 -> 4.3 updates hit TargetDown for ingress-operator, fixed in 4.2.21, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 diff --git a/blocked-edges/4.3.0.yaml b/blocked-edges/4.3.0.yaml index 273b434e0..eaa35f80c 100644 --- a/blocked-edges/4.3.0.yaml +++ b/blocked-edges/4.3.0.yaml @@ -1,4 +1,6 @@ to: 4.3.0 -from: 4\.2\..* +from: .* +# 4.2 -> 4.3 updates hit TargetDown for cluster-autoscaler-operator, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 # 4.2 -> 4.3 updates occasionally hit RequiredPoolsFailed, fixed in 4.2.18 and rc.0, but not in 4.2.16: https://bugzilla.redhat.com/show_bug.cgi?id=1782152 https://bugzilla.redhat.com/show_bug.cgi?id=1782149 # 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635 +# 4.3 -> 4.3 updates on GCP occasionally have kube-apiserver-operator panics, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1809296 diff --git a/blocked-edges/4.3.1.yaml b/blocked-edges/4.3.1.yaml new file mode 100644 index 000000000..5db293a30 --- /dev/null +++ b/blocked-edges/4.3.1.yaml @@ -0,0 +1,5 @@ +to: 4.3.1 +from: .* +# 4.2 -> 4.3 updates hit TargetDown for cluster-autoscaler-operator, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# 4.2 -> 4.3 updates on GCP occasionally have unreachable workloads: https://bugzilla.redhat.com/show_bug.cgi?id=1793635 +# 4.3 -> 4.3 updates on GCP occasionally have kube-apiserver-operator panics, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1809296 diff --git a/blocked-edges/4.3.2.yaml b/blocked-edges/4.3.2.yaml index b3f5629c2..ab5dc35f5 100644 --- a/blocked-edges/4.3.2.yaml +++ b/blocked-edges/4.3.2.yaml @@ -1,3 +1,4 @@ -# https://bugzilla.redhat.com/show_bug.cgi?id=1802248, https://bugzilla.redhat.com/show_bug.cgi?id=1805444, https://bugzilla.redhat.com/show_bug.cgi?id=1808429 to: 4.3.2 from: .* +# 4.2 -> 4.3 updates hit TargetDown for cluster-autoscaler-operator, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# 4.3 -> 4.3 updates on GCP occasionally have kube-apiserver-operator panics, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1809296 diff --git a/blocked-edges/4.3.3.yaml b/blocked-edges/4.3.3.yaml index 9b6879a26..53e24cf3b 100644 --- a/blocked-edges/4.3.3.yaml +++ b/blocked-edges/4.3.3.yaml @@ -1,3 +1,4 @@ -# https://bugzilla.redhat.com/show_bug.cgi?id=1802248, https://bugzilla.redhat.com/show_bug.cgi?id=1805444, https://bugzilla.redhat.com/show_bug.cgi?id=1808429 to: 4.3.3 from: .* +# 4.2 -> 4.3 updates hit TargetDown for cluster-autoscaler-operator, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1801300 +# 4.3 -> 4.3 updates on GCP occasionally have kube-apiserver-operator panics, fixed in 4.3.5, https://bugzilla.redhat.com/show_bug.cgi?id=1809296 diff --git a/channels/candidate-4.2.yaml b/channels/candidate-4.2.yaml index eba4d34bb..b76823b0f 100644 --- a/channels/candidate-4.2.yaml +++ b/channels/candidate-4.2.yaml @@ -20,8 +20,8 @@ versions: # no 4.1.36 because we didn't cut a release in the week after 4.1.34 - 4.1.37 - 4.1.38 -- 4.2.0 - 4.2.0-rc.5 +- 4.2.0 - 4.2.1 - 4.2.2 # no 4.2.3 because it was rolled into 4.2.4 diff --git a/channels/fast-4.3.yaml b/channels/fast-4.3.yaml index 4fc08f4d2..c5ddf0a94 100644 --- a/channels/fast-4.3.yaml +++ b/channels/fast-4.3.yaml @@ -13,7 +13,6 @@ versions: # No 4.2.24 because of the service CA rotation issue: https://bugzilla.redhat.com/show_bug.cgi?id=1810036 https://bugzilla.redhat.com/show_bug.cgi?id=1801573 - 4.3.0 - 4.3.1 -# Upgrade edges disabled for 4.3.2 and 4.3.3 because of bugs https://bugzilla.redhat.com/show_bug.cgi?id=1802248, https://bugzilla.redhat.com/show_bug.cgi?id=1805444, https://bugzilla.redhat.com/show_bug.cgi?id=1808429 - 4.3.2 - 4.3.3 # No 4.3.4 because of https://bugzilla.redhat.com/show_bug.cgi?id=1805726 diff --git a/channels/stable-4.3.yaml b/channels/stable-4.3.yaml index f37d8cda8..93e23c7b8 100644 --- a/channels/stable-4.3.yaml +++ b/channels/stable-4.3.yaml @@ -15,7 +15,6 @@ versions: # 4.2.21 edge into stable-4.3 pending further review - 4.3.0 - 4.3.1 -# Upgrade edges disabled for 4.3.2 and 4.3.3 because of bugs https://bugzilla.redhat.com/show_bug.cgi?id=1802248, https://bugzilla.redhat.com/show_bug.cgi?id=1805444, https://bugzilla.redhat.com/show_bug.cgi?id=1808429 - 4.3.2 - 4.3.3 # No 4.3.4 because of https://bugzilla.redhat.com/show_bug.cgi?id=1805726