image-references: Update maipo oscontainer

[cgwalters]

This isn't the long term path, but let's do this until
we have that implemented.

[ashcrow]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashcrow, cgwalters

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

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

[ashcrow]

aws_route_table_association.route_net.1: timeout while waiting for state to become 'success'

/test e2e-aws

[jlebon]

Can we add the corresponding OS version as a comment there?

[ashcrow]

/flake

/test e2e-aws

[ashcrow]

Different flake ...

/test e2e-aws

[ashcrow]

/test e2e-aws

[openshift-bot]

/retest

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

[cgwalters]

For reference I was confused about how things work; the images referenced here are basically never really used...we should probably replace them with dummy values now.

The source of truth (AIUI) is the imagestreams maintained at api.ci which feed into the release controller, which uses them to update the release payload's machine-os-content and oc adm release new will use that digested pull spec and replace the value here.

openshift/origin#21998 was trying to do this a different way but for now we're going to do some manual tagging.