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 1255718 - Provisioning a RHEL5.9 host and then upgrade it to 5.11 creates a localhost.localdomain host record
Summary: Provisioning a RHEL5.9 host and then upgrade it to 5.11 creates a localhost.l...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-21 11:48 UTC by Fred van Zwieten
Modified: 2017-01-12 18:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 18:41:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fred van Zwieten 2015-08-21 11:48:10 UTC 
Description of problem:
Scenario is as described in "Steps to Reproduce".

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


How reproducible:


Steps to Reproduce:
1. Have a 5.9 kickstart repo, but not in a CV
2. Have 5Server in CV
3. Provision new host using 5.9 and Red Hat Default Kickstart

Actual results:
A correcly named hostrecord with no reports. Its yaml file has no classes.
A new Operating System "Red Hat 5.11" with a host count of 1. Clicking on this "1" gives a host record "localhost.localdomain" with reports. It's yaml file has classes.


Expected results:
one host record with repords and a correct yaml file

Additional info:
Deleting the localhost.localdomain maps everything back to the correct host record.

We created a workaround by moving the "yum update" in the Red Hat Default Kickstart after all puppet related stuff, yust before the end. We did this because the initial puppet run creates the host record and if the yum update has not been done it will still use the 5.9 OS.
Comment 2 Bryan Kearney 2016-07-08 20:23:01 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 4 Bryan Kearney 2017-01-12 18:41:53 UTC 
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.
Note You need to log in before you can comment on or make changes to this bug.