Automatic association of foreman host with katello host

Support
1

Greetings,

What is necessary conditions for automatic association of puppet (foreman)
host with content host (katello host)?

Say you have a clean RHEL 6.6 system and you are manually registering and
subscribing it:

  1. subscription-manager register --autosubscribe --org=orgname
  2. puppet agent -t --server=satellite.corp.tld
    –ca_server=satellite.corp.tld --no-daemonize --report --pluginsync
    –waitforcert 1
  3. sign puppet certificate

After that steps I can get only "No provisioning details are available for
this content host." on "Provisioning Details" tab.
Of course I could always fix host field in foreman DB but I'm afraid that
it wasn't correct way to establish association.

Thanks!

2

> Greetings,
>
> What is necessary conditions for automatic association of puppet
> (foreman) host with content host (katello host)?
>
> Say you have a clean RHEL 6.6 system and you are manually registering
> and subscribing it:
> 1. subscription-manager register --autosubscribe --org=orgname
> 2. puppet agent -t --server=satellite.corp.tld
> --ca_server=satellite.corp.tld --no-daemonize --report --pluginsync
> --waitforcert 1
> 3. sign puppet certificate
>
> After that steps I can get only "No provisioning details are available
> for this content host." on "Provisioning Details" tab.
> Of course I could always fix host field in foreman DB but I'm afraid
> that it wasn't correct way to establish association.

The current logic works as follows:

  1. When registering a content host, check to see if there is an
    existing Host with the same mac address and hostname* within the same
    Organization
  2. If the Host exists and already has a Content Host, delete that
    Content Host
  3. Create a new Content Host and associate it with the Host found in
    step 2)

So for this to work the Host has to exist before registration (or else
you need to re-register after the Host has been created). The Host also
needs to be in the same Organization as what you are using to register
the Content Host with. The idea being that we were handling the
workflow of provisioning a new host, and having the host register back
as a content host.

We are working towards unifying Content Hosts and Host in the future at
a model level so they really are just a single object. I wouldn't
expect that until 2.4 or 2.5 though, as we are just starting to do the
design work now.

-Justin

  • This was the case in 2.1, in 2.2 it only uses the Hostname
··· On 03/20/2015 11:16 AM, amigo.elite@gmail.com wrote:

Thanks!

You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.