Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2079502

Summary: TALO should label copied polices so they are excluded from ACM backup
Product: OpenShift Container Platform Reporter: jun
Component: Telco EdgeAssignee: Saeid Askari <saskari>
Telco Edge sub component: TALO QA Contact: yliu1
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium CC: akrzos, aos-bugs, ijolliff, imiller, jun
Version: 4.10   
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-30 18:04:53 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 jun 2022-04-27 16:05:23 UTC
Description of problem:
Transient policies copied by TALO causing extra workload for ACM cluster-backup-operator

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:
Copied policies should have "velero.io/exclude-from-backup=true":
https://github.com/stolostron/cluster-backup-operator#steps-to-identify-backup-data

Additional info:

Comment 2 yliu1 2022-09-13 12:36:00 UTC
Verified on 4.12 TALM.

[kni@provisionhost-0-0 ~]$ oc get policies -n default spoke-2-du-upgrade-cluster-version-policy1-xbghl -o yaml 
apiVersion: policy.open-cluster-management.io/v1
kind: Policy
metadata:
  annotations:
    cluster-group-upgrades-operator/rname: spoke-2-du-upgrade-cluster-version-policy1
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"policy.open-cluster-management.io/v1","kind":"Policy","metadata":{"annotations":{"policy.open-cluster-management.io/categories":"CM Configuration Management","policy.open-cluster-management.io/controls":"CM-2 Baseline Configuration","policy.open-cluster-management.io/standards":"NIST SP 800-53","ran.openshift.io/ztp-deploy-wave":"100"},"labels":{"app.kubernetes.io/instance":"policies"},"name":"du-upgrade-cluster-version-policy1","namespace":"ztp-upgrade"},"spec":{"disabled":false,"policy-templates":[{"objectDefinition":{"apiVersion":"policy.open-cluster-management.io/v1","kind":"ConfigurationPolicy","metadata":{"name":"du-upgrade-cluster-version-policy1-config"},"spec":{"evaluationInterval":{"compliant":"10m","noncompliant":"10s"},"namespaceselector":{"exclude":["kube-*"],"include":["*"]},"object-templates":[{"complianceType":"mustonlyhave","objectDefinition":{"apiVersion":"config.openshift.io/v1","kind":"ClusterVersion","metadata":{"name":"version"},"spec":{"channel":"{{ (lookup \"config.openshift.io/v1\" \"ClusterVersion\" \"\" \"version\").spec.channel }}","clusterID":"{{ (lookup \"config.openshift.io/v1\" \"ClusterVersion\" \"\" \"version\").spec.clusterID }}","desiredUpdate":{"version":"4.11.6"},"upstream":"http://registry.ocp-edge-cluster-0.qe.lab.redhat.com:8080/images/upgrade-graph_stable-4.11"},"status":{"history":[{"state":"Completed","version":"4.11.6"}]}}}],"remediationAction":"inform","severity":"low"}}}],"remediationAction":"inform"}}
    policy.open-cluster-management.io/categories: CM Configuration Management
    policy.open-cluster-management.io/controls: CM-2 Baseline Configuration
    policy.open-cluster-management.io/standards: NIST SP 800-53
    ran.openshift.io/ztp-deploy-wave: "100"
  creationTimestamp: "2022-09-12T17:59:29Z"
  generation: 1
  labels:
    app: openshift-cluster-group-upgrades
    app.kubernetes.io/instance: policies
    openshift-cluster-group-upgrades/clusterGroupUpgrade: spoke-2
    openshift-cluster-group-upgrades/parentPolicyName: du-upgrade-cluster-version-policy1
    velero.io/exclude-from-backup: "true"

Comment 4 Rory Thrasher 2024-04-30 18:04:53 UTC
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary