Bug #2411
closed
CFEngine doesn't expireafter when installing a package
Description
Sometimes, we edit a configuration file before installing a package, which leads to questions asked by the package-manager, packages which remains without answer for it's tty who should answer, and it stall, and is SIGINTed after quite a long time, and thus the execution is incomplete.
One way to circumvent would be to expireafter the promise, however, it does not seems to work with the packages promises time (ref https://cfengine.com/bugtracker/view.php?id=1012 )
Updated by Jonathan CLARKE almost 13 years ago
- Priority changed from N/A to 4
- Target version changed from 2.3.7 to 2.3.8
This is a bit of a corner case, and while it's annoying, it's not a reason to block the upcoming release, moving to 2.3.8.
Updated by Nicolas CHARLES over 12 years ago
The statement from CFEngine devs is that the expireafter is triggered by next CFEngine execution; that's why it wasn't detected with my tests
So we should probably give the expireafter a try
Updated by Nicolas PERRON 
Updated by Matthieu CERDA
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.4.13 to 2.6.11
Since version 2.4 is not maintained anymore, retageting this issue to 2.6
Updated by François ARMAND about 10 years ago
- Target version changed from 2.6.20 to 2.10.10
Nicolas, what is status of that one ? Still relevant ?
Updated by
Updated by Jonathan CLARKE almost 8 years ago
- Status changed from New to Rejected
Since #2478 was fixed, this no longer actually has any impact in Rudder. It may be of concern to plain CFEngine users, but not Rudder users. As a result, rejecting this.