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

Bug 2101356

Summary:	SNO kdump-capture.service oom
Product:	OpenShift Container Platform	Reporter:	diflores
Component:	Telco Edge	Assignee:	Jim Ramsay <jramsay>
Telco Edge sub component:	ZTP	QA Contact:	yliu1
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	djuran, grajaiya, imiller, jramsay
Version:	4.10
Target Milestone:	---
Target Release:	4.12.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-30 18:04: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:
Bug Depends On:
Bug Blocks:	2102134, 2102328

Description diflores 2022-06-27 09:45:03 UTC

Description of problem:
SNO 4.10.17 ZTP provisioned.
kdump service is enabled by default with 256M memory, same as in docs [1] after kernel crash core is not generated, from console logs it can be seen kdump-capture.service is oom 

Version-Release number of selected component (if applicable):
4.10.15
4.10.17

How reproducible:


Steps to Reproduce:
1. ZTP SNO installation
2. kdump enabled by default
3. trigger a manual kernel crash with `echo c > /proc/sysrq-trigger` 

Actual results:


Expected results:
kdump configuration or documentation corrected.


Additional info:
[1] https://docs.openshift.com/container-platform/4.10/support/troubleshooting/troubleshooting-operating-system-issues.html#enabling-kdump

Comment 1 David Juran 2022-06-27 11:10:00 UTC

It looks to me the crashkernel memory is hardcoded in the template[1]
Maybe we could use the "auto" parameter[2] instead?

[1]
https://github.com/openshift-kni/cnf-features-deploy/blob/7be94f9bff2601d219444c082c88e503dc609dcc/ztp/source-crs/extra-manifest/06-kdump-master.yaml#L18

[2]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/configuring-kdump-on-the-command-line_managing-monitoring-and-updating-the-kernel#configuring-kdump-memory-usage_configuring-kdump-on-the-command-line

Comment 4 yliu1 2022-08-02 15:55:07 UTC

Unable to verify on 4.12 yet. Mark as verified based on verification done on 4.11 build viz bz 2102134.

Comment 6 Rory Thrasher 2024-04-30 18:04:53 UTC

OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary