Actions
Bug #24867
open
No error toast when a pending node can't be accepted because hostname already exists
Status:
New
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
79
Name check:
To do
Fix check:
To do
Regression:
No
Description
If we try to accept a pending node while its hostname matches a node already accepted, the node is refused and we have in logs:
2024-05-16 13:17:09+0000 ERROR nodes.pending - Error when trying to accept node with id 'b522c78a-3dd6-48c0-b242-71da15c99109': Inconsistency: There is already a node with hostname 'node1.rudder.local' in Rudder. You can not add it again.
This is expected and that behavior can be change with the setting:
curl -k -H "X-API-Token: xxxxx" -H "Content-Type: application/json" -X POST 'http://localhost:8082/rudder-web/api/latest/settings/node_accept_duplicated_hostname' -d '{"value":true}'
But we don't have an error notification in the UI
Files
Updated by 
Updated by
Actions