Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When creating an entry having an automembership rule which assign it to a group which does not exist, the entry is created successfully.
Only an INFO message is logged in the errors log (starting with fix for bz759142).
Prior to fix for bz1689313, creation of such an entry was rejected.
As the behavior has changed, and as having only an INFO message being logged in the errors log, lost amongst many other INFO messages, does not allow the user to be clearly aware of the potential issue with the entry creation, it would be useful to have a warning message displayed on the client side, as output of the cli.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.10.2-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. enable the memberof plugin
2. Add a configuration entry for the auto Membership Plugin, autoMemberDefaultGroup value being a non existing group. For example :
dn: cn=test users,cn=Auto Membership Plugin,cn=plugins,cn=config
objectclass: autoMemberDefinition
autoMemberScope: ou=People,dc=example,dc=com
autoMemberFilter: objectclass=nsView
autoMemberDefaultGroup: cn=invalid group,ou=Groups,dc=example,dc=com
autoMemberGroupingAttr: uniqueMember:dn
3. create en entry part of the autoMemberScope of the auto Membership plugin definition, having an attribute matching the autoMemberFilter. For example :
dn: ou=test view,ou=People,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
objectClass: nsView
ou: test view
description: test view
Or run existing test ds/dirsrvtests/tests/suites/automember_plugin/automember_test.py::test_no_default_group
Actual results:
Entry is created successfully, no warning is issued on the cli output, only an INFO message is logged in the errors log
Expected results:
An INFO message is logged in the errors log, and a warning message is displayed on the client side, as output of the cli
Additional info:
Comment 5RHEL Program Management
2021-10-06 07:27:20 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.