Project

General

Profile

Actions

Bug #6020

closed

In change only mode, when a node never answered and a given directive is applied on two differents Rules, the reports in the node details show Could not fetch reports information

Added by Nicolas CHARLES almost 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In change only mode, if a node never answered, i get the message "Could not fetch reports information" rather than the actual details of the reports.
I also have no details in the Rule screen , where it says N/A


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #5329: False "no answer" reporting when rules with "unique" directive are overriddenReleasedNicolas CHARLES2014-07-30Actions
Related to Rudder - Bug #6039: The expected reports of other rules are not correctly updated when we create a new ruleReleasedFrançois ARMAND2014-12-22Actions
Actions #1

Updated by Nicolas CHARLES almost 10 years ago

I have 2 Rules, on applied to all nodes, one applied to one node (Node2)
I have one directive (unique) APT Package Manager, that I applied to both Rules

The rule with one node ends up with status N/A; and the Rule that applis to all nodes is ok

On the Node screen, for Node2, I get "Could not fetch reports information" message

By studying what it does, it fetches the NodeConfigId of node2 from nodes_infos, and looks for it in the expectedreports
However this NodeConfigId is not in the expectedReports. I strongly suspect that the erasure of duplicate directive doesn't do what is expected (like, it updates the nodeconfigid when it shouldn't)

Actions #2

Updated by Nicolas CHARLES almost 10 years ago

Adding another directive in the Rule with N/A status solves the issue, and we do see that the Directive Unique is not there

Actions #3

Updated by François ARMAND almost 10 years ago

  • Target version changed from 3.0.0~beta2 to 3.0.0~rc1
Actions #4

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from New to Rejected

I can't reproduce. It must have been fixed by #6039

Actions

Also available in: Atom PDF