OKD-220: Update c9s.repo to install cri-o 1.29.5

[aleskandro]

Updating the repo to install the latest crio 1.29 for 4.16. the 4.17 repo is not available yet. This should be backported to release-4.16

/cc @travier

[aleskandro]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@aleskandro: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16

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-sigs/prow repository.

[openshift-ci-robot]

@aleskandro: This pull request references OKD-220 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

Updating the repo to install the latest crio 1.29 for 4.16. the 4.17 repo is not available yet. This should be backported to release-4.16

/cc @travier

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.

[travier]

We should not backport OKD-SCOS changes to branched releases. Everything should be built from the master branch.

[travier]

Change LGTM but no backport.
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleskandro, travier

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [travier]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2467e5e and 2 for PR HEAD 71f0c6b in total

[travier]

/retest

[aleskandro]

One failure is about #1540

[aleskandro]

        harness.go:1823: mach.Start() failed: machine "fdb74dc7-2401-42d2-832a-99d4eff463f5" failed basic checks: detected failed or stuck systemd units: some systemd units failed: systemd-network-generator.service; <nil>
=== RUN   rpmostree.upgrade-rollback/rollback
--- PASS: rpmostree.upgrade-rollback (135.24s)
    --- PASS: rpmostree.upgrade-rollback/upgrade (53.24s)
    --- PASS: rpmostree.upgrade-rollback/rollback (41.65s)
--- PASS: ext.config.shared.networking.nmstate.state (76.11s)
--- PASS: rhcos.network.init-interfaces-test (176.85s)
--- PASS: coreos.ignition.failure (30.27s)
--- FAIL: ext.config.shared.networking.prefer-ignition-networking (41.61s)
        harness.go:1823: mach.Start() failed: machine "ccc3eb72-4873-4f85-b223-4de8e8ca3528" failed basic checks: detected failed or stuck systemd units: some systemd units failed: systemd-network-generator.service; <nil> 
 --- PASS: ext.config.shared.ignition.resource.remote (74.59s)
--- FAIL: ext.config.shared.networking.bridge-static-via-kargs (42.05s)
        harness.go:1823: mach.Start() failed: machine "0e06ddb3-9af2-46fe-b3d5-bf94d496b894" failed basic checks: detected failed or stuck systemd units: some systemd units failed: systemd-network-generator.service; <nil>
--- PASS: ext.config.shared

[aleskandro]

/test scos-9-build-test-qemu

[jlebon]

Yeah, SCOS CI is broken right now as you see. I don't think we need to block on this.

/override ci/prow/scos-9-build-test-qemu

But as @travier said, this shouldn't be backported. It doesn't seem like there's a way to cancel a /cherrypick command, so we'll just have to close the PR it opens.

[openshift-ci]

@jlebon: Overrode contexts on behalf of jlebon: ci/prow/scos-9-build-test-qemu

In response to this:

Yeah, SCOS CI is broken right now as you see. I don't think we need to block on this.

/override ci/prow/scos-9-build-test-qemu

But as @travier said, this shouldn't be backported. It doesn't seem like there's a way to cancel a /cherrypick command, so we'll just have to close the PR it opens.

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-sigs/prow repository.

[openshift-ci]

@aleskandro: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[openshift-cherrypick-robot]

@aleskandro: new pull request created: #1543

In response to this:

/cherry-pick release-4.16

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-sigs/prow repository.