Project

General

Profile

Actions

Bug #6451

closed

Missing error message when trying to accept a node with an already existing hostname

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

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

Description

If we try to accept a node in Rudder when an other node (different UUID) with the same hostname was already accepted, the node is refused.

In 2.11 and before, an error message is displayed (see file attached).
But in 3.0, the error message explaining the problem is not displayed.


Files

Actions #1

Updated by François ARMAND about 6 years ago

  • Status changed from 8 to In progress

So, this is due to the use of lazy-load in 3.0, see: http://webmail.dev411.com/t/gg/liftweb/12cmapx88f/lift-posible-bug-in-lazyload-snippet

Nothing was one in Lift for that, the bug is still here.

Actions #2

Updated by François ARMAND about 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee set to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/841

The root problem can not be corrected, so the workaround is to put the error part outside of the lazy-load tag.

Actions #3

Updated by François ARMAND about 6 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/841 to https://github.com/Normation/rudder/pull/842

The correct PR with the correct branch is: https://github.com/Normation/rudder/pull/842

Actions #4

Updated by François ARMAND about 6 years ago

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

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.4 which was released today.

Actions

Also available in: Atom PDF