Skip to content

Commit f7ab77a

Browse files
Merge pull request #73975 from anarnold97/OADP-3327-DPA-does-not-reconcile-when-credentials-secret-is-updated
OADP-3327: DPA does not reconcile when credentials secret updated
2 parents e81e2a6 + 71ac1d5 commit f7ab77a

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

modules/oadp-release-notes-1-2-3.adoc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,5 +34,12 @@ For a complete list of all issues resolved in the release of OADP 1.2.3, see the
3434
[id="known-issues-1-2-3_{context}"]
3535
== Known issues
3636

37-
There are no known issues in the release of OADP 1.2.3.
37+
The {oadp-short} 1.2.3 has the following known issue:
3838

39+
.Data Protection Application (DPA) does not reconcile when the credentials secret is updated
40+
41+
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.
42+
43+
Workaround: Update to {oadp-short} 1.3.
44+
45+
link:https://issues.redhat.com/browse/OADP-3327[(OADP-3327)]

0 commit comments

Comments
 (0)