Bug #4895
closed
Wrong error message when accepted an already accepted node
Added by Matthieu CERDA about 8 years ago.
Updated over 7 years ago.
Category:
Web - Nodes & inventories
Description
When I try to accept a new node that for some reason already exists (on a Rudder 2.6.10 server):
Error when trying to execute pre-accepting for phase accept_new_server:check_hostname_unicity. Stop. <- There is already a node with Hostname 'centos-6-64.labo.normation.com' in database. You can not add it again.
Maybe we should display something less frightening like "There is already a node with Hostname 'centos-6-64.labo.normation.com' in database. You can not add it again." and leave "Error when trying to execute pre-accepting for phase accept_new_server:check_hostname_unicity. Stop." for the log debug output :)
- Target version changed from 2.6.13 to 2.6.14
- Target version changed from 2.6.14 to 2.6.16
- Target version changed from 2.6.16 to 2.6.17
- Target version changed from 2.6.17 to 2.6.18
- Target version changed from 2.6.18 to 2.6.19
- Target version changed from 2.6.19 to 2.6.20
- Status changed from 8 to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Target version changed from 2.6.20 to 2.10.10
- Pull Request set to https://github.com/Normation/rudder/pull/815
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Target version changed from 2.10.10 to 2.10.9
- Target version changed from 2.10.9 to 2.10.10
- Subject changed from The error thant appears while a node to be accepted already exists is frightening to Wrong error message when accepted an already accepted node
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.10 and 2.11.7, which were these days.
Also available in: Atom
PDF