-
Bug
-
Resolution: Done
-
Critical
-
4.17
Description of problem:
Attempting to deploy SNO with ZTP and Telco DU profile fails with cluster-logging operator 6.0
same PGT/siteconfig for SNO spoke works fine with CLO 5.9
Version-Release number of selected component (if applicable):
OCP 4.17.0-rc.1
SNO operator versions
cluster-logging.v6.0.0-92
local-storage-operator.v4.17.0-202409030638
packageserver
ptp-operator.v4.17.0-202409052138
sriov-fec.v2.9.0
sriov-network-operator.v4.17.0-202409040335
How reproducible:
Always
Steps to Reproduce:
1. Deploy SNO spoke with Telco DU profile
2. Obersive policies for violations
3.
Actual results:
ztp-common.common-v4.17-config-policy enforce Compliant 29m
ztp-common.common-v4.17-subscriptions-policy enforce Compliant 29m
ztp-group.group-du-sno-v4.17-config-policy enforce NonCompliant 29m
ztp-group.group-du-sno-validator-v4.17-du-policy inform Compliant 29m
ztp-site.helix55-config-policy inform Compliant 29m
NonCompliant
violation - couldn't find mapping resource with kind ClusterLogForwarder, please check if you have CRD deployed
violation - couldn't find mapping resource with kind ClusterLogging, please check if you have CRD deployed
$ oc get crd | grep log
catalogsources.operators.coreos.com 2024-09-06T16:41:54Z
clusterlogforwarders.observability.openshift.io 2024-09-06T17:10:55Z
logfilemetricexporters.logging.openshift.io 2024-09-06T17:10:56Z
Expected results:
Policies should apply correctly and CLO deploys and configures correctly.
Additional info:
must-gather, etc. will be attached in a comment.
$ oc get policies.policy.open-cluster-management.io -n helix55
NAME REMEDIATION ACTION COMPLIANCE STATE AGE
ztp-common.common-v4.17-config-policy enforce Compliant 29m
ztp-common.common-v4.17-subscriptions-policy enforce Compliant 29m
ztp-group.group-du-sno-v4.17-config-policy enforce NonCompliant 29m
ztp-group.group-du-sno-validator-v4.17-du-policy inform Compliant 29m
ztp-site.helix55-config-policy inform Compliant 29m