Rudder

On the node "compliance reports" page and rules compliance, when going to the drill down of the reports, it shows "Not applicable" rather than Non compliance, see screenshot

Note: the compliance logger isn't helpful at all

2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Run config for node 8b43e849-f0a3-499c-88bc-da6414dc4e38: ComputeCompliance : Last run at 2016-10-19T10:31:05.000Z is for the correct configId 27abc96d and not expired, compute compliance
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Computing compliance for node 8b43e849-f0a3-499c-88bc-da6414dc4e38 with: [ComputeCompliance: expected NodeConfigId: 27abc96d/[2016-10-19T10:14:49.829Z-now] | last run: nodeConfigId: 27abc96d received at 2016-10-19T10:31:05.000Z | expired at 2016-10-19T10:41:05.000Z]
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Using merge/compare strategy between last reports from run at 2016-10-19T10:31:05.000Z and expect reports 27abc96d/[2016-10-19T10:14:49.829Z-now]
[2016-10-19 10:35:15] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Compute compliance for node 8b43e849-f0a3-499c-88bc-da6414dc4e38 using: rules for which compliance is based on run reports: [ffb7c92e-a561-4300-b17d-a680ff8152fc->1][inventory-all->7][hasPolicyServer-root->7][32377fd7-02fd-43d0-aab7-28460a91347b->2]; rule updated since run: []
[2016-10-19 10:36:08] TRACE explain_compliance.8b43e849-f0a3-499c-88bc-da6414dc4e38 - Run config for node 8b43e849-f0a3-499c-88bc-da6414dc4e38: ComputeCompliance : Last run at 2016-10-19T10:36:00.000Z is for the correct configId 27abc96d and not expired, compute compliance