On Tue, 2017-10-24 at 07:45 -0700, [email protected] wrote: > So now, both are mixed and confusion happens, does anyone encountered > this before ? is this a bug ?
So it sort of is, and sort of isn't. Host renaming is mainly aimed at cloud environments which can bring up your new host with all sorts of weird names. In this scenario, you probably *don't* want to recreate the Puppet cert (because you're automating 100s of these servers, and cert re-creation is manual). So, the name is correctly changed, but the cert is not - that's deliberate based on this scenario. The second part of what you're seeing is to do with how Foreman creates new hosts - it's matching on the certname. So when you change the cert, it thinks this is a new host. That doesn't explain why the hostname is wrong, though - I'd expect both to be test-renamed. What does 'facter' show for the hostname just before the import? There was a lot of discussion about how to handle renames and identifying hosts in the past, and the general consensus (as I recall, but I can't find the ticket right now ...) was that for changing the cert, you'd probably just delete the host and rebuild. I *think* setting the build flag might clear the certname, so you could rename and rebuild if you don't want to delete entirely. Would either of those options work for you? Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
