Hey there,
I've noticed that every time I add a new puppet class and import it
via the foreman interface I see a large number of classes that are
listed as "to be removed". These classes still exist on the host and
should be in the production environment. Has anyone else seen this
before?
Yep, we discovered this problem or something very much like it, last week;
for us it was classes in an environment other than 'production' that were
to be removed.
The fix for us to the problem is as per the last entry of:
http://theforeman.org/projects/foreman/wiki/Troubleshooting
specifically:
add ":puppetconfdir: /etc/puppet/puppet.conf" in your settings.yaml.
This refers to Bug #1159: Class import behaviour not consistent "rake puppet:import:puppet_classes" x "UI" - Foreman
Researching the issue indicated to us that we had dashes in class names
(that was compounding the problem) and we applied the patch in ticket 1309
to address that:
http://theforeman.org/issues/1309
Once we'd made these changes to our configuration, importing classes
through foreman operated correctly.
Hope this helps,
Iain
···
On 24 December 2011 02:48, Luke Baker wrote:
Hey there,
I’ve noticed that every time I add a new puppet class and import it
via the foreman interface I see a large number of classes that are
listed as “to be removed”. These classes still exist on the host and
should be in the production environment. Has anyone else seen this
before?
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
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.
Thanks for the response – I'll give this a shot next week and let you
know how it goes!
···
On Dec 23, 10:30 pm, Iain Sutton wrote:
> Yep, we discovered this problem or something very much like it, last week;
> for us it was classes in an environment other than 'production' that were
> to be removed.
>
> The fix for us to the problem is as per the last entry of:
>
> http://theforeman.org/projects/foreman/wiki/Troubleshooting
>
> specifically:
>
> add ":puppetconfdir: /etc/puppet/puppet.conf" in your settings.yaml.
>
> This refers tohttp://theforeman.org/issues/1159
>
> Researching the issue indicated to us that we had dashes in class names
> (that was compounding the problem) and we applied the patch in ticket 1309
> to address that:
>
> http://theforeman.org/issues/1309
>
> Once we'd made these changes to our configuration, importing classes
> through foreman operated correctly.
>
> Hope this helps,
>
> Iain
>
> On 24 December 2011 02:48, Luke Baker wrote:
>
>
>
>
>
>
>
> > Hey there,
>
> > I've noticed that every time I add a new puppet class and import it
> > via the foreman interface I see a large number of classes that are
> > listed as "to be removed". These classes still exist on the host and
> > should be in the production environment. Has anyone else seen this
> > before?
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Foreman users" group.
> > 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.
Yep that worked, thanks again.
···
On Dec 30 2011, 9:44 pm, Luke Baker wrote:
> Thanks for the response -- I'll give this a shot next week and let you
> know how it goes!
>
> On Dec 23, 10:30 pm, Iain Sutton wrote:
>
>
>
>
>
>
>
> > Yep, we discovered this problem or something very much like it, last week;
> > for us it was classes in an environment other than 'production' that were
> > to be removed.
>
> > The fix for us to the problem is as per the last entry of:
>
> >http://theforeman.org/projects/foreman/wiki/Troubleshooting
>
> > specifically:
>
> > add ":puppetconfdir: /etc/puppet/puppet.conf" in your settings.yaml.
>
> > This refers tohttp://theforeman.org/issues/1159
>
> > Researching the issue indicated to us that we had dashes in class names
> > (that was compounding the problem) and we applied the patch in ticket 1309
> > to address that:
>
> >http://theforeman.org/issues/1309
>
> > Once we'd made these changes to our configuration, importing classes
> > through foreman operated correctly.
>
> > Hope this helps,
>
> > Iain
>
> > On 24 December 2011 02:48, Luke Baker wrote:
>
> > > Hey there,
>
> > > I've noticed that every time I add a new puppet class and import it
> > > via the foreman interface I see a large number of classes that are
> > > listed as "to be removed". These classes still exist on the host and
> > > should be in the production environment. Has anyone else seen this
> > > before?
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Foreman users" group.
> > > 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.
