# 3.1.22

2017-08-14

Maintenance release 22 of 3.1 branch

* Bug #4498: Several issues with process management on Proxmox host (and container)
* Bug #5071: Debian package management: can't specify a repository (ex: "-t wheezy-backports")
* Bug #5461: Slapd base corruption leads to slow app (for ex node deletion is terribly slow)
* Bug #5685: Raise errors if there's issues with a technique created with ncf-builder
* Bug #6166: Work lost on logout in ncf builder
* Bug #6322: "unknow status" for migrated change request in Rudder 3.0
* Bug #7850: Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP
* Bug #8752: Directive: Services Management doesn't support AIX
* Bug #9746: Multilevel technique version numbers not working
* Bug #10754: Cannot add a directive with a " in its name in Rule
* Bug #10951: Wrong XML identation in event log
* Bug #11055: Rudder can't start anymore because does not find configuration-repository techniques category in git 
* Architecture #11085: Adapt CLI to accept new end run format
* Bug #11088: Backport "rudder.json" system variable files to 3.1
* Bug #11106: 3787 is still present in 4.0+ versions of the technique
* User story #11107: Compliance logfile parsing regex
* Bug #11110: Check permissions on /var/rudder files, particularly modified-files
* Bug #11124: Invalid value BDB_PATH in  /etc/default/rudder-slapd 
* Architecture #11155: Warn on risk of updating file format
* Bug #11158: JSESSION cookie should be "httpOnly"
* Bug #11159: JSESSION cookie should be "secure"
* Bug #11160: We should not send Jetty version in header response
* Bug #11162: Put warnings (about dependencies for example) before install/upgrade instructions
* Bug #11163: Enable mod header for apache
* Bug #11182: Typo in unauthorized acces message
* Bug #11232: Typo in generation error
* Bug #11235: Aix group technique