Bug #8550
closedClicking Edit in foreman gives Error
Description
When creating a VM using foreman-xen it does create and everything, it builds, but in foreman it creates the following error:
http://cl.ly/image/2o2X0f03081C
Oops, we're sorry but something went wrong
×
Warning!
can't convert String into Integer
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.
TypeError
can't convert String into Integer
app/helpers/lookup_keys_helper.rb:24:in `block (2 levels) in new_child_fields_template'
app/helpers/lookup_keys_helper.rb:21:in `block in new_child_fields_template'
app/helpers/lookup_keys_helper.rb:20:in `new_child_fields_template'
app/views/hosts/_compute.html.erb:5:in `block in app_views_hosts_compute_html_erb___1621309881049581071_70305102757920'
app/views/hosts/_compute.html.erb:1:in `_app_views_hosts__compute_html_erb___1621309881049581071_70305102757920'
app/views/hosts/_unattended.html.erb:2:in `_app_views_hosts__unattended_html_erb___2283017419730762182_70305100151700'
app/views/hosts/_form.html.erb:94:in `block (2 levels) in app_views_hosts_form_html_erb___103949955404226462_95214380'
app/helpers/layout_helper.rb:268:in `form_for'
app/views/hosts/_form.html.erb:8:in `block in app_views_hosts_form_html_erb___103949955404226462_95214380'
app/models/taxonomy.rb:59:in `block (2 levels) in as_taxonomy'
app/models/concerns/foreman/thread_session.rb:148:in `as_location'
app/models/taxonomy.rb:58:in `block in as_taxonomy'
app/models/concerns/foreman/thread_session.rb:113:in `as_org'
app/models/taxonomy.rb:57:in `as_taxonomy'
app/views/hosts/_form.html.erb:6:in `_app_views_hosts__form_html_erb___103949955404226462_95214380'
app/views/hosts/edit.html.erb:9:in `_app_views_hosts_edit_html_erb__523214185574830038_94565300'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'
Back
Files
Updated by Joe Ortiz about 10 years ago
Forgot to mention I am using :
ruby193-rubygem-foreman_xen-0.0.4.1-1.el6.noarch
And foreman 1.7.0 , I did try it on 1.6.x why I upgraded to 1.7.x if it would fix it, I was using 0.0.3 of foreman-xen before and this error didn't happen, but after upgrading to 0.0.4 is when the error occurred.
Updated by Tom Caspy about 10 years ago
We need some more info, as the stack trace may have hidden the faulty line in the foreman_xen gem.
Can you run this with foreman-debug and send us the full trace (including gems, etc) and the relevant logs?
Another thing which will be very helpful is the contents of the options variable, if possible, can you edit the foreman gem and add the following:
in app/helpers/lookup_keys_helper.rb:19 add this line:
logger.error(options.inspect)
Thank you!
Updated by Boris Kreitchman about 10 years ago
- File foreman-debug.trace foreman-debug.trace added
I'm having the same issue.
Foreman 1.7.1 on CentOS 7, ruby193-rubygem-foreman_xen-0.0.4.1-1.el7.noarch
I've added logger.error(options.inspect) line and attaching log with debug (domain, IP and password are replaced).
Let me if more details are needed.
Thx.
Updated by Boris Kreitchman about 10 years ago
Actually it's already fixed in development branch of foreman_xen on github.
Updated by Dominic Cleal about 10 years ago
- Status changed from New to Closed
I think the 0.0.5.1 release has this fix. Please re-open if not!