Actions
Bug #7832
closedDon't copy files of local/50_techniques on the nodes - in initial promises
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
#7432 prevented nodes from downloading 50_techniques from the local ncf instance, but this was only partially applied to initial promises.
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.2.1 to 3.2.2
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.2 to 3.2.3
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.3 to 3.2.4
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.4 to 3.2.5
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.5 to 3.2.6
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.6 to 3.2.7
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.7 to 3.2.8
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.8 to 3.2.9
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.9 to 3.2.10
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.2.10 to 3.2.11
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.2.11 to 339
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 339 to 4.0.4
Updated by Jonathan CLARKE almost 8 years ago
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.4 to 4.0.5
- Priority set to 0
Updated by Jonathan CLARKE over 7 years ago
- Status changed from New to Rejected
Since 4.0 initial promises are generated from system techniques, so this un-synchronisation is no longer the case.
This bug only applied to 3.2, which is where #7432 was introduced, but 3.2 is no longer maintained (end of life), therefore this bug is no longer applicable.
Actions