Red Hat Bugzilla – Bug 768510
migrate-ds : misleading error message when invalid objectclass defined
Last modified: 2013-02-21 04:08:57 EST
Description of problem: If you define the correct user/group container but an invalid objectclass for the migrate-ds command, you get the following error .... ipa: ERROR: Container for user not found OR ipa: ERROR: Container for group not found This is confusing as the container is not the problem. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: ds-migration-cmd-004 Invalid User Object Class :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [15:32:55] :: EXECUTING: ipa migrate-ds --user-container="ou=People" --group-container="ou=groups" --user-objectclass=badclass ldap://dhcp-185-164.testrelm:389 ipa: ERROR: Container for user not found :: [ PASS ] :: Check return code :: [ FAIL ] :: File '/tmp/error.out' should contain 'ipa: ERROR: Objectclass for user not found' :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: ds-migration-cmd-005 Invalid Group Object Class :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [15:32:59] :: EXECUTING: ipa migrate-ds --user-container="ou=People" --group-container="ou=groups" --group-objectclass=badclass ldap://dhcp-185-164.testrelm:389 ipa: ERROR: Container for group not found :: [ PASS ] :: Check return code :: [ FAIL ] :: File '/tmp/error.out' should contain 'ipa: ERROR: Objectclass for group not found' Version-Release number of selected component (if applicable): ipa-server-2.1.3-9 How reproducible: always Steps to Reproduce: 1. These tests are automated and will be verified when tests are passing. 2. 3. Actual results: Expected results: Additional info:
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2206
Fixed upstream: master: https://fedorahosted.org/freeipa/changeset/d31f0c2d330488e6b351f36d5a8f4f0affda935b We cannot verify that the object class is right, user may use any custom object classes for the remote LDAP search. What we did is that the error message now does not mention the container specifically, but is more general and includes the remote LDAP search attributes which should help user discover the error.
verified :: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: ds-migration-cmd-004 Invalid User Object Class :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: EXECUTING: ipa migrate-ds --user-container="ou=People" --group-container="ou=groups" --user-objectclass=badclass ldap://qe-blade-13.testrelm.com:389 :: [ PASS ] :: Check return code :: [ PASS ] :: File '/tmp/error.out' should contain 'ipa: ERROR: user LDAP search did not return any result (search base: ou=People,dc=example,dc=com, objectclass: badclass)' :: [ LOG ] :: Related Bugzilla :: https://bugzilla.redhat.com/show_bug.cgi?id=768510 :: [ LOG ] :: Duration: 3s :: [ LOG ] :: Assertions: 2 good, 0 bad :: [ PASS ] :: RESULT: ds-migration-cmd-004 Invalid User Object Class :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: ds-migration-cmd-005 Invalid Group Object Class :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: EXECUTING: ipa migrate-ds --user-container="ou=People" --group-container="ou=groups" --group-objectclass=badclass ldap://qe-blade-13.testrelm.com:389 :: [ PASS ] :: Check return code :: [ PASS ] :: File '/tmp/error.out' should contain 'ipa: ERROR: group LDAP search did not return any result (search base: ou=groups,dc=example,dc=com, objectclass: badclass)' :: [ LOG ] :: Related Bugzilla :: https://bugzilla.redhat.com/show_bug.cgi?id=768510 :: [ LOG ] :: Duration: 3s :: [ LOG ] :: Assertions: 2 good, 0 bad :: [ PASS ] :: RESULT: ds-migration-cmd-005 Invalid Group Object Class version :: ipa-server-3.0.0-21.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html