Bug #12352
closed
When Deleting Host managed by Chef, error occurs deleting dns record?
Description
Error spit out:
Warning!
uninitialized constant Actions::Foreman::Logging
Full stack trace:
When trying to delete a libvirt guest, and having the foreman chef plugin 0.2.0 installed, from the hosts menu (Select the host and pull down and select "delete" on the right) foreman generates this error.
If you go under Compute resources and select the libvirt provider and loook there, it DOES show the host as deleted. But it does not show the host as deleted in the overall host view.
Also noticed this in the foreman-proxy log:
root@f-guest0-01-us1:/var/log/foreman-proxy# tail n 50 proxy.log | more : Couldn't enable plugin dns: Unable to find dependency 'nsupdate' of 'dns'.
E, [2015-10-29T06:50:58.959852 #26501] ERROR -
E, [2015-10-29T17:10:51.007929 #26509] ERROR -- : Omshell failed:
obj: <null>
, > obj: host
, > obj: host
, hardware-address = xx:xx:xx:xx:xx
, > can't open object: not found
, obj: host
, hardware-address = xx:xx:xx:xx:xx
, > can't destroy object: not found
, obj: host
, hardware-address = xx:xx:xx:xx:xx
, >
E, [2015-10-29T17:10:51.008312 #26509] ERROR -- : Failed to remove DHCP reservation for guest0-02-us1.example.com => guest0-02-us1.
.examplecom (172.xx.xx.x / xx:xx:xx:xx:xx)
E, [2015-10-29T17:11:56.002836 #26509] ERROR -- : Record 172.xx.xx.xx.x/xx:xx:xx:xx:xx not found
E, [2015-10-29T17:13:37.577725 #1384] ERROR -- : Couldn't enable plugin dns: Unable to find dependency 'nsupdate' of 'dns'.
E, [2015-10-29T17:14:39.243564 #1389] ERROR -- : Record 172.x.x.x.x/xx:xx:xx:xx:xx not found
E, [2015-10-29T17:18:18.596207 #9373] ERROR -- : Couldn't enable plugin dns: Unable to find dependency 'nsupdate' of 'dns'.
E, [2015-10-29T17:20:21.341051 #9378] ERROR -- : Record 172.x.x.x/xx:xx:xx:xx:xx not found
E, [2015-10-29T17:31:28.741162 #9378] ERROR -- : Record 172.x.x.x/xx:xx:xx:xx:xx not found
E, [2015-10-29T17:34:38.422172 #1391] ERROR -- : Couldn't enable plugin dns: Unable to find dependency 'nsupdate' of 'dns'.
If there's a workaround or a hack to get around this, or if you need more info, please ping me.
jlp
Updated by Marek Hulán almost 9 years ago
- Status changed from New to Assigned
- Assignee set to Marek Hulán
- Translation missing: en.field_release set to 73
I found this yesterday, it's an error which hides another error. It's very likely that you have another deletion task in progress that block a new deletion. Try restarting foreman-tasks service to finish pending tasks. I'll fix it so you see proper error message in 0.2.1.
Updated by Marek Hulán almost 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman_chef/pull/33 added
- Pull request deleted (
)
Updated by Marek Hulán almost 9 years ago
- Translation missing: en.field_release changed from 73 to 105
Updated by J LP almost 9 years ago
Marek Hulán wrote:
I found this yesterday, it's an error which hides another error. It's very likely that you have another deletion task in progress that block a new deletion. Try restarting foreman-tasks service to finish pending tasks. I'll fix it so you see proper error message in 0.2.1.
When restarting /usr/bin/foreman-tasks I get the following:
root@f-guest0-01-us1:~# foreman-tasks
Performance on MRI may be improved with the concurrent-ruby-ext gem. Please see http://concurrent-ruby.com
/usr/share/foreman/lib/foreman/logging.rb:75:in `load_config': Logging configuration 'config/logging.yaml' not present (RuntimeError)
from /usr/share/foreman/lib/foreman/logging.rb:17:in `configure'
from /usr/share/foreman/config/application.rb:166:in `<class:Application>'
from /usr/share/foreman/config/application.rb:86:in `<module:Foreman>'
from /usr/share/foreman/config/application.rb:85:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/foreman-tasks:4:in `<main>'
Please advise?
Updated by J LP almost 9 years ago
Marek Hulán wrote:
try
[...]
Does not seem to make a difference.
Oh and under ubuntu it's service ruby-foreman-tasks restart :-)
Updated by Carlos Maldonado over 8 years ago
Marek Hulán wrote:
I found this yesterday, it's an error which hides another error. It's very likely that you have another deletion task in progress that block a new deletion. Try restarting foreman-tasks service to finish pending tasks. I'll fix it so you see proper error message in 0.2.1.
Hello Marek, same situation on this side.
I tried the "pull request" suggested and I am not seeing any more information
here's my stack trace http://pastebin.com/LTmYMXVi
note that the paths indicate version foreman_chef-0.2.0 but I manually implemented the modification at
https://github.com/theforeman/foreman_chef/pull/33/files#r45294326
I also tried what is suggested by https://github.com/ehelms there as note of
https://github.com/theforeman/foreman_chef/pull/33/files#r45294326
but I don't get anything different
Hints?
Thanks in advance
KM
Updated by Marek Hulán over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
I'm closing this as the logging issue should be fixed now. I was unable to reproduce with the fix. Carlos, did you restart the foreman (httpd) after you applied the foreman_chef fix?