Red Hat Bugzilla – Bug 1255718
Provisioning a RHEL5.9 host and then upgrade it to 5.11 creates a localhost.localdomain host record
Last modified: 2017-01-12 13:41:53 EST
Description of problem:
Scenario is as described in "Steps to Reproduce".
Version-Release number of selected component (if applicable):
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
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.
one host record with repords and a correct yaml file
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.
Per 6.3 planning, moving out non acked bugs to the backlog
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.