Good catch Ellison; I haven't noticed that but nope, nothing "unusual" from facter on the affected node. Now running puppet agent -tv with certificate cleared from both master and agent yields these:
notice: Starting Puppet master version 2.7.23 > .... > .... > info: access[/certificate_request]: allowing * access > info: access[/]: adding authentication any > info: Inserting default '/status' (auth true) ACL because none were found > in '/etc/puppet/auth.conf' > info: Could not find certificate for 'serv106.syst.local' > info: Could not find certificate_request for 'serv106.syst.local' > notice: serv106.syst.local has a waiting certificate request > notice: Signed certificate request for serv106.syst.local > notice: Removing file Puppet::SSL::CertificateRequest serv106.syst.local > at '/var/lib/puppet/ssl/ca/requests/serv106.syst.local.pem' > info: Expiring the node cache of > /usr/lib/ruby/site_ruby/1.8/puppet/node.rb:110:in `names' > /usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:212:in > `evaluate_ast_node' > /usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:101:in `compile' > .... > .... > It does sign the certificate just right but again the same wired "info: Expiring the node cache of" after that. -San On Saturday, May 31, 2014 12:26:09 AM UTC+1, Ellison Marks wrote: > > It's weird, but it looks like the hostname isn't being defined, or isn't > being sent properly. See > > "info: Expiring the node cache of" > > With just a blank afterwards. Does running facter on the affected node > show anything unusual? > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5d18a945-01f6-4087-b20e-b1be9cf5099b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
