CMP-4070: Cherry Pick fix

[Vincent056]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Cherry Pick Fix

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-4070

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[openshift-ci-robot]

@Vincent056: This pull request references CMP-3537 which is a valid jira issue.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Add svirt_sandbox_domain and mcs_constrained_type attributes to selinuxrecording.process type to allow valid keycreate contexts.

Fixes container creation failure: "Invalid argument" on keycreate

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-3537

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[Vincent056]

/retest

[openshift-ci-robot]

@Vincent056: This pull request references Jira Issue OCPBUGS-55829, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected [Jira Issue CMP-3674](https://issues.redhat.com//browse/CMP-3674) to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Add svirt_sandbox_domain and mcs_constrained_type attributes to selinuxrecording.process type to allow valid keycreate contexts.

Fixes container creation failure: "Invalid argument" on keycreate

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-3537

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Vincent056: This pull request references Jira Issue OCPBUGS-55829, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected [Jira Issue CMP-3674](https://issues.redhat.com//browse/CMP-3674) to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Cherry Pick Fix

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-4070

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Vincent056: This pull request references CMP-4070 which is a valid jira issue.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Cherry Pick Fix

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-4070

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[xiaojiey]

Pre-merge verification pass.
Tried to install Compliance Operator on 4.12, 4.15, 4.19 and 4.21 rhcos10 clusters with the bundle image quay.io/redhat-user-workloads/ocp-isc-tenant/security-profiles-operator-bundle-release@sha256:7fc9c5fa7b36f420ff6b64ae5af9422c140cb7f874af2a4342ae25325fa86105, all verification pass:

$ oc get pod -l name=spod -n openshift-security-profiles
NAME         READY   STATUS    RESTARTS   AGE
spod-4xh8l   2/2     Running   0          7m25s
spod-ch455   2/2     Running   0          7m25s
spod-cp29h   2/2     Running   0          7m25s
spod-q7qnl   2/2     Running   0          7m25s
spod-r6555   2/2     Running   0          7m25s
spod-sxhmz   2/2     Running   0          7m25s

[xiaojiey]

/label qe-approved

[openshift-ci-robot]

@Vincent056: This pull request references CMP-4070 which is a valid jira issue.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Cherry Pick Fix

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/CMP-4070

Does this PR have test?

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[yuumasato]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Vincent056, yuumasato

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Vincent056,yuumasato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment