>
> Hello,
>
> I have today noticed that foreman_discovery is no longer working on our
foreman instance. When I go into 'hosts' -> 'discovered hosts' I see
nothing.
>
> I see the following error in /var/log/foreman/production.log when a host
tries to notify foreman after booting the discovery image.
>
> Started POST "/discovers" for 10.80.11.12 at 2014-06-25 17:24:16 +0200
> ActionController::RoutingError (No route matches [POST] "/discovers"):
>
> We are running foreman 1.5.1 on rhel6. We use the rpm for
foreman_discovery (version 1.3.0)
>
> I have tried reinstalling the rpm for foreman_discovery. Is there
anything else I should check?
Which discovery image are you using? Try fetching a more recent one.
Ohad
>
> Cheers,
>
> Ben
>
> –
> You received this message because you are subscribed to the Google Groups
"Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
···
On Jun 25, 2014 6:35 PM, "bmorrice" wrote:
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
I'm still getting the same errors in production.log
Anything else I should try?
Cheers,
Ben
···
On Thursday, 26 June 2014 07:57:01 UTC+2, ohad wrote:
>
>
> On Jun 25, 2014 6:35 PM, "bmorrice" <ben.m...@gmail.com > > wrote:
> >
> > Hello,
> >
> > I have today noticed that foreman_discovery is no longer working on our
> foreman instance. When I go into 'hosts' -> 'discovered hosts' I see
> nothing.
> >
> > I see the following error in /var/log/foreman/production.log when a host
> tries to notify foreman after booting the discovery image.
> >
> > Started POST "/discovers" for 10.80.11.12 at 2014-06-25 17:24:16 +0200
> > ActionController::RoutingError (No route matches [POST] "/discovers"):
> >
> > We are running foreman 1.5.1 on rhel6. We use the rpm for
> foreman_discovery (version 1.3.0)
> >
> > I have tried reinstalling the rpm for foreman_discovery. Is there
> anything else I should check?
>
> Which discovery image are you using? Try fetching a more recent one.
>
> Ohad
> >
> > Cheers,
> >
> > Ben
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
this build does contain new route (c4c33e4efa353059f3d084) so you should
not get those errors. Can you re-test?
The build does contain a "fallback" mechanism and if anything fails
during discovery via V2 API, it tries to discover via the old method,
therefore you can encounter similar errors in the log. But you should
see requests on the new API first (and root cause of the issue for you
there).
Thanks for the pointer. I've worked it out. The issue was that in our
foreman->settings->discovery the discovery_fact was referencing a fact that
didn't exist in the discovery image.
I have since fixed this and provisioning again through foreman.
Cheers.
Ben
···
On Thursday, 26 June 2014 14:30:02 UTC+2, Lukas Zapletal wrote:
>
> Hello,
>
> > have updated to the latest centos based one
> > from
> http://downloads.theforeman.org/discovery/releases/latest/foreman-discovery-image-3.0.5-20140523.0.el6.iso-img
>
> this build does contain new route (c4c33e4efa353059f3d084) so you should
> not get those errors. Can you re-test?
>
> The build does contain a "fallback" mechanism and if anything fails
> during discovery via V2 API, it tries to discover via the old method,
> therefore you *can* encounter similar errors in the log. But you should
> see requests on the new API first (and root cause of the issue for you
> there).
>
> --
> Later,
>
> Lukas "lzap" Zapletal
> irc: lzap #theforeman
>
It results in the similar 404 error, we will fix that.
LZ
···
On Fri, Jun 27, 2014 at 01:43:51AM -0700, bmorrice wrote:
> Hi Lukas,
>
> Thanks for the pointer. I've worked it out. The issue was that in our
> foreman->settings->discovery the discovery_fact was referencing a fact that
> didn't exist in the discovery image.
>
> I have since fixed this and provisioning again through foreman.
>
> Cheers.
>
> Ben
>
> On Thursday, 26 June 2014 14:30:02 UTC+2, Lukas Zapletal wrote:
> >
> > Hello,
> >
> > > have updated to the latest centos based one
> > > from
> > http://downloads.theforeman.org/discovery/releases/latest/foreman-discovery-image-3.0.5-20140523.0.el6.iso-img
> >
> > this build does contain new route (c4c33e4efa353059f3d084) so you should
> > not get those errors. Can you re-test?
> >
> > The build does contain a "fallback" mechanism and if anything fails
> > during discovery via V2 API, it tries to discover via the old method,
> > therefore you *can* encounter similar errors in the log. But you should
> > see requests on the new API first (and root cause of the issue for you
> > there).
> >
> > --
> > Later,
> >
> > Lukas "lzap" Zapletal
> > irc: lzap #theforeman
> >
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
