Issue #3313 has been reported by christian c.

Bug #3313: puppet.conf option client=true/false doesn't seem to work

• Author: christian c
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Affected version: 0.25.4
• Keywords:
• Branch:

Hi, I’m using puppet 0.25.4 on OpenSuse 11.1.

Trying to run puppet as listening client only with “listen=true” and “client=false” options in puppet.conf doesn’t seem to work. After restarting puppet with the new configuration, first thing it does is polling the puppetmaster and afterwards every 30min.

But if I start puppetd with —no-client parameter it polls the puppetmaster only after being triggered by a puppetrun-command coming from the master.

Additionally, if the option works again, you should add it to the configuration reference because right now it isn’t mentioned.

My config: [puppetd]

classfile = $vardir/classes.txt server = puppet localconfig = $vardir/localconfigi httplog = $logdir/http.log listen = true noop = false client = false puppetdlog = $logdir/puppetd.log puppetport = 8139 pluginsync = true

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3228 has been updated by Trevor Vaughan.

Alternatively/additionally (?) the ability to explicitly set the nice-ness of Exec’s and Services would be ideal.

The combination of the two would be extremely useful.

Feature #3228: Add puppet.conf for process priority of puppetd

• Author: Andrew Forgue
• Status: Needs design decision
• Priority: Low
• Assigned to: Luke Kanies
• Category: plumbing
• Target version:
• Affected version: 0.25.4
• Keywords:
• Branch:

It would be nice (no pun intended) to have a puppet.conf option that would specify the priority of the puppetd process. It appears that Ruby has a Process.setpriority that would do this. This way we wouldn’t have to worry about maintaining separate methods to set priority (whether SMF, SRC, /etc/init.d/puppet or otherwise).

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3095 has been updated by Antonio Xanxess.

• Status changed from Needs more information to Closed

Good morning, I feel the delay in writing this. Currently the problem I solved by installing graphics Foreman, due to the large volume of servers we have. Thank you very much and apologize for the inconvenience. Greetins

Feature #3095: Generate summary statistics of a change in the manifest:

• Author: Antonio Xanxess
• Status: Closed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Keywords:
• Branch:

Hi, my name is Antonio Sanchez Aguilar, am employee of CGA, the Advanced Management Center. We take care of maintenance and administration of a fairly large farm, and we puppet adapting to our needs. We currently use cfengine, but we saw that with puppet could be made better control of the changes to the servers. Recently discovered dashboard, and the truth that I really like, but need a Extending the application, because the volumes of servers manage round about two thousand and whether a change on the manifest has been effective or not is very annoying seeing reports (imagine seeing two thousand reports), then we had the need for a generator in the implementation of general statistics the last change made, setting 3 states: changes made, unrealized change and change with errors. Do not know if it would be possible, I added as a feature in Redmine to see if anyone wants to see the development. Thanks in advance, Greetings.

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3320 has been reported by Joe McDonagh.

Feature #3320: tagmail should be more robust

• Author: Joe McDonagh
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Affected version: 0.25.4
• Keywords:
• Branch:

Would be nice if tagmails were a little more configurable. Right now I just get the same e-mail and have to read the body to see what happened, and can’t really filter based on subject, etc. Since Luke said on the channel last night he would like to see it improved I thought I would at least get my idea written down here. My vision is to have tagmail operate like a resource:

tagmail { body_header => "The following is a list of security-tagged resources that were modified on $fqdn:\n\n", email_address => "security-team <at> yoursite.com", subject => "Notification of a Security Modification" tag => "security"; }

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3313 has been updated by Matt Moran.

This also happens on CentOS 5, also with version 0.25.1 as well as 0.25.4

Bug #3313: puppet.conf option client=true/false doesn't seem to work

• Author: christian c
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Affected version: 0.25.4
• Keywords:
• Branch:

Hi, I’m using puppet 0.25.4 on OpenSuse 11.1.

Trying to run puppet as listening client only with “listen=true” and “client=false” options in puppet.conf doesn’t seem to work. After restarting puppet with the new configuration, first thing it does is polling the puppetmaster and afterwards every 30min.

But if I start puppetd with —no-client parameter it polls the puppetmaster only after being triggered by a puppetrun-command coming from the master.

Additionally, if the option works again, you should add it to the configuration reference because right now it isn’t mentioned.

My config: [puppetd]

classfile = $vardir/classes.txt server = puppet localconfig = $vardir/localconfigi httplog = $logdir/http.log listen = true noop = false client = false puppetdlog = $logdir/puppetd.log puppetport = 8139 pluginsync = true

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3229 has been updated by Graham Bleach.

