Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1920602

Summary:	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
Product:	OpenShift Container Platform	Reporter:	Andreas Karis <akaris>
Component:	Unknown	Assignee:	Sudha Ponnaganti <sponnaga>
Status:	CLOSED DUPLICATE	QA Contact:	Jianwei Hou <jhou>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, eparis, jokerman
Target Milestone:	---
Target Release:	---
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:	2021-01-26 22:30:40 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 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 ***