Bug 1902029: move off docker.io in build e2e's (approximate recent 4.7 changes) #25721
Conversation
|
@gabemontero: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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
added
the
do-not-merge/work-in-progress
|
Nice! This PR has the added benefit of making it possible to run more e2e tests on s390x by removing the dependency on |
|
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25721/pull-ci-openshift-origin-release-4.6-e2e-gcp-builds/1333536681587904512 has some failures I need to look at ... most likely related to the change in images ... parsing for messages in build logs and such, build name refs, etc. |
gabemontero
force-pushed
the
more-dockerio-moves-46
branch
from
2692148
to
5cb082f
Compare
|
more cloud quota pain /test e2e-gcp-builds |
1 similar comment
|
more cloud quota pain /test e2e-gcp-builds |
|
OK all green e2e-gcp-builds !! /retest |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
gabemontero
changed the title
openshift-ci-robot
added
bugzilla/severity-high
|
@gabemontero: This pull request references Bugzilla bug 1902029, which is invalid:
Comment In response to this:
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
added
the
bugzilla/invalid-bug
|
@gabemontero: This pull request references Bugzilla bug 1902029, which is invalid:
Comment In response to this:
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
force-pushed
the
more-dockerio-moves-46
branch
from
d77afa2
to
297a0f2
Compare
|
/retest |
4 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
fip flakes unrelated to build /skip |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/hold the e2e-aws-upgrade failure around `LEASED_RESOURCE: unbound variable" is showing up in a lot of places according to https://search.ci.openshift.org/?search=LEASED_RESOURCE%3A+unbound+variable&maxAge=24h&context=2&type=all&name=&maxMatches=5&maxBytes=20971520&groupBy=job I've reached out on #4-dev-triage for BZ routing guidance |
openshift-ci-robot
added
the
do-not-merge/hold
Looks like we need openshift/ci-tools#1535, minimally |
|
/hold cancel |
openshift-ci-robot
removed
the
do-not-merge/hold
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@gabemontero: The following tests failed, say
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. |
|
/retest |
|
@gabemontero: All pull requests linked via external trackers have merged: Bugzilla bug 1902029 has been moved to the MODIFIED state. In response to this:
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 there are still some 4.6 vsphere and vsphere-upi jobs failing with the docker rate limiting issue. Are there more pending PRs that need to get in? |
|
hey @abhat - yeah for 4.6 I only handled the subset of e2e for the build component that Clayton took on with his recent changes in 4.7 I have no further PRs planned. And I don't have the bandwidth and am not taking on any throttling related updates in 4.6 for the other sig-* e2e's in the way I addressed builds, much less trying to take on backporting Clayton's entire change. I saw in the recent email from him that a 4.6.z cherrypick of his changes were being considered, and I saw an attempt in his PR to use the bot, but it hit conflicts and failed. For example, in looking at https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-vsphere/1346094150457495552 I see sig-imageregistry, sig-cli, sig-network, sig-apps but not sig-builds IMO 4.6.z BZs should be opened against each of those sig-* components for any throttling that they are hitting. |
This PR picks the move to imagestream dockerimage ref's achived via #24887 in 4.7 for the build e2e's (vs. use
of busybox, centos:7, or direct ruby etc. refs to docker.io), without the additional k8s test integration and disconnected/mirroring related changes that at the moment are only in 4.7
There is mentioned of backporting some form of that entire change to 4.6.z
But this would be a more immediate subset of that, and should not conflict if that entire backport actually occurs.
/assign @adambkaplan