Set default release image to 4.7

[pierreprinetti]

Align the default release image with the current development version.

[pierreprinetti]

/uncc jhixson74 patrickdillon

[pierreprinetti]

/cc LorbusChris jhixson74 patrickdillon

[LorbusChris]

I wonder whether we should go to 4.7 in master directly, and switch to 4.6 only on release-4.6

[pierreprinetti]

I wonder whether we should go to 4.7 in master directly, and switch to 4.6 only on release-4.6

That was my original idea TBH, however

$ podman pull registry.svc.ci.openshift.org/origin/release:4.7
Trying to pull registry.svc.ci.openshift.org/origin/release:4.7...
  manifest unknown: manifest unknown
Error: unable to pull registry.svc.ci.openshift.org/origin/release:4.7: Error initializing source docker://registry.svc.ci.openshift.org/origin/release:4.7: Error reading manifest 4.7 in registry.svc.ci.openshift.org/origin/release: manifest unknown: manifest unknown

Same with latest, master and nightly. Any ideas?

[pierreprinetti]

/retest

[staebler]

podman pull registry.svc.ci.openshift.org/origin/release:4.7

I wonder whether we should go to 4.7 in master directly, and switch to 4.6 only on release-4.6

That was my original idea TBH, however

$ podman pull registry.svc.ci.openshift.org/origin/release:4.7
Trying to pull registry.svc.ci.openshift.org/origin/release:4.7...
  manifest unknown: manifest unknown
Error: unable to pull registry.svc.ci.openshift.org/origin/release:4.7: Error initializing source docker://registry.svc.ci.openshift.org/origin/release:4.7: Error reading manifest 4.7 in registry.svc.ci.openshift.org/origin/release: manifest unknown: manifest unknown

Same with latest, master and nightly. Any ideas?

The 4.7 image exists. We should definitely move to 4.7.

$ oc image info registry.svc.ci.openshift.org/origin/release:4.7 | head -n4
Name:        registry.svc.ci.openshift.org/origin/release:4.7
Digest:      sha256:bccbfcc0d7c0ce7f1bb5ef5a3dd681cb39501a7c01822d7461440c45554531f8
Media Type:  application/vnd.docker.distribution.manifest.v2+json
Created:     14h ago

[pierreprinetti]

Created: 14h ago

:) updated

PTAL @staebler

[LorbusChris]

/approve

[staebler]

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LorbusChris, staebler

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 [staebler]

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-merge-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-crc	d438949	link	/test e2e-crc
ci/prow/e2e-aws-workers-rhel7	d438949	link	/test e2e-aws-workers-rhel7

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.