Import puppet classes fails : undefined method `any?'

Which version of Ruby are you using? It looks like you're using Ruby
1.9, but support was only added in 1.1RC2 and higher. I'd suggest
updating to the final 1.1 release if possible.

http://projects.theforeman.org/wiki/foreman/ReleaseNotes#Release-notes-for-11RC2

··· -- Dominic Cleal Red Hat Engineering

On 27/02/13 11:03, Peter Van Biesen wrote:

Hi,

I’m running a setup with foreman running on a separate server than the
puppetmaster. I installed a smart proxy on the puppetmaster server and I
try to import de classes. Foreman sees all classes prefectly, but when I
click “update” I get “We’re sorry, but something went wrong.”. In the
log I see :

Started POST “/puppetclasses/obsolete_and_new” for 172.16.4.70 at
2013-02-27 09:49:32 +0000
Processing by PuppetclassesController#obsolete_and_new as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“ulNCpjxZUV5txGAg2G5Uhgn3ZKAT/JMg/xv7V6aEa+w=”,
“changed”=>{“new”=>{“production”=>"{“sysadmin::linux::migrate-puppetmaster”:{“new”:{“newmaster”:null}},“sysadmin::linux::aptsources”:{“new”:{“needProxy”:false,“allowOtherSources”:false,“repositories”:[“defaults”,“vfrepo”]}},“sysadmin::linux::basenode”:{“new”:{“enablePam”:false,“aptNeedsProxy”:false,“baculapassword”:null,“allowRootLogin”:false,“manageAptSources”:false,“installNtp”:true,“baculabackupserver”:null,“clientEnvironment”:“prod”,“repositories”:[“defaults”,“vfrepo”],“installSnowClient”:true}},“sysadmin::linux::security”:{“new”:{“enablePam”:false,“allowRootLogin”:""}},“sysadmin::linux::basepackages”:{“new”:{}},“sysadmin::linux::baculaclient”:{“new”:{“baculapassword”:null,“baculabackupserver”:null}},“sysadmin::linux::checks”:{“new”:{}},“sysadmin::linux::snow”:{“new”:{}},“sysadmin::linux::syslog-ng”:{“new”:{}},“sysadmin::linux::ntp”:{“new”:{}},“sysadmin::linux::puppetconfig”:{“ne!
w”:{“cli
entEnvironment”:“prod”}},“sysadmin::linux::ldappam”:{“new”:{}},“sysadmin::windows::basenode”:{“new”:{}},“sysadmin::windows::puppetconfig”:{“new”:{}},“registry::purge_example”:{“new”:{}},“registry::service_example”:{“new”:{}},“registry::compliance_example”:{“new”:{}},“registry”:{“new”:{}},“splunk::windows_server”:{“new”:{}},“splunk::windows_forwarder”:{“new”:{}},“splunk::linux_server”:{“new”:{}},“splunk::params”:{“new”:{“splunkd_port”:null,“admin_port”:null,“splunk_ver”:null,“splunk_admin”:null,“deploy”:null,“syslogging_port”:null,“logging_port”:null,“installerfilespath”:null,“logging_server”:null,“splunk_admin_pass”:null}},“splunk”:{“new”:{“splunkd_port”:“8089”,“admin_port”:“8000”,“splunk_ver”:“4.3.1-119532”,“splunk_admin”:“admin”,“deploy”:“server”,“syslogging_port”:“514”,“logging_port”:“8002”,“installerfilespath”:“puppet:///modules/${module_name}/”,“logging_server”:null,!
“splunk_a
dmin_pass”:“changeme”}},“splunk::linux_syslog”:{“new”:{}},“splunk::linux_forwarder”:{“new”:{}},“development::linux::vf-buildtools”:{“new”:{}},“machinetypes::linux::apacheserver”:{“new”:{}},“machinetypes::linux::sambaserver”:{“new”:{“sambaVersion”:“installed”}},“machinetypes::linux::mta”:{“new”:{“type”:“exim4”,“smarthost”:“smtp.vaph.be”}},“machinetypes::linux::theforeman”:{“new”:{“installserver”:false,“installsmartproxy”:false,“publichostname”:"${$fqdn}"}},“machinetypes::linux::jbossserver”:{“new”:{}},“machinetypes::linux::vf_splunk”:{“new”:{}},“machinetypes::linux::informixserver”:{“new”:{“version”:“installed”,“recoveryurl”:null,“config”:null,“type”:“innoc”,“usevg”:"${clientcert}-vg01"}},“machinetypes::linux::client”:{“new”:{}},“stdlib::stages”:{“new”:{}},“stdlib”:{“new”:{}},“winntp”:{“new”:{“max_pos_phase_correction”:“0xFFFFFFFF”,“max_neg_phase_correction”:“0xFFFFFFFF”,“s!
pecial_pol
l_interval”:900,“ntp_server”:“north-america.pool.ntp.org,time.windows.com”}}}"}},
“commit”=>“Update”}
Operation FAILED: undefined method `any?’ for #String:0x00000005f0eec0
Rendered common/500.rhtml within layouts/application (1.3ms)
Completed 500 Internal Server Error in 79ms

