Project

General

Profile

Actions

Bug #3129

closed

Migrating a Directive to a new Technique version can lead to EventLog generation error

Added by Vincent MEMBRÉ over 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

It happens when computing the diff produced by the migration process.

- Migrate a Directive to a new Version (upgrade or downgrade)
- The Directive is really migrated in the LDAP and the promises are generated with success
- Compute a diff to produce an event log > Error
No Event log and no commit to configuration repository (as it depends on the event log)

To produce the diff, we use the new Directive spec to determine what had changed and look for their value in the old directive parameters.

If there is new spec parameters, it launches an error (it could not find the value for the directive)
if a spec parameters was removed, the diff is not tracked

That leads to other problem, like changing Technique version of a Directive not going into the configuration repository:

I have a directive based on "Check Generic File Content" Technique that I want to migrate to version 3.1.
When the migration is complete, the new version is correctly set to 3.1 in the LDAP. and promises generated corresponds to version 3.1.
But in the configuration repository, the directive version is set to 3.1.
So when making a restoration based on the git repository, we will always get the old version of the Directive

Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #3130: Changes on directives are not tracked by configuration repositoryRejectedVincent MEMBRÉ2013-01-02Actions
Actions

Also available in: Atom PDF