Project

General

Profile

Bug #42257

Keep AD in configured state even if service start fails

Added by Andrew Walker 11 months ago. Updated 10 months ago.

Status:
Done
Priority:
No priority
Assignee:
Andrew Walker
Category:
Services
Target version:
TrueNAS - TrueNAS-11.1-U6.1
Seen in:
TrueNAS - TrueNAS 11.1-U4
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
UNY-736-93098
Hardware Configuration:
ChangeLog Required:
No

Description

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.

History

#1 Updated by Bug Clerk 11 months ago

  • Status changed from Unscreened to In Progress

#2 Updated by Andrew Walker 11 months ago

  • Subject changed from Failure to join active directory leaves smb.conf /krb5.conf in unconfigured state to Keep samba configured and running in configured state even if service start fails

#4 Updated by Andrew Walker 11 months ago

  • Target version changed from Backlog to 11.2-BETA3

#5 Updated by Dru Lavigne 11 months 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

#7 Updated by Bug Clerk 11 months ago

  • Status changed from Ready for Testing to In Progress

#8 Updated by Dru Lavigne 11 months ago

  • Target version changed from 11.2-BETA3 to TrueNAS-11.1-U6.1
  • Needs Merging changed from No to Yes

#9 Updated by Bug Clerk 10 months ago

  • Status changed from In Progress to Ready for Testing
  • Target version changed from TrueNAS-11.1-U6.1 to TrueNAS 11.1-U6.2

#10 Updated by Dru Lavigne 10 months ago

  • Target version changed from TrueNAS 11.1-U6.2 to TrueNAS-11.1-U6.1

#11 Updated by Dru Lavigne 10 months ago

  • Needs Merging changed from Yes to No

This will also appear in the Changelog for FN 11.1-U7 and FN 11.2-BETA3.

#12 Updated by Bonnie Follweiler 10 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed in TrueNAS-11.1-U6-INTERNAL10

BUILTIN : online
X20QA2 : online
AD01 : online

#13 Updated by Dru Lavigne 10 months ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF