Skip to content

Commit b1e06b2

Browse files
authored
Merge pull request #74611 from cbippley/OCPBUGS-23172-4.15
OCPBUGS#23172 4.15 RN RODOO can't run on hypershift
2 parents c314d1b + 604613a commit b1e06b2

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

release_notes/ocp-4-15-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2592,6 +2592,8 @@ In the following tables, features are marked with the following statuses:
25922592
// TODO: This known issue should carry forward to 4.9 and beyond!
25932593
* The `oc annotate` command does not work for LDAP group names that contain an equal sign (`=`), because the command uses the equal sign as a delimiter between the annotation name and value. As a workaround, use `oc patch` or `oc edit` to add the annotation. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1917280[*BZ#1917280*])
25942594

2595+
* {run-once-operator} (RODOO) cannot be installed on clusters managed by the HyperShift Operator. (link:https://issues.redhat.com/browse/OCPBUGS-17533[*OCPBUGS-17533*])
2596+
25952597
* When installing a cluster on VMware vSphere with static IP addresses (Tech Preview), the installation program can apply an incorrect configuration to the control plane machine sets (CPMS). This can result in control plane machines being recreated without static IP addresses defined. (link:https://issues.redhat.com/browse/OCPBUGS-29236[*OCPBUGS-28236*])
25962598

25972599
* Specifying a standard Ebdsv5 or Ebsv5 family machine type instance is not supported when installing an Azure cluster. This limitation is the result of the Azure terraform provider not supporting these machine types. (link:https://issues.redhat.com/browse/OCPBUGS-18690[*OCPBUGS-18690*])

0 commit comments

Comments
 (0)