Bug 798368
Summary: | Automembership plugin fails to create member attributes, if groups are located other than the replication suffix | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sankar Ramalingam <sramling> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 14 | CC: | edewata, nhosoi, nkinder, rmeggins |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-14 20:29:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sankar Ramalingam
2012-02-28 18:13:02 UTC
The Automembership plug-in ignores replicated operations. This means that the member attribute is simply replicated from the originating master to the replicas. The Automembership plug-in on the replica does not get triggered to create the member attribute for the replicated new user entry. With the scenario that you are testing, you are replicating the user portion of the tree (which is in one backend database), but the groups are in another non-replicated tree (another backend database). This means that the member attribute that is added to the group is outside of the scope of replication, hence it will never be replicated. As mentioned in the previous paragraph, the replicated user that is being added will not trigger the Automembership plug-in on the replicas by design. I would not consider this issue to be a bug. Having the groups in a non-replicated backend while the users are in a replicated backend is not a sensible use-case. If your groups and users are all within the replicated backend, things should work just fine since the member attributes in the group entries will be replicated. Have you tested this case? |