Bug 1902215 - [sig-builds][Feature:Builds] prune builds based on settings in the buildconfig should prune completed builds based on the successfulBuildsHistoryLimit setting
Summary: [sig-builds][Feature:Builds] prune builds based on settings in the buildconfi...
Keywords:
Status: CLOSED DUPLICATE of bug 1902029
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Gabe Montero
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On: 1901982 1902205
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-27 11:39 UTC by Jiří Mencák
Modified: 2020-11-30 21:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1902205
Environment:
[sig-builds][Feature:Builds] prune builds based on settings in the buildconfig should prune completed builds based on the successfulBuildsHistoryLimit setting
Last Closed: 2020-11-30 21:06:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiří Mencák 2020-11-27 11:39:29 UTC
+++ This bug was initially created as a clone of Bug #1902205 +++

Another test failing frequently due to dockerhub pull-rate limiting.  Switch to quay.io instead?

test:
[sig-builds][Feature:Builds] prune builds based on settings in the buildconfig  should prune completed builds based on the successfulBuildsHistoryLimit setting 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-builds%5C%5D%5C%5BFeature%3ABuilds%5C%5D+prune+builds+based+on+settings+in+the+buildconfig++should+prune+completed+builds+based+on+the+successfulBuildsHistoryLimit+setting


Pulling image busybox ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://busybox" as "busybox": Error initializing source docker://busybox:latest: Error reading manifest latest in docker.io/library/busybox: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
<----end of log for "myphp-1-build"/"docker-build"

[AfterEach] [sig-builds][Feature:Builds] prune builds based on settings in the buildconfig
  github.com/openshift/origin/test/extended/util/client.go:138
STEP: Collecting events from namespace "e2e-test-build-pruning-t8grx".
STEP: Found 11 events.
Nov 27 04:01:47.379: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for myphp-1-build: { } Scheduled: Successfully assigned e2e-test-build-pruning-t8grx/myphp-1-build to ci-op-88rzjxyq-56515-8lch4-worker-g92sx
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:15 +0000 UTC - event for e2e-test-build-pruning-t8grx: {namespace-security-allocation-controller } CreatedSCCRanges: created SCC ranges
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:47 +0000 UTC - event for myphp-1-build: {multus } AddedInterface: Add eth0 [10.129.2.121/23]
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:47 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Pulled: Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:378703fbd2408cdd4152439b77ae56749fdef91e00cbd50d0a9bc400712d94e6" already present on machine
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:47 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Created: Created container manage-dockerfile
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:47 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Started: Started container manage-dockerfile
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:48 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Pulled: Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:378703fbd2408cdd4152439b77ae56749fdef91e00cbd50d0a9bc400712d94e6" already present on machine
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:49 +0000 UTC - event for myphp-1: {build-controller } BuildStarted: Build e2e-test-build-pruning-t8grx/myphp-1 is now running
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:49 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Created: Created container docker-build
Nov 27 04:01:47.379: INFO: At 2020-11-27 03:59:49 +0000 UTC - event for myphp-1-build: {kubelet ci-op-88rzjxyq-56515-8lch4-worker-g92sx} Started: Started container docker-build
Nov 27 04:01:47.379: INFO: At 2020-11-27 04:01:41 +0000 UTC - event for myphp-1: {build-controller } BuildFailed: Build e2e-test-build-pruning-t8grx/myphp-1 failed
Nov 27 04:01:47.383: INFO: POD            NODE                                     PHASE   GRACE  CONDITIONS
Nov 27 04:01:47.383: INFO: myphp-1-build  ci-op-88rzjxyq-56515-8lch4-worker-g92sx  Failed         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-11-27 03:59:48 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-11-27 04:01:41 +0000 UTC ContainersNotReady containers with unready status: [docker-build]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-11-27 04:01:41 +0000 UTC ContainersNotReady containers with unready status: [docker-build]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-11-27 03:59:44 +0000 UTC  }]
Nov 27 04:01:47.383: INFO: 
Nov 27 04:01:47.390: INFO: skipping dumping cluster info - cluster too large
Nov 27 04:01:47.418: INFO: Deleted {user.openshift.io/v1, Resource=users  e2e-test-build-pruning-t8grx-user}, err: <nil>
Nov 27 04:01:47.444: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-build-pruning-t8grx}, err: <nil>
Nov 27 04:01:47.454: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  dD-9NTZfTgmKscS0qkCPGAAAAAAAAAAA}, err: <nil>
[AfterEach] [sig-builds][Feature:Builds] prune builds based on settings in the buildconfig
  github.com/openshift/origin/test/extended/util/client.go:139
Nov 27 04:01:47.454: INFO: Waiting up to 7m0s for all (but 100) nodes to be ready
STEP: Destroying namespace "e2e-test-build-pruning-t8grx" for this suite.
Nov 27 04:01:47.468: INFO: Running AfterSuite actions on all nodes
Nov 27 04:01:47.468: INFO: Running AfterSuite actions on node 1
fail [github.com/openshift/origin/test/extended/builds/build_pruning.go:69]: Expected
    <bool>: false
to be true

Additional info:
Similar BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1901982

Comment 2 Gabe Montero 2020-11-30 21:06:40 UTC

*** This bug has been marked as a duplicate of bug 1902029 ***


Note You need to log in before you can comment on or make changes to this bug.