Project

General

Profile

Actions

Bug #4966

closed

Date/time is not defined on all reports in failsafe.cf from initial promises

Added by Jonathan CLARKE almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
3
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The common bundle "g" contains a load of globally uses variables across our CFEngine promises. One of them is "execDate" which contains the date/time that we include in all Rudder reports. This is in failsafe.cf and site.cf. However, the failsafe.cf from initial-promises is missing this variable.

This results in log lines like these:

2014-06-09T06:08:01-0400   notice: R: @@Common@@result_error@@hasPolicyServer-root@@common-root@@00@@Update@@None@@${g.execRun}##be933c39-8781-4298-8ca5-9d5b6843ecbe@#Cannot update common Rudder ncf instance
2014-06-09T06:08:01-0400   notice: R: @@Common@@result_error@@hasPolicyServer-root@@common-root@@00@@Update@@None@@${g.execRun}##be933c39-8781-4298-8ca5-9d5b6843ecbe@#Cannot update local Rudder ncf instance
2014-06-09T06:08:01-0400   notice: R: @@Common@@result_error@@hasPolicyServer-root@@common-root@@00@@Update@@None@@${g.execRun}##be933c39-8781-4298-8ca5-9d5b6843ecbe@#Cannot update node's policy

Subtasks 2 (0 open2 closed)

Bug #4974: Date/time is not defined on all reports in failsafe.cf from initial promises (AIX/other)ReleasedNicolas CHARLES2014-06-09Actions
Bug #4973: Date/time is not defined on all reports in failsafe.cf from initial promises (Android/Windows)ReleasedNicolas CHARLES2014-06-09Actions
Actions

Also available in: Atom PDF