Bug #3488
closed
Incomplete reporting in the update of promises
Added by Nicolas CHARLES almost 11 years ago.
Updated about 9 years ago.
Description
Now that the update mechanisms has been changed, the promises files are not always copied, but only when the rudder_promises_generated has been updated
The most common step for this update is the failsafe one, meaning that in the common execution it won't be reported has updated
We need to set the class persistant, so that the normal execution now it has been updated, and can properly reports based on it
Oh, and the error message appeared only when the rudder_promises_generated could be copied, but not the promises, which must be quite uncommon. Rather, the error message should also appear if rudder_promises_generated could not be copied
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/94
Now, the classes persist for 4 minutes (to prevent overlap with next run) to have complete reporting for update
As a side effect, we'll now that the promises have been updated for the execution !
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:f3580cf39ee43d285a053f3032e51e065dc0dfad.
Applied in changeset commit:6822e0f75c1aadcd093a93d37325c7a79fc97906.
- Status changed from Pending release to Released
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Nicolas PERRON 
Updated by