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.
Created attachment 1071970[details]
screenshot of host field
Description of problem:
If a host is created and assigned to a host group (with operating system settings defined) the host os field will randomly switch after what seems to be some puppet runs. We have seen hosts switch from rhel 6.6 workstation to 6.6 server and 7 server to 7 workstation randomly.
It doesn't actually affect the host unless you try to rebuild the host while the OS field is set incorrectly. When the host switches it seems to clean the installation media field and partition table so those fields need to be manually assigned again. The attached picture shows what a host does after being set as 6.6 workstation and then building and running puppet. The host automatically changed to el6s (6.6 server) and the fields were cleared.
Additional info:
Our hosts switch workstation -> server. Looking back at
our hosts it appears that every puppet run workstation builds are switching
to server builds and losing their installation media and partition
information. Server builds are not switching to workstation anymore.
I am going to close this as a duplicate of bug 1155704, since they are both tied to the same upstream issue.
*** This bug has been marked as a duplicate of bug 1155704 ***
Created attachment 1071970 [details] screenshot of host field Description of problem: If a host is created and assigned to a host group (with operating system settings defined) the host os field will randomly switch after what seems to be some puppet runs. We have seen hosts switch from rhel 6.6 workstation to 6.6 server and 7 server to 7 workstation randomly. It doesn't actually affect the host unless you try to rebuild the host while the OS field is set incorrectly. When the host switches it seems to clean the installation media field and partition table so those fields need to be manually assigned again. The attached picture shows what a host does after being set as 6.6 workstation and then building and running puppet. The host automatically changed to el6s (6.6 server) and the fields were cleared. Additional info: Our hosts switch workstation -> server. Looking back at our hosts it appears that every puppet run workstation builds are switching to server builds and losing their installation media and partition information. Server builds are not switching to workstation anymore.