Bug #8016: Missing error message in node acceptation when there is a problem with getting authorized networks - Rudder - Issue Tracker

Actions

Copy link

Bug #8016

closed

Missing error message in node acceptation when there is a problem with getting authorized networks

Bug #8016: Missing error message in node acceptation when there is a problem with getting authorized networks

Added by François ARMAND over 10 years ago. Updated over 10 years ago.

Status:

Released

Priority:

Assignee:

Nicolas CHARLES

Category:

Web - Nodes & inventories

Target version:

2.11.19

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

If the new node acceptation fails because we can't get authorized networks, the only error message for the user is "Error when trying to add node with id '000000002-55a2-4b97-8529-5154cbb63a18'", which is not informative at all.

And if you look for debug info, the error becomes:

16-03-01 10:37:25] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Node with id 'root' was refused during 'pre-accepting' step of phase 'accept_new_server:check_hostname_unicity'

Which kinda of even worse, because it let suppose that there is a problem in the hostname unicity, which is not at all the case (but at least, it allows the dev to debug the problem).