A deleted group on a Rudder server A is still there on a Rudder server B after a synchronization of /var/rudder/configuration-repository
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.
#22 Updated by François ARMAND 10 months ago
- 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.