Bug 47382 - Sysvol replication failes due to changed file permission
Sysvol replication failes due to changed file permission
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-19 14:33 CEST by Christina Scheinig
Modified: 2020-07-03 20:53 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018071821000944
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 Christina Scheinig univentionstaff 2018-07-19 14:33:18 CEST
The sysvol replication between master and school slave was not possible anymore, because the customer removed the slave server completely and added it again with the same server name.
Now the sysvol trigger file could not be added or written anymore. The file permission was still set to the old slave uid.
-----------------------------------------------------------------------------
root@master:/var/cache/univention-samba4/sysvol-sync/.trigger# ls -lah
insgesamt 8,0K
drwxrwxr-x 2 root      DC Slave Hosts 4,0K Jul 14 00:23 .
drwxr-xr-x 3 root      root           4,0K Jul 14  2017 ..
-rw-r--r-- 1 slave1$   DC Slave Hosts    0 Jul 19 13:45 slave1
-rw-r--r-- 1      9862 DC Slave Hosts    0 Jul  9 12:00 slave2
------------------------------------------------------------------------------
id slave2
id=9885(slave2$) gid=5006(DC Slave Hosts)

------------------------------------------------------------------------------
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:53:46 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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