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.

Bug 742981

Summary: ipa-managed-entries : does not work : assuming DN being searched does not exist
Product: Red Hat Enterprise Linux 6 Reporter: Jenny Severance <jgalipea>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED WORKSFORME QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.1CC: dpal, mkosek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-13 22:34:32 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:
Bug Depends On:    
Bug Blocks: 756082    

Description Jenny Severance 2011-10-03 13:26:44 UTC
Description of problem:




# ipa-managed-entries -e "NGP Definition" status
cn=NGP Definition,cn=Definitions,cn=Managed Entries,cn=etc,dc=testrelm is not a valid Managed Entry


# ldapsearch -D "cn=Directory Manager" -w Secret123 -b "cn=Definitions,cn=Managed Entries,cn=etc,dc=testrelm"
# extended LDIF
#
# LDAPv3
# base <cn=Definitions,cn=Managed Entries,cn=etc,dc=testrelm> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 32 No such object
matchedDN: cn=etc,dc=testrelm

# numResponses: 1


Version-Release number of selected component (if applicable):
ipa-server-2.1.1-101.20111003T0058zgitaaa7c05.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Rob Crittenden 2011-10-03 18:57:34 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1915

Comment 3 Rob Crittenden 2012-01-13 16:56:25 UTC
What is the bug here? The problem is that there are NO managed entries definitions, is that what you are reporting?

Comment 4 Jenny Severance 2012-01-13 18:01:11 UTC
on F16 this now works ...

# ipa-managed-entries -e "NGP Definition" status
Plugin Enabled
You have new mail in /var/spool/mail/root
[root@dhcp-185-162 ~]# ipa-managed-entries -e "NGP Definition" disable
Disabling Plugin
[root@dhcp-185-162 ~]# ipa-managed-entries -e "NGP Definition" status
Plugin Disabled


It did not work when I tried it before.

Comment 5 Rob Crittenden 2012-01-13 19:02:52 UTC
Yes, I think at one time we had either an upgrade or install bug that left managed entries unconfigured. I'm not sure what, if anything, I need to do for this bug though.

The fact that we caught that it wasn't configured right is probably a good thing, and it does seem to be configured properly, so should this be closed already fixed?

Comment 6 Jenny Severance 2012-01-13 19:10:19 UTC
I think we should close works for me.  If we run into any issues during automating the testing ... we can open issues for those specific reasons.

Comment 7 Rob Crittenden 2012-01-13 22:34:32 UTC
Agreed, closed.