I’ve just tripped up on this when using a selector. I’d like to vote for case sensitivity to be the default. Clearly changing to this is going to break things for all the people who are accidentally depending on case insensitivity, hopefully that’s not many.

In the intervening time I’m adding both mixed and lowercase versions so that things don’t break if this bug is fixed:

$string = "Hello World" $test = $string ? { /Hello/ => "yes", /hello/ => "yes", default => "no", } notify{"$test":}

Bug #3229: Case regex are not case-insensitive

• Author: Brice Figureau
• Status: Needs design decision
• Priority: Normal
• Assigned to: Brice Figureau
• Category: language
• Target version:
• Affected version: 0.25.4
• Keywords: regex case language selector
• Branch:

By default puppet case or selector statements are case insensitive. This is done by downcasing both the side of the comparison.

Unfortunately, case regexes are still case sensitive, so the following manifest fails:

$var = "CaseSensitive" case $var { /CaseSensitive/: { notice("worked") } default: { fail "miserably" } }

The proposed change is to make sure case or selector regex are insensitive by default.

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #2837 has been updated by Alan Barrett.

I get the following error with puppet 0.25.4:

warning: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml)

I have not deliberately configured any preferred_serialization_format, so I assume that some part of puppet chose to use “pson” by default. Does anybody know where that would have happened, and should I raise a separate issue about an unsupported value being chosen as a defualt?

Bug #2837: Reports should support PSON serialization

• Author: Peter Meier
• Status: Accepted
• Priority: Normal
• Assigned to: Markus Roberts
• Category: serialization
• Target version: 0.25.5
• Affected version: 0.25.1
• Keywords: pson
• Branch: http://github.com/duritong/puppet/tree/ticket/0.25.x/2837

Using latest 0.25.x I know get

warning: Value of 'preferred_serialization_format' ('pson') is invalid, using default ('yaml')

it looks like this happens because for the pson supported? is missing?

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #1597 has been updated by Ben Lavender.

• Affected version changed from 0.24.4 to 0.25.4

I am having trouble related to this with 0.25.4. In particular, booting up our EC2 nodes, we can shave 10 minutes off a boot time by adding —no-rdoc and —no-ri with a hacked copy of the gem provider distributed as a custom one.

It looks like you were working towards some more features here than just —no-rdoc and —no-ri, but I think that these two should perhaps be the default anyway. Would you merge any of the following if I wrote them up with specs?

1. A fix to the gem provider that adds —no-rdoc and —no-ri to all installations
2. A fix to the gem provider that does all of the above-described fun with —source
3. Some other design that’s been decided on somewhere

Bug #1597: managing gems with Package does not allow arguments

• Author: Ed Greenberg
• Status: Accepted
• Priority: Normal
• Assigned to:
• Category: package
• Target version: unplanned
• Affected version: 0.25.4
• Keywords:
• Branch:

When managing a gem with Package, one cannot set arguments. For instance one cannot do:

gem install mysql — —with-mysql-config=/usr/bin/mysql_config

One cannot add —no-rdoc and —no-ri, nor can one add —source in order to get a gem from github.

I realize I can install gems using Exec, but that is just installing them, not managing them.

If there is agreement, perhaps this could find itself into a future release.

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #3218 has been updated by Mark Z..

Nigel Kersten wrote:

It looks like submitting a report from a 0.24.x client through the 0.25.x server with puppet_dashboard reporting that contains errors will trigger this.

I get the error too. Client and server both run on 0.25.4 .

Bug #3218: NoMethodError in Reports#show

• Author: Nigel Kersten
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Keywords:
• Branch:

I’m not sure what’s triggering this, I just had a few clients report in after a fresh install and this started to happen.

