Bug #7653

puppet queue seems to ignore rundir in config file

Added by Digant Kasundra 12 months ago. Updated 6 months ago.

Status:Closed Start date:05/24/2011
Priority:Normal Due date:
Assignee:Daniel Pittman % Done:

0%
Category:queuing
Target version:2.6.13
Affected Puppet version:2.6.8 Branch:
Keywords:
Votes: 0

Description

When running puppet queue, it doesn’t seem to honor the rundir setting in the puppet.conf file it is using. We are currently having to specify it on the command line to get it to put the pid file in the proper directory.

History

#1
Updated by Zach Leslie 12 months ago

What configuration section do you have rundir specified in?

#2
Updated by Nan Liu 10 months ago

  • Status changed from Unreviewed to Rejected

Seems most likely to be an issue with puppet.conf settings: (it seems to load the conf setting without issues)

# puppet queue --configprint rundir
/var/run/pe-puppet/queue/queue.pid
# puppet queue
# ls /var/run/pe-puppet/queue/queue.pid
/var/run/pe-puppet/queue/queue.pid

Feel free to reopen if you have more info or conflicting results.

#3
Updated by Digant Kasundra 9 months ago

  • Status changed from Rejected to Re-opened

We have rundir configured in the [main] section:

rundir = /var/run/puppet

And we get…

# puppet queue --configprint rundir
/var/lib/puppet/run

#4
Updated by Digant Kasundra 8 months ago

Any updates?

#5
Updated by Nigel Kersten 8 months ago

So Digant, the problem is that [main] in general isn’t being inherited for settings by [queue] ? Or just this one setting?

#6
Updated by Digant Kasundra 8 months ago

It seemed to only be this one setting. At least that’s the setting that stuck out. I can certainly try other settings if you have others in mind you want me to try.

#7
Updated by Nigel Kersten 8 months ago

It would be great if you could test other queue settings, as that will help.

#8
Updated by Digant Kasundra 8 months ago

I tried some of the queue specific settings (queue_source, async_storeconfigs, etc) and they all work fine.

#9
Updated by Nigel Kersten 8 months ago

  • Status changed from Re-opened to Accepted
  • Target version set to 2.6.10

Digant, we’re going to see if this is still a problem in 2.7.x, and in any case will see if we can get a fix in for the last 2.6.x release we’re planning to do, 2.6.10.

#10
Updated by Digant Kasundra 8 months ago

Excellent! Thanks Nigel!

#11
Updated by Nigel Kersten 8 months ago

  • Target version changed from 2.6.10 to 2.6.11

#12
Updated by Nigel Kersten 8 months ago

  • Target version changed from 2.6.11 to 2.6.12

#13
Updated by Michael Stahnke 7 months ago

  • Target version changed from 2.6.12 to 2.6.13

#14
Updated by James Turnbull 7 months ago

  • Category set to queuing
  • Assignee set to Daniel Pittman

#15
Updated by Daniel Pittman 7 months ago

G'day Digant.

I am trying to reproduce this with the current latest 2.6 release, and I get the right behaviour with the default configuration file and with an explicit configuration file. I also see this with 2.6.8.

Can you still reproduce this problem?

#16
Updated by Daniel Pittman 7 months ago

  • Status changed from Accepted to Needs More Information

#17
Updated by Daniel Pittman 6 months ago

  • Status changed from Needs More Information to Closed

Daniel Pittman wrote:

I am trying to reproduce this with the current latest 2.6 release, and I get the right behaviour with the default configuration file and with an explicit configuration file. I also see this with 2.6.8. Can you still reproduce this problem?

We still can’t reproduce this, so we are going to mark this as closed. Digant, or anyone, if you can reproduce this that would be awesome; we would love to fix the issue, if we can figure out what causes it.

Also available in: Atom PDF