Project

General

Profile

Actions

Bug #22172

open

Sometime properties.json on the server contains default values - node properties reset to default

Added by Benoît PECCATTE over 1 year ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Category:
System techniques
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
I hate Rudder for that
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
94
Name check:
To do
Fix check:
To do
Regression:
No

Description

If I generate using "Regenerate all policies" all properties are back to normal on the server.

But after some times, the file /var/rudder/cfengine-community/inputs/properties.d/properties.json contains default values, with only "rudder" and "rudder_file_edit_header" as a property

Some more info:
- all properties are from Global Parameters, no group properties
- the reset to default property file is done after a policy generation
- if we add a property on the node (one that doesn't override a global param, not tested the other case), then generation remains correct
- after removing said property, the problem has disapeared


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #18084: Inventory property key disappearedRejectedFélix DALLIDETActions
Actions #1

Updated by Benoît PECCATTE over 1 year ago

  • Assignee set to François ARMAND
Actions #2

Updated by Alexis Mousset over 1 year ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
Actions #3

Updated by François ARMAND over 1 year ago

  • Description updated (diff)
Actions #4

Updated by François ARMAND over 1 year ago

  • Description updated (diff)
Actions #5

Updated by Benoît PECCATTE over 1 year ago

  • Description updated (diff)
Actions #6

Updated by Benoît PECCATTE over 1 year ago

  • Description updated (diff)
Actions #7

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.3 to 7.2.4
Actions #8

Updated by François ARMAND over 1 year ago

  • User visibility set to Infrequent - complex configurations | third party integrations

We tested a lot of cases and were never able to reproduce it - even on the same exported VM after reimport.
It might be to a side effect that is not understood for now. I'm lowering the user visibility to infrequent.

Actions #9

Updated by François ARMAND over 1 year ago

  • UX impact set to I hate Rudder for that
  • Priority changed from 0 to 112
Actions #10

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.2.4 to 7.2.5
Actions #11

Updated by François ARMAND about 1 year ago

  • Status changed from New to Rejected
  • Priority changed from 112 to 110

OK, we never successfully reproduced, and nobody else talked about it. I'm closing it.

People, if you see it: this is a major critical bug, so please please reopen it if you encounter it in the wild.

Actions #12

Updated by François ARMAND about 1 year ago

  • Priority changed from 110 to 109

Actually, it seems that #18084 could be duplicate (or at least an other instance of the problem).

Actions #13

Updated by François ARMAND about 1 year ago

  • Related to Bug #18084: Inventory property key disappeared added
Actions #14

Updated by François ARMAND about 1 year ago

  • Subject changed from Sometime properties.json on the server contains default values to Sometime properties.json on the server contains default values - node properties reset to default
Actions #15

Updated by François ARMAND about 1 year ago

  • Status changed from Rejected to New

Closing #18084, re-opening this one. 18084 description:

I had an aws node with its aws hook working fine, I came today and saw that the property was missing from its properties webpage.
Also, running an inventory on the node made it came back in the interface. This is very odd since those inventory based properties should not be removable, and they are often used
as group criteria. I have not idea of what happens nor why, it looked like it worked fine before.

Also, I found out that one of my aws region base group was based on the criteria "system=Linux" which I am pretty sure was always something like "AWS-meta-data:$.[?(@.placement.region=="eu-west-1")]" on properties:jsonpath. This is confusing since the event logs are saying that the criteria was always the default one for this group: "system=Linux".
I first thought that I just forgot to save the group when I created it, but the exact same group had the same problem on 2 others servers of mine out of 4. This looks like I was either really not paying attention to what I was doing or something odd prevented the save/change in criteria.

Also, I was fairly sure that I double check my groups since I used group based property override on them last week. There are nothing in the logs nor in event logs that could support my felling that something is broken here.

I will update the ticket if one of those 2 issues are occuring again on my servers

Actions #16

Updated by François ARMAND about 1 year ago

  • Related to deleted (Bug #18084: Inventory property key disappeared)
Actions #17

Updated by François ARMAND about 1 year ago

  • Has duplicate Bug #18084: Inventory property key disappeared added
Actions #18

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.2.5 to 7.2.6
  • Priority changed from 109 to 108
Actions #19

Updated by Benoît PECCATTE about 1 year ago

  • Category set to System techniques
Actions #20

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 7.2.6 to 7.2.7
  • Priority changed from 108 to 106
Actions #21

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 7.2.7 to 7.2.8
  • Priority changed from 106 to 105
Actions #22

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.2.8 to 7.2.9
  • Priority changed from 105 to 103
Actions #23

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.2.9 to 7.2.10
  • Priority changed from 103 to 102
Actions #24

Updated by Alexis Mousset 8 months ago

  • Target version changed from 7.2.10 to 7.2.11
  • Priority changed from 102 to 100
Actions #25

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.2.11 to 1046
  • Priority changed from 100 to 99
Actions #26

Updated by Alexis Mousset 6 months ago

  • Target version changed from 1046 to 7.3.8
  • Priority changed from 99 to 97
Actions #27

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.8 to 7.3.9
  • Priority changed from 97 to 96
Actions #28

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.9 to 7.3.10
  • Priority changed from 96 to 95
Actions #29

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 7.3.10 to 7.3.11
  • Priority changed from 95 to 94
Actions #30

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #31

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #32

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 7.3.13 to 7.3.14
Actions

Also available in: Atom PDF