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

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1328999

Summary:	Kernel Panic After Patches Update through Satellite UI
Product:	Red Hat Satellite	Reporter:	Josh Foots <jfoots>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.7	CC:	anerurka, bbuckingham, cisley, egolov, ehelms, franz.brauneder, jokot3, jsherril, kumcha.pak, mmccune, nitthoma, ramsingh, rbeyel, rmullett, rsawhill, satellite6-bugs
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 17:57:35 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 Josh Foots 2016-04-20 20:39:45 UTC

Description of problem:

The root cause is that the /boot is full due to patches updated through Satellite.  The Satellite does not honor the  feature installonly_limit=3 in the /etc/yum.conf.  The VM keeps all versions of kernels.   As a result, the /boot is full and the VM is non boot-able.  

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


How reproducible:

Very

Steps to Reproduce:
1. Apply a kernel patch via Red Hat Satellite 6.1

Actual results:

/boot is full and the VM is unbootable

Expected results:

/boot to only have the last 3 kernels present

Additional info:

current workaround:

ssh into the machines and run yum update or run  # package-cleanup --oldkernels --count=3 after completing the patching process from the satellite WebUI

Comment 8 Mike McCune 2017-07-10 16:15:10 UTC

As a workaround, customers should utilize Remote Execution to perform updates instead of the Katello Agent.

Remote Execution uses yum natively and will honor the yum configuration.

Currently there are no updates to this bug as we have not started work on it but there is immediate relief available if users switch away from Katello Agent to Remote Execution as the means to update hosts.

Comment 11 Bryan Kearney 2018-09-04 17:57:35 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.