Bug 1705318
Summary: | Ulimit too low during builds | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Adam Kaplan <adam.kaplan> |
Component: | Containers | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, dwalsh, ekuric, gblomqui, jmencak, jokerman, mmccomas, nalin |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:48:19 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: |
Description
Adam Kaplan
2019-05-02 01:35:21 UTC
Thanks for narrowing down where to look! Opened https://github.com/openshift/builder/pull/69. Checked and this issue is fixed, s2i work well with `npm install` for `oc new-app nodejs~https://github.com/lholmquist/react-web-app` # openshift-sti-build version openshift-sti-build v4.1.0-201905032232+59e5dc1-dirty # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-05-05-070156 True False 15m Cluster version is 4.1.0-0.nightly-2019-05-05-070156 # oc get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME ip-10-0-133-56.ap-northeast-1.compute.internal Ready worker 23m v1.13.4+db7b699c3 10.0.133.56 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 ip-10-0-137-75.ap-northeast-1.compute.internal Ready master 33m v1.13.4+db7b699c3 10.0.137.75 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 ip-10-0-149-8.ap-northeast-1.compute.internal Ready worker 23m v1.13.4+db7b699c3 10.0.149.8 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 ip-10-0-158-112.ap-northeast-1.compute.internal Ready master 33m v1.13.4+db7b699c3 10.0.158.112 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 ip-10-0-169-206.ap-northeast-1.compute.internal Ready worker 23m v1.13.4+db7b699c3 10.0.169.206 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 ip-10-0-174-121.ap-northeast-1.compute.internal Ready master 33m v1.13.4+db7b699c3 10.0.174.121 <none> Red Hat Enterprise Linux CoreOS 410.8.20190505.0 (Ootpa) 4.18.0-80.el8.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8 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-2019:0758 |