Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 8. Asynchronous errata updates

OpenShift Data Foundation release 4.12.13 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:3893 advisory.

OpenShift Data Foundation release 4.12.12 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:1673 advisory.

OpenShift Data Foundation release 4.12.11 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:0630 advisory.

OpenShift Data Foundation release 4.12.10 is now available. The bug fixes that are included in the update are listed in the RHSA-2023:7820 advisory.

OpenShift Data Foundation release 4.12.9 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:6169 advisory.

OpenShift Data Foundation release 4.12.8 is now available. The bug fixes that are included in the update are listed in the RHSA-2023:5377 advisory.

OpenShift Data Foundation release 4.12.7 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:4836 advisory.

OpenShift Data Foundation release 4.12.6 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:4718 advisory.

OpenShift Data Foundation release 4.12.5 is now available. The bug fixes that are included in the update are listed in the RHSA-2023:4287 advisory.

OpenShift Data Foundation release 4.12.4 is now available. The bug fixes that are included in the update are listed in the RHSA-2023:3609 advisory.

OpenShift Data Foundation release 4.12.3 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:3265 advisory.

OpenShift Data Foundation release 4.12.2 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:1816 advisory.

OpenShift Data Foundation release 4.12.1 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:1170 advisory.

8.13.1. New Feature
Link kopieren

General availability of Metropolitan disaster recovery (Metro-DR) solution

Red Hat OpenShift Data Foundation Metro-DR feature with Red Hat Advanced Cluster Management for Kubernetes 2.7 is General Available now.

Note

The Regional-DR solution for both Blocks and Files is offered as Technology Preview and is subject to Technology Preview support limitations.

For more information, see the planning guide and Metro-DR solution for OpenShift Data Foundation guide.

8.13.2. Enhancements
Link kopieren

Fixed read performance issues as found by COS

The read operations performance of Multicloud Object Gateway database is improved with this enhancement. To achieve this, certain regular expressions that are used by some of the queries that run against the database to serve the required data are pre-compiled. This saves time when running in real-time. (BZ#2149861)

Added missing annotation to CSV for disconnected environment support and RelatedImages field

The multicluster-orchestrator operator is listed under operators supporting disconnected mode installations with this enhancement. To display this operator, the disconnected mode support annotation is added to CSV as the user interface (UI) uses this annotation. (BZ#2166223)

8.13.3. Known issues
Link kopieren

Cannot initiate failover of application from hub console

While working with an active/passive Hub Metro-DR setup, you might come across a rare scenario where the Ramen reconciler stops running after exceeding its allowed rate-limiting parameters. As reconciliation is specific to each workload, only that workload is impacted. In such an event, all disaster recovery orchestration activities related to that workload stop until the Ramen pod is restarted.

Workaround: Restart the Ramen pod on the Hub cluster. 

$ oc delete pods <ramen-pod-name> -n openshift-operators
Copy to Clipboard Toggle word wrap

(BZ#2175201)

Cannot failover applications from console after the repeated Active hub zone failure

During multiple hub recoveries, in the event of a double failure such as when both the hub and managed clusters are going down, you may not be able to initiate a failover from the RHACM console if the last action was relocate.

Workaround: Use the CLI to set the DRPC.spec.action field to Failover. 

$ oc edit drpc -n app-1  app-1-placement-1-drpc
Copy to Clipboard Toggle word wrap 
spec
  action: Failover
Copy to Clipboard Toggle word wrap

Result: Failover of the workload will be initiated to the failover cluster.

(BZ#2176028)

Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat