Jira (PDB-725) host rename problems
Title: Message Title Christopher May created an issue PuppetDB / PDB-725 host rename problems Issue Type: Bug Assignee: Unassigned Created: 30/Jun/14 6:32 AM Priority: Normal Reporter: Christopher May During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-queue-s01.visualdna.com Exported resources constantly finds two hosts and I've tried everything from node clean, node deactivate, purging /var/lib/puppet on the host as well. Everytime I run puppet on bl-queue-s01, it brings back the stagdmz entries as well (on another box it spits out two files, one being the stagdmz one as well). I'm about to go do some sql-fu to nuke all references to stagdmz but thought I'd raise this first in case im doing something wrong or if there is a better way of doing this. Cheers, Chris Add Comment
Jira (PDB-725) host rename problems
Title: Message Title Kenneth Barber commented on an issue Re: host rename problems So ... 'puppet node deactivate' should be the correct trick here. If you feel it is 'coming back' this could be for a number of reasons: The data genuinely is getting re-inserted. The puppetdb.log entry for a 'replace catalog' on the hostname will show this. Check your logs to ensure the data is not getting put back. The data is coming from a place you didn't expect. I usually recommend looking at this tool first: https://forge.puppetlabs.com/zack/exports. It is able to show you what resources are exported, and what host is exporting them. Most of the time these problems stem from assumptions around where the data is coming from - often the data is coming from a hostname you didn't expect and the node deactivate hostname is a mismatch. If you can try the tool, and show the attempts at trying to clear the data with deactivate, and back it up with puppetdb.log info, that would be very useful. Your bug reports talk about the symptoms, but I need more examples and I need you to show me transcripts on the CLI of how you've come to your conclusions if you can. Thanks. Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp
Jira (PDB-725) host rename problems
Title: Message Title Christopher May commented on an issue Re: host rename problems that zack-exports module seems to have solved my issue, it seems; bl-queue-p04.visualdna.com Nagios_service[check_total_procs_bl-stream-p01.proddmz.bl.visualdna.com] So I was deactivating the new nodes hostname but because queue-p04 wasn't deactivated, it was keeping the data alive even though the hostname and the export resource caused a weird conflict. I'm sure this is working as intended, just the way puppet behaves whilst the box is being renamed underneath it. Sorry for wasting your time, and thanks for highlighting an extremely useful tool! Cheers, Chris Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-725) host rename problems
Title: Message Title Kenneth Barber commented on an issue Re: host rename problems Well, we've had discussions recently about making that tool part of core - and documented it a bit more. For now though, this seems like an information problem more than a bug. Closing . Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
