Bug #16739
closed
Error when refusing a node
Added by Félix DALLIDET about 4 years ago.
Updated almost 2 years ago.
Category:
Server components
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Description
I had a windows node waiting for acceptation, for some reason I refused it.
It seems like it worked fine, but the UI show a message:
Error while refusing node(s).
In the webapp logs I have the following:
[2020-02-17 14:21:27+0100] ERROR com.normation.rudder.web.snippet.node.AcceptNode - Refuse node '445e203d-c6ab-4b2b-97f4-5aff29f7b17c' lead to Failure.: Error refusing NodeId(445e203d-c6ab-4b2b-97f4-5aff29f7b17c): step accept_new_server:ou=node
This is reproducible using Linux agents.
- Target version changed from 6.0.3 to 6.0.4
- Target version changed from 6.0.4 to 6.0.5
- Target version changed from 6.0.5 to 6.0.6
- Target version changed from 6.0.6 to 6.0.7
- Has duplicate Bug #17182: Node refusal fails added
- Target version changed from 6.0.7 to 6.0.8
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 58
- Target version changed from 6.0.8 to 6.0.9
- Priority changed from 58 to 57
- Target version changed from 6.0.9 to 6.0.10
- Priority changed from 57 to 56
- Target version changed from 6.0.10 to 798
- Priority changed from 56 to 54
- User visibility changed from Operational - other Techniques | Rudder settings | Plugins to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 54 to 70
- Translation missing: en.field_tag_list set to Sponsored
- Priority changed from 70 to 99
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3332
- Status changed from Pending technical review to Pending release
- Priority changed from 99 to 97
- Fix check changed from To do to Checked
- Target version changed from 798 to 6.1.7
- Priority changed from 97 to 93
This bug has been fixed in Rudder 6.1.7 and 6.2.1 which were released by the end of October 2020.
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous