Project

General

Profile

Actions

Bug #3608

closed

When searching for nodes with more than 100 Mo ram, Rudder fails to return them all

Added by Nicolas CHARLES almost 11 years ago. Updated almost 11 years ago.

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

Description

I'm looking for Debian with more than 100 MB RAM with the search engine, and unfortunately, Rudder returns me only one node (namely debian-6-64) while I'm expecting 2 : debian-5-64 and debian-6-64

Here is the LDAP log. Happens on orch-3.
Debian-5-64 does have 400 MB of memory

16:31:57.732 [qtp760805843-74] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [387059846571] Start search for { returnType:'NodeReturnType' with 'And' criteria [node.OS eq Linux ; node.osName eq Debian ; node.ram gteq 100 Mo] }
16:31:57.743 [qtp760805843-74] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [387059846571] |- LDAPObjectType(ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration,One,Some((&(objectClass=linuxNode)(&(objectClass=node)(osName=Debian))(ram>=104857600))),DNJoin,Set())
16:31:57.744 [qtp760805843-74] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [387059846571] |--- SearchRequest(baseDN='ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration', scope=ONE, deref=NEVER, sizeLimit=1000, timeLimit=10, filter='(&(objectClass=linuxNode)(&(objectClass=node)(osName=Debian))(ram>=104857600))', attrs={policyServerId, osFullName, localAdministratorAccountName, cn, createTimestamp, agentName, ipHostNumber, publicKey, nodeId, nodeHostname, objectClass})
16:31:57.746 [qtp760805843-74] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [387059846571] |---- 2 result(s)
16:31:57.747 [qtp760805843-74] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [387059846571] `-> 2 results
Actions #1

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.5.4 to 2.5.5
Actions #2

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.5.5 to 2.4.7

It happens on 2.4 too

Actions #3

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from New to Rejected
  • Target version changed from 2.4.7 to 2.5.5

Sorry dear president, I am obliged to tell you that node Debian-5-64 has 89Mb of RAM.

When requesting about nodes over 80Mo, you definetrly got both ;)

I reject this bug.

Actions

Also available in: Atom PDF