Rudder

So, we have 0 property known on the intersection group.
If we add one, we have a success:

But then, when the refresh request comes, we don't have properties again:

And we do have it in the LDAP:

And API for the group returns it:

✦ [16:29:34]❯ curl -k  -H "X-API-Token:dTxvl4eL8p3YqvwefVbaJLdy8DyEt7Vw" -H "Content-Type: application/json" -X GET 'http://localhost:8082/rudder-web/api/latest/groups/4e0c8aca-47f4-45b4-9b68-45b23ecafcde' | jq '.'
{
  "action": "groupDetails",
  "id": "4e0c8aca-47f4-45b4-9b68-45b23ecafcde",
...
        "properties": [
          {
            "name": "conflicting",
            "value": "plop" 
          }
        ],
...
}

But not the inherited one:

{
  "action": "groupInheritedProperties",
  "id": "4e0c8aca-47f4-45b4-9b68-45b23ecafcde",
  "result": "success",
  "data": {
    "groups": [
      {
        "groupId": "4e0c8aca-47f4-45b4-9b68-45b23ecafcde",
        "properties": []
      }
    ]
  }
}

So something is broken for inherited properties algo for that group.

So, my screen etc were in the case where there is 0 node in the resulting group.
Because since in Group API, we check for the children node to check if there isn't any incompatibily (while on that case, we can just skip the check completely).

And when there is actually node, we get an error saying "that property is both in group A and group B with different values, you need to create a group to disambiguate" - which is exactly what the group is doing, so we need to understand why it says so.
This is likely due to the fact that the algo doesn't check if the current merge is done for a node or for a group. If we have that case for a node, it's a problem, but if it's for a group, it's a solution.

Finaly, the error is transmitted via API in JSON, but it's not displayed in the error notification.

This is solved in 8.2 thanks to the changes in properties computation and their error reporting, espacially: https://issues.rudder.io/issues/25219 https://issues.rudder.io/issues/25528.

I think we won't be able to correct it in 8.1, nor backport the changes, which are massives.