Bug #22534: List Managed Nodes API with any of the fields listed in the "full" never answer - Rudder - Issue Tracker

Actions

Copy link

Bug #22534

closed

List Managed Nodes API with any of the fields listed in the "full" never answer

Added by Nicolas CHARLES over 1 year ago. Updated over 1 year ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Category:

API

Target version:

7.2.6

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Description

running

curl  --header "X-API-Token: $(cat /var/rudder/run/api-token)" -k 'https://localhost/rudder/api/latest/nodes?where=\[\{"objectType":"node","attribute":"nodeHostname","comparator":"regex","value":"'RUDDER-TEST-111.*'"\}\]&include=managementTechnologyDetails'

curl  --header "X-API-Token: $(cat /var/rudder/run/api-token)" -k 'https://localhost/rudder/api/latest/nodes?where=\[\{"objectType":"node","attribute":"nodeHostname","comparator":"regex","value":"'RUDDER-TEST-111.*'"\}\]&include=accounts'

never finished. The logs don't show anything, it's like nothing happend after getting the list of nodes
logs are

[2023-03-27 13:20:34+0000] DEBUG api-processing - Found a valid endpoint handler: 'listAcceptedNodes' on [GET nodes] with version '17'
[2023-03-27 13:20:34+0000] DEBUG api-processing - Account 'Rudder system account' has full RW authorization.
[2023-03-27 13:20:34+0000] TRACE api-processing - Executing handler for 'GET api/latest/nodes'
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Cache for nodes info expire ?: 1ms
[2023-03-27 13:20:34+0000] DEBUG com.normation.rudder.services.nodes.NodeInfoServiceCachedImpl - NodeInfo cache is up to date, last modification time: '2023-03-27T04:50:47.000Z' for: '20230327045047.5896
90Z#000000#000#000000','20230327045047.527117Z#000000#000#000000'
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Get cache for node info (all nodeinfos): 2ms
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Get node info (all nodeinfos): 6ms - exploring the cache took 4ms 
[2023-03-27 13:20:34+0000] DEBUG com.normation.rudder.services.queries.AcceptedNodesLDAPQueryProcessor - LDAP result: 11 entries obtained in 25ms for query { returnType:'node' (identity) with 'And' criteria [node.nodeHostname regex RUDDER-TEST-111.*] }
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Cache for nodes info expire ?: 3ms
[2023-03-27 13:20:34+0000] DEBUG com.normation.rudder.services.nodes.NodeInfoServiceCachedImpl - NodeInfo cache is up to date, last modification time: '2023-03-27T04:50:47.000Z' for: '20230327045047.589690Z#000000#000#000000','20230327045047.527117Z#000000#000#000000'
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Get cache for node info (all nodes info): 3ms
[2023-03-27 13:20:34+0000] DEBUG debug_timing - Get node info (all nodes info): 10ms - exploring the cache took 7ms

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by François ARMAND over 1 year ago

Status changed from New to In progress
Assignee set to François ARMAND

Actions

Copy link

Updated by François ARMAND over 1 year ago

It works on test installation. Does the environment where it happens has performance issues?

The main difference between these requests and other one asking for additional information is that it needs to query LDAP (while other have all info in cache), and so in a system where the LDAP is loaded, it can timeout.

Nonetheless, it is strange that the timeout error never bubble-up to the API level.

(up: it's likely that, we are trying to get ALL inventories of ALL nodes, whatever the node we found in the first place)

Actions

Copy link