Bug 1714183
Summary: | Sporadic CreateContainerError, container_linux.go:336: starting container process caused "process_linux.go:399: container init caused \"\" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Marek Schmidt <maschmid> |
Component: | Containers | Assignee: | Mrunal Patel <mpatel> |
Status: | CLOSED NOTABUG | QA Contact: | weiwei jiang <wjiang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, dwalsh, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 4.2.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-08-21 21:14:20 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
Marek Schmidt
2019-05-27 10:36:00 UTC
Also note, according to grafana, memory and disk are well below 30% on all nodes (as well as CPU besides a few spikes up to 50%), so this doesn't seem to be caused by actual resource pressures. Removing just the CPU limit doesn't seem to help ( 'Error: container create failed: container_linux.go:336: starting container process caused "process_linux.go:399: container init caused \"read init-p: connection reset by peer\"' still occured) Bumping up CPU and memory requests make the pods came up reliably. |