Foreman 5 - Not seeing puppet environments

Support
1

I just migrated my Puppetmaster/Foreman to a new server and made the jump
to Foreman 5.

New server :
foreman - git @ commit from May 14, ba71c565baefbb183367e79dc1138c8258b457cb
CentOS 6.2
Mysql2 adapter

Everything is working great except when I go to import new classes, Foreman
instead wants to remove all my environments.

Here's the relevant sections in puppet.conf

[master]
certname = <omit>
report = true
reports = foreman, xmpp
pluginsync = true

environment = production

…

[production]
manifest = /etc/puppet/manifests/site.pp
modulepath =
/etc/puppet/environments/production/modules:/etc/puppet/modules
[hpc_dev]
manifest = /etc/puppet/manifests/site.pp
modulepath = /etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules
[testing]
manifest = /etc/puppet/manifests/site.pp
modulepath = /etc/puppet/environments/testing/modules

This was the same config used with Foreman 4 that worked just fine. As per
the troubleshooting instructions I have ":puppetconfdir:
/etc/puppet/puppet.conf" defined in settings.yaml just like I did in 4 but
still same result.

As a attempted fix I added the local foreman-proxy that's on same host as
Foreman and Puppetmaster to Foreman, still same result.

In Rails console I get this using Foreman 5

> Environment.puppetEnvs
=> {}

Foreman 4…
>> Environment.puppetEnvs
=>
{:hpc_dev=>"/etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules",
:staging=>"/etc/puppet/environments/staging/modules",
:production=>"/etc/puppet/environments/production/modules:/etc/puppet/modules"}

The two installs are identical (db dump) and Puppet config is identical
except I renamed staging to testing.

Any ideas or troubleshooting steps to try ?

Thanks

  • Trey
2

> I just migrated my Puppetmaster/Foreman to a new server and made the jump
> to Foreman 5.
>
> New server :
> foreman - git @ commit from May
> 14, ba71c565baefbb183367e79dc1138c8258b457cb
> CentOS 6.2
> Mysql2 adapter
>
> Everything is working great except when I go to import new classes,
> Foreman instead wants to remove all my environments.
>

I guess you are hitting http://theforeman.org/issues/1587, which is really
easy to fix, see
https://github.com/theforeman/smart-proxy/commit/083405c80fe0b872b1e159abb9c2f098d3716d09

Ohad

··· On Mon, May 21, 2012 at 9:16 PM, treydock wrote:

Here’s the relevant sections in puppet.conf

[master]
certname =
report = true
reports = foreman, xmpp
pluginsync = true

environment = production

…

[production]
manifest = /etc/puppet/manifests/site.pp
modulepath =
/etc/puppet/environments/production/modules:/etc/puppet/modules
[hpc_dev]
manifest = /etc/puppet/manifests/site.pp
modulepath =
/etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules
[testing]
manifest = /etc/puppet/manifests/site.pp
modulepath = /etc/puppet/environments/testing/modules

This was the same config used with Foreman 4 that worked just fine. As
per the troubleshooting instructions I have “:puppetconfdir:
/etc/puppet/puppet.conf” defined in settings.yaml just like I did in 4 but
still same result.

As a attempted fix I added the local foreman-proxy that’s on same host as
Foreman and Puppetmaster to Foreman, still same result.

In Rails console I get this using Foreman 5

Environment.puppetEnvs
=> {}

Foreman 4…

Environment.puppetEnvs
=>
{:hpc_dev=>"/etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules",
:staging=>"/etc/puppet/environments/staging/modules",
:production=>"/etc/puppet/environments/production/modules:/etc/puppet/modules"}

The two installs are identical (db dump) and Puppet config is identical
except I renamed staging to testing.

Any ideas or troubleshooting steps to try ?

Thanks

  • Trey

–
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/-/WWFArFCyH2QJ.
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.

3

That did the trick, thanks!

··· On Monday, May 21, 2012 1:40:36 PM UTC-5, ohad wrote: > > > > On Mon, May 21, 2012 at 9:16 PM, treydock wrote: > >> I just migrated my Puppetmaster/Foreman to a new server and made the jump >> to Foreman 5. >> >> New server : >> foreman - git @ commit from May >> 14, ba71c565baefbb183367e79dc1138c8258b457cb >> CentOS 6.2 >> Mysql2 adapter >> >> Everything is working great except when I go to import new classes, >> Foreman instead wants to remove all my environments. >> > > I guess you are hitting http://theforeman.org/issues/1587, which is > really easy to fix, see > https://github.com/theforeman/smart-proxy/commit/083405c80fe0b872b1e159abb9c2f098d3716d09 > > Ohad > >> >> Here's the relevant sections in puppet.conf >> >> [master] >> certname = >> report = true >> reports = foreman, xmpp >> pluginsync = true >> >> environment = production >> >> .... >> >> [production] >> manifest = /etc/puppet/manifests/site.pp >> modulepath = >> /etc/puppet/environments/production/modules:/etc/puppet/modules >> [hpc_dev] >> manifest = /etc/puppet/manifests/site.pp >> modulepath = >> /etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules >> [testing] >> manifest = /etc/puppet/manifests/site.pp >> modulepath = /etc/puppet/environments/testing/modules >> >> This was the same config used with Foreman 4 that worked just fine. As >> per the troubleshooting instructions I have ":puppetconfdir: >> /etc/puppet/puppet.conf" defined in settings.yaml just like I did in 4 but >> still same result. >> >> As a attempted fix I added the local foreman-proxy that's on same host as >> Foreman and Puppetmaster to Foreman, still same result. >> >> In Rails console I get this using Foreman 5 >> >> > Environment.puppetEnvs >> => {} >> >> >> Foreman 4... >> >> Environment.puppetEnvs >> => >> {:hpc_dev=>"/etc/puppet/environments/hpc_dev/modules:/etc/puppet/modules", >> :staging=>"/etc/puppet/environments/staging/modules", >> :production=>"/etc/puppet/environments/production/modules:/etc/puppet/modules"} >> >> >> The two installs are identical (db dump) and Puppet config is identical >> except I renamed staging to testing. >> >> Any ideas or troubleshooting steps to try ? >> >> Thanks >> - Trey >> >> -- >> 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/-/WWFArFCyH2QJ. >> 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. >> > >