Bug #7796
closed
Rudder agent does not detect when promise copy failed
Added by Alexis Mousset almost 9 years ago.
Updated almost 9 years ago.
Category:
System techniques
Description
The file rudder_promises_generated is kept even when the copy fails, so the copy is only fixed at the next regeneration.
- Related to Bug #7793: Random wrong or partial copy of promises from node to server added
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Target version set to 3.2.0
- Related to Bug #7086: Promise copy is not convergent: if the copy is interupted, it will never recover added
- Related to User story #5580: Check the monotony of promises generation time on copy to nodes added
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by