try out new test job in actual PR

[gabemontero]

OK @akram @waveywaves @jkhelil here we go ... let's see how the new e2e PR test looks in an actual PR

[gabemontero]

@akram @waveywaves @jkhelil after hopefully getting a passing test with what is in the repo, I'll update this PR to enable the problematic oc.run tests which caused us the recent headaches.

We should then see it fail, and hopefully see the debug I've put in.

[gabemontero]

error: build error: failed to pull image: Get https://quay.io/v2/openshift/origin-jenkins-agent-maven/manifests/v4.0: received unexpected HTTP status: 502 Bad Gateway

both e2e's .... CI woke up in a bad mood this AM .... I'll wait a little bit, then try again

[gabemontero]

/retest

[gabemontero]

OK @akram @waveywaves @jkhelil

we have a passing e2e-aws-operator in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_jenkins-client-plugin/338/pull-ci-openshift-jenkins-client-plugin-master-e2e-aws-operator/1275398029741920256

If you open that up and look at the JUnit tests that passed you'll see a Run template e2e-aws-operator - e2e-aws-operator container test that ran for 4m32s .... that is our new test here. And that time lines up with my local testing.

I'm now going to re-enable the oc.run test that now breaks (@akram discovered the behavior was explicitly changed for oc run ... now working on pods vs. DCs)

we'll see if/how it fails

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero

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

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

[gabemontero]

oc run portion of the test re-enabled with da82194

@akram @waveywaves @jkhelil

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-operator	da82194	link	/test e2e-aws-operator

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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]

OK @akram @waveywaves @jkhelil

the test run https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/pr-logs/pull/openshift_jenkins-client-plugin/338/pull-ci-openshift-jenkins-client-plugin-master-e2e-aws-operator/1275415701720403968 failed as expected !

If you look at https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_jenkins-client-plugin/338/pull-ci-openshift-jenkins-client-plugin-master-e2e-aws-operator/1275415701720403968/build-log.txt you'll see the

• the dump of the job log (if you look at it in detail, I may have had a typo and didn't disable exactly how I intended, so it is not the exact oc run can't find deployment error, but that is OK for our purposes here ;-)
• a dump of the jenkins pod
• a dump of any pods the pipeline initiated ... mongodb deployments, ruby builds whatever

I think we are good to go. Closing this PR out. Review at your convenience.