Steps to reproduce

1. In LDAP, create a user 'mofli' and add him to group 'koalas'.
2. Create a LDAP connector directory in Crowd, synchronise the directory.
3. In Crowd, navigate to view the groups user 'mofli' is in. Crowd should report 'mofli' is a member of 'koalas'.
4. In the LDAP server, remove group 'koalas'.
5. Back in Crowd, before sync happens, remove membership of 'mofli' to 'koalas'.

Expected behaviour

Crowd reacts gracefully, and either informs about the problem, or eventually reports that the operation has been 'done'. In any case, 'mofli' should not be a member of 'koalas' anymore.

Observed behaviour

Crowd reports 'Update successful', but still shows that 'mofli' is a member of 'koalas'. A stacktrace appears in the logs:

2013-09-11 09:27:57,329 http-bio-8095-exec-6 ERROR [console.action.principal.UpdateGroups] Group <koalas> does not exist
com.atlassian.crowd.exception.GroupNotFoundException: Group <koalas> does not exist
	at com.atlassian.crowd.directory.SpringLDAPConnector.findGroupWithAttributesByName(SpringLDAPConnector.java:1122)
	at com.atlassian.crowd.directory.SpringLDAPConnector.findGroupByName(SpringLDAPConnector.java:1104)
	at com.atlassian.crowd.directory.MicrosoftActiveDirectory.removeUserFromGroup(MicrosoftActiveDirectory.java:234)
	at com.atlassian.crowd.directory.DbCachingRemoteDirectory.removeUserFromGroup(DbCachingRemoteDirectory.java:776)
	at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.removeUserFromGroup(DirectoryManagerGeneric.java:824)
...
	at com.atlassian.crowd.console.action.principal.UpdateGroups.doRemoveGroups(UpdateGroups.java:64)

Notes

• The problem can also be reproduced by renaming the group in LDAP.
• The membership eventually disappears when the directory is synchronised again (FULL sync).