UPSTREAM: <carry>: Update the os image to be more accurate

[smarterclayton]

No description provided.

[openshift-ci-robot]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 83ff006|DO NOT MERGE: Test a crio binary built into a payload: does not specify an upstream backport in the commit message

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: smarterclayton
To complete the pull request process, please assign deads2k after the PR has been reviewed.
You can assign the PR to them by writing /assign @deads2k in a comment when ready.

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 444b146|DO NOT MERGE: Test a crio binary built into a payload: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• ccc7c4e|DO NOT MERGE: Test a crio binary built into a payload: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 2b5476d|DO NOT MERGE: Test a crio binary built into a payload: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• c2d1552|DO NOT MERGE: Test a crio binary built into a payload: does not specify an upstream backport in the commit message

[openshift-ci-robot]

@smarterclayton: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• [d55143c|UPSTREAM: : Update the 'os' image with the latest state

We were still pulling in 4.3 code, which is wrong](d55143c): does not specify an upstream backport in the commit message

[smarterclayton]

/retest

[openshift-ci]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-serial	d55143c	link	/test e2e-aws-serial
ci/prow/k8s-e2e-gcp-serial	d55143c	link	/test k8s-e2e-gcp-serial
ci/prow/e2e-gcp	d55143c	link	/test e2e-gcp
ci/prow/e2e-agnostic-cmd	d55143c	link	/test e2e-agnostic-cmd

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

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.