Samba DC 4.7.0 and automatic updates

The Samba project recently published a new minor release: 4.7.0. Their release schedule suggests a minor release is supported about one year and an half (i.e. 4.4 was released on March '16 and set EOL on Sep '17).

If we release 4.7 together with NethServer 7.4.1708 we could probably switch to 4.8 when 7.5 will be available.

I propose to release 4.7.0 with NethServer 7.4 and implement a new feature: automatic DC updates for the 4.7.x release series (revisions/bugfixes). A prop can be set to disable this new feature and retain the same behavior of ns7.3.

What do you think?


https://github.com/NethServer/dev/issues/5356

BTW an RPM is available for ns7.4 beta from nethserver-testing repo /cc @quality_team

4 Likes

Hi @davidep ,

I have run the following procedure, with no visible errors, but the version of Samba is still 4.6.2.
What did I do wrong?

PS:
The reboot of the NS was made after the update of the “Account provider”, from NS GUI.

Tia,
Gabriel

[root@pdc-ad ~]#
[root@pdc-ad ~]#
[root@pdc-ad ~]# yum --enablerepo=nethserver-testing update
Loaded plugins: changelog, fastestmirror, nethserver_events
Loading mirror speeds from cached hostfile
 * base: mirrors.pidginhost.com
 * epel: mirror.speedpartner.de
 * extras: mirrors.pidginhost.com
 * nethforge: mirror.nordest.systems
 * nethserver-base: mirror.nordest.systems
 * nethserver-updates: mirror.nordest.systems
 * updates: mirrors.pidginhost.com
Resolving Dependencies
--> Running transaction check
---> Package nethserver-base.noarch 0:3.0.35-1.ns7 will be updated
---> Package nethserver-base.noarch 0:3.0.35-1.2.g03bcddb.ns7 will be an update
---> Package nethserver-dc.x86_64 0:1.2.6-1.ns7 will be updated
---> Package nethserver-dc.x86_64 0:1.2.6-1.1.g2aac841.ns7 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================
 Package                      Arch                Version                                Repository                       Size
===============================================================================================================================
Updating:
 nethserver-base              noarch              3.0.35-1.2.g03bcddb.ns7                nethserver-testing              209 k
 nethserver-dc                x86_64              1.2.6-1.1.g2aac841.ns7                 nethserver-testing               14 M

Transaction Summary
===============================================================================================================================
Upgrade  2 Packages

Total download size: 14 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for nethserver-testing
(1/2): nethserver-base-3.0.35-1.2.g03bcddb.ns7.noarch.rpm                                               | 209 kB  00:00:01
(2/2): nethserver-dc-1.2.6-1.1.g2aac841.ns7.x86_64.rpm                                                  |  14 MB  00:00:29
-------------------------------------------------------------------------------------------------------------------------------
Total                                                                                          477 kB/s |  14 MB  00:00:29
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : nethserver-base-3.0.35-1.2.g03bcddb.ns7.noarch                                                              1/4
  Updating   : nethserver-dc-1.2.6-1.1.g2aac841.ns7.x86_64                                                                 2/4
  Cleanup    : nethserver-dc-1.2.6-1.ns7.x86_64                                                                            3/4
  Cleanup    : nethserver-base-3.0.35-1.ns7.noarch                                                                         4/4
  Verifying  : nethserver-dc-1.2.6-1.1.g2aac841.ns7.x86_64                                                                 1/4
  Verifying  : nethserver-base-3.0.35-1.2.g03bcddb.ns7.noarch                                                              2/4
  Verifying  : nethserver-base-3.0.35-1.ns7.noarch                                                                         3/4
  Verifying  : nethserver-dc-1.2.6-1.ns7.x86_64                                                                            4/4

Updated:
  nethserver-base.noarch 0:3.0.35-1.2.g03bcddb.ns7                nethserver-dc.x86_64 0:1.2.6-1.1.g2aac841.ns7

Complete!
[root@pdc-ad ~]#
[root@pdc-ad ~]#
[root@pdc-ad ~]# smbd -V
Version 4.6.2
[root@pdc-ad ~]#
[root@pdc-ad ~]#
[root@pdc-ad ~]# reboot now

