Sorry for the delay on this, I am merely running foreman-installer. Anyways the issue is installer doesn't source the profile script:
[[email protected] ~]$ cat /etc/profile.d/puppet-agent.sh # Add /opt/puppetlabs/bin to the path for sh compatible users if ! echo $PATH | grep -q /opt/puppetlabs/bin ; then export PATH=$PATH:/opt/puppetlabs/bin fi [[email protected] ~]$ foreman-installer should source the profile script at the end or run a setup script like the one you provided. For now manually sourcing the file or simply logging out and logging back in will do the trick. On Mon, Sep 26, 2016 at 9:24 AM, Stephen Benjamin <[email protected]> wrote: > > > ----- Original Message ----- >> From: "Üstün Kaya" <[email protected]> >> To: "Foreman users" <[email protected]> >> Sent: Wednesday, September 21, 2016 3:25:39 PM >> Subject: Re: [foreman-users] Problems with provisioning setup >> >> >> I had the same experience with Foreman 1.12.3. I noticed it it failed to >> find the command 'puppet'. After reboot, it was in path and foreman host >> was successfully registered. Looks like environment setup is incomplete >> without a reboot. It might be related. > > Are you using the latest provisioning templates? If you're using Puppet 4, > this is probably the case that it's not available in $PATH in the provisioning > environment. > > The latest puppet_setup snippet[1] should cover that case though, as it calls > the binary > explicitly with it's full path. > > [1] > https://github.com/theforeman/community-templates/blob/develop/snippets/puppet_setup.erb > > >> Ustun >> >> On Sunday, April 19, 2015 at 8:22:46 AM UTC-7, Osvaldas Šlapikas wrote: >> > >> > I don't know why I get this error but after reboot everything was fine. >> > But thaks for answer >> > >> > On 18 April 2015 at 21:20, Lukas Zapletal <[email protected] <javascript:>> >> > wrote: >> > >> >> Was the installation successful (using our installer)? >> >> >> >> Have you configured at least one proxy? Is it registered? >> >> >> >> Is the host Foreman in installed on checked in via Puppet? >> >> >> >> LZ >> >> >> >> -- >> >> Later, >> >> Lukas #lzap Zapletal >> >> >> >> -- >> >> You received this message because you are subscribed to a topic in the >> >> Google Groups "Foreman users" group. >> >> To unsubscribe from this topic, visit >> >> https://groups.google.com/d/topic/foreman-users/iV3r3qV1Lvw/unsubscribe. >> >> To unsubscribe from this group and all its topics, send an email to >> >> [email protected] <javascript:>. >> >> To post to this group, send email to [email protected] >> >> <javascript:>. >> >> Visit this group at http://groups.google.com/group/foreman-users. >> >> For more options, visit https://groups.google.com/d/optout. >> >> >> > >> > >> >> -- >> 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 [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Foreman users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/foreman-users/iV3r3qV1Lvw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
