Project

General

Profile

Actions

Bug #24866

open

Pending node say 1 node but none present

Added by François ARMAND about 1 month ago. Updated 5 days ago.

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

Description

We have seen a case where:

- pending node says there is one node present on dashboard
- if you go to pending node page, there's 0 nodes
- LDAP contains a node inventory
- the node hostname matches one already accepted in rudder
- if we delete the accepted node, then the node appears in pending node.


Files

clipboard-202405161853-xkwfg.png (136 KB) clipboard-202405161853-xkwfg.png François ARMAND, 2024-05-16 18:53
Actions #1

Updated by François ARMAND about 1 month ago

I was not able to reproduce that.

I install a rudder server 7.3, with a 7.3 node ; then updagraded to 8.0 and added a 8.0 node ; then upgraded to 8.1 and added a 8.1 node.
Then I factory-reset all the nodes, and the correctly appeared in pending nodes.
And if I try to accept them, I have the correct error message (even if not well styled).

The difference in dashboard and pending is because dashboard use a special case LDAP request and not the same logic than pending node screen.
We can make the two converge, at the price of perhaps lower perf if there is a lot of pending node (but we should do it for consistency nonetheless).

So, I believe that:
- either there is something special with Rudder 6.2 nodes in Rudder 8.1 (the problematic node were using very old rudder agent)
- or in each case, there was a problem with the inventory save in LDAP, which let things a bit broken in an interesting and complicated way to reproduce.

Actions #2

Updated by Vincent MEMBRÉ 24 days ago

  • Target version changed from 8.1.3 to 8.1.4
Actions #3

Updated by Vincent MEMBRÉ 5 days ago

  • Target version changed from 8.1.4 to 8.1.5
Actions

Also available in: Atom PDF