NoMethodError in Reports#show Showing app/views/statuses/_overview.html.haml where line #9 raised: You have a nil object when you didn't expect it! You might have expected an instance of ActiveRecord::Base. The error occurred while evaluating nil.[] Extracted source (around line #9): 6: %li 7: %span.sparkline= Status.runtime.join(', ') 8: %strong== #{"%0.2f" % Status.runtime.last}s 9: Run Time 10: %div{:style => 'text-align: right;'} 11: = link_to "Status Report »", status_path, :class => 'button' Trace of template inclusion: app/views/shared/_global_nav.html.haml, app/views/layouts/application.html.haml RAILS_ROOT: /usr/local/puppet-dashboard Application Trace | Framework Trace | Full Trace /usr/local/puppet-dashboard/app/models/status.rb:47:in `runtime' /usr/local/puppet-dashboard/app/models/status.rb:47:in `map' /usr/local/puppet-dashboard/app/models/status.rb:47:in `runtime' /usr/local/puppet-dashboard/app/views/statuses/_overview.html.haml:9:in `_run_haml_app47views47statuses47_overview46html46haml_locals_object_overview' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `send' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:306:in `with_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:30:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:20:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:19:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/template.rb:205:in `render_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:44:in `render_partial' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/partials.rb:184:in `render_partial' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:276:in `render_without_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:11:in `render' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers.rb:96:in `non_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:11:in `render' /usr/local/puppet-dashboard/app/views/shared/_global_nav.html.haml:13:in `_run_haml_app47views47shared47_global_nav46html46haml_locals_global_nav_object' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `send' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:306:in `with_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:30:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:20:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:19:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/template.rb:205:in `render_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable_partial.rb:44:in `render_partial' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/partials.rb:184:in `render_partial' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:267:in `render_without_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:11:in `render' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers.rb:96:in `non_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:11:in `render' /usr/local/puppet-dashboard/app/views/layouts/application.html.haml:20:in `_run_haml_app47views47layouts47application46html46haml' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `send' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:306:in `with_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/renderable.rb:30:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/template.rb:205:in `render_template' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:265:in `render_without_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:13:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:352:in `_render_with_layout' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_view/base.rb:262:in `render_without_haml' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/haml/helpers/action_view_mods.rb:13:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:1250:in `render_for_file' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:945:in `render_without_benchmark' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:1326:in `default_render' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/respond_to.rb:107:in `retrieve_response_from_mimes' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:164:in `call' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:164:in `default_render' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:113:in `to_html' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:129:in `send' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:129:in `call' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/responder.rb:106:in `call' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/legacy/respond_to.rb:65:in `respond_with' /usr/local/puppet-dashboard/vendor/plugins/inherited_resources/lib/inherited_resources/actions.rb:13:in `show' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/local/puppet-dashboard/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `sass_old_process' /usr/local/puppet-dashboard/vendor/gems/haml-2.2.2/lib/sass/plugin/rails.rb:19:in `process' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in `_call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/query_cache.rb:28:in `call' /usr/local/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/string_coercion.rb:25:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/head.rb:9:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/methodoverride.rb:24:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/failsafe.rb:26:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/lock.rb:11:in `synchronize' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/lock.rb:11:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:114:in `call' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/reloader.rb:34:in `run' /usr/local/puppet-dashboard/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:108:in `call' /usr/local/puppet-dashboard/vendor/rails/railties/lib/rails/rack/static.rb:31:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/urlmap.rb:46:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/urlmap.rb:40:in `each' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/urlmap.rb:40:in `call' /usr/local/puppet-dashboard/vendor/rails/railties/lib/rails/rack/log_tailer.rb:17:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/content_length.rb:13:in `call' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/handler/webrick.rb:50:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' /usr/local/puppet-dashboard/vendor/gems/rack-1.0.1/lib/rack/handler/webrick.rb:14:in `run' /usr/local/puppet-dashboard/vendor/rails/railties/lib/commands/server.rb:111 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' script/server:3 Request Parameters: {"id"=>"7"} Show session dump --- Response Headers: {"Content-Type"=>"text/html", "Cache-Control"=>"no-cache"}

If I work out what triggered it I’ll update the bug.

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #1935 has been updated by Mike Lococo.

It’s not clear to me how to specify a “related issue”, but this should be resolved as a side-effect of 2198 when that lands as long as the rpm and yum providers are handled appropriately. Circular deps are handled naturally when performed as batch operations in both rpm and yum, but until 2198 lands there’s no way to request a batch-operation except by manually coding an exec.

Bug #1935: Unable to handle 2 packages with a circular dependency

• Author: Hari Sekhon
• Status: Accepted
• Priority: Low
• Assigned to:
• Category:
• Target version:
• Affected version: 0.24.7
• Keywords:
• Branch:

When trying to remove 2 packages with circular dependencies on one another, neither is ever removed. This occurs on CentOS 5.2 using the std rpm -e operation that puppet defaults to.

The problem is that puppet attempts to remove one package at a time, so it fails on one because of the other, and then when it tries to remove the other it fails on the first.

There are 2 possible solutions that I can tell:

1. Make a list of all packages to be removed and remove them all in one go in a single rpm command (although a single package name typo may prevent all other packages from being removed in this case which is not that good)

2. Define a way of specifying that 2 or more packages must be removed simultaneously in one command. If you were to do an rpm -e PackageA PackageB then rpm is smart enough to actually resolve both deps and remove both, but if you only specify one, it will not let you.

Examples of packages with this circular dep behaviour on CentOS 5.2 include: ypbind <=> yp-tools ifd-egate <=> pcsc-lite oddjob <=> oddjob-libs … etc

I think a force or a recursive removal through yum should be avoided lest people destroy their systems with cascading package deletions.

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://reductivelabs.com/redmine/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 puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.