Bug 36832 - S3->S4 inplace migration: check irritating error messages.
S3->S4 inplace migration: check irritating error messages.
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-18 18:46 CET by Arvid Requate
Modified: 2020-07-03 20:54 CEST (History)
2 users (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
inplace_migration.log (47.58 KB, text/plain)
2014-11-18 18:46 CET, Arvid Requate
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-11-18 18:46:38 CET
Created attachment 6412 [details]
inplace_migration.log

During the S3->S4 inplace migration with Samba 4.2 a couple of irritating error messages are output. We should check how we can improve this and if any serious problem is hidden.

The messages "Could not add posix attrs for AD entry for sid=S-1-5-64-21" are probably caused by samba-tool domain classicupgrade while trying to add rfc2307 attributes. This is not strictly required at this stage.

The domain behaved ok despite the messsages:
* Logon to previously join client with pre-existing user worked
* After reboot the client synchronized his system clock
* After a second reboot the client was able to ddns update his own hostname
* And the client was able to pull GPOs, add new GPOs and apply them as well
* Client initiated user password change worked
* Printing to a memberserver worked (client side installed drivers)
* Joining a new Windows client worked.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:54:05 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.