Bug 31680 - ucs-test on DC Backup
ucs-test on DC Backup
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Stefan Gohmann
Lukas Walter
: interim-1
Depends on: 31687 31766
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-10 07:24 CEST by Stefan Gohmann
Modified: 2013-11-19 06:43 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
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 Stefan Gohmann univentionstaff 2013-06-10 07:24:56 CEST
The test cases should be checked on a DC Backup.
Comment 1 Stefan Gohmann univentionstaff 2013-06-20 11:24:33 CEST
The test cases have been adapted. The current status for the different test environments is available here:
 http://jenkins.knut.univention.de:8080/job/autotest/lastCompletedBuild/testReport/

Depending on the test, wait_for_replication* might be useful functions.

Currently, no test fails on a DC Backup:
 http://jenkins.knut.univention.de:8080/job/autotest/SambaVersion=s3,Systemrolle=backup/
 http://jenkins.knut.univention.de:8080/job/autotest/SambaVersion=s4,Systemrolle=backup/
Comment 2 Arvid Requate univentionstaff 2013-06-26 18:37:59 CEST
I changed the order of the test setup: first create all records, then check all.
Comment 3 Lukas Walter univentionstaff 2013-08-20 17:30:35 CEST
Plenty of tests have failed in the last jenkins build.

http://jenkins:8080/view/Autotest/job/UCS%203.2%20Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=backup/lastCompletedBuild/testReport/
Comment 4 Arvid Requate univentionstaff 2013-08-20 21:23:24 CEST
The autotest-093-backup-s4.log shows:

=== setup-join.sh (2013-08-20 04:48:46) ===
[...]
**************************************************************************
* Join failed!                                                           *
* Contact your system administrator                                      *
**************************************************************************
__JOINERR__:FAILED: 03univention-directory-listener.inst
* Message:  FAILED: 03univention-directory-listener.inst
**************************************************************************

For details see the join log:

http://jenkins.knut.univention.de:8080/job/UCS%203.2%20Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=backup/ws/join.log
Comment 6 Lukas Walter univentionstaff 2013-08-21 09:58:08 CEST
(In reply to Stefan Gohmann from comment #5)
> I think it was only a temporary jenkins / test repo problem. The last build
> was much better:
> 
> http://jenkins.knut.univention.de:8080/view/Autotest/job/UCS%203.
> 2%20Autotest%20MultiEnv/100/SambaVersion=s4,Systemrolle=backup/testReport/
> 
> http://jenkins.knut.univention.de:8080/view/Autotest/job/UCS%203.
> 2%20Autotest%20MultiEnv/100/SambaVersion=s3,Systemrolle=backup/testReport/

OK.
Comment 7 Stefan Gohmann univentionstaff 2013-11-19 06:43:32 CET
UCS 3.2 has been released:
 http://docs.univention.de/release-notes-3.2-en.html
 http://docs.univention.de/release-notes-3.2-de.html

If this error occurs again, please use "Clone This Bug".