Bug 46583 - App xrdp does not pass test 53_samba-common.35smbclient_auth.test
App xrdp does not pass test 53_samba-common.35smbclient_auth.test
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: xrdp
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-11 14:49 CET by Dirk Wiesenthal
Modified: 2021-05-14 16:38 CEST (History)
2 users (show)

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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2018-03-11 14:49:56 CET
Reproducable on a DC Master with samba4:

*** BEGIN *** ['/usr/bin/python', '35smbclient_auth'] ***
*** 53_samba-common/35smbclient_auth *** Check whether several parallel smbclient authentifications are possible ***
*** START TIME: 2018-03-11 14:45:57 ***
Configured for 3 times 8 processes in 6s.
Create homedir/mount
Multifile: /etc/pam.d/common-session
Creating users/user object with /usr/sbin/udm-test users/user create --position cn=users,dc=sparka-4-2,dc=intranet --set username=gq2xbuuf7c --set password=h5ehmeefak --set firstname=z5vj5ty96o --set lastname=avmb6gm8eo
Waiting for DRS replication, filter: 'cn=gq2xbuuf7c' 
DRS replication took 0 seconds
Waiting for DRS replication...
Waiting for DRS replication, filter: '(sAMAccountName=gq2xbuuf7c)' 
DRS replication took 0 seconds
Starting parallel authentication...
Round 0...
Forking 8 processes...
Round 1...
Forking 8 processes...
Round 2...
Forking 8 processes...
0: 5 < 24
1: 5 < 24
2: 5 < 24
3: 5 < 24
4: 5 < 24
5: 5 < 24
6: 5 < 24
7: 5 < 24
8: 5 < 24
9: 5 < 24
10: 5 < 24
11: 5 < 24
12: 5 < 24
13: 5 < 24
14: 5 < 24
15: 5 < 24
16: 5 < 24
17: 5 < 24
18: 5 < 24
19: 5 < 24
20: 5 < 24
21: 5 < 24
22: 5 < 24
23: 5 < 24
24: 5 < 24
25: 5 < 24
26: 5 < 24
27: 5 < 24
28: 5 < 24
29: 5 < 24
5 of 24 have been successfull.
### FAIL ###
Cleanup after exception: <type 'exceptions.SystemExit'> 1
Performing UCSTestUDM cleanup...
removing DN: uid=gq2xbuuf7c,cn=users,dc=sparka-4-2,dc=intranet
trying to restart UDM CLI server
sending signal 15 to process 32544 (['/usr/bin/python2.7', '/usr/share/univention-directory-manager-tools/univention-cli-server'])
process already terminated
UCSTestUDM cleanup done
Unsetting homedir/mount
Multifile: /etc/pam.d/common-session
*** END TIME: 2018-03-11 14:46:54 ***
*** TEST DURATION (H:MM:SS.ms): 0:00:56.903111 ***
*** END *** 1 ***
Comment 1 Dirk Wiesenthal univentionstaff 2018-03-11 14:51:29 CET
5 of 24 have been successful. Maybe just performance? Tagging 4.3 until decision.
Comment 2 Stefan Gohmann univentionstaff 2018-03-11 16:39:24 CET
(In reply to Dirk Wiesenthal from comment #1)
> 5 of 24 have been successful. Maybe just performance? Tagging 4.3 until
> decision.

It doesn't seem to be a general issue. Moving to erratum.
Comment 3 Ingo Steuwer univentionstaff 2021-05-14 16:38:21 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.