Project

General

Profile

Actions

Bug #2848

closed

The initial promises on a node have a disturbing error message about rudder-passwords.conf

Added by Nicolas PERRON over 12 years ago. Updated about 12 years ago.

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

Description

The use of initial promises on a node result in these messages:

!!! System error for fopen: "No such file or directory" 
!! File "/opt/rudder/etc/rudder-passwords.conf" could not be read in getfields()

This is disturbing as these messages are considered as errors.

The problem here is that one of the promises need to make an action on /opt/rudder/etc/rudder-passwords.conf which doesn't exist on nodes and even if the promise is not applied, it is parsed by CFEngine.

Actions #1

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Actions #2

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~beta5 to 2.4.0~rc1
Actions #3

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from New to 2

We discussed adding this file to all nodes to avoid the error message... but that's an ugly workaround.

A better solution would be to parameterize the CFEngine "inputs" by using a different list and not including distributePolicy/* for nodes. This can be acheived by referencing a list defined in a bundle common (for example "bundle common va" that already exists).

Actions #4

Updated by Nicolas PERRON over 12 years ago

  • Status changed from 2 to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf5175581.

Actions #5

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Pending technical review to Discussion

Nicolas PERRON wrote:

Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf5175581.

This looks fine, except for common/1.0/cf-served.cf, which should be included on all nodes, not just policy_servers. The cf-serverd component is also used on node (to allow for remote execution, for example).

Actions #6

Updated by Nicolas PERRON over 12 years ago

  • Status changed from Discussion to Pending technical review

Jonathan CLARKE wrote:

Nicolas PERRON wrote:

Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf5175581.

This looks fine, except for common/1.0/cf-served.cf, which should be included on all nodes, not just policy_servers. The cf-serverd component is also used on node (to allow for remote execution, for example).

You're absolutly right. It is done.

Actions #7

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Pending technical review to Released

Looks good, thanks.

Actions #8

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Actions

Also available in: Atom PDF