# 6.1.6

2020-10-29

Maintenance release 6.1.6

* User story #17588: Add email path parameter in RUDDER config file
* Architecture #17752: Reorganize dockerfiles and start documentation
* Bug #18098: Alert user if they named a technique with a name that already exists in provided techniques
* Bug #18188: Error log about duplicates entries when saving node compliance levels
* Bug #18190: Add agent-server troubleshooting section
* Bug #18260: Selecting "latest" version for package installation in techniques Packages only checks for existence
* Bug #18265: Broken display of error icon in menu when there is a plugin error
* Bug #18279: Incorrect configuration when the database is not hosted on the rudder server itself
* Bug #18282: null value in status API on simple relay
* Bug #18303: Calling the relay-api to trigger a remote run on all nodes do an infinite loop on root server, killing it
* Bug #18308: rudder package throws exceptions when the connection timeouts
* Bug #18333: Replace apache config in /opt/rudder/etc on upgrade
* Bug #18336: Improve documentation on how to change a key for a node by stating that \n is mandatory around begin and end
* Bug #18346: Make the group option to include the Rudder server or not in the group clearer
* Bug #18348: After a factory reset agents can no longer download their policies from the new server they are managed by
* Bug #18353: Intermitent failure test on certificate inventory
* Bug #18356: Add a command to reset trust
* Bug #18370: Technique parameter description is not valid in technique.cf file
* Bug #18377: Duplicated code from a merge #16513
* Bug #18380: tests broken by parent ticket
* Bug #18382: Parent also needed in 6.1
* Bug #18383: Broken API doc build
* Bug #18391: Add a documentation page on how to manually distribute plugin licenses
* Bug #18399: Improve messages in agent about server key reset
* Bug #18404: systemctl restart rudder-server does nothing
* Bug #18407: Factory reset does not work
* Bug #18427: USEMETHODREPORTING is missing in metadata documentation
* Bug #18430: server-reset-keys should call a reset