[Bug 1737534] Re: smbd/nmbd don't restart after upgrade if started but disabled

[Launchpad Bug Tracker]

[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

** Changed in: samba (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1737534

Title:
  smbd/nmbd don't restart after upgrade if started but disabled

Status in samba package in Ubuntu:
  Expired

Bug description:
  If smbd and nmbd are started and running but their service is
  disabled, and an apt-get upgrade is performed which updates samba
  /samba-common, at the end of the upgrade the smbd and nmbd daemons
  will not be running anymore.

  Distribution: Ubuntu 16.04

  Pre-upgrade version: 4.3.8+dfsg-0ubuntu1 
  Post-upgrade version: 4.3.11+dfsg-0ubuntu0.16.04.12

  What I expected to happen:
  After the dist-upgrade, since smbd and nmbd services were running, they should have been started again

  What happened instead:
  smbd and nmbd services are inactive.

  
  The problem doesn't arise if the service is enabled; I suppose that somewhere after the upgrade, the samba package queries for the global unit enablement status rather than the unit status before the upgrade; this is especially problematic with unattended-upgrades, there're reasons for which I don't start samba at boot (it gets started by an ansible task after a disk is checked, decrypted and mounted), and it has happened to me to have a machine with samba properly running and then dead after an automated upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1737534/+subscriptions