[4.5] disable broken jenkins test

[bparees]

this test consistently fails because the pipeline references a second deployment which does not exist.

[openshift-ci-robot]

@bparees: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[4.5] disable broken jenkins test

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.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees

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:

• test/extended/builds/OWNERS [bparees]

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

[bparees]

@akram @gabemontero 4.5 backport to unblock 4.5 merges.

[openshift-ci-robot]

@bparees: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[4.5] disable broken jenkins test

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]

@bparees yep saw that as well this weekend and have #25179 up .. though only in master for now ... I tagged most everyone but you in the recent PR comments.

reader's digest version: it got fixed a week or so ago and then rebroke over the last few days

my PR removes the problematic scneario vs. disables the whole test, but I'm fine with what you have done going in followed by my PR

I'm also working on updates to the jenkins client plugin to move the test removed from my PR into that repo via a operator golang styled e2e ... this should resolve that old problem we've had if you recall with testing the master branch of that test file vs. and PR version of it.

I'm testing that now and will tag you in the client plugin PR when it is up.

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-disruptive	55b53c6	link	/test e2e-aws-disruptive
ci/prow/e2e-vsphere	55b53c6	link	/test e2e-vsphere

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.

[bparees]

failures not related to this change and this is deadlocked w/ the DR etcd test fix, so manually merging this one.

[akram]

@bparees and @gabemontero , I saw this also. We also have them failing in 4.2 for which I proposed a first fix changing the the origin-cli that we depend on openshift/jenkins#1089 , because, there was a regression on oc run command that now creates pods instead of deployments.
This fixed 2 e2e over the 4 failing. But, there is still something remaining. I put them on hold then.

skipping these tests for now would help