Project

General

Profile

Actions

Bug #8016

closed

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

Added by François ARMAND about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
2
Category:
Web - Nodes & inventories
Target version:
Severity:
User visibility:
Effort required:
Priority:

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).

Actions #1

Updated by François ARMAND about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1055
Actions #2

Updated by François ARMAND about 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.

Actions

Also available in: Atom PDF