Skip to content

Allow proper GLUE2 bools in LDAP GLUE2 rendering - Fix for BUGZ-3929

nordugrid-arc-bot requested to merge floridop/arc:dev-glue2bools-Execenv into next

Begin arcbot message
This merge request is automatically copied from !1123 (merged) orginally made by @floridop
End arcbot message

## Allow proper GLUE2 bools in LDAP GLUE2 rendering - Fix for BUGZ-3929

Link to Bugzilla ticket

BUGZ-3929

Description

undefined bools would prevent some GLUE2 objects to be published in GLUE2 and correctly picked up by the client.

GLUE2 bools have three values (case sensitive) : true false undefined They were set to TRUE FALSE in the past due to legacy settings this prevented some objects like ExecutionEnvironments to be rendered correctly when things like ConnectivityIN/OUT where not specified, these values depend on nodeaccess=inbound|outbound in config This bug would mainly show up on LRMS that do not support ExecutionEnvironment information With this patch the info should be published independently from the LRMS support.

NOTE: clients of the infosys that rely on case may need to be review. I suggest the following line in release notes:

  • LDAP GLUE2 booleans are now consistent with the specification, their values are case sensitive "true,false,undefined" please review your LDAP clients if you rely on the previous representation, which was uppercase "TRUE,FALSE".

Testing of the clients against this change is also required, I do not know how much we rely on case in the clients.

Merge request reports