Keep AD in configured state even if service start fails
Current behavior is that if "ix-activedirectory start" fails, or other AD startup-related scripts fail, we disable active directory in the config db. This causes Samba to come up as a standalone server rather than an AD member server. The following is an example of why this behavior is a problem:
(1) Customer had to perform scheduled maintenance at a datacenter, which involved powering off their NAS as well as networking hardware.
(2) NAS powered on and booted before networking was restored. Since the NAS couldn't contact a DC, the scripts failed, resulting in Active Directory becoming disabled. This caused unexpected outage and unanticipated difficulty bringing the NAS back online.
(3) The situation in (2) would have automatically recovered if the relevant config files were generated and samba was started. The winbind connection manager would have detected the domain becoming available and done what was necessary to restore AD integration.
#5 Updated by Dru Lavigne almost 2 years ago
- Subject changed from Keep samba configured and running in configured state even if service start fails to Keep AD in configured state even if service start fails
- Status changed from In Progress to Ready for Testing
- Assignee changed from Release Council to Andrew Walker
- Needs Doc changed from Yes to No
- Needs Merging changed from Yes to No