Bug 1890141: move off docker.io in templates/builds/jenkins tests

[gabemontero]

@openshift/openshift-team-build-api FYI

@sbose78 this PR currently assumes we can push docker.io/openshift/test-build-simples2i:latest to quay.io/redhat-developer/test-build-simples2i:latest

/assign @adambkaplan

[sbose78]

That was quick, thank you Gabe!

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-fips	8d27e17	link	/test e2e-aws-fips
ci/prow/e2e-gcp	8d27e17	link	/test e2e-gcp
ci/prow/e2e-gcp-builds	8d27e17	link	/test e2e-gcp-builds

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.

[gabemontero]

Other than the aforementioned quay.io/redhat-developer/test-build-simples2i:latest not existing yet, this look OK so far e2e wise.
Or at least that is the vast majority of failures.

@sbose78 @adambkaplan - do either of your have to authority to create such a repo in quay.io/redhat-developer so I can push to it like I did with the recent jenkins e2e PR that merged ?

[gabemontero]

ok @adambkaplan has created quay.io/redhat-developer/test-build-simples2i:latest

/retest

[gabemontero]

OK I think we are down to multistage.go failing consistently ... the switch to quay.io/fedora/fedora:34-x86_64 does not seem to be happy (though it is not an image pull thing).

gonna try registry.access.redhat.com/rhel7 instead (since this is a from via dockerfile test, not going to do registry.redhat.io)

[gabemontero]

/retest

[gabemontero]

OK @adambkaplan we are running clean (enough - I believe the e2e-cmd errors are non related flakes) with this move off of docker.io images

PTAL

/retest

[gabemontero]

Also @adambkaplan I'm thinking we should open/associate a BZ with this and backport to releases we still actively maintain (and I shudder to say ... 3.11 even)

thoughts?

[gabemontero]

again unrelated cmd flakes ... cmds that failed different than last run

/retest

[gabemontero]

There might be a known oc bug related to the recent e2e-cmd errors. I've reached out to Maciej for opinions.

Note, this test did pass back with https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25595/pull-ci-openshift-origin-master-e2e-cmd/1314302332669792256 on Oct 8 .... I'm still of the belief that nothing in this PR would have lead to the subsequent failed runs.

[coreydaley]

/retest

[openshift-ci-robot]

@gabemontero: This pull request references Bugzilla bug 1890141, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.0) matches configured target release for branch (4.7.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1890141: move off docker.io in templates/builds/jenkins tests

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.

[adambkaplan]

Generally looks good.

I have a concern about using registry.redhat.io - will this present a challenge backporting to 4.4 and 3.11? Do you plan on using registry.access.redhat.com for those?

I think moving forward registry.redhat.io is the right host for Red Hat images, since registry.access.redhat.com is somewhat deprecated.

[adambkaplan]

/approve

[gabemontero]

Generally looks good.

I have a concern about using registry.redhat.io - will this present a challenge backporting to 4.4 and 3.11? Do you plan on using registry.access.redhat.com for those?

I think moving forward registry.redhat.io is the right host for Red Hat images, since registry.access.redhat.com is somewhat deprecated.

exactly ... my general plan is to use the TBR until I can't but of course as a result that will entail manual cherrypicks vs. the bot

[gabemontero]

different set of cmd test failures with https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25595/pull-ci-openshift-origin-master-e2e-cmd/1318905854161850368

this time just timeout connecting to api server flakes

still unrelated to these changes

/retest

[gabemontero]

@adambkaplan we have managed to avoid e2e-cmd flakes ... all tests green ... how about an lgtm

oh, and based on the files touched, also need an approval from

/assign @bparees

for https://github.com/openshift/origin/blob/master/test/OWNERS

to complete this move off of docker.io images

[bparees]

/approve

[adambkaplan]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, bparees, gabemontero

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:

• test/OWNERS [bparees]

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

[openshift-merge-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-csi	696f71a	link	/test e2e-aws-csi

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-ci-robot]

@gabemontero: All pull requests linked via external trackers have merged:

• openshift/origin#25595

Bugzilla bug 1890141 has been moved to the MODIFIED state.

In response to this:

Bug 1890141: move off docker.io in templates/builds/jenkins tests

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.

[gabemontero]

/cherrypick release-4.6

[openshift-cherrypick-robot]

@gabemontero: new pull request created: #25622

In response to this:

/cherrypick release-4.6

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.