Actions
User story #8248
closedWithout config changes, two promise generation may lead to differently ordered value in promises
Status:
Rejected
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
When debugging #8247, I noticed that other changes are random, creating false cache invalidation. The resutl is correct, because unordered sets of values, but a lot of things are moved around for nothing.
Example (traced with git on /var/rudder/share directory, with word diff, so look for [-xxx-] and {+yyy+}):
+++ b/share/f2ad48f3-66b8-4270-9fd6-cf3c0426034b/rules/cfengine-community/checkGenericFileContent/5.0/checkGenericFileContent.cf .... @@ -104,8 +104,8 @@ bundle agent check_generic_file_content { "generic_file_content_owner[25]" string => "expd_of"; "generic_file_content_owner[26]" string => "root"; "generic_file_content_owner[27]" string => "root"; "generic_file_content_owner[28]" string => "$([-root-]{+generic_variable_definition.expuser+})"; "generic_file_content_owner[29]" string => "[-generic_variable_definition.expuser-]{+root+}"; "generic_file_content_owner[30]" string => "root"; "generic_file_content_owner[31]" string => "root"; "generic_file_content_owner[32]" string => "root"; ...
Or:
+++ b/share/f2ad48f3-66b8-4270-9fd6-cf3c0426034b/rules/cfengine-community/copyGitFile/1.5/copyFileFromSharedFolder.cf @@ -25,8 +25,8 @@ bundle agent download_from_shared_folder ..... "copyfile[4][name]" string => "sources/[-drush/drush-]{+postgresql/postgresql+}-$(generic_variable_definition.version_[-drush).tgz-]{+postgresql).run+}"; "copyfile[5][name]" string => "sources/[-postgresql/postgresql-]{+drush/drush+}-$(generic_variable_definition.version_[-postgresql).run-]{+drush).tgz+}"; .....
Not sur we can do something, because order may have a meaning in the general case, but it's really not clean as it is.
Updated by François ARMAND over 8 years ago
- Related to User story #8247: Changing hostname or policy server of one node force regeneration of all rules on the node added
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE over 7 years ago
- Tracker changed from Bug to User story
Requalifying as user story since everything is working properly, it's just that it could be better
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Benoît PECCATTE about 7 years ago
- Target version changed from 3.1.25 to 4.1.9
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.17 to 4.1.18
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset almost 6 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND over 5 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.21 to 4.1.22
Updated by Benoît PECCATTE over 5 years ago
- Target version changed from 4.1.22 to 5.0.10
Updated by François ARMAND over 5 years ago
- Status changed from In progress to Rejected
This is not the case anymore, and promise generation are deterministic. This is documented here: https://docs.rudder.io/reference/5.0/usage/advanced_configuration_management.html#_directives_ordering
Actions