Project

General

Profile

Actions

Feature #3701

closed

Fail if a hostname has a dot in it

Added by Anonymous over 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Low
Category:
Host creation
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Today a colleague created a new host for building, he entered hostname.customername as "Name" and selected company.tld as domain (this was a wrong precedure anyway...). A host with the correct FQDN was created in Foreman, but the machine's FQDN was hostname.company.tld and with this is was auto-created in foreman again. It would be nice if there would be a check for dots in the hostname when creating a new host.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #3697: Field Validations Should be more ComprehensiveClosedStephen Benjamin11/20/2013Actions
Actions #1

Updated by Dominic Cleal over 10 years ago

  • Related to Bug #3697: Field Validations Should be more Comprehensive added
Actions #2

Updated by Stephen Benjamin over 10 years ago

  • Assignee set to Stephen Benjamin

Historically it's been allowed to have hostnames with a "." in them. IIRC, even bind allows an A record "foo.bar" in zone "example.com". There's an open request in puppet labs for facter to support that scenario: http://projects.puppetlabs.com/issues/9766. But facter doesn't, and there's probably any number of other issues with doing it.

So I included this in the PR I have for the other validation effort: https://github.com/theforeman/foreman/pull/1041

Actions #3

Updated by Dominic Cleal about 10 years ago

  • Category set to Host creation
  • Status changed from New to Ready For Testing
  • Target version set to 1.9.2
  • translation missing: en.field_release set to 2
Actions #4

Updated by Anonymous about 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF