Project

General

Profile

Actions

Bug #6631

closed

Interface name not correctly detected in search

Added by Olivier Mauras almost 9 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
1
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

This a major issue as the server doesn't get assigned to a critical group based on interface name.
See screenshot attached


Files

interface_name_wtf.png (29.9 KB) interface_name_wtf.png Olivier Mauras, 2015-05-21 13:55
Actions #1

Updated by François ARMAND almost 9 years ago

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/.

Actions #2

Updated by François ARMAND almost 9 years ago

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

Actions #3

Updated by François ARMAND almost 9 years ago

  • Assignee set to François ARMAND
  • Target version set to 2.11.11
Actions #4

Updated by François ARMAND almost 9 years ago

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.

Actions #5

Updated by François ARMAND almost 9 years ago

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 ?

Actions #6

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.11 to 2.11.12
Actions #7

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.12 to 2.11.13
Actions #8

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.13 to 2.11.14
Actions #9

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.14 to 2.11.15
Actions #10

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.15 to 2.11.16
Actions #11

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.16 to 2.11.17
Actions #12

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.17 to 2.11.18
Actions #13

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #14

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #15

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #16

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #17

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #19

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #20

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #21

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #22

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #23

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #24

Updated by François ARMAND over 7 years ago

  • Status changed from New to Rejected

For post-mortem, the server that wasn't appearing in results was deleted from Rudder and added back, and it started to work again.
We never succeeded in reproducing it again, so closing it because we can't do much more.

Please, feel free to reopen if the problem happen again.

Actions

Also available in: Atom PDF