Bug #18084
closedInventory property key disappeared
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
Updated by François ARMAND over 4 years ago
- Target version changed from 6.1.3 to 6.1.4
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.4 to 6.1.5
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.5 to 6.1.6
- Priority changed from 65 to 64
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
- Priority changed from 64 to 63
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.7 to 6.1.8
- Priority changed from 63 to 62
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.8 to 6.1.9
- Priority changed from 62 to 60
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.9 to 6.1.10
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.10 to 6.1.11
- Priority changed from 60 to 58
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.11 to 6.1.12
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.12 to 6.1.13
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.13 to 6.1.14
- Priority changed from 58 to 56
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
- Priority changed from 56 to 55
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
- Priority changed from 55 to 54
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by Félix DALLIDET about 2 years ago
- Priority changed from 54 to 0
- Regression set to No
Not seen since.
Updated by François ARMAND over 1 year ago
- Related to Bug #22172: Sometime properties.json on the server contains default values - node properties reset to default added
Updated by François ARMAND over 1 year ago
- Related to deleted (Bug #22172: Sometime properties.json on the server contains default values - node properties reset to default)
Updated by François ARMAND over 1 year ago
- Is duplicate of Bug #22172: Sometime properties.json on the server contains default values - node properties reset to default added