Description of problem: The DisableSnoNetworkDiag CR is not included in the reference configuration for DU deployment. The source-cr exists but if customers do not update the group-du-sno PGT to add the file it will not be configured on deployed clusters. Version-Release number of selected component (if applicable): 4.9 How reproducible: always Steps to Reproduce: 1. Note that DisableSnoNetworkDiag is included in source-crs but not group-du-sno.yaml Correct inclusion is already in the master branch: https://github.com/openshift-kni/cnf-features-deploy/blob/master/ztp/gitops-subscriptions/argocd/example/policygentemplates/group-du-sno-ranGen.yaml#L81-L82 Actual results: Expected results: Additional info:
Verified it's in latest 4.9 ztp site generator container image: [yliu1@yliu1 ~]$ podman run registry-proxy.engineering.redhat.com/rh-osbs/openshift4-ztp-site-generate:v4.9.0 cat /usr/src/hook/ztp/gitops-subscriptions/argocd/resource-hook-example/policygentemplates/group-du-sno-ranGen.yaml Trying to pull registry-proxy.engineering.redhat.com/rh-osbs/openshift4-ztp-site-generate:v4.9.0... Getting image source signatures Copying blob 16b78ed2e822 done Copying blob 131f1a26eef0 done Copying blob ed912394b615 done Copying config cde60e5d63 done Writing manifest to image destination Storing signatures apiVersion: v1 kind: Namespace metadata: name: group-du-sno labels: name: group-du-sno --- apiVersion: ran.openshift.io/v1 kind: PolicyGenTemplate metadata: # The name will be used to generate the placementBinding and placementRule names as {name}-placementBinding and {name}-placementRule name: "group-du-sno" namespace: "group-du-sno" spec: bindingRules: group-du-sno: "" mcp: "master" sourceFiles: - fileName: ConsoleOperatorDisable.yaml policyName: "console-policy" # Set ClusterLogForwarder & ClusterLogging as example might be better to create another policyTemp-Group - fileName: ClusterLogForwarder.yaml policyName: "log-forwarder-policy" spec: outputs: - type: "kafka" name: kafka-open # below url is an example url: tcp://10.46.55.190:9092/test pipelines: - name: audit-logs inputRefs: - audit outputRefs: - kafka-open - name: infrastructure-logs inputRefs: - infrastructure outputRefs: - kafka-open - fileName: ClusterLogging.yaml policyName: "log-policy" spec: curation: curator: schedule: "30 3 * * *" collection: logs: type: "fluentd" fluentd: {} - fileName: MachineConfigSctp.yaml policyName: "mc-sctp-policy" metadata: labels: machineconfiguration.openshift.io/role: master - fileName: MachineConfigDisableChronyd.yaml policyName: "mc-chronyd-policy" - fileName: PtpConfigSlave.yaml policyName: "ptp-config-policy" metadata: name: "du-ptp-slave" spec: profile: - name: "slave" interface: "ens5f0" ptp4lOpts: "-2 -s --summary_interval -4" phc2sysOpts: "-a -r -n 24" - fileName: SriovOperatorConfig.yaml policyName: "sriov-conf-policy" spec: disableDrain: true - fileName: MachineConfigAcceleratedStartup.yaml policyName: "mc-accelerated-startup-policy" metadata: name: 04-accelerated-container-startup-master labels: machineconfiguration.openshift.io/role: master - fileName: StorageLV.yaml policyName: "local-disks-policy" - fileName: DisableSnoNetworkDiag.yaml policyName: "config-policy"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.18 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0279