josorior ~ development rhacm-talk export KUBECONFIG=/home/josorior/development/managed-cluster-configs/managed-env-1/auth/kubeconfig josorior ~ development rhacm-talk oc project jaosorior-managed-1 Now using project "jaosorior-managed-1" on server "https://api.jaosorior-managed-1.devcluster.openshift.com:6443". josorior ~ development rhacm-talk oc get compliancesuites NAME PHASE RESULT ocp4-e8-custom RUNNING NOT-AVAILABLE josorior ~ development rhacm-talk oc get compliancesuites ocp4-e8-custom -o yaml apiVersion: compliance.openshift.io/v1alpha1 kind: ComplianceSuite metadata: creationTimestamp: "2020-05-27T13:29:03Z" generation: 2 labels: cluster-namespace: jaosorior-managed-1 name: ocp4-e8-custom namespace: jaosorior-managed-1 ownerReferences: - apiVersion: policy.mcm.ibm.com/v1alpha1 blockOwnerDeletion: true controller: true kind: Policy name: openshift-compliance-profile-operator.ocp4-e8-custom uid: 7f1429a5-ef4e-443e-a1d4-7a851fca989c resourceVersion: "28499" selfLink: /apis/compliance.openshift.io/v1alpha1/namespaces/jaosorior-managed-1/compliancesuites/ocp4-e8-custom uid: de628ed2-e819-4213-897e-3069df8d8ad1 spec: autoApplyRemediations: false remediationAction: inform scans: - content: ssg-ocp4-ds.xml contentImage: quay.io/complianceascode/ocp4:latest name: ocp4-e8-custom-worker-scan nodeSelector: node-role.kubernetes.io/worker: "" profile: xccdf_compliance.openshift.io_profile_ocp4-e8-custom tailoringConfigMap: name: ocp4-e8-custom-tp schedule: 0 1 * * * status: aggregatedPhase: AGGREGATING aggregatedResult: NOT-AVAILABLE scanStatuses: - name: ocp4-e8-custom-worker-scan phase: AGGREGATING result: NOT-AVAILABLE josorior ~ development rhacm-talk oc get compliancesuites -w NAME PHASE RESULT ocp4-e8-custom DONE NON-COMPLIANT ^C⏎ josorior ~ development rhacm-talk 1 [0] 0:fish- 1:fish* "fish /home/josorior/d" 16:30 27-May-20