Bug 1920602 - Upgrade from 4.5.20 -> 4.6.12 on vSphere, Infra nodes become unresponsive and need to be hard rebooted, OOM and systemd-journal coredumps
Summary: Upgrade from 4.5.20 -> 4.6.12 on vSphere, Infra nodes become unresponsive and...
Keywords:
Status: CLOSED DUPLICATE of bug 1906496
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Unknown
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sudha Ponnaganti
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-26 17:23 UTC by Andreas Karis
Modified: 2021-01-26 22:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-26 22:30:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andreas Karis 2021-01-26 17:23:16 UTC 
Upgrade from 4.5.20 -> 4.6.12 on vSphere, Infra nodes become unresponsive and need to be hard rebooted, OOM and systemd-journal coredumps

This issue only affects Infra nodes during the upgrade process. During upgrade when coreos is updating on infra nodes, the process hangs and we can see messages on node console.
The system coredump and the system consume full cpu and a lots of IO. Reboot of nodes repairs the problem, but this should not be the normal process.

The customer can reproduce the issue in various environments with the same setup.
Comment 5 Andreas Karis 2021-01-26 22:30:40 UTC 

*** This bug has been marked as a duplicate of bug 1906496 ***
Note You need to log in before you can comment on or make changes to this bug.