Project

General

Profile

Actions
Copy link

Bug #9746

closed

Multilevel technique version numbers not working

Bug #9746: Multilevel technique version numbers not working

Added by Joonas Harjumaki almost 10 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Web - Config management
Target version:
3.1.22
Pull Request:
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.

Updated by François ARMAND almost 10 years ago Actions
Copy link
 #1

  • Category set to Web - Config management
  • Assignee set to François ARMAND
  • Priority changed from N/A to 4
  • Target version set to 3.1.17

Hello,

Thanks for reporting. I'm going to try to reproduce, not sure why you are seing that (it seems that the backend code should correctly handle arbitrary technique version, even if we use X.Y in our cases).

Updated by Vincent MEMBRÉ almost 10 years ago Actions
Copy link
 #2

  • Target version changed from 3.1.17 to 3.1.18

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #3

  • Target version changed from 3.1.18 to 3.1.19

Updated by Benoît PECCATTE over 9 years ago Actions
Copy link
 #4

This is probably because we never supported x.y.z versioning in techniques, only x.y

Updated by Benoît PECCATTE over 9 years ago Actions
Copy link
 #5

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 34

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #6

  • Target version changed from 3.1.19 to 3.1.20

Updated by Jonathan CLARKE over 9 years ago Actions
Copy link
 #7

  • Assignee deleted (François ARMAND)

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #8

  • Target version changed from 3.1.20 to 3.1.21
  • Priority changed from 34 to 33

Updated by Vincent MEMBRÉ about 9 years ago Actions
Copy link
 #9

  • Target version changed from 3.1.21 to 3.1.22

Updated by Benoît PECCATTE about 9 years ago Actions
Copy link
 #10

  • Priority changed from 33 to 47

Updated by Benoît PECCATTE about 9 years ago Actions
Copy link
 #11

  • Status changed from New to Rejected

Technique versions of the form x.y.z are not supported.
Only versions of the form x.y are supported.

Actions
Copy link

Also available in: PDF Atom