Actions
Bug #16838
closed
undefined method `host_expiry_warning_message'
Status:
Resolved
Priority:
Normal
Assignee:
-
Description
Hello,
I updated foreman from version 1.12.3 to 1.13.0. I got below error when I hit the host for details. I got following error "Oops, we're sorry but something went wrong undefined method `host_expiry_warning_message' for #<#<Class:0x0000000e3094f0>:0x007f7a23877db0>"I attached the screenshot. Please help me.
Thanks
Laxman
Files
| foreman_error.PNG | View foreman_error.PNG | 28.1 KB | |||
| foreman error.png | View foreman error.png | 12.5 KB | |||
| foreman_error1.PNG | View foreman_error1.PNG | 94.3 KB |
Updated by Ohad Levy about 8 years ago
this seems to be related to the host expiry plugin? if you remove it does it still occurs ?
Updated by Dominic Cleal about 8 years ago
- Project changed from Smart Proxy to Plugins
- Subject changed from Foreman 1.13.0 to undefined method `host_expiry_warning_message'
- Status changed from New to Feedback
Please see https://github.com/theforeman/foreman_expire_hosts/issues/3 in the expire_hosts plugin bug tracker.
Updated by Tauseef Khan about 8 years ago
Ohad Levy wrote:
this seems to be related to the host expiry plugin? if you remove it does it still occurs ?
No, I have disabled that plugin too but still getting the same error
Updated by Dominic Cleal about 8 years ago
It looks likely that the plugin is still loaded, restart apache2/httpd or Foreman with touch ~foreman/tmp/restart.txt
Updated by laxman veeturi about 8 years ago
- File foreman_error1.PNG foreman_error1.PNG added
I removed tfm-rubygem-foreman_expire_hosts. I could see host properties now.
Updated by Anonymous
Actions