-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21
-
None
Description of problem:
When using ZTP Policy Generator with ARM 4.21 and the telco reference design,
The Policy Generator appears to be incorrectly merging [nodeAgent + restic] configurations ,
leading to conflicting configuration that causes reconciliation failures.
Used source-cr :
https://github.com/openshift-kni/telco-reference/blob/main/telco-ran/configuration/source-crs/data-protection/OadpDataProtectionApplication.yaml#L11-L14
OadpDataProtectionApplication.yaml:
configuration:
nodeAgent:
enable: false
uploaderType: restic
The Policy Generator creates a policy that includes both configurations:
configuration:
nodeAgent:
enable: false
uploaderType: restic
restic:
enable: false
resulting to error in the dataprotectionapplication CR::
status:
conditions:
- message: Delete restic object from spec.configuration, use spec.configuration.nodeAgent instead
reason: Error
status: "False"
type: Reconciled
As a workaround using a custom source CR that omits the nodeAgent configuration entirely allows the policy to work, this sourc-cr was used :
https://gitlab.cee.redhat.com/ocp-edge-qe/ztp-site-configs/-/blob/helix95-4.21/policygentemplates/source-crs/custom-source-crs/DataProtectionApplication.yaml?ref_type=heads#L9
Version-Release number of selected component (if applicable):
4.21
How reproducible:
100%
Steps to Reproduce:
1.Deploy ARM 4.21 cluster with ZTP
2.Use Policy Generator with the telco reference OadpDataProtectionApplication.yaml source CR
3.the generated policy contains both nodeAgent and restic configurations
4. Deploy the policy and check DataProtectionApplication status
Actual results:
ZTP Policy Generator Creates Invalid OADP Configuration on ARM 4.21 Conflicting restic and nodeAgent Settings
Expected results:
1.Not add deprecated restic configuration 2.Generate a valid DataProtectionApplication CR that reconciles successfully
Additional info:
