Issue #12140 has been updated by Daniel Pittman.

Category set to queuing
Status changed from Unreviewed to Needs More Information

Hey.  Trying to work out what is going on here, I would appreciate a couple of 
bits more information from you:

Can you tell me the certname of one of the catalogs that is being improperly 
updated, and the certname of the machine that runs the Puppet queue daemon?

You can extract that with `puppet agent --configprint certname`

Can you also show `puppet agent --configprint node_terminus` on the queue 
machine only?

It looks like what is happening is that the queue daemon is getting node 
details that it *thinks* belong to the target node, but are really local, and 
is updating the request as a consequence.  Those details will help track down 
the configuration causes of the problem.
----------------------------------------
Bug #12140: puppetqd incorrectly updating hosts.ip of agent to IP of system 
puppetqd is running on
https://projects.puppetlabs.com/issues/12140

Author: Jacob  McCann
Status: Needs More Information
Priority: Normal
Assignee: 
Category: queuing
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


I have recently started to use async_storeconfigs.  My setup for this is I have 
puppetmaster, activemq and puppetqd all running on a system.

So what is happening is an agent performs a run.  After the run the 
storeconfigs DB has the hosts.ip for the agent updated to the IP of the system 
that puppetqd is running on.  If I turn async_storeconfigs off then the 
hosts.ip for the agent is updated to the correct IP of the agent itself.

I figured out that the incorrect IP being updated in hosts.ip from where 
puppetqd is running from because I took puppetqd off of the puppetmaster and 
ran it temporarily on another system to consume the queue from the 
puppetmaster.  In this setup the IP changed from the IP of the puppetmaster 
(where puppetqd was previously running) to the new system running puppetqd.

I am using puppet 2.7.5 on SLES11.


-- 
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.

Reply via email to