mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
31 lines
1.4 KiB
Plaintext
31 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
||
//
|
||
// * backup_and_restore/oadp-release-notes-1-2.adoc
|
||
|
||
:_mod-docs-content-type: REFERENCE
|
||
[id="migration-oadp-release-notes-1-2-4_{context}"]
|
||
= OADP 1.2.4 release notes
|
||
|
||
{oadp-first} 1.2.4 is a Container Grade Only (CGO) release, released to refresh the health grades of the containers, with no changes to any code in the product itself compared to that of {oadp-short} 1.2.3.
|
||
|
||
|
||
[id="resolved-issues-1-2-4_{context}"]
|
||
== Resolved issues
|
||
|
||
There are no resolved issues in {oadp-short} 1.2.4.
|
||
|
||
|
||
[id="known-issues-1-2-4_{context}"]
|
||
== Known issues
|
||
|
||
The {oadp-short} 1.2.4 has the following known issue:
|
||
|
||
.Data Protection Application (DPA) does not reconcile when the credentials secret is updated
|
||
|
||
Currently, the {oadp-short} Operator does not reconcile when you update the `cloud-credentials` secret. This occurs because there are no {oadp-short} specific labels or owner references on the `cloud-credentials` secret. If you create a `cloud-credentials` secret with incorrect credentials, such as empty data, the Operator reconciles and creates a Backup Storage Location (BSL) and registry deployment with the empty data. As a result, when you update the `cloud-credentials` secret with the correct credentials, the Operator does not immediately reconcile to catch the new credentials.
|
||
|
||
Workaround: Update to {oadp-short} 1.3.
|
||
|
||
link:https://issues.redhat.com/browse/OADP-3327[(OADP-3327)]
|
||
|