Project

General

Profile

Actions

Bug #9746

closed

Multilevel technique version numbers not working

Added by Joonas Harjumaki over 7 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Web - Config management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
47
Name check:
Fix check:
Regression:

Description

If technique library contains a technique with version number x.x and new version x.x.d is added, rudder doesn't work properly.

Adding 1.0.1 version when 1.0 existed rudder logs show following:

2016-11-29 15:54:23] INFO com.normation.cfclerk.services.impl.TechniqueRepositoryImpl - Reloading technique library, found modified technique(s): ['testtechnique': updated (1.0: VersionAdded)]
[2016-11-29 15:54:24] WARN com.normation.rudder.repository.xml.GitDirectiveArchiverImpl - Auto-archive git failure: not found in git added files: 'directives/cc6f5912-f091-47ac-a6d5-51c0b95ffe68/publicIp/
fb581319-16ac-489d-9bb8-23af70028503.xml'. You can safelly ignore that warning if the file was already existing in Git and was not modified by that archive.

Only version 1.0.1 is available for creating new directive after adding version 1.0.1.

Actions

Also available in: Atom PDF