Bug 36900 - Failed UCS 4.0-0 test case: 00_base.90change_user_pwd_via_udm.test
Summary: Failed UCS 4.0-0 test case: 00_base.90change_user_pwd_via_udm.test
Status: CLOSED FIXED
Alias: None
Product: UCS Test
Classification: Unclassified
Component: UMC
Version: unspecified
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Stefan Gohmann
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-20 08:40 CET by Stefan Gohmann
Modified: 2023-03-25 06:47 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments
ucs-test.log (3.05 MB, application/text)
2014-11-20 08:40 CET, Stefan Gohmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-11-20 08:40:13 CET
Created attachment 6447 [details]
ucs-test.log

The following UCS 4.0 test case failed in Jenkins:
 00_base.90change_user_pwd_via_udm.test

Attached you find the ucs-test log file.

Please check if it is a problem in the test case. If it is a test case problem, please fix it.

If it is a problem with UCS 4.0, please file a bug against UCS 4 and disable this test case until the bug has been fixed in UCS 4.0

http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-0/job/Autotest%20MultiEnv/67/SambaVersion=s4,Systemrolle=master/
Comment 1 Dmitry Galkin univentionstaff 2014-11-21 16:45:09 CET
r56062 :
  * 00_base/90change_user_pwd_via_udm,
    60_umc-system/31_umc-service-user-authentication,
    60_umc-system/30_umc-service-user-modules,
    60_umc/04_policies,
    60_umc/06_non-ucr-policies:
    when modifying a 'policy-reference' via udm - pass it with an underscore
    instead of dash (Bug #36893, #36894, #36895, #36900, #36901).

Some details about changes are in Bug #36893
Comment 2 Dmitry Galkin univentionstaff 2014-11-25 10:10:22 CET
Test has to be adapted a bit more to changes in UCS 4.0
Comment 3 Dmitry Galkin univentionstaff 2014-11-25 14:41:08 CET
(In reply to Dmitry Galkin from comment #2)
> Test has to be adapted a bit more to changes in UCS 4.0

Actually, renamed and re-wrote the whole script. Like the original test -> it changes own user password via the UMC request, but since there is no need for 'acl' and 'udm-self' policy -> that stuff is removed. Request format itself changed too. Perhaps, the test should also be moved to another section (60-umc for instance).

r56125:
  * 00_base/90change_user_pwd_via_umcp: test user own password change via
    '/umcp/set' command (Bug #36900).
Comment 4 Stefan Gohmann univentionstaff 2015-10-31 08:27:31 CET
It failed again:

*** BEGIN *** ['/usr/bin/python', '90change_user_pwd_via_umcp'] ***
*** 01_base/90change_user_pwd_via_umcp *** Test password change via UMC (/umcp/set) by the user itself. ***
*** START TIME: 2015-10-30 19:25:37 ***
Creating container/cn object with {'position': 'dc=AutoTest091,dc=local', 'name': 'ucs_test_rdnmh0uazz'}
Cleanup after exception: <class 'univention.testing.udm.UCSTestUDM_CreateUDMObjectFailed'> {'returncode': 3, 'stdout': "LDAP Error: Can't contact LDAP server\n", 'stderr': '', 'module': 'container/cn', 'kwargs': {'position': 'dc=AutoTest091,dc=local', 'name': 'ucs_test_rdnmh0uazz'}}
Performing UCSTestUDM cleanup...
UCSTestUDM cleanup done
Traceback (most recent call last):
  File "90change_user_pwd_via_umcp", line 67, in <module>
    name='ucs_test_' + uts.random_string())
  File "/usr/lib/pymodules/python2.7/univention/testing/udm.py", line 188, in create_object
    raise UCSTestUDM_CreateUDMObjectFailed({'module': modulename, 'kwargs': kwargs, 'returncode': child.returncode, 'stdout': stdout, 'stderr': stderr})
univention.testing.udm.UCSTestUDM_CreateUDMObjectFailed: {'returncode': 3, 'stdout': "LDAP Error: Can't contact LDAP server\n", 'stderr': '', 'module': 'container/cn', 'kwargs': {'position': 'dc=AutoTest091,dc=local', 'name': 'ucs_test_rdnmh0uazz'}}
*** END TIME: 2015-10-30 19:25:38 ***
Comment 5 Stefan Gohmann univentionstaff 2015-10-31 09:00:04 CET
It seems the LDAP server was not available while the test case was trying to create a container. I've added a timeout for that case.
Comment 6 Stefan Gohmann univentionstaff 2015-12-29 14:41:41 CET
Looks better now.
Comment 7 Stefan Gohmann univentionstaff 2016-10-12 07:48:22 CEST
For this bug is no separate QA needed.