Project

General

Profile

Bug #7499

Use of nonexistant class cfengine_community makes failsafe.cf not copy CFEngine binaries to /var/rudder

Added by Jonathan CLARKE over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

In failsafe.cf:

130   files:
131     cfengine_community.!windows::
132       "${sys.workdir}/bin/${components}" 
133         perms     => u_p("700"),
134         copy_from => cp("${cfengine_install_path}/bin/${components}","localhost"),
135         action    => immediate;

The class cfengine_community does not exist. It should be community_edition.

This exact same promise also exists in the main promises.cf, so the action is performed anyway, so this is not a grave bug. However, in the case of a corrupt binary, this could cause trouble.


Related issues

Related to Rudder - User story #6082: Make CFEngine binaries usable by everyone (mode 755)ReleasedBenoît PECCATTE2015-01-06Actions
#1

Updated by Jonathan CLARKE over 5 years ago

  • Related to User story #6082: Make CFEngine binaries usable by everyone (mode 755) added
#2

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE
#3

Updated by Jonathan CLARKE over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/798
#4

Updated by Jonathan CLARKE about 5 years ago

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

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.20, 2.11.17, 3.0.12 and 3.1.5 which were released today.

Also available in: Atom PDF