[root@pdc-ad ~]# smbd -V
Version 4.6.2
[root@pdc-ad ~]# 

1 Like

You’re right there’s apparently no visible changes… We should display the Samba DC version somewhere in the UI!

See the samba DC logs for the version number:

 journalctl -u samba -M nsdc

Please remember the samba package in NethServer is not at the same version of the one in the nsdc container!

2 Likes

Will be nice!

You are right! I forgot this! :blush:

Oct 04 08:07:28 nsdc-pdc-ad.abt.ro systemd[1]: Started Samba domain controller daemon.
Oct 04 08:07:28 nsdc-pdc-ad.abt.ro systemd[1]: Starting Samba domain controller daemon...
Oct 04 08:07:30 nsdc-pdc-ad.abt.ro samba[26]: samba version 4.6.5 started.
Oct 04 08:07:30 nsdc-pdc-ad.abt.ro samba[26]: Copyright Andrew Tridgell and the Samba Team 1992-2017
Oct 04 08:07:33 nsdc-pdc-ad.abt.ro samba[26]: samba: using 'standard' process model
Oct 04 08:07:34 nsdc-pdc-ad.abt.ro winbindd[39]: [2017/10/04 08:07:34.680269,  0] ../source3/winbindd/winbindd_cache.c:3171(initialize_winbindd_cache)
Oct 04 08:07:34 nsdc-pdc-ad.abt.ro winbindd[39]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Oct 04 08:07:38 nsdc-pdc-ad.abt.ro winbindd[39]: [2017/10/04 08:07:38.717222,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 04 08:07:38 nsdc-pdc-ad.abt.ro winbindd[39]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections
Oct 04 08:07:39 nsdc-pdc-ad.abt.ro smbd[31]: [2017/10/04 08:07:39.642880,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 04 08:07:39 nsdc-pdc-ad.abt.ro smbd[31]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Oct 06 20:02:52 nsdc-pdc-ad.abt.ro winbindd[39]: [2017/10/06 20:02:52.327946,  0] ../source3/winbindd/winbindd.c:280(winbindd_sig_term_handler)
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 36 on SIGTERM
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 42 on SIGTERM
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 41 on SIGTERM
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 40 on SIGTERM
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 38 on SIGTERM
Oct 06 20:02:53 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 37 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 35 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 34 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 33 on SIGTERM
Oct 06 20:02:52 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Samba domain controller daemon...
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 32 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 30 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 28 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 29 on SIGTERM
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: SIGTERM: killing children
Oct 06 20:02:54 nsdc-pdc-ad.abt.ro samba[26]: Exiting pid 26 on SIGTERM
Oct 06 20:02:56 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Samba domain controller daemon.
-- Reboot --
Oct 06 20:06:37 nsdc-pdc-ad.abt.ro systemd[1]: Started Samba domain controller daemon.
Oct 06 20:06:37 nsdc-pdc-ad.abt.ro systemd[1]: Starting Samba domain controller daemon...
Oct 06 20:06:37 nsdc-pdc-ad.abt.ro samba[27]: samba version 4.7.0 started.
Oct 06 20:06:37 nsdc-pdc-ad.abt.ro samba[27]: Copyright Andrew Tridgell and the Samba Team 1992-2017
Oct 06 20:06:38 nsdc-pdc-ad.abt.ro samba[27]: samba: using 'standard' process model
Oct 06 20:06:39 nsdc-pdc-ad.abt.ro winbindd[43]: [2017/10/06 20:06:39.093964,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
Oct 06 20:06:39 nsdc-pdc-ad.abt.ro winbindd[43]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Oct 06 20:06:40 nsdc-pdc-ad.abt.ro winbindd[43]: [2017/10/06 20:06:40.795182,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 06 20:06:40 nsdc-pdc-ad.abt.ro winbindd[43]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections
Oct 06 20:06:41 nsdc-pdc-ad.abt.ro smbd[32]: [2017/10/06 20:06:41.461394,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 06 20:06:41 nsdc-pdc-ad.abt.ro smbd[32]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[54]: [2017/10/06 20:14:55.966187,  0] ../source3/winbindd/winbindd.c:281(winbindd_sig_term_handler)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 29 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[54]:   Got sig[15] terminate (is_parent=0)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 31 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[55]: [2017/10/06 20:14:55.971821,  0] ../source3/winbindd/winbindd.c:281(winbindd_sig_term_handler)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 34 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[55]:   Got sig[15] terminate (is_parent=0)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 36 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[56]: [2017/10/06 20:14:55.977845,  0] ../source3/winbindd/winbindd.c:281(winbindd_sig_term_handler)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 37 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro winbindd[56]:   Got sig[15] terminate (is_parent=0)
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 39 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 40 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 41 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 44 on SIGTERM
Oct 06 20:14:55 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Samba domain controller daemon...
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 45 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 33 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 35 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 38 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: SIGTERM: killing children
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: SIGTERM: killing children
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 27 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 44 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 38 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 45 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 37 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 31 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 39 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 34 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 36 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 40 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 29 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 33 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 35 on SIGTERM
Oct 06 20:14:56 nsdc-pdc-ad.abt.ro samba[27]: Exiting pid 41 on SIGTERM
Oct 06 20:14:57 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Samba domain controller daemon.
-- Reboot --
Oct 06 20:15:50 nsdc-pdc-ad.abt.ro systemd[1]: Started Samba domain controller daemon.
Oct 06 20:15:50 nsdc-pdc-ad.abt.ro systemd[1]: Starting Samba domain controller daemon...
Oct 06 20:15:51 nsdc-pdc-ad.abt.ro samba[26]: samba version 4.7.0 started.
Oct 06 20:15:51 nsdc-pdc-ad.abt.ro samba[26]: Copyright Andrew Tridgell and the Samba Team 1992-2017
Oct 06 20:15:56 nsdc-pdc-ad.abt.ro samba[26]: samba: using 'standard' process model
Oct 06 20:15:58 nsdc-pdc-ad.abt.ro winbindd[42]: [2017/10/06 20:15:58.351750,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
Oct 06 20:15:58 nsdc-pdc-ad.abt.ro winbindd[42]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Oct 06 20:16:01 nsdc-pdc-ad.abt.ro smbd[32]: [2017/10/06 20:16:01.023487,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 06 20:16:01 nsdc-pdc-ad.abt.ro smbd[32]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Oct 06 20:16:01 nsdc-pdc-ad.abt.ro winbindd[42]: [2017/10/06 20:16:01.087503,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Oct 06 20:16:01 nsdc-pdc-ad.abt.ro winbindd[42]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections
lines 2092-2135/2135 (END)
2 Likes

Excellent @GG_jr!

Your Samba 4.7.0 DC is ready to serve connections

Beautiful :blush:

Please go on with shared folders, user and groups creation, joining a workstation and so on…

Cmon guys, who lends an hand to Gabriel?

2 Likes

Thank you @davidep !

More tests from Monday, at the office!

Kind regards,
Gabriel

1 Like

Tested on 7.4b1 fully updated with the testing packages.
Shared folder auth read and write tests:
guest share :white_check_mark:
home share :white_check_mark:
non browsable acl share :white_check_mark:
user and group acl :white_check_mark:

User/group creation:
Create user :white_check_mark:
Create group with members :white_check_mark:

Joining workstation:
Win 7 :white_check_mark:
Win 10 :white_check_mark:

Browse NSDC :white_check_mark:

Reboot Nethserver and check if samba still works :white_check_mark:

No errors in log files. Earlier when Nethserver booted and I browsed to Dashboard too fast I had AccountProvider Error 1 in Dashboard, this is away now (or I was too slow).

The new samba container rocks! :sunglasses:

4 Likes

I rather like to have Samba updates consistent with any other updates.

So my proposal:

  • remove the prop AutoUpdateType
  • automatically update Samba when we decide to release it (after normal QA)

Pros:

  • less code! :sparkles:
  • nothing to document
  • works as expected: until now, ns-samba was the only package with manual update from the UI
4 Likes

I definitely agree. While implementing my initial proposal I recalled the reason because a “manual update” button exists is behind our little experience about how the Samba project releases its updates and if applying them is safe enough.

After some month, four patch releases and a minor release too, I’m confident with it and I think this safety measure is useless because we run update test during the QA phase and we can decide to disable new features from Samba selectively.

So I fully endorse @giacomo’s proposal: let’s remove it and make it simple.

In the future, we’ll add a “Configuration” panel if we need to selectively disable/enable specific features. For instance “NTLM compatibility” flag for legacy printers (already planned).

3 Likes

The new samba release is available from testing repos. Now the upgrade runs automatically. See the issue for test case:

https://github.com/NethServer/dev/issues/5356

Samba is a QA hot point. Please test it thoroughly! /cc @quality_team

2 Likes

Test case 1:

  • Install the testing package:
[root@pdc-ad ~]# yum --enablerepo=nethserver-testing update
Loaded plugins: changelog, fastestmirror, nethserver_events
nethserver-testing                                                                                        | 2.9 kB  00:00:00
nethserver-testing/7/x86_64/primary_db                                                                    |  38 kB  00:00:00
Loading mirror speeds from cached hostfile
 * base: mirrors.leadhosts.com
 * epel: fedora.mirrors.telekom.ro
 * extras: mirrors.leadhosts.com
 * nethforge: mirror2.nethserver.org
 * nethserver-base: mirror2.nethserver.org
 * nethserver-updates: mirror2.nethserver.org
 * updates: mirrors.leadhosts.com
Resolving Dependencies
--> Running transaction check
---> Package nethserver-dc.x86_64 0:1.2.6-1.ns7 will be updated
---> Package nethserver-dc.x86_64 0:1.2.6-1.6.g5d1cacc.ns7 will be an update
---> Package nethserver-sssd.noarch 0:1.3.0-1.ns7 will be updated
---> Package nethserver-sssd.noarch 0:1.3.0-1.3.ga7c698a.ns7 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

=================================================================================================================================
 Package                       Arch                 Version                               Repository                        Size
=================================================================================================================================
Updating:
 nethserver-dc                 x86_64               1.2.6-1.6.g5d1cacc.ns7                nethserver-testing                14 M
 nethserver-sssd               noarch               1.3.0-1.3.ga7c698a.ns7                nethserver-testing                94 k

Transaction Summary
=================================================================================================================================
Upgrade  2 Packages

Total download size: 14 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for nethserver-testing
(1/2): nethserver-sssd-1.3.0-1.3.ga7c698a.ns7.noarch.rpm                                                  |  94 kB  00:00:00
(2/2): nethserver-dc-1.2.6-1.6.g5d1cacc.ns7.x86_64.rpm                                                    |  14 MB  00:00:27
---------------------------------------------------------------------------------------------------------------------------------
Total                                                                                            501 kB/s |  14 MB  00:00:27
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : nethserver-sssd-1.3.0-1.3.ga7c698a.ns7.noarch                                                                 1/4
  Updating   : nethserver-dc-1.2.6-1.6.g5d1cacc.ns7.x86_64                                                                   2/4
  Cleanup    : nethserver-dc-1.2.6-1.ns7.x86_64                                                                              3/4
  Cleanup    : nethserver-sssd-1.3.0-1.ns7.noarch                                                                            4/4
  Verifying  : nethserver-sssd-1.3.0-1.3.ga7c698a.ns7.noarch                                                                 1/4
  Verifying  : nethserver-dc-1.2.6-1.6.g5d1cacc.ns7.x86_64                                                                   2/4
  Verifying  : nethserver-dc-1.2.6-1.ns7.x86_64                                                                              3/4
  Verifying  : nethserver-sssd-1.3.0-1.ns7.noarch                                                                            4/4

Updated:
  nethserver-dc.x86_64 0:1.2.6-1.6.g5d1cacc.ns7                  nethserver-sssd.noarch 0:1.3.0-1.3.ga7c698a.ns7

Complete!
[root@pdc-ad ~]#
  • Check in “Doman accounts” page is OK:

  • Check the Samba version in “Accounts provider” is 4.7.0:

Test case 2

  • After test case 1, run manually

    signal-event nethserver-dc-update

The upgrade action must not trigger the upgrade event.

Result: Nothing changed in “Doman accounts” page, in “Accounts provider” page or in “Software center -> Updates”

From /var/log/messages:

Oct 10 21:33:34 pdc-ad esmith::event[28742]: Event: nethserver-dc-update 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database configuration 
Oct 10 21:33:34 pdc-ad dbus[647]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' 
Oct 10 21:33:34 pdc-ad dbus-daemon: dbus[647]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' 
Oct 10 21:33:34 pdc-ad systemd: Starting Time & Date Service... 
Oct 10 21:33:34 pdc-ad dbus[647]: [system] Successfully activated service 'org.freedesktop.timedate1' 
Oct 10 21:33:34 pdc-ad dbus-daemon: dbus[647]: [system] Successfully activated service 'org.freedesktop.timedate1' 
Oct 10 21:33:34 pdc-ad systemd: Started Time & Date Service. 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database certificates 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database networks 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database routes 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database accounts 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database hosts 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database proxypass 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database fwrules 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database fwservices 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database portforward 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database tc 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Migrating existing database dhcp 
Oct 10 21:33:34 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/nethserver-dc-update/S00initialize-default-databases SUCCESS [0.675099] 
Oct 10 21:33:35 pdc-ad esmith::event[28742]: expanding /etc/sysconfig/nsdc 
Oct 10 21:33:35 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/actions/generic_template_expand SUCCESS [0.414975] 
Oct 10 21:33:35 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/nethserver-dc-update/S40nethserver-dc-fixchroot SUCCESS [0.684068] 
Oct 10 21:33:36 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/nethserver-dc-update/S50nethserver-dc-autoupdate SUCCESS [0.51121] 
Oct 10 21:33:37 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/nethserver-dc-update/S95nethserver-dc-firststart SUCCESS [0.577975] 
Oct 10 21:33:38 pdc-ad esmith::event[28742]: Action: /etc/e-smith/events/nethserver-dc-update/S96nethserver-dc-machine-grants SUCCESS [1.096814] 
Oct 10 21:33:38 pdc-ad esmith::event[28742]: Event: nethserver-dc-update SUCCESS

EDIT:

During installation, I didn’t see this package to be installed/upgraded:

nethserver-dc-debuginfo-1.2.6-1.6.g5d1cacc.ns7.x86_64.rpm

The new samba module release was installed in two mods:

2 Likes

Thank you for testing, Gabriel!

Debuginfo are special packages associated to an arch-dependant package. They are useful to debug application crashes and inspect stack traces. They aren’t required during normal system run time.

1 Like

You are welcome! I’m glad to help!

About “nethserver-dc-debuginfo” module (i know for what it use), I saw it listed in github and I want just to inform about this. I understand now that can be installed separately and is available for NS 7.3 and 7.4.

Thanks to @GG_jr and @mrmarkuz we discovered an issue with Samba 4.7 in the backup-config procedure.

We can’t release Samba 4.7.0 by now, we must wait until that issue is solved. However the new “automatic updates” policy can be released, so I’m preparing the latest ns-samba package from branch 4.6 for NethServer 7.4.

3 Likes

A new nethserver-dc is available in testing repo (7.4 only)

See https://github.com/NethServer/dev/issues/5360

3 Likes

Tested on a system with Samba already updated to 4.7.0 and with backup (data) with errors (already known):

  1. Configuration -> Accounts provider -> Uninstall ==> OK
  2. Install the new testing packages ==> OK
  3. Configuration -> Accounts provider -> Active directory -> Create new domain ==> OK
  4. Check in “Domain accounts” page is OK ==> OK
  5. Check the Samba version in “Accounts provider” is 4.6.8 ==> OK
  6. Run manually signal-event nethserver-dc-update ==> OK (The upgrade action did not trigger the upgrade event.)
  7. Run the backup-config procedure and ensure it is successful ==> OK (no any errors in /var/log/messages and in email report!)

To you: :trophy:

3 Likes

I may confirm: No errors anymore! :clap:

3 Likes