Bug #4614
closed
A deleted group on a Rudder server A is still there on a Rudder server B after a synchronization of /var/rudder/configuration-repository
Added by Nicolas PERRON over 10 years ago.
Updated over 7 years ago.
Category:
System integration
Description
On a Rudder server A, a group is deleted but after a synchronization of the folder /var/rudder/configuration-repository (by git push) on a Rudder server B, the group is still present. The synchronization of the repository is followed by a post-hook which trigger a "restore archive".
Nevertheless, on the /var/rudder/configuration-repository, the XML file associated to the deleted group is present although Rudder should remove it and commit the change. The git log show only commits of archive.
I suppose a bug permitted to erase the group from the LDAP and not into the git.
- Category set to System integration
- Target version set to 2.10.14
- Target version changed from 2.10.14 to 2.10.15
- Target version changed from 2.10.15 to 2.10.16
- Target version changed from 2.10.16 to 2.10.17
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Status changed from New to Rejected
- Priority set to 0
I'm closing that ticket because it is about a non supported synchronization scheme and lacks a lot of thing to be able to analysis it further (basically, if the group is /var/rudder/configuration-repository, it is normal that the archive restaure does not delete it).
Even if the problem is "deleting a group does not correctly delete the corresponding xml file in /var/rudder/configuration-repository", the problem is either not here anymore (works as expected in 3.1.x) or the steps to reproduce it are not present.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by