Bug #5413
closedThe Rule compliance explanations in Rudder's web UI are not clear
Description
In the node reports it says
"No answer: No reports were received from this node for this Rule for over 10 minutes. Compliance is unknown - the node may be non responsive, or temporarily isolated from the network."
The actual status seems to be named "No report" though.
Files
Updated by Matthieu CERDA over 9 years ago
- Status changed from New to In progress
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 3
- Target version set to 2.10.5
All right, let's correct this \o/
Updated by Matthieu CERDA over 9 years ago
- Subject changed from minor naming issue in web ui to The Rule compliance explanations in Rudder's web UI are not clear
I also noticed that some explanations are wrong and need corrections.
Updated by Matthieu CERDA over 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder/pull/597
PR is ready. Careful though, this is a UI change and will require an attentive review to check if the explanation logic is correct and acceptable.
Updated by Nicolas CHARLES over 9 years ago
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
a native english speaker would be better than me for reviewing it
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.5 to 2.10.6
Updated by Matthieu CERDA over 9 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset c01864b8cc8798c1306dcd04bd1582a480ec2e8a.
Updated by Jonathan CLARKE over 9 years ago
Applied in changeset 3828c074d16bb14a05407c0d95f4cad0e8f07080.
Updated by Matthieu CERDA over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000038.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Matthieu CERDA over 9 years ago
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-October/000109.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/