Jira (MCO-187) mco puppet ignores --no-noop or --noop options

[Pieter Loubser (JIRA)]

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) -- 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.