[Bug 1397898] Re: incorrect PID in initscript

2014-12-01 Thread Matthaus Owens
The puppet agent writes its own pidfile, to $vardir/run/agent.pid
depending on what is in puppet.conf. If you are seeing problems with
that, I would encourage you to open a bug upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397898

Title:
  incorrect PID in initscript

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397898/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1397898] Re: incorrect PID in initscript

2014-12-01 Thread Matthaus Owens
Sorry, I should have said pidfile is written to $rundir/agent.pid.
$rundir defaults to $vardir/run if not specified in puppet.conf.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397898

Title:
  incorrect PID in initscript

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397898/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1397898] Re: incorrect PID in initscript

2014-12-01 Thread Matthaus Owens
The puppet agent writes its own pidfile, to $vardir/run/agent.pid
depending on what is in puppet.conf. If you are seeing problems with
that, I would encourage you to open a bug upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397898

Title:
  incorrect PID in initscript

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397898/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1397898] Re: incorrect PID in initscript

2014-12-01 Thread Matthaus Owens
Sorry, I should have said pidfile is written to $rundir/agent.pid.
$rundir defaults to $vardir/run if not specified in puppet.conf.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397898

Title:
  incorrect PID in initscript

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397898/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1310149] Re: Puppet looking for update-alternatives in another path

2014-04-21 Thread Matthaus Owens
That looks like a bug with the puppet-alternatives module. There is
already a github issue open at https://github.com/adrienthebo/puppet-
alternatives/pull/3 that looks like it covers this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1310149

Title:
  Puppet looking for update-alternatives in another path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310149/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1310149] Re: Puppet looking for update-alternatives in another path

2014-04-21 Thread Matthaus Owens
That looks like a bug with the puppet-alternatives module. There is
already a github issue open at https://github.com/adrienthebo/puppet-
alternatives/pull/3 that looks like it covers this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310149

Title:
  Puppet looking for update-alternatives in another path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310149/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1215282] Re: Possible puppet performance regression with 2.7.11-1ubuntu2.4

2013-08-22 Thread Matthaus Owens
This is probably related to upstream bug
https://projects.puppetlabs.com/issues/21337

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1215282

Title:
  Possible puppet performance regression with 2.7.11-1ubuntu2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1215282/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1215282] Re: Possible puppet performance regression with 2.7.11-1ubuntu2.4

2013-08-22 Thread Matthaus Owens
This is probably related to upstream bug
https://projects.puppetlabs.com/issues/21337

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215282

Title:
  Possible puppet performance regression with 2.7.11-1ubuntu2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1215282/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1143009] Re: Sync puppet 3.1.0-1 (main) from Debian experimental (main)

2013-03-07 Thread Matthaus Owens
Yes, please forward them. :)

On Thu, Mar 7, 2013 at 2:30 PM, Benjamin Kerensa bkere...@ubuntu.com wrote:
 Stig,

 Let me know if you plan to take some of these changes upstream... I
 wonder why we didn't forward them :) anyways if need be I can propose a
 Merge proposal but I would like to reduce the deltas too.

 --
 You received this bug notification because you are subscribed to puppet
 in Ubuntu.
 Matching subscriptions: Puppet Ubuntu Bugs
 https://bugs.launchpad.net/bugs/1143009

 Title:
   Sync puppet 3.1.0-1 (main) from Debian experimental (main)

 Status in “puppet” package in Ubuntu:
   Confirmed

 Bug description:
   Summary (one line):
   Sync puppet 3.1.0-1 (main) from Debian experimental (main)

   Description:
   Please sync puppet 3.1.0-1 (main) from Debian experimental (main)

   Explanation of the Ubuntu delta and why it can be dropped:
 * Resynchronise with Debian. (LP: #1023931) Remaining changes:
   - debian/puppetmaster-passenger.postinst: Make sure we error if puppet
 config print doesn't work
   - debian/puppetmaster-passenger.postinst: Ensure upgrades from
 = 2.7.11-1 fixup passenger apache configuration.
 * Dropped upstreamed patches:
   - debian/patches/CVE-2012-1906_CVE-2012-1986_to_CVE-2012-1989.patch
   - debian/patches/puppet-12844
   - debian/patches/2.7.17-Puppet-July-2012-CVE-fixes.patch
 * Drop Build-Depends on ruby-rspec (in universe):
   - debian/control: remove ruby-rspec from Build-Depends
   - debian/patches/no-rspec.patch: make Rakefile work anyway if rspec
 isn't installed so we can use it in debian/rules.


   Changelog entries since current raring version 2.7.18-1ubuntu1:

   puppet (3.1.0-1) experimental; urgency=low

 * New upstream release
 * Add no-rubygems patch

-- Stig Sandbeck Mathisen s...@debian.org  Mon, 04 Mar 2013 08:48:15
   +0100

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions


--
Matthaus Owens
Release Manager, Puppet Labs

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1143009

Title:
  Sync puppet 3.1.0-1 (main) from Debian experimental (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 1143009] Re: Sync puppet 3.1.0-1 (main) from Debian experimental (main)

2013-03-07 Thread Matthaus Owens
Yes, please forward them. :)

