Actions
Bug #7796
closed
Rudder agent does not detect when promise copy failed
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The file rudder_promises_generated is kept even when the copy fails, so the copy is only fixed at the next regeneration.
Updated by Alexis Mousset almost 9 years ago
- Related to Bug #7793: Random wrong or partial copy of promises from node to server added
Updated by Alexis Mousset almost 9 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Target version set to 3.2.0
Updated by Alexis Mousset almost 9 years ago
The problem is that https://github.com/Normation/rudder-techniques/pull/737 (#7086) was merged directly in 3.2 but it required modifications because of https://github.com/Normation/rudder-techniques/pull/735 (#5580) (particularly renaming the update "flag" file).
Updated by Alexis Mousset almost 9 years ago
- Related to Bug #7086: Promise copy is not convergent: if the copy is interupted, it will never recover added
Updated by Alexis Mousset almost 9 years ago
- Related to User story #5580: Check the monotony of promises generation time on copy to nodes added
Updated by Alexis Mousset almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/852
Updated by Alexis Mousset almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|0f69fa159dbc6b1f4e225bc11bd2f26515dfe4ff.
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0 which were released today.
Actions