# 2.9.5

2014-06-06

Maintenance release 5 for 2.9 version

* Bug #4357: Editing a Directive, after creating/cloning, does not show the workflow popup nor redirect to the change request
* Bug #4640: Changing server security settings should trigger a promise generation
* Bug #4660: A developpment log line is displayed when saving Directive edit form
* Bug #4686: Typo in /opt/rudder/bin/check-rudder-agent, prevent cleaning of cf-lock and floods with cron mails
* Bug #4716: Promises generation fails on relay server
* Bug #4742: Process start date are displayed as "bad format" in Rudder web interface
* Bug #4743: Process start date are displayed as "bad format" in Rudder web interface (inventory part) 
* Bug #4745: CFEngine complains about a Typo in policy_server initial promises
* Bug #4752: cf_lock.tcdb is not cleaned by check-rudder-agent script when update file is older than 10 minutes
* Bug #4755: Default file header should be one liner to prevent header repetition.
* Bug #4756: Default file header should be one liner to prevent header repetition on upgrade
* Bug #4769: rudder-agent may be stucked by tokyo cabinet database bloating
* Bug #4787: In Rule grid, mouse hover on "Not applied" Rules display a wrong tooltip
* Bug #4800: Latest API prefix is not correct
* Bug #4837: Copy of ncf files on the Policy Server leave removed files, resulting in duplicate promises if we rename or move files
* Bug #4841: Job Scheduler Technique should not use ifelapsed to avoid running several time same job
* Bug #4894: The initial promises use a remote copy which does not permit the copy of ncf files to /var/rudder/ncf/ and generation of promises fails.
* Bug #4923: check-rudder-agent is broken on 2.9 nightly because of a bad merge
* Bug #4946: Rule category can be deleted after the a Rule was added to the category
* Bug #4947: If we select a Rule category (other than top) then reload the Rule page, the state of the Rule table is not coherent.