yahoo-eng-team team mailing list archive

[James Falcon <1724414@xxxxxxxxxxxxxxxxxx>]

I'm closing this as Wont' Fix. There's a fairly high regression
potential involved in changing the default hostname. We can't justify
changing it without a substantial reason.

If this causes problems, we're open to pursuing other options, but we'd
need to know the use case. For example, an alternative to changing the
default hostname used could be to add a configuration option to specify
whether to use the short hostname or fqdn.

** Changed in: cloud-init
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1724414

Title:
  rhel distro selects FQDN as hostname

Status in cloud-init:
  Won't Fix

Bug description:
  Currently cloud-init rhel distro selects FQDN over short hostname for set_hostname and 
  update_hostneme. 

  RHEL limits max hostname to 64 bytes by default:

      $ getconf HOST_NAME_MAX 
      64 

  According to RFC 1035, the FQDN could up to 255 bytes. Setting
  hostname to FQDN will fail if FQDN > 64 byets.

  Normally the cloud will provide "local-hostname" in instance metadata,
  which usually a short hostname. In sources/__init__.py get_hostname(),
  we default FQDN to <local-hostname>.localdomain. If rhel set it as
  hostname, then that's just wrong.

  The proposal is to make rhel distro select shorter hostname over FQDN,
  just as other distros. RHEL has its own preference, but not
  prohibiting us doing improvement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1724414/+subscriptions