Bug 1620272
Summary: | Binary builds hang the openshift api server in cluster up | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> | ||||||
Component: | Master | Assignee: | David Eads <deads> | ||||||
Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 3.10.0 | CC: | aos-bugs, claprun, gandrian, jokerman, lmohanty, mfojtik, mmccomas, rruss, wewang, xxia, yinzhou | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 3.11.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1624197 (view as bug list) | Environment: | |||||||
Last Closed: | 2018-10-11 07:25:25 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1624197 | ||||||||
Attachments: |
|
Description
Ben Parees
2018-08-22 20:46:46 UTC
Created attachment 1477966 [details]
pprof output after a binarybuild is started
Earlier i thought this was not affecting 3.11 but it looks like it is hanging there also. Blocked by Bug 1627005 Verified with ocp: [root@Master-cluster-up ~]$ oc version oc v3.11.0-0.32.0 kubernetes v1.11.0+d4cacc0 Can't reproduce it. @zhou ying verified in ocp:v3.11.0-0.28.0 too @Ben Parees What's the special of your source.tar? if we create tar file from https://github.com/sclorg/nodejs-ex/, it cannot met the issue, right? I just want to know how to make it payload,just a curiosity, thanks. Any sufficiently large source.tar file will trigger the issue. Make one that's about 10megs. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652 |