Bug #8399: Misleading message on node compliance detail when run's configID is unknown - Rudder - Issue Tracker

Actions

Copy link

Bug #8399

closed

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

Bug #8399: Misleading message on node compliance detail when run's configID is unknown

Added by François ARMAND over 10 years ago. Updated about 10 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

Web - Compliance & node report

Target version:

3.0.16

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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".