Rudder

The trivial tries to reproduced that problem didn't work.

Could you edit /opt/rudder/etc/logback.xml and set to debug the line about "LDAP query processor", so that we have a precise feedback about what is going wrong here. The line is:

     <!-- Uncomment and set to "debug" to have precise log about LDAP queries done by the node search engine -->
     <logger name="com.normation.rudder.services.queries" level="debug" /> 

Rudder need to be restarted for that change to be taken into account, safe if the root element of logback.xml contains the "scan=true" attribute like in: <configuration scan="true" scanPeriod="5 seconds">

Then, could you post logs from the webapp (/var/log/rudder/webapp/xxxx.log).

If the query logic does not rise suspicious results, the next ideas are some problem with the LDAP, so sending us LDAP log in /var/log/rudder/.

Some interactive debug show that the problem also happen with direct query on hostname, and in that case, the LDAP seems to return adequate result:

[2015-05-21 14:47:54] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [0] Start search for { returnType:'NodeReturnType' with 'And' criteria [node.nodeHostname eq XXXXXX] }
[2015-05-21 14:47:54] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [0] |- (final query) LDAPObjectType(ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration,One,LDAPObjectTypeFilter((objectClass=*)),Some(nodeHostname=XXXXXX),DNJoin,Set())
[2015-05-21 14:47:54] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [0] |--- SearchRequest(baseDN='ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration', scope=ONE, deref=NEVER, sizeLimit=0, timeLimit=0, filter='(&(objectClass=*)(nodeHostname=XXXXXX))', attrs={policyServerId, osFullName, localAdministratorAccountName, container, cn, osServicePack, createTimestamp, agentName, osName, ipHostNumber, publicKey, osVersion, nodeId, nodeHostname, objectClass})
[2015-05-21 14:47:54] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [0] |---- 1 result(s)
[2015-05-21 14:47:54] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [0] `-> 1 results

So something remove the node from the list of nodes of the search between the ldap query result and the query displaying.
We do post-filter the ldap query results for node not in the "ou=Nodes,cn=rudder-configuration" branch, or policy servers. The debug display that.

The node may also be missing if some error happened in the transformation between back-end data and displaying one, but these error are logged on the logs, to.

Next idea: could you please try to search on:

- the UUID of the node ? Is it found with that in place of the hostname ? (here, I want to know if the problem is hostname or something with the node)
- the OS=linux (most generic query with the node) ? Is it in the list of nodes ? (here, I want to test if the problem is with queries on attribute specific to the node or with something else).

- quick search on the node hostname ? Is this ok and the node details are seen ?