Actions
Bug #2636
closedMigration from Rudder 2.3 to 2.4 complains about variable parsing in LDAP
Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If I try to migrate Rudder 2.3 to 2.4, all seems to work perfectly until the application is started.
Extract from the /var/log/rudder/webapp/XXXXX.stderrout.log:
18:11:46.601 [main] ERROR com.normation.rudder.domain.RudderLDAPConstants - Can not parse variable 'R0VORVJJQ19GSUxFX0NPTlRFTlRfUEFZTE9BRFsyXTojIFJ1ZGRlciBtYW5hZ2VzIHRoaXMgZmlsZQ0KcGFzc3dvcmQgcmVxdWlyZWQgICAgICAgcGFtX3B3Y2hlY2suc28gIG1kNSB1c2VfY3JhY2tsaWINCnBhc3N3b3JkIHJlcXVpcmVkICAgICAgIHBhbV9jcmFja2xpYi5zbyB1c2VfYXV0aHRvayByZXRyeT01IG1pbmxlbj0xMiB1Y3JlZGl0PS0xIGRjcmVkaXQ9LTENCnBhc3N3b3JkIHJlcXVpcmVkICAgICBwYW1fdW5peDIuc28gICAgbWQ1IHVzZV9maXJzdF9wYXNzIHVzZV9hdXRodG9r', bad pattern. That variable will be ignored 18:11:46.602 [main] ERROR com.normation.rudder.domain.RudderLDAPConstants - Can not parse variable 'R0VORVJJQ19GSUxFX0NPTlRFTlRfUEFZTE9BRFszXTojIFJ1ZGRlciBtYW5hZ2VzIHRoaXMgZmlsZQ0Kc2Vzc2lvbiBvcHRpb25hbCAgIHBhbV9ta2hvbWVkaXIuc28NCnNlc3Npb24gICAgcmVxdWlyZWQgICAgcGFtX2xpbWl0cy5zbw0Kc2Vzc2lvbiAgcmVxdWlyZWQgICAgIHBhbV91bml4Mi5zbyAgICBkZWJ1ZyAjIHRyYWNlIG9yIG5vbmUNCnNlc3Npb24gIHJlcXVpcmVkICAgICAgIHBhbV9kZXZwZXJtLnNvDQpzZXNzaW9uICByZXF1aXJlZCAgICAgICBwYW1fcmVzbWdyLnNv', bad pattern. That variable will be ignored 18:11:46.602 [main] ERROR com.normation.rudder.domain.RudderLDAPConstants - Can not parse variable 'R0VORVJJQ19GSUxFX0NPTlRFTlRfUEFZTE9BRFswXTojIFJ1ZGRlciBtYW5hZ2VzIHRoaXMgZmlsZSINCmFjY291bnQgIHJlcXVpcmVkICAgICBwYW1fdW5peDIuc28=', bad pattern. That variable will be ignored 18:11:46.603 [main] ERROR com.normation.rudder.domain.RudderLDAPConstants - Can not parse variable 'R0VORVJJQ19GSUxFX0NPTlRFTlRfUEFZTE9BRFsxXTojIFJ1ZGRlciBtYW5hZ2VzIHRoaXMgZmlsZQ0KYXV0aCAgIHJlcXVpcmVkICAgIHBhbV9lbnYuc28NCmF1dGggICAgIHJlcXVpcmVkICAgICBwYW1fdW5peDIuc28gICAgI3NldF9zZWNycGM=', bad pattern. That variable will be ignored 18:11:46.617 [main] ERROR net.liftweb.http.provider.HTTPProvider - Failed to Boot! Your application may not run properly java.util.NoSuchElementException: key not found: GENERIC_FILE_CONTENT_DELETION_BOOLEAN
It could be the rudder-upgrade script which convert base64 entries (entry::) to not base64 (entry:).
Updated by Jonathan CLARKE over 12 years ago
- Status changed from New to In progress
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
I'm on it.
Looks like the LDAP migration script is reinserting base64 values where they should be decoded first.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:4f25a56372bc73634c5b637458abd6867d1d7264.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions