The nethserver-samba-update event already ships the fix, but is not automatically triggered by upstream updates. We probably need to cover this scenario with better code.
It is the first time 7.6 receives a samba package update.
The issue could hit only servers updated from 7.5 (or previous) because they have sssd-libwbclient installed. As alternative fix run:
Removed sssd-libwbclient and updated my production system with subscription.
Almost same packages as mentioned by @pfornara.
Due to a new kernel (957.27.2) rebooted system.
All Shares are still accessible after update and reboot.
Thank’s a lot for this to all. So I’m happy, that I had no issue with my system!
@giacomo and I are talking about how to implement the fix. Removing that old dependency seems safer over trying to workaround the alternatives symlink labyrinth.
However we have to introduce an Obsoletes/Conflicts RPM tag, which is somewhat evil too!
Does this issue come down to having the package being left over from the CentOS 7.5 to 7.6 upgrade? Or is it specific to the NethServer 7.5 to 7.6 upgrade?
It comes from NethServer 7.5 setup, that used to run without winbind until upstream changed the game with 7.6.
Different packages (namely libwbclient and sssd-libwbclient) try to configure alternatives when they are added/updated/removed and lead to inconsistent and faulty results.
The nethserver-samba attempted to fix this condition since 7.6 but was not enough: the first samba update caused the wrong library to be loaded by winbind.