# 4.0.3

2017-02-20

Maintenance release 3 of 4.0 branch

* User story #9771: Document the overriding mechanism for policy mode
* Bug #9821: When upgrading to 4.0.x, Directives are lost 
* Bug #9826: Broken tests after 9770
* Bug #9827: Broken tests after 9668
* Bug #9853: Incomplete logging in debug_timming
* Bug #9856: MergeCompareByRule is called for each nodes, and can add up to slow compliance
* Bug #9857: ReportingServiceImpl moves around a lot of data and is fairly slow
* Bug #9858: When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors."
* Bug #9859: "Migrate" button is displayed for deprecated techniques even if all version are deprecated
* Bug #9864: getNodeStatusReports is called for each node, and is slow to compute PolicyMode Inconsistency
* Bug #9894: Broken build of the manual in 4.0
* Bug #9936: Users with "node_all" security role can not change Agent Policy Mode
* Bug #9937: Missing "Policy Mode (Audit/Enforce)" documentation page in internal documentation
* Bug #9939: Broken build in 4.x since the merge of parent ticket
* User story #9955: Remove the "disabled rule" notice 
* Bug #9979: Simple relay tries to configure rsyslog-pgsql
* User story #9981: Add node policy mode api documentation
* Bug #10012: Cannot select by status on the "Change Requests" page
* Bug #10030: Clean test files (rudder-project)
* Bug #10034: Error when upgrading rudder-agent
* Bug #10077: (old) Autocomplete jar is still present
* Bug #10173: Display of new "Display compliance and recent changes columns on rule summary" setting is broken
* Bug #10177: Status dropdown's display is broken
* Bug #10198: EventLog at promise generation for datasources change, even if nothing changed
* Bug #10206: Merge error - Link check disappeared in 4.0
* Bug #10230: Fix compilation error after merge