Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Pieter Loubser Release Notes Summary: Running "puppet apply" or "puppet resource" to modify state would update the transaction.yaml file used to determine corrective vs intentional change. The transaction.yaml file will now only be updated during an agent run. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Pieter Loubser Sprint: SI Backlog - DAVIS, SCR 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Pieter Loubser Sprint: SI Backlog - DAVIS, SCR 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Pieter Loubser moved an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Pieter Loubser Affects Version/s: PE 2017.3.0 Component/s: Reporting Key: PE PUP - 22634 8227 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: SI Backlog - DAVIS, SCR 2017-11-01, SCR 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: SCR 2017-11-01 , SCR 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: SI Backlog - DAVIS, SCR 2017-11-01 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Assignee: Scott Walker Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Team: Security, Compliance, & Reporting Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7819) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Nick Lewis created an issue Puppet / PUP-7819 Filtering resources by tag interferes with corrective vs. intentional change determination Issue Type: Bug Assignee: Unassigned Created: 2017/08/07 3:24 AM Priority: Normal Reporter: Nick Lewis Reproduction steps: • Add a new resource to site.pp • Run puppet agent -t on the node • Observe that the change is properly marked as intentional • Modify the resource on disk • Run puppet agent -t on the node • Observe that the change is properly marked as corrective • Modify the resource on disk • Run puppet agent -t --tags faketag on the node (this can be done before or after the previous step) • Observe that no change is made • Run puppet agent -t on the node • Observe that the change is wrongly marked as intentional The agent uses a transaction persistence file to store the previous desired state (or actual state? unclear) which it can compare to the current state on the next run. That file seems to only include resources that are actually managed on a given run, so any resource that is skipped due to tags is omitted. That causes the agent to think that every change is intentional the next time around. I expect this is also broken for resources which are skipped due to failed dependencies, though I haven't tested that. Add Comment
Jira (PUP-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Team: Security, Compliance, & Reporting Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Team: Security, Compliance, & Reporting Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: Ready For Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7324) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-7324 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: Release Backlog Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Pieter Loubser updated an issue PuppetDB / PDB-3092 Improve performance of resource_events queries with 'corrective_change = true Change By: Pieter Loubser Sprint: SCR 2016-10-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Pieter Loubser updated an issue PuppetDB / PDB-3092 Improve performance of resource_events queries with 'corrective_change = true Change By: Pieter Loubser Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Pieter Loubser moved an issue PuppetDB / PDB-3092 Improve performance of resource_events queries with 'corrective_change = true Change By: Pieter Loubser Key: PE PDB - 17908 3092 Project: Puppet Enterprise [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5444) Failing tests on OSX
Title: Message Title
Pieter Loubser created an issue
Puppet / PUP-5444
Failing tests on OSX
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/10/28 8:00 AM
Priority:
Normal
Reporter:
Pieter Loubser
symbolic_modes tests occasionally fail on OS X like:
Errored Tests Cases:
Test Case tests/resource/file/symbolic_modes.rb reported: #
env PATH="/opt/puppetlabs/puppet/bin:${PATH}" ruby -e 'require "etc"; puts (Etc.getgrgid(File.stat("/var/folders/zz/zyxvpxvq6csfxvn_n0/T/symbolic-modes.XX.oAsbXzPO/file").gid).name)'
Last 10 lines of output were:
Jira (PUP-5444) Failing tests on OSX
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-5444 Failing tests on OSX Change By: Pieter Loubser Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (MCO-187) mco puppet ignores --no-noop or --noop options
Title: Message Title Pieter Loubser commented on an issue Re: mco puppet ignores --no-noop or --noop options Hi Jose, thanks for the feedback. A quick workaround would be to add this to the top of the post_option_parser method in the application (application/puppet.rb) file. 81 def post_option_parser(configuration) 82 # Workaround for 2.4.x option parser not setting --no-xx correctly 83 if configuration.include?(:no_noop) 84 configuration[:no_noop] = true 85 end 86 We will attempt to release a permanent solution to this soon. Add Comment MCollective / MCO-187 mco puppet ignores --no-noop or --noop options When running mco runall 10 --no-noop the command launched in the nodes is: Started a background Puppet run using the 'puppet agent --onetime --daemonize --color=false' command meanwhile in version 2.2.4 is: Puppet command 'puppet agent --onetime --daemonize --color=false --no-noop' so it does not send the puppet options specified in the command... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser commented on an issue Re: Update stomp gem rpm Have you tried 1.3.2? We are aware that 1.3.0 and 1.3.1 do not work. Add Comment MCollective / MCO-170 Update stomp gem rpm The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above. https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-178) Plugin Packager documentation
Title: Message Title Pieter Loubser created an issue MCollective / MCO-178 Plugin Packager documentation Issue Type: Improvement Assignee: Pieter Loubser Components: DOCS Created: 10/Feb/14 3:49 AM Priority: Normal Reporter: Pieter Loubser http://docs.puppetlabs.com/mcollective/deploy/plugins.html The Packaging Custom Plugins section mentions that we hope to publish a guide to the packaging tool soon. We need to write this guide. Add Comment This message was sent by
Jira (MCO-179) Remove reference to package iteration in #package_information
Title: Message Title Pieter Loubser created an issue MCollective / MCO-179 Remove reference to package iteration in #package_information Issue Type: Bug Affects Versions: 2.4.0 Assignee: Pieter Loubser Created: 10/Feb/14 4:10 AM Fix Versions: 2.4.1 Priority: Normal Reporter: Pieter Loubser When deprecating and renaming the iteration flag one reference to it was left in OspackagePackager#package_information. Add Comment
Jira (MCO-179) Remove reference to package iteration in #package_information
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-179 Remove reference to package iteration in #package_information Change By: Pieter Loubser Sprint: 2014_02_12-2014_02_26 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-179) Remove reference to package iteration in #package_information
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-179 Remove reference to package iteration in #package_information Change By: Pieter Loubser Sprint: 2014_02_12 2014_01_29 - 2014_02_26 2014_02_12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser commented on an issue Re: Update stomp gem rpm Thanks for the feedback. Would it be possible to give us a bit more information regarding how it doesn't work with the 1.3.2 gem? Add Comment MCollective / MCO-170 Update stomp gem rpm The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above. https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-170 Update stomp gem rpm Change By: Pieter Loubser Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-170 Update stomp gem rpm Change By: Pieter Loubser Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-170 Update stomp gem rpm Change By: Pieter Loubser Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-173) Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-173 Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 Change By: Pieter Loubser Assignee: RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-173) Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0
Title: Message Title Pieter Loubser commented on an issue Re: Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 https://github.com/puppetlabs/marionette-collective/pull/159 Add Comment MCollective / MCO-173 Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 When enabling STOMP 1.1 features like heartbeat_interval with a stomp gem that only supports STOMP 1.0 mcollectived will fail to start (as expected) but with no useful feedback about why it happened. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-174) Update RabbitMQ federation documentation
Title: Message Title Pieter Loubser created an issue MCollective / MCO-174 Update RabbitMQ federation documentation Issue Type: Improvement Assignee: Pieter Loubser Created: 30/Jan/14 6:48 AM Fix Versions: 2.4.1 Priority: Normal Reporter: Pieter Loubser Update documentation to reflect that federation is supported in 2.4.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-174) Update RabbitMQ federation documentation
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-174 Update RabbitMQ federation documentation Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-174) Update RabbitMQ federation documentation
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-174 Update RabbitMQ federation documentation Change By: Pieter Loubser Sprint: 2014_01_29-2014_02_12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-174) Update RabbitMQ federation documentation
Title: Message Title Pieter Loubser commented on an issue Re: Update RabbitMQ federation documentation Updating docs depends successful functional review of implementation. Add Comment MCollective / MCO-174 Update RabbitMQ federation documentation Update documentation to reflect that federation is supported in 2.4.1 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-173) Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0
Title: Message Title Pieter Loubser created an issue MCollective / MCO-173 Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 Issue Type: Improvement Affects Versions: 2.4.0 Assignee: Pieter Loubser Created: 29/Jan/14 3:31 AM Fix Versions: 2.4.1 Priority: Normal Reporter: Pieter Loubser When enabling STOMP 1.1 features like heartbeat_interval with a stomp gem that only supports STOMP 1.0 mcollectived will fail to start (as expected) but with no useful feedback about why it happened. Add Comment
Jira (MCO-172) RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-172 RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124 Change By: Pieter Loubser Fix Version/s: 2.4.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-172) RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-172 RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124 Change By: Pieter Loubser Sprint: 2014_01_29-2014_02_05 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-173) Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-173 Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 Change By: Pieter Loubser Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-173) Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-173 Improve logging when using STOMP 1.1 features with a gem that only supports STOMP 1.0 Change By: Pieter Loubser Sprint: 2014_01_29-2014_02_05 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-172) RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-172 RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124 Change By: Pieter Loubser Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-172) RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-172 RabbitMQ Federation: Missed lines of patch from pr#107 to pr#124 Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-170) Update stomp gem rpm
Title: Message Title Pieter Loubser created an issue MCollective / MCO-170 Update stomp gem rpm Issue Type: Improvement Assignee: Matthaus Owens Components: RE Created: 24/Jan/14 6:03 AM Priority: Normal Reporter: Pieter Loubser The current rubygem rpm is version 1.2.2-1. Some MCollective features require version 1.2.10 and above. https://groups.google.com/d/msg/mcollective-users/uDGP87TSw2I/PC1H6TTjQUkJ Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-168 release MCollective 2.4.0 Change By: Pieter Loubser Fix Version/s: 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser commented on an issue Re: release MCollective 2.4.0 https://github.com/puppetlabs/marionette-collective/pull/155 Add Comment MCollective / MCO-168 release MCollective 2.4.0 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser created an issue MCollective / MCO-168 release MCollective 2.4.0 Issue Type: Task Assignee: Pieter Loubser Created: 23/Jan/14 8:14 AM Due Date: 23/Jan/14 Priority: Normal Reporter: Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-168 release MCollective 2.4.0 Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-167) Mcollective forks to much processes
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-167 Mcollective forks to much processes Change By: Pieter Loubser Assignee: R.I.Pienaar RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-163) MCollective service cannot stop on Windows if it is in a connecting state
Title: Message Title Pieter Loubser created an issue MCollective / MCO-163 MCollective service cannot stop on Windows if it is in a connecting state Issue Type: Bug Assignee: Unassigned Created: 17/Jan/14 3:39 AM Priority: Normal Reporter: Pieter Loubser If the MCollective service starts and cannot connect to its message queue, it goes into a state where it cannot be exited cleanly on Windows. This can be fixed by refactoring the runner code to keep track of its threads and implementing a real way to control its state. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-163) MCollective service cannot stop on Windows if it is in a connecting state
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-163 MCollective service cannot stop on Windows if it is in a connecting state Change By: Pieter Loubser Affects Version/s: 2.4.0-rc2 Affects Version/s: 2.4.0-rc1 Affects Version/s: 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-143) Windows agents stop working when the mcollective service cannot be restarted
Title: Message Title Pieter Loubser commented on an issue Re: Windows agents stop working when the mcollective service cannot be restarted Rob Reynolds Partially. There is still a state where it can fail (see MCO-163). This will however require a major rewrite of the runner class and is out of scope for 2.4.0. Add Comment MCollective / MCO-143 Windows agents stop working when the mcollective service cannot be restarted The windows mcollective service fails to restart from puppet after multiple restarts in a row. The easiest way I found to reproduce the issue is the following: 1. Install PE3.1 with one windows agent 2. Run `puppet agent -t` on the windows agent and make sure the pe_mcollective module has been applied 3. Change `/etc/puppetlabs/mcollective/cr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Pieter Loubser commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package Thank you all for the feedback. As of right now we're going to not change the other plugin repos until I've had more time to discuss it with release engineering. I will report back with any decisions we make here but in the mean time please keep the discussion going. I want to mention that we have no plans (and never even considered) to remove the plugin packager. In fact we have actively been working on it for 2.4.0. I do however understand that our users want parity between how we package plugins and how we tell our community to do it but also that our release team would prefer to use the same method for packaging that they use for all our other products. It would be great if we could find a middle ground here. On a side note, it would be wonderful if mco plugin generate got expanded to at least generate a 'does it compile' test, as I have actually had but mco plugin generate doesn't generate tests? offered as an explanation for why at least a smoke test isn't a basic necessity. Tomas Doran That is a good idea and something we would like to ship. It would be great if you could open a ticket so we can discuss it in a different thread. Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package.
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser created an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Issue Type: Bug Affects Versions: 2.4.0-rc1 Assignee: Unassigned Created: 16/Jan/14 3:11 AM Priority: Normal Reporter: Pieter Loubser Previous attempt at fixing http://projects.puppetlabs.com/issues/20467 was unsuccessful because of blocking threads. We need forcefully kill the threads so that we can exit cleanly. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Change By: Pieter Loubser Fix Version/s: 2.4.0-rc2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Change By: Pieter Loubser Assignee: RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser commented on an issue Re: MCollective service doesn't exit on Windows https://github.com/puppetlabs/marionette-collective/pull/152 Add Comment MCollective / MCO-158 MCollective service doesn't exit on Windows Previous attempt at fixing http://projects.puppetlabs.com/issues/20467 was unsuccessful because of blocking threads. We need forcefully kill the threads so that we can exit cleanly. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Pieter Loubser commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package The change was merged in the package agent as https://github.com/puppetlabs/mcollective-package-agent/pull/6 Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Pieter Loubser created an issue MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package Issue Type: Task Assignee: Unassigned Created: 16/Jan/14 7:51 AM Priority: Normal Reporter: Pieter Loubser User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-2) mcollective daemon can crash at startup on Windows
Title: Message Title Pieter Loubser commented on an issue Re: mcollective daemon can crash at startup on Windows Kenn Hussey PE-1840 was most likely the cause which should be fixed in 3.2.0 rc0-829. Branan Purvine-Riley Can you confirm? Add Comment MCollective / MCO-2 mcollective daemon can crash at startup on Windows This does NOT affect all windows machines, but does seem to hit our test machines with decent regularity. http://projects.puppetlabs.com/issues/22369 indicated that this could be related to http://projects.puppetlabs.com/issues/20467, but I am not convinced yet. Tailing the mcollective logs on windows shows that the service does not even initialize ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-3) CLONE - A single malformed fact can break mcollective fact filtering in PE
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-3 CLONE - A single malformed fact can break mcollective fact filtering in PE Change By: Pieter Loubser Assignee: RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-3) CLONE - A single malformed fact can break mcollective fact filtering in PE
Title: Message Title Pieter Loubser commented on an issue Re: CLONE - A single malformed fact can break mcollective fact filtering in PE Kenn Hussey Being dealt with by the PE team in PE-1518 Add Comment MCollective / MCO-3 CLONE - A single malformed fact can break mcollective fact filtering in PE We have a cron job that dumps facter output as a yaml file to /etc/puppetlabs/mcollective/facts.yaml. If this file gets corrupted, or bad yaml is written, or debug output ends up in it, fact filtering no longer works. If a fact is bad or not returning the right parseable output, then not being able to filter by it could be expected. But a single bad / m... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-31) Manage daemonising puppet agent when run_in_background
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-31 Manage daemonising puppet agent when run_in_background Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-156) MCollective Shell sets LC_ALL to C by default
Title: Message Title Pieter Loubser created an issue MCollective / MCO-156 MCollective Shell sets LC_ALL to C by default Issue Type: Bug Assignee: Unassigned Created: 10/Jan/14 3:43 AM Priority: Normal Reporter: Pieter Loubser The Shell command runner class sets LC_ALL to C by default. We need to investigate if this is the correct behaviour or implement an easier way to override the default. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-152) release 2.4.0-rc1
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-152 release 2.4.0-rc1 Change By: Pieter Loubser Fix Version/s: 2.4.0 Fix Version/s: 2.4.0-rc1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-152) release 2.4.0-rc1
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-152 release 2.4.0-rc1 Change By: Pieter Loubser Fix Version/s: 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-147) PR (143): Close code block with missing end - croomes
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-147 PR (143): Close code block with missing end - croomes Change By: Pieter Loubser Fix Version/s: 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-147) PR (143): Close code block with missing end - croomes
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-147 PR (143): Close code block with missing end - croomes Change By: Pieter Loubser Assignee: PieterLoubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-148) Add test coverage for logaudit plugin
Title: Message Title Pieter Loubser created an issue MCollective / MCO-148 Add test coverage for logaudit plugin Issue Type: Bug Assignee: Pieter Loubser Created: 08/Jan/14 3:20 AM Fix Versions: 2.4.0 Priority: Normal Reporter: Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (MCO-148) Add test coverage for logaudit plugin
Title: Message Title Pieter Loubser commented on an issue Re: Add test coverage for logaudit plugin https://github.com/puppetlabs/marionette-collective/pull/144 Add Comment MCollective / MCO-148 Add test coverage for logaudit plugin This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-148) Add test coverage for logaudit plugin
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-148 Add test coverage for logaudit plugin Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-98) Add tests for shipped agents
Title: Message Title Pieter Loubser commented on an issue Re: Add tests for shipped agents https://github.com/puppetlabs/marionette-collective/pull/141 Add Comment MCollective / MCO-98 Add tests for shipped agents We ship two agents by default and they don't have any tests. We need to add some. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-98) Add tests for shipped agents
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-98 Add tests for shipped agents Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-146) MCO ping logs bogus warning
Title: Message Title Pieter Loubser created an issue MCollective / MCO-146 MCO ping logs bogus warning Issue Type: Bug Affects Versions: 2.3.3 Assignee: Unassigned Created: 07/Jan/14 7:06 AM Fix Versions: 2.4.0 Priority: Normal Reporter: Pieter Loubser In 2.3.3 we added logging on client timeout stating how many responses we received vs how many we expected to receive. This will however always log a warning if expected is 0, like in the case of the ping application. Add Comment
Jira (MCO-146) MCO ping logs bogus warning
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser MCollective / MCO-146 MCO ping logs bogus warning Change By: Pieter Loubser Assignee: PieterLoubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-146) mco ping logs bogus warning
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-146 mco ping logs bogus warning Change By: Pieter Loubser Summary: MCO mco pinglogsboguswarning Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-146) mco ping logs bogus warning
Title: Message Title Pieter Loubser commented on an issue Re: mco ping logs bogus warning https://github.com/puppetlabs/marionette-collective/pull/142 Add Comment MCollective / MCO-146 mco ping logs bogus warning In 2.3.3 we added logging on client timeout stating how many responses we received vs how many we expected to receive. This will however always log a warning if expected is 0, like in the case of the ping application. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-146) mco ping logs bogus warning
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-146 mco ping logs bogus warning Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-84) deprecate and remove flattened output
Title: Message Title Pieter Loubser commented on an issue Re: deprecate and remove flattened output To be removed in the next minor release. Add Comment MCollective / MCO-84 deprecate and remove flattened output the flattened output feature was available in earlier versions but not in the recent versions, am not sure why this feature is removed. I found some code for this feature still remaining in the recent versions and i have tweaked it to get the feature back. https://groups.google.com/forum/?fromgroups=#!topic/mcollective-users/N5Ed8j62ZkI The details a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-84) deprecate and remove flattened output
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-84 deprecate and remove flattened output Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-145) Remove flatten display option
Title: Message Title Pieter Loubser created an issue MCollective / MCO-145 Remove flatten display option Issue Type: Bug Affects Versions: 2.4.0 Assignee: Unassigned Created: 06/Jan/14 8:03 AM Priority: Normal Reporter: Pieter Loubser MCO-84 adds deprecation warnings when using the :flatten display option. :flatten should be removed in the next minor release. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-84) deprecate and remove flattened output
Title: Message Title Pieter Loubser commented on an issue Re: deprecate and remove flattened output https://github.com/puppetlabs/marionette-collective/pull/140 Add Comment MCollective / MCO-84 deprecate and remove flattened output the flattened output feature was available in earlier versions but not in the recent versions, am not sure why this feature is removed. I found some code for this feature still remaining in the recent versions and i have tweaked it to get the feature back. https://groups.google.com/forum/?fromgroups=#!topic/mcollective-users/N5Ed8j62ZkI The details a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title
Pieter Loubser commented on an issue
Re: mcollective-package-agent broken with Puppet 3.4
It looks like the change in behaviour was introduced in https://github.com/puppetlabs/puppet/commit/732d4509ac52010727ac0331a5470833dc438c85. In the past our package agent was expecting a hash with fields {symbol = string}
instead of {symbol = Puppet::Util::Execution::ProcessOutput}
.
This causes a problem when MCollective tries to deserialise the reply from the package agent. It has no notion of Puppet::Util::Execution::ProcessOutput which causes Marshal.load to fail.
Add Comment
MCollective / MCO-144
mcollective-package-agent broken with Puppet 3.4
As per the thread on the list, the mcollective-package-agent fails when used with Puppet 3.4. The data structure that the provider methods return has changed slightly and we should update the agent to deal with this.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (MCO-97) Config class does not parse fixnum config parameters correctly
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-97 Config class does not parse fixnum config parameters correctly Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-20) add unit tests for MCollective::Facts::Yaml_facts
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-20 add unit tests for MCollective::Facts::Yaml_facts Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 Change By: Pieter Loubser Assignee: PieterLoubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Pieter Loubser created an issue MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 Issue Type: Bug Assignee: Unassigned Created: 02/Jan/14 8:56 AM Priority: Normal Reporter: Pieter Loubser As per the thread on the list, the mcollective-package-agent fails when used with Puppet 3.4. The data structure that the provider methods return has changed slightly and we should update the agent to deal with this. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Pieter Loubser commented on an issue Re: mcollective-package-agent broken with Puppet 3.4 https://github.com/ploubser/mcollective-package-agent/tree/bug/master/mco-144 Add Comment MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 As per the thread on the list, the mcollective-package-agent fails when used with Puppet 3.4. The data structure that the provider methods return has changed slightly and we should update the agent to deal with this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 Change By: Pieter Loubser Labels: mcollective-plugins Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-142) MCollective logger plugin should display updated log format
Title: Message Title Pieter Loubser created an issue MCollective / MCO-142 MCollective logger plugin should display updated log format Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 2:47 AM Fix Versions: 2.4.0 Priority: Normal Reporter: Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving
Jira (MCO-142) MCollective logger plugin should display updated log format
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser MCollective / MCO-142 MCollective logger plugin should display updated log format Change By: Pieter Loubser Assignee: PieterLoubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
