Bug #4393
closed
The default disclaimer message loaded initially into LDAP has an invalid charachter in it
Description
This issue is similar to the one addressed by http://www.rudder-project.org/redmine/issues/4032, however unlike that one, the typo is not in the policy but in the ldif file used to seed the LDAP database (file rudder-sources/rudder/rudder-core/src/main/resources/ldap/bootstrap.ldif).
When applied, the files have the line "...infrastructure to change back the server?s...".
What is annoying - after the parameter is changed manually via the web interface, the files touched by the disclaimer rule have both the correct and incorrect disclaimers and require manual intervention to fix affected files across the entire network population.
Updated by Alex Tkachenko almost 11 years ago
Note that the ldif file has the message encoded (I assume in the Unicode) so it is not directly evident.
Updated by Nicolas CHARLES almost 11 years ago
- Category set to Web - Config management
Thank you Alex for this bug report, indeed the stored ' is a ’ (non standart quote)
It hsould not fail, but it seems related to http://www.rudder-project.org/redmine/issues/4381 (non ascii text not always written)
Updated by Nicolas CHARLES almost 11 years ago
- Status changed from New to 8
Jon, which version should have a change in it ?
I believe we shouldn't do migration script (for it would duplicate the header), but should we dot he change in 2.10 or in 2.7 (when parameters where introduced)
Updated by Jonathan CLARKE almost 11 years ago
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
Nicolas CHARLES wrote:
Jon, which version should have a change in it ?
I believe we shouldn't do migration script (for it would duplicate the header), but should we dot he change in 2.10 or in 2.7 (when parameters where introduced)
I agree that we shouldn't write a migration for this - it would cause a lot of unwanted changes to files.
Let's change it for new installs (ie in the LDIF files, IIRC), from the branch where it appeared (2.7 IIUC).
Updated by Nicolas CHARLES almost 11 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/437
PR is there: https://github.com/Normation/rudder/pull/437
Updated by Nicolas CHARLES almost 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 5ad0b6cd7bf186c180da70789249ee4fd2eb1a95.
Updated by Vincent MEMBRÉ almost 11 years ago
Applied in changeset bd9e496b1d210aa8888ece776f5aff4b4a4602ef.
Updated by Vincent MEMBRÉ almost 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.3, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000079.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/