Bug 37973 - Test rename_class script should be run on the slave in a multi server env
Test rename_class script should be run on the slave in a multi server env
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: ucs-test
UCS@school 4.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks: 36784
  Show dependency treegraph
 
Reported: 2015-03-10 09:40 CET by Ammar Najjar
Modified: 2019-02-05 21:46 CET (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.
Description Ammar Najjar univentionstaff 2015-03-10 09:40:06 CET
Test rename_class script "102_rename_class" should be run on the slave in a multi server env, not only on the single server master (see Bug #36784)

The reason for its current restriction is that ucs-school-import package is only installed on the master.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2015-03-16 11:41:41 CET
When rename_class is called, not only the group name is altered but also the class share and the UNIX path to the class share. Since the class shares are located at a slave, the test script should be somehow called on a DC slave and check if the UNIX path is correctly modified.

Please do not try to install ucs-school-import on a DC slave. This will create some new problem (and ucs-test errors!).
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:46:07 CET
This issue has been filled against UCS@school 4.0. The maintenance with bug 
and security fixes for UCS@school 4.0 has ended on May 31, 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

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