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 1279979 - tftpboot files are not deleted when OS name is changed
Summary: tftpboot files are not deleted when OS name is changed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.1.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Ohad Levy
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1287901
TreeView+ depends on / blocked
 
Reported: 2015-11-10 15:59 UTC by Jacob Hunt
Modified: 2021-12-10 14:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:02:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12474 0 None None None 2016-04-26 16:56:37 UTC

Description Jacob Hunt 2015-11-10 15:59:32 UTC 
Description of problem:

If an OS is changed or renamed to a name a different OS had the boot files in /var/lib/tftpboot/boot are not deleted. 

We have two OSs RedHat 6.6 server and RedHat 6.6 Workstation. When creating an OS we are only able to specify Name = RedHat, Major Version = 6, Minor Version = 6 but we cannot do that because the names conflict. Instead we have named our server version RedHat and workstation version RedHat-1. We found out that this caused an error so we switch the names. Now server is RedHat-1 and workstation is RedHat. However when we try to build a workstation or server it was kernel panicing. The solution was to remove the files in /var/lib/tftpboot/boot so they would be re-cached from the installation media the next time a machine is going to be built. The deletion of those files should happen automatically when the OS name is change. There also should be a way to specify the flavor or version or even distid from factor so we can differentiate our OS types.

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

Satellite 6.1.3
Comment 2 Bryan Kearney 2015-11-13 16:50:07 UTC 
Created redmine issue http://projects.theforeman.org/issues/12474 from this bug
Comment 3 Bryan Kearney 2015-11-16 09:01:33 UTC 
Upstream bug component is TFTP
Comment 6 Bryan Kearney 2016-08-10 19:10:55 UTC 
Upstream bug component is Provisioning Templates
Comment 7 Bryan Kearney 2016-08-10 20:11:56 UTC 
Upstream bug component is TFTP
Comment 8 Bryan Kearney 2016-08-10 22:11:40 UTC 
Upstream bug component is Provisioning Templates
Comment 9 Bryan Kearney 2018-09-04 18:02:55 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.
Note You need to log in before you can comment on or make changes to this bug.