From 5175f10f48f4309c3e48111e28b8533d486356e6 Mon Sep 17 00:00:00 2001 From: "A.Arnold" Date: Mon, 18 Mar 2024 15:20:07 +0000 Subject: [PATCH] OADP-3716: seg fault in openshift-adp-controller-manager Signed-off-by: A.Arnold --- .../oadp-features-plugins-known-issues.adoc | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/modules/oadp-features-plugins-known-issues.adoc b/modules/oadp-features-plugins-known-issues.adoc index b1a3cf0eeb51..a9d0b5a7b23e 100644 --- a/modules/oadp-features-plugins-known-issues.adoc +++ b/modules/oadp-features-plugins-known-issues.adoc @@ -49,3 +49,22 @@ You can force the reconciliation by making any minor change to the DPA itself. ---- $ oc -n openshift-adp get secret/oadp---registry-secret -o json | jq -r '.data' ---- + + +[id="openshift-adp-controller-manager-seg-fault_{context}"] +== OpenShift ADP Controller segmentation fault + +If you configure a DPA with both `cloudstorage` and `restic` enabled, the `openshift-adp-controller-manager` pod crashes and restarts indefinitely until the pod fails with a crash loop segmentation fault. + +You can have either `velero` or `cloudstorage` defined, because they are mutually exclusive fields. + +* If you have both `velero` and `cloudstorage` defined, the `openshift-adp-controller-manager` fails. +* If you have neither `velero` nor `cloudstorage` defined, the `openshift-adp-controller-manager` fails. + +For more information about this issue, see link:https://issues.redhat.com/browse/OADP-1054[OADP-1054]. + + +[id="openshift-adp-controller-manager-seg-fault-workaround_{context}"] +=== OpenShift ADP Controller segmentation fault workaround + +You must define either `velero` or `cloudstorage` when you configure a DPA. If you define both APIs in your DPA, the `openshift-adp-controller-manager` pod fails with a crash loop segmentation fault.