Missing registered smart proxy foreman.domain, please ensure it is registered

Support
1

Hello,

I have the following setup:

Host1: mysql/maria DB
Host2: foreman
Host3: smart proxy + puppetmaster
Host4: smart proxy + puppet ca

I added/registered both smart proxies (host 3 and 4) to foreman. They show
up below "Infrastructure->Smart proxies".

in foreman UI in Provisioning setup ("Infrastructure->Provisioning setup")
foreman insists on the following prerequisite:
1.) …
2.) Missing registered smart proxy foreman.domain (== host 2), please
ensure it is registered
3.) …

As far as I understand, I dont need smart proxy on foreman. Is that correct
?

I am using centos 7.3, foreman 1.15, puppet 4.10.1, puppet server 2.7.2

Regards,
Marian

2

That's correct if you want to provisioning or distribute repos you can use
the smartproxy but if you want to provisioning in the same foreman network
you need the smart proxy because the proxy host the services of dhcp tftp
dns plus any plugin you want to have

··· On Monday, June 12, 2017 at 6:36:57 PM UTC+2, marian...@gmail.com wrote: > > Hello, > > > I have the following setup: > > Host1: mysql/maria DB > Host2: foreman > Host3: smart proxy + puppetmaster > Host4: smart proxy + puppet ca > > I added/registered both smart proxies (host 3 and 4) to foreman. They show > up below "Infrastructure->Smart proxies". > > in foreman UI in Provisioning setup ("Infrastructure->Provisioning setup") > foreman insists on the following prerequisite: > 1.) ... > 2.) Missing registered smart proxy foreman.domain (== host 2), please > ensure it is registered > 3.) ... > > As far as I understand, I dont need smart proxy on foreman. Is that > correct ? > > I am using centos 7.3, foreman 1.15, puppet 4.10.1, puppet server 2.7.2 > > Regards, > Marian > >
3

Hello Mario,

If I understand you correctly you say in case of provisioning using using
features like pxe boot and dhcp a smart proxy with this particular feature
set (tftp, dns, dhcp) is required. But it can be a different host, right ?

··· Am Montag, 12. Juni 2017 21:08:58 UTC+2 schrieb Mario Gamboa: > > That's correct if you want to provisioning or distribute repos you can use > the smartproxy but if you want to provisioning in the same foreman network > you need the smart proxy because the proxy host the services of dhcp tftp > dns plus any plugin you want to have > > > On Monday, June 12, 2017 at 6:36:57 PM UTC+2, marian...@gmail.com wrote: >> >> Hello, >> >> >> I have the following setup: >> >> Host1: mysql/maria DB >> Host2: foreman >> Host3: smart proxy + puppetmaster >> Host4: smart proxy + puppet ca >> >> I added/registered both smart proxies (host 3 and 4) to foreman. They >> show up below "Infrastructure->Smart proxies". >> >> in foreman UI in Provisioning setup ("Infrastructure->Provisioning >> setup") foreman insists on the following prerequisite: >> 1.) ... >> 2.) Missing registered smart proxy foreman.domain (== host 2), please >> ensure it is registered >> 3.) ... >> >> As far as I understand, I dont need smart proxy on foreman. Is that >> correct ? >> >> I am using centos 7.3, foreman 1.15, puppet 4.10.1, puppet server 2.7.2 >> >> Regards, >> Marian >> >>
4

That's correct if you want to provisioning or distribute repos you can use
> the smartproxy but if you want to provisioning in the same foreman network
> you need the smart proxy because the proxy host the services of dhcp tftp
> dns plus any plugin you want to have
>
>

Yes I want to do VM provisioning ! … and I added smart proxies with
feature dhcp/dns/tftp to my setup. So, now I am running the following
machines:

  • db
  • foreman (enc, reports, gui) -> foreman.domain
  • foreman-gwy (smartproxy for dhcp/dns)
  • foreman-tftp (smartproxy for tftp)
  • puppet-master
  • puppet-ca

Both machines foreman-gwy and foreman-tftp are registered as smart proxies.
Unfortunately I am still unable to start provisioning. Foreman continues to
complain with the beforementioned error: "Missing registered smart proxy foreman.domain,
please ensure it is registered"

Question: What do I need to do else in order to fix this error and to start
provisioning ? According to foreman manual 1.15 (especially in the
archtiecture diagram:
Foreman :: Manual) there shouldnt
be any problem with respect to this setup, isnt it ?

5

I want to mention that all machines are in the same subnetwork (like
192.168.1.0/24)