-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
CMP Sprint 105, CMP Sprint 106
-
Moderate
Description of problem:
@ktalathi and I were running a debug of *PR #12895* with a single rule setup and hit `Could not check whether the Profile used by ComplianceScan is deprecated` from [compliancescan/compliancescan_controller.go#L371](https://github.com/ComplianceAsCode/compliance-operator/blob/003f7012cf2b43afd55245b20bb465d1bd3bad13/pkg/controller/compliancescan/compliancescan_controller.go#L371) and caused by [compliancescan_controller.go#L299](https://github.com/ComplianceAsCode/compliance-operator/blame/master/pkg/controller/compliancescan/compliancescan_controller.go#L299)
This is on the dev branch (yaml included in thread). Kaushik and I can provide detailed yaml.
```
apiVersion: compliance.openshift.io/v1alpha1
kind: ComplianceSuite
metadata:
name: onerule-debug
namespace: openshift-compliance
spec:
showNotApplicable: true
scans:
- name: onerule-debug-scan
profile: xccdf_org.ssgproject.content_profile_stig
content: ssg-rhcos4-ds.xml
contentImage: ghcr.io/complianceascode/k8scontent:12895
rule: xccdf_org.ssgproject.content_rule_imagestream_sets_schedule
scanType: Platform
debug: true
nodeSelector:
node-role.kubernetes.io/worker: ""
```
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Setup Compliance Operator
2.
3.
Actual results:
Expected results:
Additional info: