[Bug 1878417] Re: Floppy causes processes to hang when trying to access an empty drive
Puppet loads Facter, which has a "partitions" fact and a "disks" fact, both of which may be worth investigating. I'm moving this to the "facter" package. ** Package changed: puppet (Ubuntu) => facter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878417 Title: Floppy causes processes to hang when trying to access an empty drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1878417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573561] Re: /etc/default/varnish is ignored (fixed values in systemd service)
I strongly recommend you to use a way to configure your service in a way as to keep the entire commandline in one place, instead of keeping it in several files. Environmentfiles are good for giving a running service environment variables for it to use after startup. I do not recommend using it for creating commandlines when there are other options available. With sysvinit it was the least-worst option. If you _do_ want to split the options into another file, and you use systemd, please consider adding a /etc/systemd/system/varnish.service.d /read-options-from-environment.conf with: [Service] # at least one of... EnvironmentFile=-/etc/sysconfig/varnish EnvironmentFile=-/etc/default/varnish EnvironmentFile=-/etc/varnish/environment # Reset and set commandline ExecStart= ExecStart=/usr/sbin/varnishd $OPTIONS Also, look at man:systemd.service(5) for how systemd parses whitespace inside variables for constructing command line arguments. You may need to add several option variables if some arguments contain whitespace. Also, I do not think you should blame systemd for this. As the package maintainer, _I_ discourage the use of EnviromentFile= for command line arguments. Systemd does not, and documents it rather well. You are free to use both ways to configure your service, and you can add a service configuration fragment to do so if you like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573561 Title: /etc/default/varnish is ignored (fixed values in systemd service) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676242] Re: reload-vcl doesn't support -j option
In varnish 5.2.0-1, the "reload-vcl" script was replaced with a "varnishreload" script from upstream. This should take care of this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676242 Title: reload-vcl doesn't support -j option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1676242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Correct behaviour (default to systemd, determine if it is running, fallback to upstart / sysvinit) seems to have been added to puppet upstream at 4.1.0-87-g7fe6164, just a few days ago. This looks like it will be part of the puppet 4.1.1 release. The packages currently in debian stable was changed to use the service command, which should work with all init systems in Debian/Ubuntu at this time. The upstream changes look possible to backport to puppet 3.7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Correct behaviour (default to systemd, determine if it is running, fallback to upstart / sysvinit) seems to have been added to puppet upstream at 4.1.0-87-g7fe6164, just a few days ago. This looks like it will be part of the puppet 4.1.1 release. The packages currently in debian stable was changed to use the service command, which should work with all init systems in Debian/Ubuntu at this time. The upstream changes look possible to backport to puppet 3.7. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+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 1397910] [NEW] Puppet daemon dies from SIGUSR1 if no certificate
Jurjen Bokma j.bo...@rug.nl writes: Right after boot, the Puppet agent daemon is started. It may be running before hostname resolution is available. If it is, Puppet is unable to receive a certificate. A Puppet daemon that receives SIGUSR1 should try to do a Puppet run immediately. But if it has no certificate, it dies instead, leaving the host unable to receive further configuration until the next reboot. IMHO, Puppet should not die, but retry fetching a certificate. Barring that, an upstart job could restart the daemon when it dies. I could write that upstart job, but I wonder how the maintenance of such distribution-specific config is organized, and whether to push it upstream through Ubuntu or through PuppetLabs. The init scripts, upstart jobs, systemd services, and whatever someone will think of next to start a service, is handled by the distribution packaging. The puppet packages in Ubuntu trusty, utopic and vivid are unmodified from the ones in Debian. I will gladly add upstart jobs for the various puppet services to the Debian packaging. If you would like to contribute some of them, please attach them to this Launchpad bug, or to a Debian BTS bug. Using respawn does sounds like a workaround in this case, though. I'd say that puppet agent dying on SIGUSR1 in some phase of startup is a bug. I did a few searches at the upstream bug tracker (https://tickets.puppetlabs.com/browse/PUP), but could not find any bug filed for it, open or closed. -- Stig Sandbeck Mathisen -- 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/1397910 Title: Puppet daemon dies from SIGUSR1 if no certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910/+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 1397898] [NEW] incorrect PID in initscript
Jurjen Bokma j.bo...@rug.nl writes: ** Patch added: Patch to make Puppet initscript find the PID of the daemon https://bugs.launchpad.net/bugs/1397898/+attachment/4271933/+files/puppet-init.patch That's a delightfully evil hack. Will using an upstart job work instead, or do you need to keep track of the PID there, as well (something for post-start, then)? -- Stig Sandbeck Mathisen -- 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
Re: [Bug 1397910] [NEW] Puppet daemon dies from SIGUSR1 if no certificate
Jurjen Bokma j.bo...@rug.nl writes: Right after boot, the Puppet agent daemon is started. It may be running before hostname resolution is available. If it is, Puppet is unable to receive a certificate. A Puppet daemon that receives SIGUSR1 should try to do a Puppet run immediately. But if it has no certificate, it dies instead, leaving the host unable to receive further configuration until the next reboot. IMHO, Puppet should not die, but retry fetching a certificate. Barring that, an upstart job could restart the daemon when it dies. I could write that upstart job, but I wonder how the maintenance of such distribution-specific config is organized, and whether to push it upstream through Ubuntu or through PuppetLabs. The init scripts, upstart jobs, systemd services, and whatever someone will think of next to start a service, is handled by the distribution packaging. The puppet packages in Ubuntu trusty, utopic and vivid are unmodified from the ones in Debian. I will gladly add upstart jobs for the various puppet services to the Debian packaging. If you would like to contribute some of them, please attach them to this Launchpad bug, or to a Debian BTS bug. Using respawn does sounds like a workaround in this case, though. I'd say that puppet agent dying on SIGUSR1 in some phase of startup is a bug. I did a few searches at the upstream bug tracker (https://tickets.puppetlabs.com/browse/PUP), but could not find any bug filed for it, open or closed. -- Stig Sandbeck Mathisen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397910 Title: Puppet daemon dies from SIGUSR1 if no certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1397898] [NEW] incorrect PID in initscript
Jurjen Bokma j.bo...@rug.nl writes: ** Patch added: Patch to make Puppet initscript find the PID of the daemon https://bugs.launchpad.net/bugs/1397898/+attachment/4271933/+files/puppet-init.patch That's a delightfully evil hack. Will using an upstart job work instead, or do you need to keep track of the PID there, as well (something for post-start, then)? -- Stig Sandbeck Mathisen -- 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 1390771] Re: vim-puppet syntax highlighting scripts are not effective
The package description for vim-puppet says: # As per the Debian vim policy, installed addons are not activated # automatically, but the vim-addon-manager tool can be used for this # purpose. Not sure if this is also the Ubuntu policy for vim addons, but since this package is unmodified from its Debian version, that's what you see. -- 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/1390771 Title: vim-puppet syntax highlighting scripts are not effective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1390771/+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 1390771] Re: vim-puppet syntax highlighting scripts are not effective
The package description for vim-puppet says: # As per the Debian vim policy, installed addons are not activated # automatically, but the vim-addon-manager tool can be used for this # purpose. Not sure if this is also the Ubuntu policy for vim addons, but since this package is unmodified from its Debian version, that's what you see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390771 Title: vim-puppet syntax highlighting scripts are not effective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1390771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322757] Re: Mysql_grant not idempotent
There is no mysql_grant resource in the puppet-module-puppetlabs- apache package. I guess this should have been filed on the puppet-module-puppetlabs- mysql package instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322757 Title: Mysql_grant not idempotent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet-module-puppetlabs-apache/+bug/1322757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1276766] Re: puppet incorrectly enumerates upstart jobs when called with puppet resource service
On Wed, Apr 30, 2014 at 05:02:44PM -, Matthew Wedgwood wrote: Fixed in upstream: https://tickets.puppetlabs.com/browse/PUP-1332 Not sure about the fixed. They are adding to a list of services which are known to need parameters to start. They are not fixing the upstart service provider. -- 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/1276766 Title: puppet incorrectly enumerates upstart jobs when called with puppet resource service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+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 1276766] Re: puppet incorrectly enumerates upstart jobs when called with puppet resource service
On Wed, Apr 30, 2014 at 05:02:44PM -, Matthew Wedgwood wrote: Fixed in upstream: https://tickets.puppetlabs.com/browse/PUP-1332 Not sure about the fixed. They are adding to a list of services which are known to need parameters to start. They are not fixing the upstart service provider. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276766 Title: puppet incorrectly enumerates upstart jobs when called with puppet resource service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: This is a bug in puppet, then; there's no reason that puppet should be trying to call 'status startpar-bridge', and the fact that it's doing so is a bug in the puppet code in question. When you run puppet resource service, puppet will enumerate _all_ services on that server (init scripts, upstart jobs, systemd services, whatnot, and then check if it is running, and if it is enabled on boot. When the operatingsystem is ubuntu, the service provider is upstart, The relevant code for handling services on ubuntu is: defaultfor :operatingsystem = :ubuntu commands :start = /sbin/start, :stop= /sbin/stop, :restart = /sbin/restart, :status_exec = /sbin/status, :initctl = /sbin/initctl Is this wrong for Ubuntu? -- Stig Sandbeck Mathisen -- 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/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+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 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: Not being particularly familiar with puppet's internals, I don't know if the above is wrong per se. But startpar-bridge (and other jobs present on Ubuntu by default, such as network-interface and network-interface-security) are instantiated jobs; calling 'status network-interface' without specifying a network interface is not meaningful, and any errors returned from 'status' about 'unknown parameter' or 'unknown instance' should not be treated as failures by puppet. That was what I was missing; instantiation. Thanks. :) If puppet needs to get a list of all jobs running on the system, including instantiated jobs, it should use the 'initctl list' interface. It does, but I think something is off inside puppet's guts. As far as I can see in the source (ruby code at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb#L47) it does initctl list, and picks the first word of each line, unless the service in question is network-interface or network-interface-security. It looks like puppet does not handle instances in a generic way, but special cases it for network-interface and network-interface-security, and then hardcoded with INTERFACE=foo and JOB=bar. It looks like the instance variable name differs between services, so if my assumption is correct, I wonder what would be the generic way of enumerating services the correct way would be to find this variable for all instanciated services. -- Stig Sandbeck Mathisen -- 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/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+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 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: This is a bug in puppet, then; there's no reason that puppet should be trying to call 'status startpar-bridge', and the fact that it's doing so is a bug in the puppet code in question. When you run puppet resource service, puppet will enumerate _all_ services on that server (init scripts, upstart jobs, systemd services, whatnot, and then check if it is running, and if it is enabled on boot. When the operatingsystem is ubuntu, the service provider is upstart, The relevant code for handling services on ubuntu is: defaultfor :operatingsystem = :ubuntu commands :start = /sbin/start, :stop= /sbin/stop, :restart = /sbin/restart, :status_exec = /sbin/status, :initctl = /sbin/initctl Is this wrong for Ubuntu? -- Stig Sandbeck Mathisen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: Not being particularly familiar with puppet's internals, I don't know if the above is wrong per se. But startpar-bridge (and other jobs present on Ubuntu by default, such as network-interface and network-interface-security) are instantiated jobs; calling 'status network-interface' without specifying a network interface is not meaningful, and any errors returned from 'status' about 'unknown parameter' or 'unknown instance' should not be treated as failures by puppet. That was what I was missing; instantiation. Thanks. :) If puppet needs to get a list of all jobs running on the system, including instantiated jobs, it should use the 'initctl list' interface. It does, but I think something is off inside puppet's guts. As far as I can see in the source (ruby code at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb#L47) it does initctl list, and picks the first word of each line, unless the service in question is network-interface or network-interface-security. It looks like puppet does not handle instances in a generic way, but special cases it for network-interface and network-interface-security, and then hardcoded with INTERFACE=foo and JOB=bar. It looks like the instance variable name differs between services, so if my assumption is correct, I wonder what would be the generic way of enumerating services the correct way would be to find this variable for all instanciated services. -- Stig Sandbeck Mathisen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1284095] [NEW] add configtest action to init.d script
Samuele Giovanni Tonon 1284...@bugs.launchpad.net writes: i think they are two totally different scenarios. i'd use -C or configtest just as a syntax check, the same way apachectl configtest or nginx -t -c /etc/nginx/nginx.conf . Actually, good point. I've been using varnishadm vcl.load instead of -C. It does check the config, but I guess that only works if you have a running varnish. -- Stig Sandbeck Mathisen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284095 Title: add configtest action to init.d script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1284095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1284095] [NEW] add configtest action to init.d script
On Mon, Feb 24, 2014 at 01:02:41PM -, Samuele Giovanni Tonon wrote: Public bug reported: hello, it would be awesome to have a configtest action in the init.d script , in this way you can safely test a vcl configuration by just doing /etc/init.d/varnish configtest Thank you. Automatic testing of the configuration with this before starting the service is a very good feature. I'm less convinced it should replace varnishadm for interactive use, though. -- Stig -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284095 Title: add configtest action to init.d script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/1284095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Puppet will need hiera when you apply a manifest containing any parameterized class, like the one in your example. -- 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/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
(and this is new functionality in puppet 3.x, it does not apply to puppet 2.7) -- 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/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
(and this is new functionality in puppet 3.x, it does not apply to puppet 2.7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Puppet will need hiera when you apply a manifest containing any parameterized class, like the one in your example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Correct. This packaging bug was fixed in the debian repository just before the 3.3.0-1 release, with commit id 11a376f8348dfa2c254b19f7b29aec13940aeb92. The ruby-hiera dependency was moved from the puppetmaster-common package to the puppet-common package. Previously, this was only needed by the puppet master, and the dependency was not moved to the correct place until 3.3.0-1 See also http://anonscm.debian.org/gitweb/?p=pkg- puppet/puppet.git;a=commitdiff;h=11a376f8348dfa2c254b19f7b29aec13940aeb92 -- 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/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Correct. This packaging bug was fixed in the debian repository just before the 3.3.0-1 release, with commit id 11a376f8348dfa2c254b19f7b29aec13940aeb92. The ruby-hiera dependency was moved from the puppetmaster-common package to the puppet-common package. Previously, this was only needed by the puppet master, and the dependency was not moved to the correct place until 3.3.0-1 See also http://anonscm.debian.org/gitweb/?p=pkg- puppet/puppet.git;a=commitdiff;h=11a376f8348dfa2c254b19f7b29aec13940aeb92 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197392] Re: puppetmaster-passenger fails to install
Related Debian bug is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070 When this is resolved, it should work both apache2.2 and apache2.4. -- Stig ** Bug watch added: Debian Bug tracker #713070 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070 -- 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/1197392 Title: puppetmaster-passenger fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1197392/+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 1197392] Re: puppetmaster-passenger fails to install
Related Debian bug is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070 When this is resolved, it should work both apache2.2 and apache2.4. -- Stig ** Bug watch added: Debian Bug tracker #713070 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197392 Title: puppetmaster-passenger fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1197392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1182613] Re: puppet completely broken on saucy
On Thu, May 23, 2013 at 01:33:28PM -, Matthias Klose wrote: falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. At a glance, it looks like facter is not available in the load path of ruby1.9. I'd start looking at the facter package. -- Stig -- 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/1182613 Title: puppet completely broken on saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1182613/+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 1182613] Re: puppet completely broken on saucy
On Thu, May 23, 2013 at 01:33:28PM -, Matthias Klose wrote: falling back to ruby1.8 is not a solution. Are there any extensions not yet built for 1.9? If not, please do so. At a glance, it looks like facter is not available in the load path of ruby1.9. I'd start looking at the facter package. -- Stig -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1182613/+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)
On Thu, Mar 07, 2013 at 06:59:44PM -, Adam Gandelman wrote: - The *.postinst changes still look valid, but you haven't specified why they can be dropped. (aside: It looks like these changes would be suitable candidates for submitting to debian in the future to reduce the delta?) How would I be able to see these changes? I'm not too familiar with the ubuntu packaging helpers and tools, but I'd love to be able to reduce the differences between the Ubuntu and Debian versions. -- 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)
On Thu, Mar 07, 2013 at 06:59:44PM -, Adam Gandelman wrote: - The *.postinst changes still look valid, but you haven't specified why they can be dropped. (aside: It looks like these changes would be suitable candidates for submitting to debian in the future to reduce the delta?) How would I be able to see these changes? I'm not too familiar with the ubuntu packaging helpers and tools, but I'd love to be able to reduce the differences between the Ubuntu and Debian versions. -- 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
Re: [Bug 1143009] Re: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main)
On Mon, Mar 04, 2013 at 07:59:33AM -, Benjamin Kerensa wrote: @Micah: Hi, This we actually just a test I was doing at our jam today but we did discuss plans to land a newer version of puppet and I do agree it would be most appropriate to have a released version and get that through debian. @Michael: Hi, So we would love to land a newer version of puppet and it seems Nigel is the maintainer in Debian so if he could bring debian up to a newer released version we could indeed sync that down instead of carrying a delta Debian is currently in freeze but I think it might be possible for him to upload a new released version to experimental and then we could sync? (Micah ??) I'll push the 3.1 release to Debian experimental. -- 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.0.0~rc2-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.0.0~rc2-1 (main) from Debian experimental (main)
On Mon, Mar 04, 2013 at 07:59:33AM -, Benjamin Kerensa wrote: @Micah: Hi, This we actually just a test I was doing at our jam today but we did discuss plans to land a newer version of puppet and I do agree it would be most appropriate to have a released version and get that through debian. @Michael: Hi, So we would love to land a newer version of puppet and it seems Nigel is the maintainer in Debian so if he could bring debian up to a newer released version we could indeed sync that down instead of carrying a delta Debian is currently in freeze but I think it might be possible for him to upload a new released version to experimental and then we could sync? (Micah ??) I'll push the 3.1 release to Debian experimental. -- 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.0.0~rc2-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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
The source of this problem is in the debian packaging repository for 2.7.11-1. The /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb file is included in the debian/2.7.11-1 packaging when it shouldn't. The difference in the puppet source between the upstream and the packaging branches reverts back to expected when 2.7.12 is imported, so the problem is isolated to 2.7.11, which unfortunately is in an LTS release. It should be safe to remove this file from the 2.7.11 packaging for an eventual point release. All it does, if present, is to change the process name in the process table. I've tested operation on a precise puppet node before and after removing the file. I have observed the process hanging before removing the file. It runs normally after removing it, and I have not observed hangs for the last 20 runs. -- 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
The source of this problem is in the debian packaging repository for 2.7.11-1. The /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb file is included in the debian/2.7.11-1 packaging when it shouldn't. The difference in the puppet source between the upstream and the packaging branches reverts back to expected when 2.7.12 is imported, so the problem is isolated to 2.7.11, which unfortunately is in an LTS release. It should be safe to remove this file from the 2.7.11 packaging for an eventual point release. All it does, if present, is to change the process name in the process table. I've tested operation on a precise puppet node before and after removing the file. I have observed the process hanging before removing the file. It runs normally after removing it, and I have not observed hangs for the last 20 runs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1076286] [NEW] Puppet agent not correcly configuring facts synch'd from master
Hello, and thanks for reporting an issue with puppet.
Andrea Biancini andrea.bianc...@gmail.com writes:
To reproduce the error, for example, I could define in the master a site.pp
as follow:
node puppetclient {
include modulewithfact
}
You do not need a manifest in order to check if facts propagate from
master to nodes. Factsync takes place before the manifest is compiled.
1: Set pluginsync=true in /etc/puppet/puppet.conf on the node
2: Run puppet agent --test --noop on the node
3: If you have authenticated the node to the master, you should see the
fact being transmitted.
4: Verify by:
run facter --puppet on the node. Do you see your fact?
check /var/lib/puppet/yaml/facts/node.yaml on the master, do you
see the new fact there?
What is your puppet version, your facter version, and your ubuntu
version?
To avoid this situation I simply added to the /etc/default/puppet file
the following line:
FACTERLIB=/var/lib/puppet/lib/facter
which permits to include in the facterlib the folder where facts from
the server are synchronized by the agent.
I don't think this is the correct fix. This will not have any effect if
you run puppet agent --test on the command line.
--
Stig Sandbeck Mathisen
--
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
Re: [Bug 1076286] [NEW] Puppet agent not correcly configuring facts synch'd from master
Hello, and thanks for reporting an issue with puppet.
Andrea Biancini andrea.bianc...@gmail.com writes:
To reproduce the error, for example, I could define in the master a site.pp
as follow:
node puppetclient {
include modulewithfact
}
You do not need a manifest in order to check if facts propagate from
master to nodes. Factsync takes place before the manifest is compiled.
1: Set pluginsync=true in /etc/puppet/puppet.conf on the node
2: Run puppet agent --test --noop on the node
3: If you have authenticated the node to the master, you should see the
fact being transmitted.
4: Verify by:
run facter --puppet on the node. Do you see your fact?
check /var/lib/puppet/yaml/facts/node.yaml on the master, do you
see the new fact there?
What is your puppet version, your facter version, and your ubuntu
version?
To avoid this situation I simply added to the /etc/default/puppet file
the following line:
FACTERLIB=/var/lib/puppet/lib/facter
which permits to include in the facterlib the folder where facts from
the server are synchronized by the agent.
I don't think this is the correct fix. This will not have any effect if
you run puppet agent --test on the command line.
--
Stig Sandbeck Mathisen
--
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
Re: [Bug 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
the reason appears to be because the /etc/init.d/puppet file contains the
line:
PIDFILE=/var/run/puppet/${NAME}.pid
I assume in this case ${NAME} resolves to puppet
[...]
Simply changing the line in the /etc/init.d/puppet file from ${NAME}
to agent should (and does) solve the problem
There is no need to assume, that is set explicitly in the init script.
What does the command 'grep ^NAME /etc/init.d/puppet' give as output in
your case?
In the debian packaging, it was set to puppetd in 0.25.5-1, but
changed to agent in 2.6.0-1. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An md5sum /etc/init.d/puppet may
also help, if they differ.
--
Stig Sandbeck Mathisen
--
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/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
Indeed the only difference between the two files is one (the one
installed by the puppetmaster) has PIDFILE=/var/run/puppet/agent.pid
and the other (before puppetmaster changed it) had
/var/run/puppet/${NAME}.pid (difference tracked with mercurial)
After setting NAME in /etc/init.d/puppet, the file /etc/default/puppet
is sourced, so a NAME=puppet in /etc/default/puppet could give the
reported behaviour. Apart from that, I'm out of ideas.
Anyhow, thanks for a very thorough report, even if the source of the bug
was not found. :)
--
Stig Sandbeck Mathisen
--
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/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
the reason appears to be because the /etc/init.d/puppet file contains the
line:
PIDFILE=/var/run/puppet/${NAME}.pid
I assume in this case ${NAME} resolves to puppet
[...]
Simply changing the line in the /etc/init.d/puppet file from ${NAME}
to agent should (and does) solve the problem
There is no need to assume, that is set explicitly in the init script.
What does the command 'grep ^NAME /etc/init.d/puppet' give as output in
your case?
In the debian packaging, it was set to puppetd in 0.25.5-1, but
changed to agent in 2.6.0-1. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An md5sum /etc/init.d/puppet may
also help, if they differ.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
Indeed the only difference between the two files is one (the one
installed by the puppetmaster) has PIDFILE=/var/run/puppet/agent.pid
and the other (before puppetmaster changed it) had
/var/run/puppet/${NAME}.pid (difference tracked with mercurial)
After setting NAME in /etc/init.d/puppet, the file /etc/default/puppet
is sourced, so a NAME=puppet in /etc/default/puppet could give the
reported behaviour. Apart from that, I'm out of ideas.
Anyhow, thanks for a very thorough report, even if the source of the bug
was not found. :)
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012649] Re: puppet-common postinst assumes puppet group is present if puppet user is present
Related debian bug is http://bugs.debian.org/650527, and this is fixed in 2.7.12-2. ** Bug watch added: Debian Bug tracker #650527 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650527 -- 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/1012649 Title: puppet-common postinst assumes puppet group is present if puppet user is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1012649/+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 1012649] Re: puppet-common postinst assumes puppet group is present if puppet user is present
Related debian bug is http://bugs.debian.org/650527, and this is fixed in 2.7.12-2. ** Bug watch added: Debian Bug tracker #650527 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650527 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012649 Title: puppet-common postinst assumes puppet group is present if puppet user is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1012649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 885471] Re: move DAEMON_OPTS to /etc/default/varnishncsa
In varnish 3.0.1-2 and on it is possible to set DAEMON_OPTS in /etc/default/varnishncsa without it being overwritten in /etc/init.d/varnishncsa. The first ubuntu release which includes this change is precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885471 Title: move DAEMON_OPTS to /etc/default/varnishncsa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/885471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 914989] Re: cpm crashes when trying to use gpg key with UTF-8 extended characters
Forwarded upstream to https://github.com/comotion/cpm/issues/25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/914989 Title: cpm crashes when trying to use gpg key with UTF-8 extended characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpm/+bug/914989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682680] Re: New upstream release, gearmand 0.24
gearmand 0.27-1 has been uploaded to debian. When that version is pulled into Ubuntu, this bug should auto-close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682680 Title: New upstream release, gearmand 0.24 To manage notifications about this bug go to: https://bugs.launchpad.net/pkg-gearman/+bug/682680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682680] Re: New upstream release, gearmand 0.24
** Summary changed: - New upstream release, gearmand 0.23 + New upstream release, gearmand 0.24 ** Description changed: - There is a new upstream release, gearmand 0.17, available from upstream + There is a new upstream release, gearmand 0.24, available from upstream at https://launchpad.net/gearmand. - I'm working on Debian packaging of mod_gearmand for Nagios/Icinga, - this needs at least version 0.14 of gearmand. - Please let me know if I can assist with packaging in any way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682680 Title: New upstream release, gearmand 0.24 To manage notifications about this bug go to: https://bugs.launchpad.net/pkg-gearman/+bug/682680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793632] Re: puppetmaster and puppet have clashing logrotate configs
This is fixed in 2.6.5-1 and later, in commit c29ee05efdfbfaf0fe96573571047bd74a27bc11 in the debian packaging repository. -- 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/793632 Title: puppetmaster and puppet have clashing logrotate configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/793632/+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 793632] Re: puppetmaster and puppet have clashing logrotate configs
This is fixed in 2.6.5-1 and later, in commit c29ee05efdfbfaf0fe96573571047bd74a27bc11 in the debian packaging repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793632 Title: puppetmaster and puppet have clashing logrotate configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/793632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789998] Re: Varnish startscript broken in natty
:-, in combination with set -u in shell scripts, used to allow some
variables to be empty. That it looks like a smiley is just an added
bonus.
Example:
$ set -u
$ echo ${START}
bash: START: unbound variable
$ echo ${START:-}
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789998
Title:
Varnish startscript broken in natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747214] [NEW] Wireless interface disabled after upgrade to natty and reboot
Public bug reported: Binary package hint: module-init-tools In the file /etc/modprobe.d/intel-3945-iwlagn-disable11n.conf, the line options iwl3945 11n_disable=1 prevents loading of the iwl3945 module in natty. This fails, on kernel 2.6.38-7-generic, with the following error message in the kernel log: iwl3945: Unknown parameter `11n_disable' ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: module-init-tools 3.12-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Fri Apr 1 14:03:54 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: module-init-tools UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago) ** Affects: module-init-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747214 Title: Wireless interface disabled after upgrade to natty and reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747214] Re: Wireless interface disabled after upgrade to natty and reboot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747214 Title: Wireless interface disabled after upgrade to natty and reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682680] Re: New upstream release, gearmand 0.17
** Summary changed: - New upstream release, gearmand 0.14 + New upstream release, gearmand 0.17 ** Description changed: - There is a new upstream release, gearmand 0.14, available from upstream + There is a new upstream release, gearmand 0.17, available from upstream at https://launchpad.net/gearmand. I'm working on Debian packaging of mod_gearmand for Nagios/Icinga, - this needs version 0.14 of gearmand. + this needs at least version 0.14 of gearmand. Please let me know if I can assist with packaging in any way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682680 Title: New upstream release, gearmand 0.17 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 723172] [NEW] lvresize/lvextend manpages missing --resizefs option
Public bug reported: Binary package hint: lvm2 When running lvresize or lvextend with the --help option, it mentions a --resizefs option which is not covered in the man page. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: lvm2 2.02.54-1ubuntu6 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 Date: Tue Feb 22 15:26:03 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: lvm2 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug manpage maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/723172 Title: lvresize/lvextend manpages missing --resizefs option -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 723172] Re: lvresize/lvextend manpages missing --resizefs option
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/723172 Title: lvresize/lvextend manpages missing --resizefs option -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682680] Re: New upstream release, gearmand 0.14
I've made mod-gearman packages from 0.14, available at http://people.debian.org/~ssm/debs/unstable/source/ I added one IPv6 fix to debian/patches, from https://bugs.launchpad.net/gearmand/+bug/635476 (A struct sockaddr isn't big enough to hold an ipv6 address) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682680 Title: New upstream release, gearmand 0.14 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645745] Re: Some package dependency should be moved to puppet
Not exactly true anymore. The client and the puppetmaster is in the puppet-common package, all the puppet and the puppetmaster packages contain are the compatibility links used to retain the old script names, their man pages, and the init scripts. The puppet binary is now in the puppet-common package, and that one does agent, master, cert, doc, etcetera... A bit confusing, that's true. -- Some package dependency should be moved to puppet https://bugs.launchpad.net/bugs/645745 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in ubuntu. -- 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 645745] Re: Some package dependency should be moved to puppet
Not exactly true anymore. The client and the puppetmaster is in the puppet-common package, all the puppet and the puppetmaster packages contain are the compatibility links used to retain the old script names, their man pages, and the init scripts. The puppet binary is now in the puppet-common package, and that one does agent, master, cert, doc, etcetera... A bit confusing, that's true. -- Some package dependency should be moved to puppet https://bugs.launchpad.net/bugs/645745 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 488258] Re: libvarnish-dev does not install /usr/lib/libvarnishapi.so
** Branch linked: lp:debian/sid/varnish -- libvarnish-dev does not install /usr/lib/libvarnishapi.so https://bugs.launchpad.net/bugs/488258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569060] Re: varnish daemon should not start by default
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue. http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html Chances are, it'll be available for Ubuntu quite soon. -- varnish daemon should not start by default https://bugs.launchpad.net/bugs/569060 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 488258] Re: libvarnish-dev does not install /usr/lib/libvarnishapi.so
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue. http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html Chances are, it'll be available for Ubuntu quite soon. -- libvarnish-dev does not install /usr/lib/libvarnishapi.so https://bugs.launchpad.net/bugs/488258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 461593] Re: varnishlog should not run as root
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue. http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html Chances are, it'll be available for Ubuntu quite soon. -- varnishlog should not run as root https://bugs.launchpad.net/bugs/461593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 605977] [NEW] emacs puppet-mode not auto loaded in lucid
Thanks for the bug report. This issue is fixed in the 0.25.5 release, which will be available (or superseded by 2.6.0) in maverick. -- Stig Sandbeck Mathisen ooo, shiny! -- emacs puppet-mode not auto loaded in lucid https://bugs.launchpad.net/bugs/605977 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in ubuntu. -- 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 605977] [NEW] emacs puppet-mode not auto loaded in lucid
Thanks for the bug report. This issue is fixed in the 0.25.5 release, which will be available (or superseded by 2.6.0) in maverick. -- Stig Sandbeck Mathisen ooo, shiny! -- emacs puppet-mode not auto loaded in lucid https://bugs.launchpad.net/bugs/605977 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 488258] [NEW] libvarnish-dev does not install /usr/lib/libvarnishapi.so
Thanks, I'll take a look at this issue. -- Stig Sandbeck Mathisen ooo, shiny! -- libvarnish-dev does not install /usr/lib/libvarnishapi.so https://bugs.launchpad.net/bugs/488258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 461593] Re: varnishlog should not run as root
Thanks, I agree it should not run as root. I'll add an unprivileged user for varnishlog. -- varnishlog should not run as root https://bugs.launchpad.net/bugs/461593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 331521] Re: please sync varnish from unstable
On 19. feb.. 2009, at 19.17, Jamie Strandboge wrote: Is 2.0.3 bug fix only, or does it add any new features over 2.0.2? Almost entirely a bug fix release, but there has been one enhancement to an existing function in VCL, and some defaults have been changed. Changelog: http://varnish.projects.linpro.no/browser/tags/varnish-2.0.3/varnish- cache/doc/changes-2.0.2-2.0.3.xml The 2.1.* releases will bring new features. -- please sync varnish from unstable https://bugs.launchpad.net/bugs/331521 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
