> > We're seeing that PUT api/v2/discovered_hosts/:id/refresh_facts is causing > a new discovered_host. Have you seen this before?
Hmm, that looks like a bug. Is it possible that IP address or MAC address of the host changed? > Also, I don't see GET /features in the routes file for foreman_discovery. > This is a route for the smart_proxy, right? Am I missing something? This is a call you do against the discovered node itself. > > Any other "ping status" API call? > > > > Nope, all other ports except 8443 and 8448 (http) are firewalled. I think there's a misunderstanding. I was under impression you want to determine if the node is running or not. That's the way how you do this (directly), we currently do not have any API call that checks that. You can always use refresh_facts in order to check that, it will give you an error when the node is not running, but there's no separate API call as a "health-check". -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
