Project

General

Profile

Actions

Bug #11583

closed

Rudder creates DSC based group and rules and breaks policy generation

Added by François ARMAND about 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
94
Name check:
Fix check:
Regression:

Description

Rudder create DSC based rule and group, even when there is no DSC plugin installed.

The problem is that the Technique dsc-common only comes with the plugin. So we are ending with a directive using a non-existing version of a Techniques, which is an error.

At least on one case, it lead to an user not being able to regenerate policies with the message:

Policy update process was stopped due to an error:
⇨ Policy update error for process '932' at 2017-10-04 11:00:20
⇨ Cannot build Rule vals
⇨ Could not find configuration vals
⇨ Version '1.0' of technique 'dsc-common' is not available for directive 'DSC Based agent configuration' [dsc-common-all]

I was not able to reproduce that problem on a fresh install, so perhaps the problem only happens if the missing technique is used - which it shouldn't, so perhaps it was in conjunction with #11168.

For now, I'm setting it in "critical", because no generation without workaround is hardcore. We may decrease the severity when we understand the root cause and/or find a workaround.

  • WORAROUND ***

If your generation is broken because of that one + #11168 and you don't actually have any windows node, you can workaround the problem, see: https://www.rudder-project.org/redmine/issues/11168#note-10


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #11168: Search believe that CFEngine agents with "dsc" in their keys are also DSC agent ReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF