Bug #9082
closed
Auto search throwing "ActionController::RoutingError" on editing discovery rule
Description
Steps to reproduce:
1. create a discovery rule
2. edit the rule
3. go to search bar and edit the fact like ip = ' '
logs from production.log: =========================
ActionController::RoutingError (No route matches [GET] "/discovery_rules/2-test/discovered_hosts/auto_complete_search"):
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'
ActionController::RoutingError (No route matches [GET] "/discovery_rules/2-test/discovered_hosts/auto_complete_search"):
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'
Files
Updated by Sachin Ghai over 9 years ago
Missed to mention the version: here is the version of rpm's against which this issue is reproducible:
rubygem-smart_proxy_discovery-1.0.1-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc1.el6.noarch
foreman-release-1.8.0-0.develop.201501211657git1cf860b.el6.noarch
Updated by Ori Rabin over 9 years ago
- Related to Bug #9021: Discovery rules is missing scoped search added
Updated by Lukas Zapletal over 9 years ago
Is the bug only related, or does it really fix this particular issue? If it does, let's close it as duplicate.
Also wondering if this patch does fix this or not: https://github.com/theforeman/foreman/pull/2105
Updated by Ori Rabin over 9 years ago
- Status changed from New to Assigned
- Assignee changed from Lukas Zapletal to Ori Rabin
Updated by The Foreman Bot over 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman_discovery/pull/140 added
- Pull request deleted (
)
Updated by Ori Rabin over 9 years ago
- Status changed from Ready For Testing to Resolved
I saw this happening too but it is no longer reproducible.
If you succeed in reproducing with RC2 please reopen.