Bug 1797828
Summary: | Can't oc login nor ssh access master node. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ryoji noma <rnoma> |
Component: | Node | Assignee: | Ryan Phillips <rphillips> |
Status: | CLOSED DUPLICATE | QA Contact: | Sunil Choudhary <schoudha> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.0 | CC: | aos-bugs, bbreard, dustymabe, imcleod, jligon, jokerman, nstielau |
Target Milestone: | --- | ||
Target Release: | 4.5.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: | 2020-03-12 13:32:53 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
ryoji noma
2020-02-04 00:59:00 UTC
From those logs, it appears that hyperkube is panicking trying to start the `console-operator` and `authentication-operator` pods. Not sure how this would impact the ability to SSH to a host, but may affect the ability to `oc login`? Sending over to Node for additional investigation. This may be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1801826. The fix that merged reserves more CPU and RAM for Kubelet and CRIO. How much memory is available on the masters? Hi. Your question is about the master node spec? The master node has 16GB memory. $ head sosreport-ip-10-0-158-144-02570287-2020-01-28-ckwjjxh/proc/meminfo MemTotal: 16420432 kB MemFree: 9454948 kB MemAvailable: 13928356 kB Buffers: 116 kB Cached: 4213008 kB SwapCached: 0 kB Active: 3081624 kB Inactive: 3248440 kB Active(anon): 1693472 kB Inactive(anon): 508 kB There are various efforts to fix this... We have the previously mentioned fix going into 4.2 as well as other performance fixes going in. *** This bug has been marked as a duplicate of bug 1801826 *** |