Bug 41990 - Reactivate home directory from backup if user is recreated/reactivated for a specific OU
Summary: Reactivate home directory from backup if user is recreated/reactivated for a ...
Status: RESOLVED WONTFIX
Alias: None
Product: UCS@school
Classification: Unclassified
Component: Listener modules
Version: UCS@school 4.1 R2
Hardware: Other Linux
: P5 enhancement
Target Milestone: UCS@school 4.1.x
Assignee: UCS@school maintainers
QA Contact:
URL:
Keywords:
Depends on: 41989
Blocks:
  Show dependency tree / graph
 
Reported: 2016-08-15 10:58 CEST by Sönke Schwardt-Krummrich
Modified: 2019-02-05 21:16 CET (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
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):
Customer ID: 00009
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2016-08-15 10:58:57 CEST 
Since UCS@school 4.1R2 users may be moved between schools and may be active in several schools. If a user is removed from a school, the listener module
remove-old-homedirs.py moves the home directory into a backup directory.

Feature request:
If the user is reactivated for this school/OU later on, the home directory shall be recovered from backup directory (if possible).
Comment 1 Florian Best univentionstaff 2017-06-28 14:56:52 CEST 
There is a Customer ID set so I set the flag "School Customer affected".
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:16:26 CET 
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 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.