Bug #2656
closed
Archiving Directive library doesn't work if LDAP references Techniques which doesn't exist anymore
Description
Is this normal that we can't archive directives if it remain some directives using erased techniques (and which result in error in the logs) ?
[2012-07-16 05:05:06] DEBUG com.normation.rudder.repository.xml.GitActiveTechniqueArchiverImpl - Archived technique library template: /var/rudder/configuration-repository/directives/userlib_systemSettings/userlib_userManagement/groupManagement/activeTechniqueSettings.xml [2012-07-16 05:05:06] DEBUG com.normation.rudder.repository.xml.UpdatePiOnActiveTechniqueEvent - Executing archivage of PIs for UPT 'ActiveTechnique(ActiveTechniqueId(73f0dad5-c0a9-4e88-a679-882f9d3c77cd),groupManagement,Map(1.0 -> 2012-07-16T04:51:34.966-04:00),List(),true,false)' [2012-07-16 05:05:06] DEBUG com.normation.rudder.repository.xml.GitActiveTechniqueArchiverImpl - Archived technique library template: /var/rudder/configuration-repository/directives/userlib_systemSettings/userlib_userManagement/userDirectoryPermissions/activeTechniqueSettings.xml [2012-07-16 05:05:06] DEBUG com.normation.rudder.repository.xml.UpdatePiOnActiveTechniqueEvent - Executing archivage of PIs for UPT 'ActiveTechnique(ActiveTechniqueId(5014bc9b-3f66-4499-93e1-69e101401974),userDirectoryPermissions,Map(1.0 -> 2011-11-23T09:24:04.100-05:00),List(DirectiveId(290e232b-b868-4b1f-bbc9-44e6ccb0d81f), DirectiveId(efeb4364-e039-462c-9a2e-05feb4e29bb2)),true,false)' [2012-07-16 05:05:06] DEBUG com.normation.cfclerk.services.impl.TechniqueRepositoryImpl - Required technique 'userDirectoryPermissions/1.0' was not found [2012-07-16 05:05:06] ERROR com.normation.rudder.web.snippet.administration.Archives - Error when exporting groups, Directive library and Rules. [2012-07-16 05:05:06] ERROR com.normation.rudder.web.snippet.administration.Archives - 2012-07-16 05:05:16.343:INFO::Graceful shutdown SelectChannelConnector@127.0.0.1:8080
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta3 to 2.4.0~beta4
I suppose that this is not a blocking issue so I moved it to the next run
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Updated by François ARMAND about 12 years ago
That error happens only on the first archiving attempt after a technique is removed, what is even more strange.
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 2.4.0~beta5 to 2.4.0~rc1
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Updated by François ARMAND about 12 years ago
It was decided that in the case were some directives are in error, we don't archive them, so that the archive contains as much directive as possible.
Updated by Jonathan CLARKE about 12 years ago
François ARMAND wrote:
It was decided that in the case were some directives are in error, we don't archive them, so that the archive contains as much directive as possible.
Yes, but only so long as we display a clear warning message to the user with a list of problematic directives.
Updated by François ARMAND about 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 66f71f9a8ea1a6527af8449142a43d044d5f919d.
Updated by François ARMAND about 12 years ago
- Target version changed from 2.4.0~rc2 to 2.4.0~beta5
Updated by Nicolas CHARLES about 12 years ago
- Status changed from Pending technical review to Released
This looks valid, thank you Francois !