On 03/28/2017 09:34 PM, William Brown wrote:
> Hi Mark,
>
> Could this be related to the change you made for minage? You did change
> the internal_op setting, perhaps this required it? 
My change only affected the password minimum age check.  This is a
failure in password history.  This test passes for me on my laptop - so
perhaps we need a longer sleep?   I've found that all the password
policy tests require a sleep between making the password update and
checking the result
>
>
>> =================================== FAILURES 
>> ===================================
>> _____________________ test_ticket48228_test_subtree_policy 
>> _____________________
>>
>> topology_st = <lib389.topologies.TopologyMain object at 0x7f52d0432850>
>>
>>     def test_ticket48228_test_subtree_policy(topology_st):
>>         """
>>         Check subtree level password policy
>>         """
>>     
>>         log.info('\''        Set inhistory = 6'\'')
>>         set_subtree_pwpolicy(topology_st)
>>     
>>         log.info('\''        Bind as directory manager'\'')
>>         log.info("Bind as %s" % DN_DM)
>>         topology_st.standalone.simple_bind_s(DN_DM, PASSWORD)
>>     
>>         log.info('\''        Add an entry'\'' + USER2_DN)
>>         try:
>>             topology_st.standalone.add_s(
>>                 Entry((USER2_DN, {'\''objectclass'\'': "top person 
>> organizationalPerson inetOrgPerson".split(),
>>                                   '\''sn'\'': '\''2'\'',
>>                                   '\''cn'\'': '\''user 2'\'',
>>                                   '\''uid'\'': '\''user2'\'',
>>                                   '\''givenname'\'': '\''user'\'',
>>                                   '\''mail'\'': '\''us...@example.com'\'',
>>                                   '\''userpassword'\'': '\''password'\''})))
>>         except ldap.LDAPError as e:
>>             log.fatal('\''test_ticket48228: Failed to add user'\'' + 
>> USER2_DN + '\'': error '\'' + e.message['\''desc'\''])
>>             assert False
>>     
>>         log.info('\''        Update the password of '\'' + USER2_DN + '\'' 6 
>> times'\'')
>>>       update_passwd(topology_st, USER2_DN, '\''password'\'', 6)
>> <http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-NIGHTLY/ws/source/389-ds-base/dirsrvtests/tests/tickets/ticket48228_test.py>:224:
>>  
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>> _ _ 
>>
>> topology_st = <lib389.topologies.TopologyMain object at 0x7f52d0432850>
>> user = '\''uid=user2,dc=example,dc=com'\'', passwd = '\''password'\'', times 
>> = 6
>>
>>     def update_passwd(topology_st, user, passwd, times):
>>         cpw = passwd
>>         for i in range(times):
>>             log.info("               Bind as {%s,%s}" % (user, cpw))
>>             topology_st.standalone.simple_bind_s(user, cpw)
>>             cpw = '\''password%d'\'' % i
>>             try:
>>                 topology_st.standalone.modify_s(user, [(ldap.MOD_REPLACE, 
>> '\''userpassword'\'', cpw)])
>>             except ldap.LDAPError as e:
>>                 log.fatal(
>>                     '\''test_ticket48228: Failed to update the password '\'' 
>> + cpw + '\'' of user '\'' + user + '\'': error '\'' + e.message[
>>                         '\''desc'\''])
>>                 assert False
>>             time.sleep(1)
>>     
>>         # checking the first password, which is supposed to be in history
>>         inhistory = check_passwd_inhistory(topology_st, user, cpw, passwd)
>>>       assert inhistory == 1
>> E       assert 0 == 1
>>
>> <http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-NIGHTLY/ws/source/389-ds-base/dirsrvtests/tests/tickets/ticket48228_test.py>:135:
>>  AssertionError
>> ----------------------------- Captured stderr call 
>> -----------------------------
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:     Set inhistory = 6
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:     +++++ Enable subtree 
>> level password policy +++++
>>
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Add the 
>> container
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Add the 
>> password policy subentry {passwordHistory: on, passwordInHistory: 6}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Add the COS 
>> template
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Add the COS 
>> definition
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:     Bind as directory 
>> manager
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:Bind as cn=Directory Manager
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:     Add an 
>> entryuid=user2,dc=example,dc=com
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:     Update the password of 
>> uid=user2,dc=example,dc=com 6 times
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password0}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password1}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password2}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password3}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password4}
>> INFO:dirsrvtests.tests.tickets.ticket48228_test:             Bind as 
>> {uid=user2,dc=example,dc=com,password5}
>> ______________________________ test_delete_entry 
>> _______________________________
>>
>> topo = <lib389.topologies.TopologyMain object at 0x7f52c756bd50>
>> test_entry = None
>>
>>     def test_delete_entry(topo, test_entry):
>>         """Check that entry deletion is replicated after delete operation
>>     
>>         :ID: 18437262-9d6a-4b98-a47a-6182501ab9bc
>>         :feature: Multi master replication
>>         :setup: Four masters replication setup, an entry
>>         :steps: 1. Delete the entry from master1
>>                 2. Wait for replication to happen
>>                 3. Check entry on all other masters
>>         :expectedresults: Entry deletion should be replicated
>>         """
>>     
>>         log.info('\''Deleting entry {} during the 
>> test'\''.format(TEST_ENTRY_DN))
>>         topo.ms["master1"].delete_s(TEST_ENTRY_DN)
>>     
>>         entries = get_repl_entries(topo, TEST_ENTRY_NAME, ["uid"])
>>>       assert not entries, "Entry deletion {} wasn'\''t replicated 
>>> successfully".format(TEST_ENTRY_DN)
>> E       AssertionError: Entry deletion uid=mmrepl_test,dc=example,dc=com 
>> wasn'\''t replicated successfully
>> E       assert not [dn: uid=mmrepl_test,dc=example,dc=com\nuid: 
>> mmrepl_test\n\n, dn: uid=mmrepl_test,dc=example,dc=com\nuid: 
>> mmrepl_test\n\n, dn: uid=mmrepl_test,dc=example,dc=com\nuid: mmrepl_test\n\n]
>>
>> <http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-NIGHTLY/ws/source/389-ds-base/dirsrvtests/tests/suites/replication/acceptance_test.py>:154:
>>  AssertionError
>> ---------------------------- Captured stderr setup 
>> -----------------------------
>> INFO:dirsrvtests.tests.suites.replication.acceptance_test:Adding entry 
>> uid=mmrepl_test,dc=example,dc=com
>> ----------------------------- Captured stderr call 
>> -----------------------------
>> INFO:dirsrvtests.tests.suites.replication.acceptance_test:Deleting entry 
>> uid=mmrepl_test,dc=example,dc=com during the test
>> INFO:dirsrvtests.tests.suites.replication.acceptance_test:Wait for 
>> replication to happen
>> =================== 2 failed, 500 passed in 10973.19 seconds 
>> ==================='
>> + '[' 1 -ne 0 ']'
>> + echo CI Tests 'FAILED!'
>> CI Tests FAILED!
>> + MSG=FAILED
>> + RC=1
>> + sudo /usr/sbin/sendmail mreyno...@redhat.com firsty...@redhat.com
>> + sudo rm -rf /var/tmp/slapd.vg.28550 /var/tmp/slapd.vg.50045 
>> /var/tmp/slapd.vg.50147 /var/tmp/slapd.vg.58762
>> + exit 1
>> Build step 'Execute shell' marked build as failure
>> _______________________________________________
>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>
>
> _______________________________________________
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

_______________________________________________
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

Reply via email to