Dear Stephen,
You could check that no object types or attribute names have vanished - something like
grep objectClass | sort | uniq
grep ^GLUE2 | cut -d: -f1 | sort | uniq
That seems to be fine: ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep objectClass | sort | uniq | wc -l 32 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h lcg-bdii -p 2170 -b o=glue | grep objectClass | sort | uniq | wc -l 32 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep ^GLUE2 | cut -d: -f1 | sort | uniq | wc -l 223 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h lcg-bdii -p 2170 -b o=glue | grep ^GLUE2 | cut -d: -f1 | sort | uniq | wc -l 223
(I haven't tested those so the syntax may not be quite right). Also I assume you checked for errors in the log? The only specific change is for Boolean attributes, so you could look for those and check they're the same. You could also perhaps try injecting the correct value, e.g. "true" rather than "TRUE".
There are no errors in the log. I can still see many "TRUE" and "FALSE" being published, but no "true" or "false". Should I tell the developers that they should be publishing "true" or "false" instead? ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep TRUE | sort | uniq -c 36 GLUE2ComputingManagerHomogeneous: TRUE 39 GLUE2ComputingManagerWorkingAreaShared: TRUE 131 GLUE2EntityOtherInfo: ArgusEnabled=TRUE 106 GLUE2ExecutionEnvironmentConnectivityIn: TRUE 433 GLUE2ExecutionEnvironmentConnectivityOut: TRUE 42 GLUE2ExecutionEnvironmentVirtualMachine: TRUE ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep FALSE | sort | uniq -c 7 GLUE2AdminDomainDistributed: FALSE 51 GLUE2ComputingManagerBulkSubmission: FALSE 15 GLUE2ComputingManagerHomogeneous: FALSE 49 GLUE2ComputingManagerWorkingAreaGuaranteed: FALSE 10 GLUE2ComputingManagerWorkingAreaShared: FALSE 269 GLUE2EntityOtherInfo: ArgusEnabled=FALSE 357 GLUE2ExecutionEnvironmentConnectivityIn: FALSE 30 GLUE2ExecutionEnvironmentConnectivityOut: FALSE Regards, Maria