Project

General

Profile

Bug #5996

Directory services setup should validate hostname values

Added by Jordan Hubbard about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Nice to have
Assignee:
John Hixson
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

We hit a problem today where the hostnames weren't FQDNs and/or a DC / GC were confused for one another in the configuration. This caused tracebacks and other "weird behavior" further down the line, suggesting that even more robust validation checks (not just "correct password") need to be added. This ticket is intended to track those checks.

Associated revisions

Revision bc266984 (diff)
Added by John Hixson about 6 years ago

If a DC or GC host has been specified, check if it's up Ticket: #5996

History

#1 Updated by John Hixson about 6 years ago

  • Status changed from Unscreened to Screened

#2 Updated by John Hixson about 6 years ago

  • Status changed from Screened to Resolved

#3 Updated by Dru Lavigne about 6 years ago

  • Status changed from Resolved to Closed

Verified in M4 and added to 9.3 docs.

Also available in: Atom PDF