Project

General

Profile

Bug #19212

Unable refresh facts on newly-registered systems within first 3-5 minutes

Added by Konstantin Orekhov over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Discovery plugin
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

As reported in https://groups.google.com/forum/#!topic/foreman-users/XzT9iEhpjRg, facts_refresh in UI on newly-discovered hosts is failing during first 3-5 minutes of discovery with this message:

Error: ERF50-7522 [Foreman::WrappedException]: Failed to refresh facts for mac38eaa7314178 with error Could not get facts from proxy https://10.98.59.254:8443: undefined local variable or method `reports' for #<Host::Discovered:0x000000072807b0> ([RuntimeError]: Could not get facts from proxy https://10.98.59.254:8443: undefined local variable or m...)

On the host side the following is logged by Foreman discovery process:

Registering host with Foreman (https://spc.vip)
Response from Foreman 422: {"message":"undefined local variable or method `reports' for #\u003cHost::Discovered:0x007ff6d7093000\u003e"}

After that initial period is over and system is successfully registered, the facts refresh work fine. It is unclear to me what prevents a system to register within those 3-5 minutes as no changes are being made and all of the sudden the registration process completes.

There are more details in https://groups.google.com/forum/#!topic/foreman-users/XzT9iEhpjRg

I also strongly believe that this issue either an result or a cause of duplicate discovered host entries (with empty values). This also described in above post.


Related issues

Related to Discovery - Bug #19231: Improve error message for refresh fact errorClosed2017-04-10

History

#3 Updated by Lukas Zapletal over 2 years ago

  • Related to Bug #19231: Improve error message for refresh fact error added

#4 Updated by Lukas Zapletal over 2 years ago

Thanks for detailed report, please apply the associated patch so we can see the actual error backtrace, must be a plugin.

#5 Updated by Lukas Zapletal over 2 years ago

  • Status changed from New to Need more information

So according to the mailing thread this is a bug in foreman_hostgroups plugin, is it?

#6 Updated by Michael Moll over 2 years ago

  • Status changed from Need more information to Rejected

no reaction, closing.

#7 Updated by Konstantin Orekhov over 2 years ago

  • Status changed from Rejected to New

Also available in: Atom PDF