Description of problem (please be detailed as possible and provide log snippests): After upgrade from 4.10 to 4.11 default scc is now restricted-v2 and fails insight rule **Cu env ODF 4.11 The following pods do not have the default SCC's defined by OCS Operator: NAME: csi-addons-controller-manager-58c7cc7789-llzd6 SCC: restricted-v2 NAME: noobaa-core-0 SCC: restricted-v2 NAME: noobaa-operator-74fcd597bc-5lbt7 SCC: restricted-v2 NAME: ocs-operator-7ff4cfc85f-pj6d7 SCC: restricted-v2 NAME: odf-console-579876cccb-622wd SCC: restricted-v2 NAME: odf-operator-controller-manager-6466fb5bdd-plcjt SCC: restricted-v2 Version of all relevant components (if applicable): ODF 4.11 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Unknown at this time. Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hello khover, Can I close this bug?
(In reply to Nitin Goyal from comment #5) > Hello khover, > > Can I close this bug? Yes we can close.