Bug 28348 - ucs-test 50samba/35smbclient_auth an samba4 anpassen
ucs-test 50samba/35smbclient_auth an samba4 anpassen
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: Samba
unspecified
Other Linux
: P5 normal (vote)
: UCS 3.1-x
Assigned To: Arvid Requate
:
: 29452 (view as bug list)
Depends on:
Blocks: 28262
  Show dependency treegraph
 
Reported: 2012-08-28 13:23 CEST by Tobias Peters
Modified: 2023-03-25 06:48 CET (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 Tobias Peters univentionstaff 2012-08-28 13:23:50 CEST
Es soll eine an samba4 angepasste Version des samba3-Tests
35smbclient_auth erstellt werden.
Comment 1 Tobias Peters univentionstaff 2012-09-05 09:27:07 CEST
Es wurde eine an Samba4 angepasste Version erstellt und dem Paket ucs-test-samba4 hinzugefügt.
Comment 2 Tobias Peters univentionstaff 2012-11-29 13:23:50 CET
Der Test weist starke Schwankungen je nach Systemleistung bzw -auslastung auf und wird deshalb überarbeitet.
Comment 3 Tobias Peters univentionstaff 2012-11-29 13:26:06 CET
*** Bug 29452 has been marked as a duplicate of this bug. ***
Comment 4 Stefan Gohmann univentionstaff 2013-02-26 06:37:25 CET
Kein Blocker für UCS 3.1-1.
Comment 5 Stefan Gohmann univentionstaff 2013-03-11 08:15:42 CET
Der Test schlägt im Jenkins jede Nach fehl:
Fehlermeldung

Test failed

Standard Ausgabe (STDOUT)

Object created: uid=T5870a8484ba,cn=users,dc=eu-west-1,dc=compute,dc=amazonaws,dc=com
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Connection to \\ip36e4617a.eu-west-1.compute.amazonaws.com\sysvol failed - NT_STATUS_BAD_NETWORK_NAME
Using username "T5870a8484ba"
�
	Sharename       Type       Comment�
	---------       ----       -------�
	netlogon        Disk       Domain logon service�
	sysvol          Disk       �
	IPC$            IPC        IPC Service (Univention Corporate Server)�
	print$          Disk       Printer Drivers�
REWRITE: list servers not implemented�

/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
/usr/bin/smbclient4 -UT5870a8484ba%univention //ip36e4617a.eu-west-1.compute.amazonaws.com/sysvol
12�

12 of 24 have been successfull.
Object removed: uid=T5870a8484ba,cn=users,dc=eu-west-1,dc=compute,dc=amazonaws,dc=com


Auf meinem Testsystem schlägt der Test auch fehl, wenn ich den Timeout von 20 auf 90 erhöhe, dann ist der Test auf meinem Testsystem erfolgreich.
Comment 6 Arvid Requate univentionstaff 2013-03-25 16:47:10 CET
* Der Test sollte erstmal nur die Authentifikation gegen das lokale System testen, aktuell wird immer gegen ldap/master getestet. Dadurch sollte dann auch univention-ssh entfallen, da der Erfolgstest über das lokale Dateisystem erfolgen kann.
* Lieber smbclient statt smbclient4
Comment 7 Tobias Peters univentionstaff 2013-03-27 17:04:57 CET
Es wird nun die Authentifikation gegen das lokale System anstatt gegen ldap/master getestet. Zudem wurde smbclient4 durch smbclient ersetzt.
Comment 8 Arvid Requate univentionstaff 2013-06-25 20:59:32 CEST
The test was still flaky on Samba4 DC Slaves as DRS replication can take a long time (~300 seconds). The waiting code is now improved to actually wait for the account to appear in the local sam.ldb. changelog-3.2-0 is updated.
Comment 9 Stefan Gohmann univentionstaff 2016-10-12 07:48:33 CEST
For this bug is no separate QA needed.