Description: ---------------------- Provisioning a VM on GCE CR is creating two host profiles in foreman. The one is along with domain which we have provided while provisioning and another is with the actual domain appends from GCE. Like : 1. testgceHost.domain-from-foreman 2. testgceHost.domain-from-foreman.us-east1-gce-internal Steps: --------- 1. Create GCE CR 2. Create a domain in foreman 3. Provision a VM on GCE CR and assign the domain created while provisioning Actual Behavior: -------------------- Two host profiles are created in foreman instead of one for a provisioned VM on GCE as described in the description of this bug. Expected Behavior: -------------------- Single host profiles should be created in foreman for a provisioned VM on GCE.
Created redmine issue https://projects.theforeman.org/issues/27158 from this bug
When I tried to reproduce this issue on latest foreman, found below observations. There is a setting called "Use UUID for certificates" which says "Satellite will use random UUIDs for certificate signing instead of hostnames". In case of google compute resource, it is recommended to enable this setting for consistent Puppet certificate IDs instead of hostnames. Upstream documentation link - https://theforeman.org/manuals/1.22/index.html#5.2.4GoogleComputeEngineNotes By observation is that if this setting is disabled(by default it is) and user tries to provision a system with puppet integration using google compute resource, it creates two host profiles. One which is already created while provisioning & other one is when facts from provisioned system are collected to the server. The reason behind this is because of hostnames are different. With this setting, it will not create two host profiles. so closing this BZ.