Bug 35693 - Test 51_samba4.52replication_sysvol.test failed in jenkins
Test 51_samba4.52replication_sysvol.test failed in jenkins
Status: CLOSED WORKSFORME
Product: UCS Test
Classification: Unclassified
Component: Samba
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks: 56645
  Show dependency treegraph
 
Reported: 2014-08-22 21:24 CEST by Dirk Wiesenthal
Modified: 2023-09-23 13:42 CEST (History)
1 user (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.
Comment 1 Dirk Wiesenthal univentionstaff 2014-08-28 09:17:29 CEST
This time Slave S4:

Fehlermeldung

Test failed

Standard Ausgabe (STDOUT)

## create the GPO '85Wd8PiK' on remote DC master105.autotest105.local
## GPO was created on master105.autotest105.local with ID {F1227957-DB28-4657-ACA3-CF3554072AF0}
## check whether the directory has been created on remote DC master105.autotest105.local
## check whether samba-tool lists the GPO on remote DC master105.autotest105.local
## check whether the directory for the GPO has been replicated to the local system (waiting about 300 seconds)
## Note: to speed things up for interactive tests, you may run /usr/share/univention-samba4/scripts/sysvol-sync.sh manually now.

GPO {F1227957-DB28-4657-ACA3-CF3554072AF0} deleted.

Standard Fehler (STDERR)

error 2014-08-27 17:50:39	 Directory for GPO has not been created
error 2014-08-27 17:50:39	 **************** Test failed above this line (1) ****************
Comment 2 Stefan Gohmann univentionstaff 2015-03-24 20:36:12 CET
Please reopen if it still fails.
Comment 3 Stefan Gohmann univentionstaff 2016-10-12 07:49:21 CEST
For this bug is no separate QA needed.