[release-3.7] setup selinux labels for build containers

[runcom]

back ports #17094 to release-3.7

@smarterclayton PTAL

[gabemontero]

@openshift/sig-developer-experience fyi / ptal

[bparees]

i thought we agreed not to do this. but ok.

/lgtm

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[runcom]

/test crio

[runcom]

ok, crio's failing because this is 3.7 and we are testing with a 3.8 CRI-O (v1.8.2) system container 😕 @mrunalp @stevekuznetsov we need a way to tell the CI that this should pull "docker.io/runcom/cri-o:v1.0.7" based on the fact this PR is against release-1.7 branch

[stevekuznetsov]

The branch is available to you in the job -- write code to pull the right CRI-O

[runcom]

The branch is available to you in the job -- write code to pull the right CRI-O

Awesome, ill do that thanks Steve

[runcom]

/test crio

[runcom]

/test crio

[runcom]

mmm crio job not kicking....does anyone know why? @mrunalp @stevekuznetsov @ashcrow

[runcom]

/test crio

[stevekuznetsov]

The job is running, it is set to not report as it's running by default on all PRs like y'all asked for more signal. Look at your PR Overview to see the cri-o test runs.

[runcom]

/retest

[runcom]

/retest

[runcom]

/test crio

[runcom]

@bparees @stevekuznetsov @smarterclayton can we get this in? we support cri-o in 3.7 and we need this backport for Prow as well https://deck-ci.svc.ci.openshift.org/?job=test_pull_request_origin_extended_conformance_crio (failing jobs are mainly 3.7)

[derekwaynecarr]

/approve
/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, derekwaynecarr, runcom

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

Needs approval from an approver in each of these OWNERS Files:

• pkg/build/OWNERS [bparees,derekwaynecarr]
• vendor/k8s.io/kubernetes/pkg/kubelet/OWNERS [bparees,derekwaynecarr]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[runcom]

/test end_to_end

[ashcrow]

/retest

[runcom]

/retest

[runcom]

/retest

[openshift-merge-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[ashcrow]

🤞

[openshift-ci-robot]

@runcom: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/extended_conformance_crio	727f0af	link	/test crio
ci/openshift-jenkins/extended_conformance_gce	727f0af	link	/test extended_conformance_gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

[runcom]

/retest

[ashcrow]

I jinxed it 😭

[openshift-merge-robot]

Automatic merge from submit-queue.