Project

General

Profile

Actions
Copy link

Bug #4205

closed

Cannot add node: "Error when trying to accept node"

Added by Cédric Cabessa about 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
Cédric Cabessa
Category:
Web - Nodes & inventories
Target version:
2.10.5
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When adding a node, the following error occurs:
"""
Error when trying to accept node fca7ec51-f65f-4441-810f-a04137b67448 <- Error when executing accept node process named accept_new_server:add_system_configuration_rules <- Technical group with ID 'NodeGroupId(hasPolicyServer-ddd20cd5-4e96-4d44-b699-cd93a7347309)' was not found <- Error when retrieving the entry for NodeGroup 'NodeGroupId(hasPolicyServer-ddd20cd5-4e96-4d44-b699-cd93a7347309)'
"""

Compliance on server is set in the past (date the bug occurs?)

http://rudder/uuid => ddd20cd5-4e96-4d44-b699-cd93a7347309
(instead of root)

Workaround: (thanks to jooooooon)
echo root > /opt/rudder/etc/uuid.hive

The steps to reach this state are still unknown
Rudder 2.8.1
Red Hat Enterprise Linux Server release 6.3 (Santiago)

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from New to Discussion
  • Assignee set to Cédric Cabessa
  • Target version set to 2.8.2

Thanks for reporting this issue Cédric.

uuid seems to have been replaced by our cron... maybe the uuid file was deleted without backup...

Did you just upgraded your server, or it happend a long time after your upgrade ?

Actions
Copy link
 #2

Updated by Cédric Cabessa about 11 years ago

Vincent MEMBRÉ wrote:

Thanks for reporting this issue Cédric.

uuid seems to have been replaced by our cron... maybe the uuid file was deleted without backup...

Did you just upgraded your server, or it happend a long time after your upgrade ?

It happened a long time after.

I cannot exclude a bad action on our side (I am not the only one with access to the server). I'll let you know if this bug occurs again.

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.8.2 to 2.8.3
Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 11 years ago

Hi Cédric

Did the problem occured again ?

Actions
Copy link
 #5

Updated by Cédric Cabessa almost 11 years ago

did not occured again.

I think you can close.

Thx

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.8.3 to 2.8.4
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.8.4 to 133
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 133 to 2.9.5
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.9.5 to 2.9.6
Actions
Copy link
 #10

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.9.6 to 2.9.7
Actions
Copy link
 #11

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.9.7 to 150
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 150 to 2.10.4
Actions
Copy link
 #13

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.10.4 to 2.10.5
Actions
Copy link
 #14

Updated by Jonathan CLARKE over 10 years ago

  • Status changed from Discussion to Rejected

Never reproduced, and likely fixed with extra checks on the UUID added in 2.11. Closing.

Actions
Copy link

Also available in: Atom PDF