Project

General

Profile

Bug #26976

Provisioning a VM on GCE creating two Host Profiles in foreman

Added by Jitendra Yejare over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
High
Category:
Compute resources - GCE
Target version:
-
Difficulty:
trivial
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

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.

History

#1 Updated by Kavita Gaikwad over 2 years ago

  • Bugzilla link set to 1721899
  • Status changed from New to Rejected
  • Subject changed from Provisionoing a VM on GCE creating two Host Profiles in foreman to Provisioning a VM on GCE creating two Host Profiles in foreman

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

Also available in: Atom PDF