Actions
Bug #25154
closed
Creating conflicting properties can break the server
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
I hate Rudder for that
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
136
Name check:
To do
Fix check:
To do
Regression:
No
Description
If I create a property on group1 and create the same property on group2.
If group1 and group2 have nodes in common, this is a conflict.
When there is a conflict, it is not possible anymore to view group properties because of the error.
It is thus not possible to fix the problem.
And since generation stop, the server is completely broken
Updated by Vincent MEMBRÉ 5 months ago
- Target version changed from 8.1.6 to 8.1.7
Updated by Clark ANDRIANASOLO 4 months ago
- Is duplicate of Bug #22077: Group properties web page of a group of groups containing conflicting properties are unaccessible added
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from New to Rejected
- Priority changed from 142 to 141
Duplicate of #22077
Updated by Clark ANDRIANASOLO 2 months ago
- Status changed from Rejected to New
- Target version changed from 8.1.7 to 8.1.8
- Priority changed from 141 to 137
It is still the case in 8.1.7, but no longer in 8.2 (which has the same problem resolved in #22077)
Updated by Clark ANDRIANASOLO 2 months ago
Workaround : delete the conflicting properties from the error message. It would have to be done from the REST API, since the UI is not accessible
Updated by Clark ANDRIANASOLO 2 months ago
- Is duplicate of Bug #25687: Same as parent ticket for branch 8.1 added
Updated by Vincent MEMBRÉ about 1 month ago
- Target version changed from 8.1.8 to 8.1.9
- Priority changed from 137 to 136
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from New to Released
This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.
Actions