Bug #6768: Sometimes, promises get corrupted to the point they can't be automatically repaired on a node - Rudder - Issue Tracker

Actions

Copy link

Bug #6768

closed

Sometimes, promises get corrupted to the point they can't be automatically repaired on a node

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Category:

System integration

Target version:

2.10.15

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Sometimes, for some unknown reasons, promises get corrupted (files are not there) on the node.

A workaround to restore the situation is to add a step in check_rudder_agent script that would:
- check if failsafe.cf, promises.cf and common/1.0/update.cf are there and non empty
- if they are there, do nothing
- if not, copy from /opt/rudder/share/initial-promises to /var/rudder/cfengine-community/inputs, and execute then cf-agent -Kf failsafe.cf && cf-agent

The rational is:

if any of these file is empty, nothing can work at all
running cf-promises can be ressource intensive, so running it always is not a so great idea
if these files are empty, then the failsafe has just be run, so the -K is mandatory. The cf-agent was not run recently (valid promises are more than 5 minutes old), so no need of -K for that

Subtasks 1 (0 open — 1 closed)