-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.14.z
-
No
-
False
-
-
Description of problem:
Using ZTP with the DU profile in 4.14, and using the default configuration for ClusterLogging: - fileName: ClusterLogging.yaml policyName: "config-policy" seeing a violation when trying to create the clusterloggings CR: message: 'NonCompliant; violation - clusterloggings [instance] in namespace openshift-logging is missing, and cannot be created, reason: `ClusterLogging.logging.openshift.io "instance" is invalid: spec.curation.type: Required value`; Looking at the source for 4.14: https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.14/ztp/source-crs/ClusterLogging.yaml, it does not have spec.curation.type defined. Contrast this to 4.13, which contains the spec.curation.type value: https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.13/ztp/source-crs/ClusterLogging.yaml
Version-Release number of selected component (if applicable):
ZTP image: registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4.14.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install a managed SNO using ZTP 2. Have a PGT that references ClusterLogging.yaml with the default configuration 3. ClusterLogging CR is never created
Actual results:
Unable to create ClusterLogging CR, which renders the installation stuck.
Expected results:
ClusterLogging CR is created successfully.
Additional info:
OpenShift 4.14.1 RHACM 2.8.1 GitOps 1.9.2 Logging 5.8.0