Project

General

Profile

Bug #8399

Misleading message on node compliance detail when run's configID is unknown

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 send a run with a config ID that is not known by Rudder, we are displaying the message:

"no configuration ID found for that node, but a run was received at DATE. There is probably a problem with that node, perhaps was it deleted and reaccepted, and it is not yet up to date"

This is not very usefull, because:
- the bad config ID is not displayed (hared that necessary to debug)
- the cause explanation is most of the time not that. All we can say is: "the node sent a run with a config ID that is not in Rudder base. Either that config ID was deleted from Rudder DB or the node is sending a corrupted config ID. You should update node policies with "rudder agent update", and if the problem persist, try to regenerate policies with the "clear cache" action".

#1

Updated by François ARMAND almost 5 years ago

  • Status changed from New to In progress
#2

Updated by François ARMAND almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1106
#3

Updated by François ARMAND almost 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.0.17 to 3.0.16
#5

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Also available in: Atom PDF