Project

General

Profile

Actions

Bug #5536

closed

A new node can hide another new node

Added by Benoît PECCATTE over 10 years ago. Updated over 9 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

When 2 nodes with a different uuid but the same hostname send their inventory, only one of them appear in the "Accept new node" page.

This makes it difficult to choose between them or even know that there is another node.


Files

Actions #1

Updated by François ARMAND about 10 years ago

I can't reproduce it by sending by hand two inventories with different UUID but same hostname to the endpoint. In that case, they actually appears in the "Accept new node" with the same hostname.

So, we need more information. What can have happen;

- a node N1 is created and send its inventory to Rudder
- N1 is (vm-)copied to N1-copy.
- N1-copy UUID is changed by hand
- N1-copy send its inventoy.

On that last step, the inventory name used by fusion will be the same than for N1. So the last inventory file received will win, and only one will reach the endpoint.
That explanation does not works if the node N1 was already in the "pending" panel in Rudder.

Could you please try to reproduce and better describe the step leading to that observed result ?

Actions #2

Updated by Benoît PECCATTE over 9 years ago

  • Category set to Web - Nodes & inventories
  • Status changed from New to Rejected
  • Target version set to 2.11.11

It was at a client's site and I can't reproduce it.

Actions

Also available in: Atom PDF