Project

General

Profile

Bug #8409

When a node send reports with an unknow configID, no expected reports are showned

Added by François ARMAND almost 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
1
Category:
Web - Compliance & node report
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

When a node sends reports with a bad config ID (for example, because someone changed the value of rudder_node_config_id to something that that node never had), then we get a VersionNotFound with the message "run received but no version in db", and no expected reports at all displayed above.

The correct behavior should be to:

- display a clear message explaining what is going wrong (better than the current one, at least with links toward documentation about how to debug/solve the situation)
- display the list of directive configured on the node but WITHOUT compliance, to make it clear that the reports received are not compatible with the expected ones. And so, the user know what directives are actually wanted on the node.

We also thought to:

- get the expected config id for that node,
- get expected reports for that config id,
- behave exactly like when we have a bad config id, with missing/unknown (perhaps it could be made better with a merge between expected reports / what we get + a big WARNING: the config ID IS NOT CORRECT, THERE IS A PROBLEM).

But the last part lead to quite hard to understand compliance tree (basically, if you don't know how the calculus are implemented, it's really hard to understand what you are seing)


Subtasks

Bug #8722: Missing pattern matching caseReleasedNicolas CHARLES2016-07-20Actions
Bug #8725: Missing pattern matching case (cfclerck)ReleasedNicolas CHARLES2016-07-20Actions
#1

Updated by François ARMAND almost 5 years ago

  • Status changed from New to In progress
#2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.0.17 to 2.11.23
#3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.23 to 302
#4

Updated by Alexis MOUSSET over 4 years ago

  • Target version changed from 302 to 3.1.12
#5

Updated by François ARMAND over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1118
#6

Updated by François ARMAND over 4 years ago

  • Description updated (diff)

Corrected the description text and closed the pull request that doesn't match what we want.

#7

Updated by François ARMAND over 4 years ago

  • Status changed from Pending technical review to New
  • Assignee deleted (Vincent MEMBRÉ)
#8

Updated by François ARMAND over 4 years ago

  • Assignee set to Vincent MEMBRÉ
#9

Updated by François ARMAND over 4 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/1118 to https://github.com/Normation/rudder/pull/1131
#10

Updated by François ARMAND over 4 years ago

  • Status changed from New to Pending release
  • % Done changed from 0 to 100
#11

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.12 and 3.2.5 which were released today.

Also available in: Atom PDF