Build PXE default fails with RC1.1

Development
1

Hi!

would really appreciate if somebody could tell
me whether there's any chance that the following
error message that Foreman UI throws at me
could be a pilot error of some kind:

··· ========================================= failed to process template: exp not empty after Safemode::Parser.process_call on s(s(:call, s(:lvar, :profile), :[], s(:lit, :hostgroup))) =========================================

I’m essentially following this tutorial:
http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html
and have a fresh Foreman RC1.1 installation
on Ubuntu Lucid/Postgres

If this does look like a bug I’d appreciate any
advice on how to figure out what exactly is
failing (sorry – new to Foreman – just learning
my way around it).

Thanks,
Roman.

2

This is due to safemode and ruby_parser gem versions. Try updating the
gems to safemode 1.1.0 and ruby_parser 3.0.4. We've updated them in the
upcoming 1.1 RC2 release.

http://theforeman.org/issues/2029

··· On 19/12/12 02:42, Roman Shaposhnik wrote: > Hi! > > would really appreciate if somebody could tell > me whether there's any chance that the following > error message that Foreman UI throws at me > could be a pilot error of some kind: > ========================================= > failed to process template: exp not empty after > Safemode::Parser.process_call on s(s(:call, s(:lvar, :profile), :[], > s(:lit, :hostgroup))) > ========================================= > > I'm essentially following this tutorial: > http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html > and have a fresh Foreman RC1.1 installation > on Ubuntu Lucid/Postgres

–
Dominic Cleal
Red Hat Engineering

3

Thats a known safemode issue. For now, try disabling Safemode
Rendering in the Settings page.

··· On 19 December 2012 02:42, Roman Shaposhnik wrote: > Hi! > > would really appreciate if somebody could tell > me whether there's any chance that the following > error message that Foreman UI throws at me > could be a pilot error of some kind: > ========================================= > failed to process template: exp not empty after > Safemode::Parser.process_call on s(s(:call, s(:lvar, :profile), :[], > s(:lit, :hostgroup))) > =========================================
4

I removed the non-maintained gem "has_many_polymorphs". It appears that Rails supports this functionality out of the box by defining relationships using :source and :source_type.

I read that this functionality was fixed in Rails 3.1.2, but I assume somebody backported it to 3.0.17, since it appears to work. (however, I didn't find it in the release notes). All the tests pass, but I don't know how comprehensive the testing suite is in the area of usergroups, users, permissions roles, etc.

Can you provide feedback where this change might break the behavior of current installations. Hopefully, it wont.

usergroup.rb

  • has_many_polymorphs :members, :from => [:usergroups, :users ], :as => :member,
  • :through => :usergroup_member, :foreign_key => :usergroup_id, :dependent => :destroy
  • has_many :usergroup_members
  • has_many :users, :through => :usergroup_members, :source => :member, :source_type => 'User'
  • has_many :usergroups, :through => :usergroup_members, :source => :member, :source_type => 'Usergroup'
··· ----- Original Message ----- From: "Greg Sutcliffe" To: "Foreman ." Sent: Thursday, December 20, 2012 7:58:49 PM Subject: Re: [foreman-dev] Build PXE default fails with RC1.1

On 19 December 2012 02:42, Roman Shaposhnik shaposhnik@gmail.com wrote:

Hi!

would really appreciate if somebody could tell
me whether there’s any chance that the following
error message that Foreman UI throws at me
could be a pilot error of some kind:

failed to process template: exp not empty after
Safemode::Parser.process_call on s(s(:call, s(:lvar, :profile), :[],
s(:lit, :hostgroup)))

Thats a known safemode issue. For now, try disabling Safemode
Rendering in the Settings page.