On Thu, Mar 7, 2013 at 2:30 PM, Benjamin Kerensa bkere...@ubuntu.com wrote:
 Stig,

 Let me know if you plan to take some of these changes upstream... I
 wonder why we didn't forward them :) anyways if need be I can propose a
 Merge proposal but I would like to reduce the deltas too.

 --
 You received this bug notification because you are subscribed to puppet
 in Ubuntu.
 Matching subscriptions: Puppet Ubuntu Bugs
 https://bugs.launchpad.net/bugs/1143009

 Title:
   Sync puppet 3.1.0-1 (main) from Debian experimental (main)

 Status in “puppet” package in Ubuntu:
   Confirmed

 Bug description:
   Summary (one line):
   Sync puppet 3.1.0-1 (main) from Debian experimental (main)

   Description:
   Please sync puppet 3.1.0-1 (main) from Debian experimental (main)

   Explanation of the Ubuntu delta and why it can be dropped:
 * Resynchronise with Debian. (LP: #1023931) Remaining changes:
   - debian/puppetmaster-passenger.postinst: Make sure we error if puppet
 config print doesn't work
   - debian/puppetmaster-passenger.postinst: Ensure upgrades from
 = 2.7.11-1 fixup passenger apache configuration.
 * Dropped upstreamed patches:
   - debian/patches/CVE-2012-1906_CVE-2012-1986_to_CVE-2012-1989.patch
   - debian/patches/puppet-12844
   - debian/patches/2.7.17-Puppet-July-2012-CVE-fixes.patch
 * Drop Build-Depends on ruby-rspec (in universe):
   - debian/control: remove ruby-rspec from Build-Depends
   - debian/patches/no-rspec.patch: make Rakefile work anyway if rspec
 isn't installed so we can use it in debian/rules.


   Changelog entries since current raring version 2.7.18-1ubuntu1:

   puppet (3.1.0-1) experimental; urgency=low

 * New upstream release
 * Add no-rubygems patch

-- Stig Sandbeck Mathisen s...@debian.org  Mon, 04 Mar 2013 08:48:15
   +0100

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions


--
Matthaus Owens
Release Manager, Puppet Labs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1143009

Title:
  Sync puppet 3.1.0-1 (main) from Debian experimental (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1081253] [NEW] hiera-puppet should depend on puppet-common

2012-11-20 Thread Matthaus Owens
Public bug reported:

The hiera-puppet backend needs both hiera and puppet to properly
function so the hiera-puppet package should depend on puppet-common.

** Affects: ruby-hiera-puppet (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081253

Title:
  hiera-puppet should depend on puppet-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-hiera-puppet/+bug/1081253/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-16 Thread Matthaus Owens
Andrea,
Can you post the output of your puppet run using `puppet agent -t --trace 
--debug` on the agent? That might help figure out what's going on.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-16 Thread Matthaus Owens
Andrea,
Can you post the output of your puppet run using `puppet agent -t --trace 
--debug` on the agent? That might help figure out what's going on.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-15 Thread Matthaus Owens
Andrea,

The first example was master and agent on the same machine, so it found the 
module in the modulepath without pluginsync. The second example was agent and 
master on different machines.
Can you post the output of your puppet.conf and `puppet agent -t --trace 
--debug` on the agent? That might help figure out what's going on.

Here is the output from that second run.

# Cleanup
root@lucid-64:~# rm -rf /tmp/puppettest 
root@lucid-64:~# rm -rf /var/lib/puppet/lib/

# Puppet Run
root@lucid-64:~# puppet agent -t
info: Retrieving plugin
notice: /File[/var/lib/puppet/lib/facter]/ensure: created
notice: /File[/var/lib/puppet/lib/facter/test_fact.rb]/ensure: defined content 
as '{md5}fc59074ecb5d02756ee6c2095677bb92'
info: Loading downloaded plugin /var/lib/puppet/lib/facter/test_fact.rb
info: Loading facts in /var/lib/puppet/lib/facter/test_fact.rb
info: Caching catalog for lucid-64.localdomain
info: Applying configuration version '1352931741'
notice: /Stage[main]//Node[default]/File[/tmp/puppettest]/ensure: created
notice: Finished catalog run in 0.03 seconds

# Correct content in file
root@lucid-64:~# cat /tmp/puppettest 
Content from the fact

# Correct facter in lib
root@lucid-64:~# find /var/lib/puppet/lib/
/var/lib/puppet/lib/
/var/lib/puppet/lib/facter
/var/lib/puppet/lib/facter/test_fact.rb

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-15 Thread Matthaus Owens
Andrea,

The first example was master and agent on the same machine, so it found the 
module in the modulepath without pluginsync. The second example was agent and 
master on different machines.
Can you post the output of your puppet.conf and `puppet agent -t --trace 
--debug` on the agent? That might help figure out what's going on.

Here is the output from that second run.

# Cleanup
root@lucid-64:~# rm -rf /tmp/puppettest 
root@lucid-64:~# rm -rf /var/lib/puppet/lib/

# Puppet Run
root@lucid-64:~# puppet agent -t
info: Retrieving plugin
notice: /File[/var/lib/puppet/lib/facter]/ensure: created
notice: /File[/var/lib/puppet/lib/facter/test_fact.rb]/ensure: defined content 
as '{md5}fc59074ecb5d02756ee6c2095677bb92'
info: Loading downloaded plugin /var/lib/puppet/lib/facter/test_fact.rb
info: Loading facts in /var/lib/puppet/lib/facter/test_fact.rb
info: Caching catalog for lucid-64.localdomain
info: Applying configuration version '1352931741'
notice: /Stage[main]//Node[default]/File[/tmp/puppettest]/ensure: created
notice: Finished catalog run in 0.03 seconds

# Correct content in file
root@lucid-64:~# cat /tmp/puppettest 
Content from the fact

# Correct facter in lib
root@lucid-64:~# find /var/lib/puppet/lib/
/var/lib/puppet/lib/
/var/lib/puppet/lib/facter
/var/lib/puppet/lib/facter/test_fact.rb

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
And running it from a remote agent had the correct content as well once
pluginsync=true was added to the agent's puppet.conf.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
So if the problem is that custom facts don't get to agents by default
after installing the puppet package, a solution could be to add
pluginsync=true to the puppet.conf in the package, but that might be
surprising to users, depending on what behavior they expect.

Side note: pluginsync defaults to true in Puppet 3.0

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
Robie,
I used a puppetmaster in both cases. In the first example the agent and master 
were on the same sytem, in the second they were on seperate systems.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
And running it from a remote agent had the correct content as well once
pluginsync=true was added to the agent's puppet.conf.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
So if the problem is that custom facts don't get to agents by default
after installing the puppet package, a solution could be to add
pluginsync=true to the puppet.conf in the package, but that might be
surprising to users, depending on what behavior they expect.

Side note: pluginsync defaults to true in Puppet 3.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1076286] Re: Puppet agent not correcly configuring facts synch'd from master

2012-11-14 Thread Matthaus Owens
Robie,
I used a puppetmaster in both cases. In the first example the agent and master 
were on the same sytem, in the second they were on seperate systems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286

Title:
  Puppet agent not correcly configuring facts synch'd from master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs