Foreman 1.0 no puppet classes

Are you running foreman on a different host than the puppetmaster?

Is your modulepath setup correctly in puppet? Are you using puppet classes or modules, as foreman does not support classes by themselves unless they are part of a module.

Thanks,

Corey Osman
corey@logicminds.biz

Green IT and Data Center Automation Specialist

··· On Aug 3, 2012, at 11:19 AM, Dave Nash wrote:

Hello All,

I am trying to setup foreman as a fresh install to replace cobbler in our infrastructure. The problem I am having is foreman is not seeing the puppet classes and when I attempt to import them from the Web UI I get “No changes to your environment detected”. Any idea’s?

puppet version is 2.7.18-1 using storeconfig in postgresql
foreman version is 1.0 sharing the same DB as puppets storeconfigs

thanks!
–dn


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

No foreman is running on the same host as puppet as well as the
foreman-proxy.

Yes the module path for each environment is setup correctly in the
puppet.conf and I am using modules not just classes.

[production]
manifest = /home/puppet/master/production/site.pp
modulepath = /workplace/puppet/modules/production
[development]
manifest = /home/puppet/master/development/site.pp
modulepath = /workplace/puppet/modules/development
[testing]
manifest = /home/puppet/master/testing/site.pp
modulepath = /workplace/puppet/modules/testing
[staging]
manifest = /home/puppet/master/staging/site.pp
modulepath = /workplace/puppet/modules/staging
[perf]
manifest = /home/puppet/master/perf/site.pp
modulepath = /workplace/puppet/modules/perf

–dn

··· On Friday, August 3, 2012 11:43:59 AM UTC-7, Corey Osman wrote: > > Are you running foreman on a different host than the puppetmaster? > > Is your modulepath setup correctly in puppet? Are you using puppet > classes or modules, as foreman does not support classes by themselves > unless they are part of a module. > > > Thanks, > > Corey Osman > corey@logicminds.biz > > Green IT and Data Center Automation Specialist > > > > > > > On Aug 3, 2012, at 11:19 AM, Dave Nash wrote: > > Hello All, > > I am trying to setup foreman as a fresh install to replace cobbler in > our infrastructure. The problem I am having is foreman is not seeing the > puppet classes and when I attempt to import them from the Web UI I get "No > changes to your environment detected". Any idea's? > > puppet version is 2.7.18-1 using storeconfig in postgresql > foreman version is 1.0 sharing the same DB as puppets storeconfigs > > thanks! > --dn > > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en. > > >

So the first thing I would do, is hit the proxy to make sure it is
configured properly (You have to hit it from a node that is in the ACL
in smartproxyhome/config/settings.yaml): (You can use a browser or
curl)

The following URL (basically) will give you back a big list of
classes, if the proxy is configured correctly.
http://foreman.domain.com:8443/puppet/environments/my_puppetenvironment/classes

You can also hit /puppet/environments and confirm the list of
environments is being served.

Let us know the results.

Cheers,
-Brian

··· On Fri, Aug 3, 2012 at 3:27 PM, Dave Nash wrote: > No foreman is running on the same host as puppet as well as the > foreman-proxy. > > Yes the module path for each environment is setup correctly in the > puppet.conf and I am using modules not just classes. > > [production] > manifest = /home/puppet/master/production/site.pp > modulepath = /workplace/puppet/modules/production > [development] > manifest = /home/puppet/master/development/site.pp > modulepath = /workplace/puppet/modules/development > [testing] > manifest = /home/puppet/master/testing/site.pp > modulepath = /workplace/puppet/modules/testing > [staging] > manifest = /home/puppet/master/staging/site.pp > modulepath = /workplace/puppet/modules/staging > [perf] > manifest = /home/puppet/master/perf/site.pp > modulepath = /workplace/puppet/modules/perf > > --dn > > On Friday, August 3, 2012 11:43:59 AM UTC-7, Corey Osman wrote: >> >> Are you running foreman on a different host than the puppetmaster? >> >> Is your modulepath setup correctly in puppet? Are you using puppet >> classes or modules, as foreman does not support classes by themselves unless >> they are part of a module. >> >> >> Thanks, >> >> Corey Osman >> corey@logicminds.biz >> >> Green IT and Data Center Automation Specialist >> >> >> >> >> >> >> On Aug 3, 2012, at 11:19 AM, Dave Nash wrote: >> >> Hello All, >> >> I am trying to setup foreman as a fresh install to replace cobbler in our >> infrastructure. The problem I am having is foreman is not seeing the puppet >> classes and when I attempt to import them from the Web UI I get "No changes >> to your environment detected". Any idea's? >> >> puppet version is 2.7.18-1 using storeconfig in postgresql >> foreman version is 1.0 sharing the same DB as puppets storeconfigs >> >> thanks! >> --dn >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ. >> To post to this group, send email to foreman-users@googlegroups.com. >> To unsubscribe from this group, send email to >> foreman-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/foreman-users?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/foreman-users/-/VRzzPqDKMU0J. > > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en.

Hitting http://foreman:8443/puppet/environments returns

["perf","testing","dntest","development","staging"]

which is correct, if I hit http://foreman:8443/puppet/environments/production I get

{"name":"production","paths":["/workplace/puppet/modules/production"]}

but when I go to http://foreman:8443/puppet/environments/production/classes I just get

[]

and I see E, [2012-08-03T14:01:18.307209 #1737] ERROR – : Not found in the smart proxy debug log

This is everything concerning puppet in the settings.yaml for the smart proxy

enable PuppetCA management

:puppetca: true

enable Puppet management

:puppet: true
:puppetconfdir: /etc/puppet/puppet.conf
:puppet_conf: /etc/puppet/puppet.conf
:ssldir: /var/lib/puppet/ssl
:puppetdir: /etc/puppet

I have tried a couple different ways I found through google search to make
sure it sees the puppet.conf

Thanks!

–dn

··· On Friday, August 3, 2012 12:42:46 PM UTC-7, Brian Gupta wrote: > > So the first thing I would do, is hit the proxy to make sure it is > configured properly (You have to hit it from a node that is in the ACL > in smartproxyhome/config/settings.yaml): (You can use a browser or > curl) > > The following URL (basically) will give you back a big list of > classes, if the proxy is configured correctly. > > http://foreman.domain.com:8443/puppet/environments/my_puppetenvironment/classes > > You can also hit /puppet/environments and confirm the list of > environments is being served. > > Let us know the results. > > Cheers, > -Brian > > On Fri, Aug 3, 2012 at 3:27 PM, Dave Nash > wrote: > > No foreman is running on the same host as puppet as well as the > > foreman-proxy. > > > > Yes the module path for each environment is setup correctly in the > > puppet.conf and I am using modules not just classes. > > > > [production] > > manifest = /home/puppet/master/production/site.pp > > modulepath = /workplace/puppet/modules/production > > [development] > > manifest = /home/puppet/master/development/site.pp > > modulepath = /workplace/puppet/modules/development > > [testing] > > manifest = /home/puppet/master/testing/site.pp > > modulepath = /workplace/puppet/modules/testing > > [staging] > > manifest = /home/puppet/master/staging/site.pp > > modulepath = /workplace/puppet/modules/staging > > [perf] > > manifest = /home/puppet/master/perf/site.pp > > modulepath = /workplace/puppet/modules/perf > > > > --dn > > > > On Friday, August 3, 2012 11:43:59 AM UTC-7, Corey Osman wrote: > >> > >> Are you running foreman on a different host than the puppetmaster? > >> > >> Is your modulepath setup correctly in puppet? Are you using puppet > >> classes or modules, as foreman does not support classes by themselves > unless > >> they are part of a module. > >> > >> > >> Thanks, > >> > >> Corey Osman > >> corey@logicminds.biz > >> > >> Green IT and Data Center Automation Specialist > >> > >> > >> > >> > >> > >> > >> On Aug 3, 2012, at 11:19 AM, Dave Nash > wrote: > >> > >> Hello All, > >> > >> I am trying to setup foreman as a fresh install to replace cobbler in > our > >> infrastructure. The problem I am having is foreman is not seeing the > puppet > >> classes and when I attempt to import them from the Web UI I get "No > changes > >> to your environment detected". Any idea's? > >> > >> puppet version is 2.7.18-1 using storeconfig in postgresql > >> foreman version is 1.0 sharing the same DB as puppets storeconfigs > >> > >> thanks! > >> --dn > >> > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Foreman users" group. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ. > >> To post to this group, send email to foreman-users@googlegroups.com. > >> To unsubscribe from this group, send email to > >> foreman-users+unsubscribe@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/foreman-users?hl=en. > >> > >> > > -- > > You received this message because you are subscribed to the Google > Groups > > "Foreman users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/foreman-users/-/VRzzPqDKMU0J. > > > > To post to this group, send email to foreman-users@googlegroups.com. > > To unsubscribe from this group, send email to > > foreman-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/foreman-users?hl=en. >

> Hitting http://foreman:8443/puppet/environments returns
>
> ["perf","testing","dntest","development","staging"]
>
> which is correct, if I hit http://foreman:8443/puppet/environments/production I get
>
> {"name":"production","paths":["/workplace/puppet/modules/production"]}
>
> but when I go to http://foreman:8443/puppet/environments/production/classes I just get
>
> []
>

Check permissions that the smart proxy (running as foreman-proxy(?)) can view read the
class files.

··· On Aug 3, 2012, at 11:09 PM, Dave Nash wrote:

and I see E, [2012-08-03T14:01:18.307209 #1737] ERROR – : Not found in the smart proxy debug log

This is everything concerning puppet in the settings.yaml for the smart proxy

enable PuppetCA management

:puppetca: true

enable Puppet management

:puppet: true
:puppetconfdir: /etc/puppet/puppet.conf
:puppet_conf: /etc/puppet/puppet.conf
:ssldir: /var/lib/puppet/ssl
:puppetdir: /etc/puppet

I have tried a couple different ways I found through google search to make sure it sees the puppet.conf

Thanks!

–dn

On Friday, August 3, 2012 12:42:46 PM UTC-7, Brian Gupta wrote:
So the first thing I would do, is hit the proxy to make sure it is
configured properly (You have to hit it from a node that is in the ACL
in smartproxyhome/config/settings.yaml): (You can use a browser or
curl)

The following URL (basically) will give you back a big list of
classes, if the proxy is configured correctly.
http://foreman.domain.com:8443/puppet/environments/my_puppetenvironment/classes

You can also hit /puppet/environments and confirm the list of
environments is being served.

Let us know the results.

Cheers,
-Brian

On Fri, Aug 3, 2012 at 3:27 PM, Dave Nash puppet@dragonswhisper.com wrote:

No foreman is running on the same host as puppet as well as the
foreman-proxy.

Yes the module path for each environment is setup correctly in the
puppet.conf and I am using modules not just classes.

[production]
manifest = /home/puppet/master/production/site.pp
modulepath = /workplace/puppet/modules/production
[development]
manifest = /home/puppet/master/development/site.pp
modulepath = /workplace/puppet/modules/development
[testing]
manifest = /home/puppet/master/testing/site.pp
modulepath = /workplace/puppet/modules/testing
[staging]
manifest = /home/puppet/master/staging/site.pp
modulepath = /workplace/puppet/modules/staging
[perf]
manifest = /home/puppet/master/perf/site.pp
modulepath = /workplace/puppet/modules/perf

–dn

On Friday, August 3, 2012 11:43:59 AM UTC-7, Corey Osman wrote:

Are you running foreman on a different host than the puppetmaster?

Is your modulepath setup correctly in puppet? Are you using puppet
classes or modules, as foreman does not support classes by themselves unless
they are part of a module.

Thanks,

Corey Osman
corey@logicminds.biz

Green IT and Data Center Automation Specialist

On Aug 3, 2012, at 11:19 AM, Dave Nash puppet@dragonswhisper.com wrote:

Hello All,

I am trying to setup foreman as a fresh install to replace cobbler in our
infrastructure. The problem I am having is foreman is not seeing the puppet
classes and when I attempt to import them from the Web UI I get “No changes
to your environment detected”. Any idea’s?

puppet version is 2.7.18-1 using storeconfig in postgresql
foreman version is 1.0 sharing the same DB as puppets storeconfigs

thanks!
–dn


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/VRzzPqDKMU0J.

To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/9ZGat48-j_AJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

Yes it was a permissions issue /workplace/puppet was not group or world
readable. So even though I ensured /workplace/puppet/modules was I had stil
locked myself out.

Thanks for all the help!

–dn

··· On Saturday, August 4, 2012 11:08:46 AM UTC-7, Steve Traylen wrote: > > > On Aug 3, 2012, at 11:09 PM, Dave Nash wrote: > > > Hitting http://foreman:8443/puppet/environments returns > > > > ["perf","testing","dntest","development","staging"] > > > > which is correct, if I hit > http://foreman:8443/puppet/environments/production I get > > > > {"name":"production","paths":["/workplace/puppet/modules/production"]} > > > > but when I go to > http://foreman:8443/puppet/environments/production/classes I just get > > > > [] > > > > Check permissions that the smart proxy (running as foreman-proxy(?)) can > view read the > class files. > > > and I see E, [2012-08-03T14:01:18.307209 #1737] ERROR -- : Not found in > the smart proxy debug log > > > > This is everything concerning puppet in the settings.yaml for the smart > proxy > > > > # enable PuppetCA management > > :puppetca: true > > > > # enable Puppet management > > :puppet: true > > :puppetconfdir: /etc/puppet/puppet.conf > > :puppet_conf: /etc/puppet/puppet.conf > > :ssldir: /var/lib/puppet/ssl > > :puppetdir: /etc/puppet > > > > > > > > I have tried a couple different ways I found through google search to > make sure it sees the puppet.conf > > > > Thanks! > > > > --dn > > > > > > On Friday, August 3, 2012 12:42:46 PM UTC-7, Brian Gupta wrote: > > So the first thing I would do, is hit the proxy to make sure it is > > configured properly (You have to hit it from a node that is in the ACL > > in smartproxyhome/config/settings.yaml): (You can use a browser or > > curl) > > > > The following URL (basically) will give you back a big list of > > classes, if the proxy is configured correctly. > > > http://foreman.domain.com:8443/puppet/environments/my_puppetenvironment/classes > > > > You can also hit /puppet/environments and confirm the list of > > environments is being served. > > > > Let us know the results. > > > > Cheers, > > -Brian > > > > On Fri, Aug 3, 2012 at 3:27 PM, Dave Nash > wrote: > > > No foreman is running on the same host as puppet as well as the > > > foreman-proxy. > > > > > > Yes the module path for each environment is setup correctly in the > > > puppet.conf and I am using modules not just classes. > > > > > > [production] > > > manifest = /home/puppet/master/production/site.pp > > > modulepath = /workplace/puppet/modules/production > > > [development] > > > manifest = /home/puppet/master/development/site.pp > > > modulepath = /workplace/puppet/modules/development > > > [testing] > > > manifest = /home/puppet/master/testing/site.pp > > > modulepath = /workplace/puppet/modules/testing > > > [staging] > > > manifest = /home/puppet/master/staging/site.pp > > > modulepath = /workplace/puppet/modules/staging > > > [perf] > > > manifest = /home/puppet/master/perf/site.pp > > > modulepath = /workplace/puppet/modules/perf > > > > > > --dn > > > > > > On Friday, August 3, 2012 11:43:59 AM UTC-7, Corey Osman wrote: > > >> > > >> Are you running foreman on a different host than the puppetmaster? > > >> > > >> Is your modulepath setup correctly in puppet? Are you using puppet > > >> classes or modules, as foreman does not support classes by themselves > unless > > >> they are part of a module. > > >> > > >> > > >> Thanks, > > >> > > >> Corey Osman > > >> corey@logicminds.biz > > >> > > >> Green IT and Data Center Automation Specialist > > >> > > >> > > >> > > >> > > >> > > >> > > >> On Aug 3, 2012, at 11:19 AM, Dave Nash > wrote: > > >> > > >> Hello All, > > >> > > >> I am trying to setup foreman as a fresh install to replace cobbler in > our > > >> infrastructure. The problem I am having is foreman is not seeing the > puppet > > >> classes and when I attempt to import them from the Web UI I get "No > changes > > >> to your environment detected". Any idea's? > > >> > > >> puppet version is 2.7.18-1 using storeconfig in postgresql > > >> foreman version is 1.0 sharing the same DB as puppets storeconfigs > > >> > > >> thanks! > > >> --dn > > >> > > >> > > >> -- > > >> You received this message because you are subscribed to the Google > Groups > > >> "Foreman users" group. > > >> To view this discussion on the web visit > > >> https://groups.google.com/d/msg/foreman-users/-/SuhfrvoAj5AJ. > > >> To post to this group, send email to foreman-users@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> foreman-users+unsubscribe@googlegroups.com. > > >> For more options, visit this group at > > >> http://groups.google.com/group/foreman-users?hl=en. > > >> > > >> > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Foreman users" group. > > > To view this discussion on the web visit > > > https://groups.google.com/d/msg/foreman-users/-/VRzzPqDKMU0J. > > > > > > To post to this group, send email to foreman-users@googlegroups.com. > > > To unsubscribe from this group, send email to > > > foreman-users+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > > http://groups.google.com/group/foreman-users?hl=en. > > > > -- > > You received this message because you are subscribed to the Google > Groups "Foreman users" group. > > To view this discussion on the web visit > https://groups.google.com/d/msg/foreman-users/-/9ZGat48-j_AJ. > > To post to this group, send email to foreman-users@googlegroups.com. > > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en. > >