Issue #3762 has been updated by Paul Nasrat.
We can close, I'd like to put the detailed info from comment #3 into the other bug. I also think uniqueid probably needs to die, but we can only do that in a major rev and we should use UUID which is better defined than hostid. We probably want a fact deprecation system that puppet can warn on to give people notice to change. There are ruby implementations of this RFC, eg http://github.com/spectra/ruby-uuid/blob/master/uuid.rb ---------------------------------------- Bug #3762: uniqueid is not unique on Debian http://projects.puppetlabs.com/issues/3762 Author: Daniel Pope Status: Needs design decision Priority: Normal Assigned to: Category: library Target version: Keywords: Branch: Debian-based systems in particular (possibly others) ship with an /etc/hosts file that starts 127.0.0.1 localhost 127.0.1.1 hostname.domain.tld hostname This is used to specify the FQDN of the machine independently of its physical IP address, and I believe their expectation is that you are not required to change this. However, this breaks the hostid command that is used to provide the uniqueid fact. I would expect the uniqueid fact to be unique on out-of-the-box Debian machines - perhaps munging Facter.ipaddress in the same way as the hostid command would. I also tested CentOS, but this does not use the same "hack", and it looks like you are expected to reconfigure /etc/hosts so that applications can find the hostname and FQDN. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
