Grouper Users - Open Discussion List

[Akki Kumar <>]

Hi Chris,

Grouper is having a problem when we run the grouper loader for the First time. Looks like Grouper loader does not add members until we manually delete Group B from Group A and then re-run the loader.

Testing Behavior:

During testing in the debug more, we noticed that when we remove membership of the Group B from Group A and then re-run the loader, all members are added correctly and log contain GrouperLoaderType.syncOneMemberAddMemberLogic statements.

2017-02-16 11:10:34,500: [pool-1-thread-107] DEBUG GrouperLoaderType.syncOneMemberAddMemberLogic(3737) -  - Group: College:Departments:Information Tech - All add Subject groupName: College:Departments:Information Tech:Networking Dept - All, sourceId: g:gsa, alreadyAdded: false

2017-02-16 11:10:34,500: [pool-1-thread-107] DEBUG GrouperLoaderType.syncOneMemberAddMemberLogic(3737) -  - Group: College:Departments:Information Tech - All add Subject groupName: College:Departments:Information Tech:Networking Dept - All, sourceId: g:gsa, alreadyAdded: false

Whereas, when we run the loader first time, log do not have GrouperLoaderType.syncOneMemberAddMemberLogic statement in it. 

Questions:

* Is there any reason why grouper loader do not run GrouperLoaderType.syncOneMemberAddMemberLogic statement during the initial loader run?

* Is there command that we can manually run using gsh that would check and add missing members of the linked group?

Note: We ran new edu.internet2.middleware.grouper.misc.AddMissingGroupSets().addAllMissingGroupSets(); on gsh, but members were not added to the group.

Any guidance is truly appreciated.

Thank you,

Akki

On Tue, Feb 14, 2017 at 1:06 AM, Hyzer, Chris <> wrote:

When you have the problem, does running this from GSH help?

 

new edu.internet2.middleware.grouper.misc.AddMissingGroupSets().addAllMissingGroupSets();

 

Shilen, you have other ideas?

 

Thanks

Chris

 

From: Stephen A Sazama [mailto:]
Sent: Monday, February 13, 2017 4:39 PM
To: Hyzer, Chris <>;
Cc: Akki Kumar <>
Subject: Re: [grouper-users] Re: Hierarchical Loader Bug

 

Hi,

 

I work with Akki. What we're trying to do with the second loader is assign all sub-department groups as members of their parent departments (creating rollup groups). So if Group A is the parent department of Group B, and Group B is the parent department of Group C, then Group A has one direct member (B) and B has one direct member (C). They also have some other members that are people from LDAP. The behavior we're seeing is that in this scenario:

- Group B shows up as a direct member of A (correct).

- Group B's people members show up as indirect members of A (correct).

- Group C shows up as an indirect member of A (correct).

- Group C's people members do NOT show up as members of A (unexpected).

 

Departmental groups with a depth of 2 or more do not have their LDAP subjects added as indirect members of the top-level parent department, even though the group containing them is an indirect member. We were wondering if anyone else has seen this behavior. Are there any cases in Grouper where a group's members are not supposed to be inherited by groups of which it is a member, or any kind of caching we should look out for? Apparently, if we remove the membership linking A to B/C and then re-run the loader, the members are all added correctly.

 

Thanks again,

Stephen Sazama

 

On Fri, Feb 10, 2017 at 10:53 AM, Akki Kumar <> wrote:

Hi Chris,

 

I have attached below screenshots (https://drive.google.com/drive/folders/0BwgGnZC7vA-6eFVUMThjUzNWc0k):

• Departmental Loader - Configuration
• Rollup Loader - Configuration
• Departmental.jpg – Showing folders and group’s structure.
• Hierarchy 1.jpg – Showing Networking Apps group with one member added to it.
• Hierarchy 2.jpg – Showing Networking Research group with one member added to it.
• Hierarchy 3.jpg – Showing Networking Dept - All group is linked directly to the subgroups (Networking Apps & Networking Research) and members are added indirectly to it.
• Hierarchy 4.jpg – Showing Information Tech - All group is linked directly to the subgroups (Networking Dept - All) and members are not added to the group (BUG).

 

Issue: As shown in the Hierarchy 4.jpg screenshot, in the top level group (Information Tech – All), the subgroups are linked, but the members from the subgroups are not shown (after loader run). However, after manually deleting the Networking Dept – All group from the top level group, and re-running the loader, the members are shown in the top level group (Refer to screenshot Manually Delete.jpg). Not sure why grouper loader only links all members after manually deleting the group from the top level. Any guidance is truly appreciated.

 

Please let me know if you need more details.

 

Thank you,

Akki

 

On Thu, Feb 9, 2017 at 4:06 PM, Hyzer, Chris <> wrote:

I understand you have a problem but I cant really understand what it is by your email.  Can you send along the loader configuration and be a little more explicit with screenshots etc?

 

Thanks

Chris

 

 

From: Akki Kumar [mailto:]
Sent: Thursday, February 09, 2017 3:21 PM
To: Hyzer, Chris <>;
Subject: Hierarchical Loader Bug

 

Hi Chris,

 

I created Organization Hierarchical groups using two loaders:

• Departmental Hierarchy
• Rollup Hierarchy

 

When I ran the Rollup Hierarchy loader, and it link group as described below (screenshot):

1)  All groups under Networking Dept folder are linked to the Networking Dept – All group, and it shows all linked group members under the Networking Dept – All. (Expected Behavior)

2)  All groups under Networking Dept – All group are futher linked to the Information Tech – All group, but it didn’t show members of the sub-groups (such as Networking Dept group). (Bug)

Screenshot link: https://drive.google.com/drive/folders/0BwgGnZC7vA-6eFVUMThjUzNWc0k

 

 

However, during testing, I noticed that when I manually delete the Networking Dept – All group from the Information Tech – All group and then re-run the Rollup Hierarchies loader, it would link the Networking Dept – All groups and also show all members of its sub-groups. As per logs, the loader is running successfully and there are no errors.

 

We are baffled by the loader behavior and checking to see if there are any solution for the bug. (We are using Grouper 2.2.2)

 

 

Thank you,

Akki