Bug 2040791

Summary:	Default PGT policies must be 'inform' to integrate with the Lifecycle Operator
Product:	OpenShift Container Platform	Reporter:	Jim Ramsay <jramsay>
Component:	Telco Edge	Assignee:	Jim Ramsay <jramsay>
Telco Edge sub component:	ZTP	QA Contact:	yliu1
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	imiller, keyoung
Version:	4.10
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Telco:RAN
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:39:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jim Ramsay 2022-01-14 17:22:51 UTC

Description of problem:
In order to cut over to full integration with the lifecycle operator, we need to change the default example PGTs to be inform policies, not enforce as they are today.

How reproducible:
100%

Steps to Reproduce:
1. Try to use the default PGTs to do a ZTP installation with Lifecycle Operator

Actual results:
Default policies are not inform policies

Expected results:
Default policies must be inform policies

Additional info:

Comment 2 yliu1 2022-01-24 14:33:04 UTC

@jramsay policies for day2 configs are now inform by default, but then none of day2 configs are being done in ztp. 

What are we going to do for initial deployment in this case? Should argocd example be updated to add enforce remediation actions?

NAME                                           REMEDIATION ACTION   COMPLIANCE STATE   AGE
ztp-common.common-accelerator-catsrc-policy    inform               NonCompliant       4h48m
ztp-common.common-accelerator-sub-policy       inform               NonCompliant       4h48m
ztp-common.common-log-sub-policy               inform               NonCompliant       4h48m
ztp-common.common-mon-offload-policy           inform               NonCompliant       4h48m
ztp-common.common-oper-hub-policy              inform               Compliant          4h48m
ztp-common.common-pao-sub-policy               inform               NonCompliant       4h48m
ztp-common.common-ptp-sub-policy               inform               NonCompliant       4h48m
ztp-common.common-rh-operators-catsrc-policy   inform               Compliant          4h48m
ztp-common.common-sriov-sub-policy             inform               NonCompliant       4h48m
ztp-common.common-storage-sub-policy           inform               NonCompliant       4h48m
ztp-group.group-du-sno-console-policy          inform               NonCompliant       4h48m
ztp-group.group-du-sno-disable-network-diag    inform               NonCompliant       4h48m
ztp-group.group-du-sno-log-forwarder-policy    inform               NonCompliant       4h48m
ztp-group.group-du-sno-log-policy              inform               NonCompliant       4h48m
ztp-group.group-du-sno-mc-accelerated-policy   inform               Compliant          4h48m
ztp-group.group-du-sno-mc-sctp-policy          inform               Compliant          4h48m
ztp-group.group-du-sno-ptp-config-policy       inform               NonCompliant       4h48m
ztp-group.group-du-sno-sriov-conf-policy       inform               NonCompliant       4h48m
ztp-site.cnfde7-perfprofile-policy             inform               NonCompliant       4h48m
ztp-site.cnfde7-sriov-nnp-fh-policy            inform               NonCompliant       4h48m
ztp-site.cnfde7-sriov-nnp-mh-policy            inform               NonCompliant       4h48m
ztp-site.cnfde7-sriov-nw-fh-policy             inform               NonCompliant       4h48m
ztp-site.cnfde7-sriov-nw-mh-policy             inform               NonCompliant       4h48m
ztp-site.cnfde7-tuned-perf-patch-policy        inform               NonCompliant       4h48m

Comment 5 errata-xmlrpc 2022-03-10 16:39:45 UTC

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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056