ci: Use cosa init --transient

[cgwalters]

Opt into the faster infrastructure from
coreos/coreos-assembler#2889
for CI builds where we do not maintain any state across builds.

[miabbott]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, miabbott, travier

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 [cgwalters,miabbott,travier]

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

[cgwalters]

Well, this didn't have much of an effect. One bit I'm zooming in on here is this:

2022-06-03T16:37:49.182685225Z + ostree container unencapsulate --repo=/tmp/rootfs/ostree/repo ostree-unverified-image:oci-archive:/tmp/cosa/builds/411.85.202206031456-0/x86_64/rhcos-411.85.202206031456-0-ostree.x86_64.ociarchive
2022-06-03T16:56:38.219610733Z Imported: bb632d58f214c9bec4a2ea1b897eca8ba722217bb5c7a2bf9f601b1f92098d90
2022-06-03T16:56:38.314351800Z 
2022-06-03T16:56:38.314351800Z real	18m49.131s
2022-06-03T16:56:38.314351800Z user	6m0.457s
2022-06-03T16:56:38.315771853Z sys	9m39.067s

But, looking at this recent job in coreos-assembler which is also running in the same build02 cluster, we see:

+ ostree container unencapsulate --repo=/tmp/rootfs/ostree/repo ostree-unverified-image:oci-archive:/tmp/tmp.BDRy4R02rU/builds/411.85.202206030021-0/x86_64/rhcos-411.85.202206030021-0-ostree.x86_64.ociarchive
Imported: b4d6c33eb37a2ba4fd373a22910a6bdc870b4ac06bec6f11686b453f9df5acef

real	1m46.456s
user	0m31.721s
sys	0m48.465s

That's a pretty dramatic performance difference, almost an order of magnitude.

I think this must have something to do (as I think Micah mentioned) with jobs here running in a build pod as opposed to a regular pod.

[openshift-ci-robot]

/retest-required

Remaining retests: 2 against base HEAD c6bf5a9 and 8 for PR HEAD 4d84d12 in total

[travier]

We might have consider moving back to test pods again for builds for PR and keep it as is for periodic jobs.

[openshift-ci-robot]

/retest-required

Remaining retests: 1 against base HEAD c6bf5a9 and 7 for PR HEAD 4d84d12 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c6bf5a9 and 6 for PR HEAD 4d84d12 in total

[openshift-ci]

@cgwalters: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/test-qemu-kola	4d84d12	link	true	/test test-qemu-kola
ci/prow/test-in-cluster	4d84d12	link	true	/test test-in-cluster

Full PR test history. Your PR dashboard.

Details

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.