Empty /etc/mesos-slave/hostname causes strange agent registration behavior

[drcrallen]

Using the mesosphere packaged Mesos 1.0.0 I had a node that ended up with a blank /etc/mesos-slave/hostname due to something going wrong during the auto-config process.
When the agent registered with the master, it ended up reporting very strangely, including reporting the agent IP as the master's and having a master IP blank.

The following items are in the /etc config:

$ ls /etc/mesos-slave/
attributes  cgroups_hierarchy  cgroups_limit_swap  gc_delay  hostname  isolation  resources  slave_subsystems  work_dir

Not sure if this is the right place to report mesosphere package config problems, but it seems odd the agent would start under such a broken config.