Project

General

Profile

Actions

Bug #5614

closed

Two techniques with the same ID leads to strange error about git tree ids

Bug #5614: Two techniques with the same ID leads to strange error about git tree ids

Added by François ARMAND over 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
3
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Typical error returned displayed in promise generation or webapp logs:

[2014-10-07 18:19:19] ERROR com.normation.cfclerk.services.impl.GitTechniqueReader - More than exactly one ids were found in the git tree for template modoboa/0.1/rudder_reporting, I can not know which one to choose. IDs: AnyObjectId[0dc1c79ede134ef2c405692d558f4e9aed6d8197], AnyObjectId[0dc1c79ede134ef2c405692d558f4e9aed6d8197]
[2014-10-07 18:19:19] ERROR com.normation.rudder.batch.AsyncDeploymentAgent$DeployerAgent - Error when updating policy, reason Cannot write configuration node <- Error when trying to open template 'foo/0.1/some_file.st'. Check that the file exists and is correctly commited in Git, or that the metadata for the technique are corrects.

The problem here is really that the foo/0.1 is duplicated in several categories, for example:

/var/rudder/configuration-repository/techniques/applications/foo/0.1
And
/var/rudder/configuration-repository/techniques/applications/applications/foo/0.1

So, we should better check for techniques ID duplication and output a more understandable error in that case: "the technique with ID foo/0.1 is in both categories "applications" and "applications/applications", which is forbiden, techniqe IDs have to be unique in all categories. Please change one technique name or version, or keep only one of them".

Updated by François ARMAND over 11 years ago Actions #1

  • Description updated (diff)
  • Status changed from 8 to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/cf-clerk/pull/55

Updated by François ARMAND over 11 years ago Actions #2

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

Applied in changeset clerk:commit:8a32c6c660ccf69f84d876b059c281b6e1ad4159.

Updated by Nicolas CHARLES over 11 years ago Actions #3

Applied in changeset clerk:commit:2f5296c2e5b0d93d7082cf8630d8b6e087535af1.

Updated by Vincent MEMBRÉ over 11 years ago Actions #4

  • Category changed from System techniques to 14

Updated by Vincent MEMBRÉ over 11 years ago Actions #5

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.19, 2.10.7 and 2.11.4, which were these days.

Updated by Benoît PECCATTE almost 11 years ago Actions #6

  • Category changed from 14 to Web - Config management
Actions

Also available in: PDF Atom