From f27f52f8fd57b24307ca93b5b9040995a8389a01 Mon Sep 17 00:00:00 2001 From: Tim Beale Date: Tue, 5 Mar 2019 12:32:10 +1300 Subject: [PATCH] WHATSNEW: Add Bug 13760 to Known Issues/Upgrading There is currently a problem upgrading from v4.7 or earlier to Samba v4.9 or v4.10. We should warn users and give them the work-around, before they try to upgrade to 4.10. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13760 Signed-off-by: Tim Beale --- WHATSNEW.txt | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/WHATSNEW.txt b/WHATSNEW.txt index 2d53561..a25cd0e 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -12,6 +12,9 @@ Samba 4.10 will be the next version of the Samba suite. UPGRADING ========= +When upgrading from Samba v4.7 (or an earlier release), please follow the +Bug 13760 work-around in the 'Known Issues' section. + NEW FEATURES/CHANGES ==================== @@ -292,6 +295,21 @@ KNOWN ISSUES https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.10#Release_blocking_bugs +Bug 13760: An in-place upgrade from Samba v4.7 (or earlier) to v4.10 can result +in Samba AD services failing to function properly. This problem will not +occur if the Samba AD DC has already been successfully running v4.8 or v4.9. + +To avoid this problem, after you have upgraded Samba, but before you start +the samba process, run the following command on the upgraded DC: +samba-tool dbcheck --reindex + +This problem is due to the database indexing scheme changing between v4.7 and +v4.8. To support upgrading an older database, Samba has a mechanism to +automatically update the database indexes after a upgrade. While this automatic +re-indexing worked successfully on v4.8, currently v4.9 and v4.10 releases +contain a bug which means the database needs to be re-indexed manually. + +For more details, see: https://bugzilla.samba.org/show_bug.cgi?id=13760 ####################################### Reporting bugs & Development Discussion -- 2.7.4