Bug #2301

Nodes with puppet running are not always listed in REST responses

Added by Romain Vrignaud over 7 years ago. Updated about 7 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


I'm using a lot the puppet function to query foreman from puppet (
in my manifest.
I noticed that when nodes where running puppet they might not be listed when querying Foreman in the REST API.

ie: If I have 2 nodes in hostgroup webservers and I query all hosts in that hostgroup
and I run puppet in the 2 nodes at the same time, foreman may list only one node instead of 2 in the answer.

I reproduced that with debug using http client when puppet was running on my nodes :
  • you can see that the 3 queries are only 1 second spaced
  • obvioulsy shinken51 was not deleted during the process
  • during the second request foreman replied only 2 facts instead of 3

I'm running foreman 1.1 with passenger + mysql
Puppet is puppet 3.0 (behavior was the same with puppet2.7)
Using puppetdb

This is quite painfull for us as a big part of our manifest is
writted to rely on Foreman and to reload dynamically the daemons.

Related issues

Related to Foreman - Bug #2486: Fact values importer recreating all values in the databaseClosed2013-05-10


#1 Updated by Romain Vrignaud over 7 years ago

  • Target version set to 1.2.0

#2 Updated by Dominic Cleal over 7 years ago

  • Status changed from New to Feedback

I think this might be #2486, but I'm not certain - I found that problem in the process of investigating this one. The issue there was all facts relating to a host were deleted and then recreated when they were uploaded, rather than just updating the ones that changed.

Do you have a more complete log file? I'm particularly interested if you get /fact_values/create requests at the same time as your queries.

#3 Updated by Dominic Cleal over 7 years ago

(alternatively, if you can test the patch in #2486 that would be fantastic.. I think it'll apply against 1.1)

#4 Updated by Ohad Levy over 7 years ago


#5 Updated by Joseph Magen over 7 years ago

  • Assignee set to Joseph Magen

#6 Updated by Ohad Levy over 7 years ago

Joseph, I'm not sure if there is anything to do here besides asking Romain to retry, I believe we solved this issue.

#7 Updated by Romain Vrignaud about 7 years ago

  • Status changed from Feedback to Resolved

Can't reproduce since migration to 1.2-RC3.
Seems to be fixed by #2486.
Closing it

Also available in: Atom PDF