Project

General

Profile

Actions
Copy link

Bug #12233

closed

Discovery doesn't reboot due to remote execution become extenstion

Added by Ivan Necas about 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ivan Necas
Category:
-
Target version:
foreman_remote_execution 0.1.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_remote_execution/pull/59
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When using foreman remote execution (0.0.10) with discovery (4.1.0), the discovered host doesn't reboot on turning into managed,
getting:

 | NoMethodError: undefined method `drop_execution_interface_cache' for #<Host::Discovered:0x007f6e28913ac8>
 | /opt/rh/ruby193/root/usr/share/gems/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:407:in `method_missing'
 | /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/attribute_methods.rb:149:in `method_missing'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_remote_execution-0.0.10/app/models/concerns/foreman_remote_execution/host_extensions.rb:53:in `becomes_with_remote_execution'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.1/app/models/host/managed_extensions.rb:28:in `setReboot'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:162:in `execute'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:107:in `block in process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:99:in `each'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:99:in `process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:39:in `post_commit'
Actions
Copy link

Also available in: Atom PDF