Yes, I know. At first I didn't anticipate that it was a foreman issue. To be honest I've found foremans usefulness marginal at best and its performance hit on the Puppet master server quite significant, so I'm not inclined to pursue it further.
On Wednesday, 16 October 2013 17:26:33 UTC+8, Andreas Ntaflos wrote: > > On 2013-10-16 10:07, Steve Wray wrote: > > It turned out that there was an update to the foreman package which > > completely broke Puppets ability to enroll new nodes. > > > > Call me old fashioned, I've been a Debian sysadmin for over 10 years, > > but on a 'stable' system an apt-get upgrade is not supposed to break > > things. Thats one of the things Debian is famous for. Just so happens my > > server is running Ubuntu server 'long term support' version and I > > expected something similar there. > > > > I've spent some time now ripping Foreman out. Its too unreliable and I > > don't think the benefits outweigh the costs. Puppet *without* foreman is > > just fine. > > > > Bye bye, foreman, I'll hardly miss you. > > You are complaining on the wrong mailing list. If you have feedback for > the Foreman developers please head over to > https://groups.google.com/forum/#!forum/foreman-users and bring the > topic up there. > > Andreas > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
