Project

General

Profile

Actions

Bug #16739

closed

Error when refusing a node

Added by Félix DALLIDET almost 5 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
Server components
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
93
Name check:
To do
Fix check:
Checked
Regression:

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


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #17182: Node refusal failsRejectedActions
Actions #1

Updated by Félix DALLIDET almost 5 years ago

This is reproducible using Linux agents.

Actions #2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 6.0.3 to 6.0.4
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.4 to 6.0.5
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.5 to 6.0.6
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions #6

Updated by Alexis Mousset over 4 years ago

  • Has duplicate Bug #17182: Node refusal fails added
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #8

Updated by François ARMAND over 4 years ago

  • 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
Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
  • Priority changed from 58 to 57
Actions #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.9 to 6.0.10
  • Priority changed from 57 to 56
Actions #11

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 56 to 54
Actions #12

Updated by Alexis Mousset about 4 years ago

  • 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
Actions #13

Updated by Alexis Mousset about 4 years ago

  • Translation missing: en.field_tag_list set to Sponsored
  • Priority changed from 70 to 99
Actions #14

Updated by Elaad FURREEDAN about 4 years ago

  • Status changed from New to In progress
  • Assignee set to Elaad FURREEDAN
Actions #15

Updated by Elaad FURREEDAN about 4 years ago

  • 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
Actions #16

Updated by Anonymous about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #17

Updated by François ARMAND almost 4 years ago

  • Priority changed from 99 to 97
  • Fix check changed from To do to Checked
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 798 to 6.1.7
  • Priority changed from 97 to 93
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

This bug has been fixed in Rudder 6.1.7 and 6.2.1 which were released by the end of October 2020.

Actions #20

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF