# 3.0.16

2016-06-02

Maintenance release 16 of 3.0 branch

* Bug #7042: Directive detail don't show the OS compatibility version
* Bug #7336: Node stuck in "Applying" status
* Bug #7348: rudder-jetty initialisation should not support Java 6
* Bug #7735: OOM in Rudder when there are too many repaired reports
* Bug #7825: Add a left margin to the Rudder search box
* User story #7889: Move Relay doc to the install section
* Bug #7976: rudder doc can be misleading on the repo to use for Centos/RHEL
* Bug #8045: Using Rudder server 3.x + rudder agent 2.11.x, a node doesn't properly detect its change of relay server
* Bug #8051: Compliance is not correctly computed if we receive run agent right after generation
* User story #8107: Augment default number of lines displayed and add more options
* Bug #8136: Fix display issues on IE11
* Bug #8147: Message about cron on windows are confusing
* Bug #8162:  Document usage of line replacement in Enforce a file content technique
* Bug #8189:  It is not possible to define value with " in generic variable definition (branch 3.0 and more)
* Bug #8192: Better document Node Api: include detail always returns "default"
* Bug #8195: Correct memory profile and efficiency of non-compliant-reports logger
* Bug #8201: Priority field in Directive form does not show it has a tooltip and has wrong description
* Bug #8203: permissions technique tries to set a group even when we do not ask for it - 3.0 branch / technique versions 2.0 and 2.1
* User story #8204: Adapt "Troubleshooting" section for 3.0
* Bug #8212: The start at boot does not work in the openssh technique on systemd OSes - 3.0 branch
* Bug #8213: Change audit message is not checked in the "Clone Directive" popup
* Bug #8254: Double reporting for group creation - 3.0 branch
* Bug #8262: Prevent red color usage in inventory graphs
* Bug #8265: Clear package caches when repairing a package repository for apt - branch 3.0
* Bug #8298: rudder doc can be misleading on the repo to use for Centos/RHEL fix typo
* Bug #8303: Broken xml output after #8233
* Bug #8317: "rudder agent enable -s" doesn't return an error code if it can't start the agent
* User story #8332: Move man pages into the reference section
* Bug #8336: Error on windows: agent tries to check if /usr/bin/env supports the -0 option
* Bug #8344: Missing relevant information about why the compliance is what it is on node
* Bug #8346: rudder agent update doesn't always update policy
* Bug #8364: Only invalidate cache for node with new completed runs
* Bug #8370: Makefile missing in rudder-server-relay package
* Bug #8373: Remove duplicate java version check from init script
* Bug #8382: In case of error in logrotate check, there is no report
* Bug #8387: check-techniques script doesn't properly exit non-zero on errors
* Bug #8388: rudder-jetty build fails when applying a removed patch
* Bug #8395: applications/aptPackageManagerSettings/3.1 missing from list of maintained techniques
* Bug #8396: "repaired" are counted as "required attention" on node compliance details
* Bug #8399: Misleading message on node compliance detail when run's configID is unknown
* Bug #8400: "All the last execution reports for this server are ok" displayed when no report received