ActionView::Template::Error (undefined method each' for "backtrace":String): 8: <p> 9: If you feel this is an error with Foreman itself, please open a new issue with <%= link_to "Foreman ticketing system", "http://theforeman.org/projects/foreman/issues", :rel => "external" %>, 10: You would probably need to attach the 11: <%= link_to_function "Full trace", toggle_div("backtrace") %> and relevant log entries. 12: </p> 13: 14: <div id="backtrace" <%= display? %> class="alert alert-message alert-block alert-error base in fade"> app/helpers/application_helper.rb:43:inblock in toggle_div’
app/helpers/application_helper.rb:42:in toggle_div' app/views/common/500.rhtml:11:in_app_views_common_____rhtml___263495083987961335_46869360_1126578794824654230’
app/controllers/application_controller.rb:291:in `generic_exception’

Foreman is 1.1RC1, puppetmaster is 2.7.18, smart proxy on the
puppetmaster is 1.1+debian1, all servers are debian.

Did I do something wrong ?

Kindest regards,

Peter.

IK GA ERVOOR
Een zorgjob. Da’s werken met je hoofd, handen en hart.
http://www.ikgaervoor.be http://www.ikgaervoor.be/


DISCLAIMER :
De personeelsleden van het agentschap doen hun best om in e-mails
betrouwbare informatie te geven. Toch kan niemand rechten doen gelden op
basis van deze inhoud. Als in de e-mail een stellingname voorkomt, is
dat niet noodzakelijk het standpunt van het agentschap. Rechtsgeldige
beslissingen of officiele standpunten worden alleen per brief toegestuurd.


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Upgrade worked perfectly. Classes were imported without error.

Thanks !

Peter.

··· --

IK GA ERVOOR
Een zorgjob. Da’s werken met je hoofd, handen en hart.



DISCLAIMER :
De personeelsleden van het agentschap doen hun best om in e-mails
betrouwbare informatie te geven. Toch kan niemand rechten doen gelden op
basis van deze inhoud. Als in de e-mail een stellingname voorkomt, is
dat niet noodzakelijk het standpunt van het agentschap. Rechtsgeldige
beslissingen of officiele standpunten worden alleen per brief toegestuurd.

Good to hear! We've got Debian 7/Wheezy packaging on the todo list, but
if you would like to contribute, it might be worth talking to Greg and
looking at the misnomer that is the foreman-rpms repo.

··· -- Dominic Cleal Red Hat Engineering

On 27/02/13 13:02, Peter Van Biesen wrote:

Upgrade worked perfectly. Classes were imported without error.

Thanks !

Peter.

IK GA ERVOOR
Een zorgjob. Da’s werken met je hoofd, handen en hart.
http://www.ikgaervoor.be http://www.ikgaervoor.be/


DISCLAIMER :
De personeelsleden van het agentschap doen hun best om in e-mails
betrouwbare informatie te geven. Toch kan niemand rechten doen gelden op
basis van deze inhoud. Als in de e-mail een stellingname voorkomt, is
dat niet noodzakelijk het standpunt van het agentschap. Rechtsgeldige
beslissingen of officiele standpunten worden alleen per brief toegestuurd.


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Dominic,

anything to promote debian :wink: . Anyway, I just followed the instructions
on http://jurjenbokma.com/ApprenticesNotes/wp_foreman.html , this person
seems much more proficient in building foreman packages than I am. But I'm
certainly willing to test and supply feedback. I'm still learning how to
use foreman to its fullest, so I suspect I'll be reinstalling it a couple
of times. Atm we're maintaining 120 vms, this should become 500 in the end.
I also would like to setup a developer cluster where they can deploy and
destroy vms themselves from foreman.

Also maybe an interesting given is that we are running on xenserver.
Interfacing with that for provisioning will probably be difficult. I dont
know if this is on the wishlist. If its not to difficult, i could look at
the code. My collegues prefer to ditch xenserver and migrate to kvm/libvirt.

Anyway, one happy customer here :wink:

Peter.

Indeed, I have done cursory testing of our packages on Wheezy and they seem
fine, although they pull in some probably unrequired deps (harmless but
irritating).

It's not looking like I'm going to get to test it thoroughly any time soon

  • perhaps I should create the wheezy repo and see what problems people send
    us :slight_smile:

Greg

··· On 27 February 2013 13:13, Dominic Cleal wrote:

Good to hear! We’ve got Debian 7/Wheezy packaging on the todo list, but
if you would like to contribute, it might be worth talking to Greg and
looking at the misnomer that is the foreman-rpms repo.