Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title
Henrik Lindberg commented on PUP-4094
Re: Default environment_timeout should be 0, not infinity.
How about:
"The default value '0' is not optimal for large scale production, but helps keep things from being confusing when you are getting started and making frequent changes to your manifests. When the number of nodes go up and changes are not so frequent you may want to change this parameter to 'unlimited' to make repeated catalog compilations of unchanged code run faster. The trade-off is that you must then manually tell the server to reload the code when changes are made. Values in-between these two ('0' and 'unlimited') means that you make a compromise regarding convenience vs. performance. When setting it to some other value you have to wait for the timeout before changes take effect, but all compilations during that time period will be faster, followed by one slower compilation and then again faster until the next timeout."
If we also want to say something about the gain in performance:
"The performance gained by caching depends on the amount of puppet code that is used to compile a catalog. The more code the bigger the reduction in wall clock time spent per compilation. To decide on how much is gained in your configuration, set the timeout to a value longer than it takes to request 2-3 catalogs in sequence. Then compare the compilation times. Under optimal conditions you may observe up to a 60% reduction in compilation time."
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title Simon Aquino commented on PUP-4203 Re: Add ':uninstall_options' to gem provider The work to resolve this issue is contained in this PR: https://github.com/puppetlabs/puppet/pull/3708 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title
Simon Aquino updated an issue
Puppet / PUP-4203
Add ':uninstall_options' to gem provider
Change By:
Simon Aquino
I'd be nice to pass custom flags to the gem provider to uninstall ruby gems.The `uninstall_options` attribute within the package resource can be set and consumed by the uninstall method within the gem provider in order to achieve this goal.Example: {code:puppet} package { 'mechanize': \\ ensure => absent, \\ provider => 'gem', \\ uninstall_options => '--ignore-dependencies', \\ } {code} This resource results in the following command to be issued:/usr/bin/gem uninstall --executables --all --ignore-dependencies mechanizePlease note that the ['--executables', '--all'] flags are added to the `gem uninstall` command by default.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title
Simon Aquino updated an issue
Puppet / PUP-4203
Add ':uninstall_options' to gem provider
Change By:
Simon Aquino
I'd be nice to pass custom flags to the gem provider to uninstall ruby gems.The `uninstall_options` attribute within the package resource can be set and consumed by the uninstall method within the gem provider in order to achieve this goal.Example:package { 'mechanize': \\ ensure => absent, \\ provider => 'gem', \\ uninstall_options => '--ignore-dependencies', \\ }This resource results in the following command to be issued:/usr/bin/gem uninstall --executables --all --ignore-dependencies mechanizePlease note that the ['--executables', '--all'] flags are added to the `gem uninstall` command by default.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title
Simon Aquino updated an issue
Puppet / PUP-4203
Add ':uninstall_options' to gem provider
Change By:
Simon Aquino
I'd be nice to pass custom flags to the gem provider to uninstall ruby gems.The `uninstall_options` attribute within the package resource can be set and consumed by the uninstall method within the gem provider in order to achieve this goal.Example:package { 'mechanize': ensure => absent, provider => 'gem', uninstall_options => '--ignore-dependencies',}This resource results in the following command to be issued:/usr/bin/gem uninstall --executables --all --ignore-dependencies mechanizePlease note that the ['--executables', '--all'] flags are added to the `gem uninstall` command by default.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (PUP-4200) puppet-lint reports incorrect line numbers
Title: Message Title Henrik Lindberg commented on PUP-4200 Re: puppet-lint reports incorrect line numbers puppet-lint issues are not tracked in Puppet Labs jira. Please log this in the issue tracker used by the puppet-lint community project. IIRC, you can find it here: http://puppet-lint.com/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4204) Handle view options
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4204 Handle view options Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/13 3:09 PM Fix Versions: PUP 3.8.0 Priority: Normal Reporter: Henrik Lindberg By default, the preview application outputs a summary to stdout. The user can select one of the other produced artifacts as output instead of the summary. The options is --view, and its value is one of: summary (the default) baseline_catalog preview_catalog diff baseline_log preview_log The option simply copies one of the artifacts to stdout.
Jira (PUP-4203) Add {{:uninstall_options}} to gem provider
Title: Message Title
Melissa Stone created an issue
Puppet / PUP-4203
Add {{:uninstall_options}} to gem provider
Issue Type:
Task
Assignee:
Unassigned
Created:
2015/03/13 3:06 PM
Priority:
Normal
Reporter:
Melissa Stone
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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
Jira (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title
Melissa Stone updated an issue
Puppet / PUP-4203
Add ':uninstall_options' to gem provider
Change By:
Melissa Stone
Summary:
Add {{ ' :uninstall_options }} ' to gem provider
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 (PUP-4202) Handle exit code options
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4202 Handle exit code options Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/13 3:05 PM Fix Versions: PUP 3.8.0 Priority: Normal Reporter: Henrik Lindberg The puppet preview should: Exit with 0 if it was possible to compile both catalogs, else -1 if baseline failed, -2 if preview failed. This means no diff was produced, there may be 0-2 log output files produced depending on where the failure was. If the option --assert=equal fail with -5 if catalogs are not equal if the option --assert=compilant ail with -6 if catalogs are neither equal nor compliant. (equality and compliance are values produced by the catalog diff)
Jira (PUP-4201) Add support for structured logging
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-4201 Add support for structured logging Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4201) Add support for structured logging
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4201 Add support for structured logging Issue Type: Improvement Assignee: Unassigned Created: 2015/03/13 2:55 PM Priority: Normal Reporter: Henrik Lindberg It is difficult to use the logging system to output structured logs where values for file, line, position, issue-code etc. is output as separate and identifiable items (e.g. logging using JSON). This is needed for post-processing (searching, transforming) log output. The work includes adding required fields to the Log object, and to make sure the features that are already present in Puppet's logging framework gets used. Basiclly the responsibility to format the message with location (and other structural information) should be made by a logging destination (since it knows what the underlying technology expects; a formatted text string, or structured output. We want the pops issue based feature to integrate well with logging. It should probably bypass the simple text-based logging functions in favor of the underlying API where structured information can be passed to the Log object. As part of this, a :jsonfile destination should be implemented. Add Comment
Jira (FACT-654) facter ldom.rb generate virtinfo usage error on Solaris 11.2 x86 boxes
Title: Message Title Kylo Ginsberg commented on FACT-654 Re: facter ldom.rb generate virtinfo usage error on Solaris 11.2 x86 boxes Celia Cottle a crude but effective workaround we used once before (assuming they don't use the ldom fact) is to remove lib/facter/ldom.rb. Does that work? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Kylo Ginsberg commented on PUP-4196 Re: agent command line options ignored running under systemd Melissa Stone ideas? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Kylo Ginsberg assigned an issue to Melissa Stone Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Kylo Ginsberg Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4091) puppet apply does not recognize arguments when called not-interactively
Title: Message Title Kylo Ginsberg assigned an issue to Michael Wodniok Puppet / PUP-4091 puppet apply does not recognize arguments when called not-interactively Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Michael Wodniok Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4091) puppet apply does not recognize arguments when called not-interactively
Title: Message Title
Kylo Ginsberg commented on PUP-4091
Re: puppet apply does not recognize arguments when called not-interactively
I can't reproduce the problem description in the summary:
[75] puppet git:(master) be puppet apply --detailed-exitcode -e 'notice("hi")'
Notice: Scope(Class[main]): hi
Notice: Compiled catalog for kylo.corp.puppetlabs.net in environment production in 0.36 seconds
Notice: Applied catalog in 0.01 seconds
[76] puppet git:(master) cat foo.sh
#!/bin/bash
bundle exec puppet apply --detailed-exitcodes -e 'notice("hi")'
[77] puppet git:(master) ./foo.sh
Notice: Scope(Class[main]): hi
Jira (PUP-4151) Add a preview_output_dir setting
Title: Message Title Henrik Lindberg assigned an issue to Hailee Kenney Puppet / PUP-4151 Add a preview_output_dir setting Change By: Henrik Lindberg Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4119) Create a preview puppet subcommand
Title: Message Title Henrik Lindberg assigned an issue to Hailee Kenney Puppet / PUP-4119 Create a preview puppet subcommand Change By: Henrik Lindberg Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4125) Add migration check for upper case bare word evaluation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4125 Add migration check for upper case bare word evaluation Change By: Henrik Lindberg Fix Version/s: PUP 3.8 Fix Version/s: PUP 3.8.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4149) Create private repo for new preview module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4149 Create private repo for new preview module Change By: Henrik Lindberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4200) puppet-lint reports incorrect line numbers
Title: Message Title Todd Lewis created an issue Puppet / PUP-4200 puppet-lint reports incorrect line numbers Issue Type: Bug Assignee: Unassigned Created: 2015/03/13 2:28 PM Environment: RedHat EL6 on x86_64 Priority: Normal Reporter: Todd Lewis puppet-lint reports incorrect line numbers for issues it finds if there are multi-line string constants preceding the issue. For example, if the .pp file being examined has a 6 line string starting on line 100 and a 46 line string starting on line 150, then a problem with line 250 is reported as being on line 200. Also, the --with-context option will show the text of line 200 rather than the text of line 250 where the actual error is. In short, multi-line strings throws puppet-lint's error reporting off.That is, line counting gets thrown off by N-1 for each N-line string. Our "puppet-lint --version" returns "puppet-lint 1.1.0" if that helps. Add Comment
Jira (PUP-4149) Create private repo for new preview module
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-4149 Create private repo for new preview module Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1291) PR (1302): (maint) fix -F/-C/-R options for benchmark tool - wkalt
Title: Message Title gepetto-bot commented on PDB-1291 Re: PR (1302): (maint) fix -F/-C/-R options for benchmark tool - wkalt Pull request (maint) fix -F/-C/-R options for benchmark tool has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-282) hiera binary with `-i nodename.domain.com` fails under puppet 3
Title: Message Title Luke Schierer commented on HI-282 Re: hiera binary with `-i nodename.domain.com` fails under puppet 3 I am hitting this issue with hiera 1.3.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4197) Puppet creates production directory in first directory listed in environment_path
Title: Message Title Arnd Hannemann commented on PUP-4197 Re: Puppet creates production directory in first directory listed in environment_path Hi Henrik Lindberg, that sounds ok. At least for our use case, it's unlikely that the production environment will temporarily not exist. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1296) PR (1303): (maint) Remove facter requirement from rpm specfile - haus
Title: Message Title gepetto-bot commented on PDB-1296 Re: PR (1303): (maint) Remove facter requirement from rpm specfile - haus pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/861/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4199) config.ru is missing codedir argument
Title: Message Title Michael Stahnke created an issue Puppet / PUP-4199 config.ru is missing codedir argument Issue Type: Bug Assignee: Unassigned Created: 2015/03/13 12:39 PM Priority: Normal Reporter: Michael Stahnke config.ru in master doesn't work because it is missing a codedir. Patch incoming. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1297) Ensure acceptance tests work with Puppet 4
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-1297 Ensure acceptance tests work with Puppet 4 Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4198) Add install_options feature to pip provider
Title: Message Title Nathan Butler commented on PUP-4198 Re: Add install_options feature to pip provider Submitted PR: https://github.com/puppetlabs/puppet/pull/3711 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1297) Ensure acceptance tests work with Puppet 4
Title: Message Title
Rob Browning created an issue
PuppetDB / PDB-1297
Ensure acceptance tests work with Puppet 4
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/03/13 11:04 AM
Priority:
Normal
Reporter:
Rob Browning
Some of the comments here may be relevant: https://github.com/puppetlabs/puppetdb/pull/1300
In particular perhaps, these from joshcooper:
@rbrw I have a few path related questions:
https://github.com/puppetlabs/puppetdb/blob/stable/acceptance/helper.rb#L212: if your acceptance tests only need to execute puppet, facter, etc it should be using /opt/puppetlabs/bin (for AIO). If it needs to execute ruby or openssl it should be using /opt/puppetlabs/puppet/bin.
https://github.com/puppetlabs/puppetdb/blob/stable/acceptance/helper.rb#L393: this is PE specific, so should not need to change
https://github.com/puppetlabs/puppetdb/blob/stable/acceptance/helper.rb#L766-L770: FYI, the puppetpath setting is essentially deprecated in beaker, and non-existent when running aio type acceptance tests, see https://github.com/puppetlabs/beaker/blob/master/lib/beaker/host/unix.rb#L65-L72. It is preferrable to execute host.puppet('confdir'). That way the host will tell you where it's confdir is, and your test will work against puppet 3.x and 4.0 versions. Similarly comment in https://github.com/puppetlabs/puppetdb/blob/stable/acceptance/helper.rb#L969-L971
https://github.com/puppetlabs/puppetdb/blob/stable/acceptance/helper.rb#L978: the master's pidfile has changed in puppet 4/puppetserver 2.0. If you are using webrick, it will be /var/run/puppetlabs/master.pid. If you are using puppetserver, it will be /var/run/puppetlabs/puppetserver/puppetserver.pid. See h
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Melissa Stone commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Apologies it's taken me so long to respond to this ticket. Henrik Lindberg are you referring to `conf/environment.conf`? I don't think releng owns that file explicitly. It does get copied into place during packaging (at least for puppet 4 it does), but any changes to the file itself shouldn't impact that. The interesting thing is that I'm not seeing where this is copied into place except in Puppet 4 build automation in the puppet-agent repo Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1296) PR (1303): (maint) Remove facter requirement from rpm specfile - haus
Title: Message Title gepetto-bot commented on PDB-1296 Re: PR (1303): (maint) Remove facter requirement from rpm specfile - haus stahnma commented: :+1: Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4198) Add install_options feature to pip provider
Title: Message Title Nathan Butler created an issue Puppet / PUP-4198 Add install_options feature to pip provider Issue Type: New Feature Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/03/13 10:56 AM Fix Versions: PUP 3.7.4 Priority: Normal Reporter: Nathan Butler Currently there is no way to submit additional options to the pip install. Using the install_options feature, we can allow additional options to be passed to pip. I have found this useful since at work we maintain a custom pypi repository that we want to hit, so passing --find-links is a requirement. Add Comment
Jira (PDB-1296) PR (1303): (maint) Remove facter requirement from rpm specfile - haus
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1296 PR (1303): (maint) Remove facter requirement from rpm specfile - haus Issue Type: Task Assignee: Unassigned Created: 2015/03/13 10:53 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Remove facter requirement from rpm specfile Author: Matthaus Owens Company: Puppet Labs Github ID: haus Pull Request 1303 Discussion Pull Request 1303 File Diff Pull Request Description Nothing in puppetdb's runtime requires facter itself. Facter is a transitive dependency of puppet, but does not need to be called out by itself in the specfile. Puppet is required for the ssl setup.
Jira (PUP-2173) puppet config set certname accepts upper-case names
Title: Message Title
Sharon Fonge updated an issue
Puppet / PUP-2173
puppet config set certname accepts upper-case names
Change By:
Sharon Fonge
On CentOS 6 with Puppet 3.5.0, the certname subcommand accepts upper case letters for the certname. If you then try to change the name to lower-case, puppet complains and refuses to do so: {code}# [sharon.fonge@puppetmaster ~]$ sudo puppet config set certname Jenny cert list[sharon . I fonge@puppetmaster ~]$ puppet cert sign puppetclient . Got nal . Your usda . Number# puppet config print certname centos6-master.localdomain gov Error: Could not initialize global default settings: Certificate names must be lower case; see #1168# cat /etc/puppet/puppet find certificate request for puppetclient . conf local.org [ main]# The Puppet log directory sharon . # The default value is ' fonge@puppetmaster ~] $ vardir sudo rm -rf / log'.logdir = etc / var/log/ puppet # Where Puppet PID files are kept.# The default value is '$vardir / run'.rundir = ssl /var/ run lib /puppet # Where SSL certificates are kept.# The default value is '$confdir /ssl ' [sharon . ssldir = fonge@puppetmaster ~] $ vardir/sslserver = centos6 sudo rm - master.localdomaincertname = Jenny.I.Got.Your.Number[agent]# The file in which puppetd stores a list of the classes# associated with the retrieved configuratiion. Can be loaded in# the separate `` rf /etc/ puppet `` executable using the ``--loadclasses``# option.# The default value is '$confdir / classes.txt'.classfile = $vardir ssl / classes.txt# Where puppetd caches the local configuration. An# extension indicating the cache format is added automatically.# The default value is '$confdir usr / localconfig'.localconfig = $vardir lib / localconfig# puppet config set centos6-master.localdomainError: Could not initialize global default settings: Certificate names must be lower case; see #1168{code} /ssl
Add Comment
Jira (PUP-2173) puppet config set certname accepts upper-case names
Title: Message Title Sharon Fonge updated an issue Puppet / PUP-2173 puppet config set certname accepts upper-case names Change By: Sharon Fonge On CentOS 6 with Puppet 3.5.0, the certname subcommand accepts upper case letters for the certname. If you then try to change the name to lower-case, puppet complains and refuses to do so:[sharon.fonge@puppetmaster ~]$ sudo puppet cert list[sharon.fonge@puppetmaster ~]$ puppet cert sign puppetclient. nal local . usda.gov org Error: Could not find certificate request for puppetclient.local.org[sharon.fonge@puppetmaster ~]$ sudo rm -rf /etc/puppet/ssl /var/lib/puppet/ssl [sharon.fonge@puppetmaster ~]$ sudo rm -rf /etc/puppet/ssl /usr/lib/puppet/ssl Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4194) Puppet's logdir permissions prevent puppetserver service start
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-4194 Puppet's logdir permissions prevent puppetserver service start Change By: Aaron Armstrong Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4194) Puppet's logdir permissions prevent puppetserver service start
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4194 Puppet's logdir permissions prevent puppetserver service start Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4197) Puppet creates production directory in first directory listed in environment_path
Title: Message Title Henrik Lindberg commented on PUP-4197 Re: Puppet creates production directory in first directory listed in environment_path This gets trickier... If fixing this so that the default "production" environment is not created if it exists somewhere on the path, then later, if that production environment does not exist (temporarily), it will be created in the first directory. Then, if it appears again, the automatically created "production" will mask the later (wanted) "production" environment now again appearing later in the path. Is that ok? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-855) Ensure acceptance tests pass
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-855 Ensure acceptance tests pass Change By: Kylo Ginsberg Some of this should just work but some notes on this:* making sure the executable produced is *facter* not *cfacter** removing the test of `facter --puppet`, since that is removed functionality* removing the current (json-based) schema acceptance test, which no longer applies* integrating the new schema test, which runs as part of the compiled test executable, so that needs to travel with the installed package, either as part of that package or as a parallel `-test` package We also need to sort out if this will be testing in an AIO pipeline or a classic pipeline. I'm thinking the former, and that facter 3 would never be delivered standalone. But this needs to be discussed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1283) PR (169): (bugfix) Use test_url in connection validator for puppetdb - ajroetker
Title: Message Title gepetto-bot commented on PDB-1283 Re: PR (169): (bugfix) Use test_url in connection validator for puppetdb - ajroetker kbarber commented: Testing for hipchat integration Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-855) Ensure acceptance tests pass
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-855 Ensure acceptance tests pass Change By: Kylo Ginsberg Summary: Then, ensure Ensure acceptance tests pass Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-855) Then, ensure acceptance tests pass
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-855 Then, ensure acceptance tests pass Change By: Kylo Ginsberg Summary: Then, e]nsure ensure acceptance tests pass Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-855) Then, e]nsure acceptance tests pass
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-855 Then, e]nsure acceptance tests pass Change By: Kylo Ginsberg Summary: Ensure Then, e]nsure acceptance tests pass Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-855) Ensure acceptance tests pass
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-855 Ensure acceptance tests pass Change By: Kylo Ginsberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-854) Move native facter code to facter#master
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-854 Move native facter code to facter#master Change By: Kylo Ginsberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-856) Update cfacter repo README.md
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-856 Update cfacter repo README.md Change By: Kylo Ginsberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1295) PR (170): Add subparam passing for advanced database SSL options. - jonkelleyatrackspace
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1295 PR (170): Add subparam passing for advanced database SSL options. - jonkelleyatrackspace Issue Type: Task Assignee: Unassigned Created: 2015/03/13 8:13 AM Labels: github module Priority: Normal Reporter: gepetto-bot Add subparam passing for advanced database SSL options. Author: Jon Kelley Company: Github ID: jonkelleyatrackspace Pull Request 170 Discussion Pull Request 170 File Diff Pull Request Description In my organization there's a need to pass additional parameters when dealing with SSL. This allows opting for custom SSL Factories, defining the SSL verify mode, and allows the power
Jira (PUP-4197) Puppet creates production directory in first directory listed in environment_path
Title: Message Title Arnd Hannemann created an issue Puppet / PUP-4197 Puppet creates production directory in first directory listed in environment_path Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Components: Puppet Server Created: 2015/03/13 7:56 AM Environment: Debian Jessie 8.0 Priority: Normal Reporter: Arnd Hannemann When supplied with multiple directories in environmentpath, puppet will in the first run create the empty directory "production" in the first directory listed, even if that environment already exists in another directory listed in environmentpath. Successive puppet runs will detect the empty production environment and do nothing. Example:
Jira (PDB-814) Add latest-report? query field on reports endpoint
Title: Message Title Erik Dalén updated an issue PuppetDB / PDB-814 Add latest-report? query field on reports endpoint Change By: Erik Dalén Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1294) Add indices to foreign key columns
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1294 Add indices to foreign key columns Change By: Kenneth Barber Sprint: PuppetDB 2015-04-08 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1136 communicate v4 API changes to stakeholders ahead of release Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1294) Add indices to foreign key columns
Title: Message Title Erik Dalén created an issue PuppetDB / PDB-1294 Add indices to foreign key columns Issue Type: Improvement Assignee: Unassigned Created: 2015/03/13 7:21 AM Priority: Normal Reporter: Erik Dalén There are a bunch of foreign key columns that are missing indices. This script can be used to find out which ones: http://mlawire.blogspot.se/2009/08/postgresql-indexes-on-foreign-keys.html Adding them should improve query performance. Also the columns fact_paths.depth and certnames.deactivated are frequently queried but are missing indices. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3827) Errors from indirected routes don't match error schema
Title: Message Title Christopher Price updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Christopher Price Sprint: On Deck - Tier 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Kenneth Barber commented on PDB-1136 Re: communicate v4 API changes to stakeholders ahead of release This needs document index changes now. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1293) Change filesystem paths to represent Puppet Enterprise paths & correct '--tslv1' typo
Title: Message Title Kenneth Barber commented on PDB-1293 Re: Change filesystem paths to represent Puppet Enterprise paths & correct '--tslv1' typo Fixed. FWIW, its faster and cheaper to raise a PR for such a minor change, rather than raising a ticket . Also, I can't just switch the example to be PE only, these docs are both FOSS + PE. One day we'll sort out this pathing nightmare, and we won't have to suffer so much. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1293) Change filesystem paths to represent Puppet Enterprise paths & correct '--tslv1' typo
Title: Message Title Kenneth Barber moved an issue PuppetDB / PDB-1293 Change filesystem paths to represent Puppet Enterprise paths & correct '--tslv1' typo Change By: Kenneth Barber Scrum Team: PuppetDB Component/s: PuppetDB Component/s: DOCS Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 1721 1293 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Kenneth Barber commented on PDB-1292 Re: puppetdb api docs should include concrete examples I'm glad you also like the forgeapi docs, I was a part of that way back when. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-1292 puppetdb api docs should include concrete examples Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1292 puppetdb api docs should include concrete examples Commands aren't necessarily restful, so not 100% a swagger implementation is a good idea here. But I'm keen on automation at some point in the future, the REST query side would be tackled first I presume before commands. For now though, we could improve some of this manually. Change By: Kenneth Barber Sprint: PuppetDB 2015-04-08 Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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:
Jira (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Kenneth Barber moved an issue PuppetDB / PDB-1292 puppetdb api docs should include concrete examples Change By: Kenneth Barber Scrum Team: PuppetDB Component/s: PuppetDB Component/s: DOCS Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 1658 1292 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Steve Traylen commented on PUP-4196 Re: agent command line options ignored running under systemd Steps to reproduce: Start with a working CentOS 7 agent. Set PUPPET_EXTRA_OPTS="--masterport=22 -d" Start service systemctl start puppet.service Check process table it will have masterport preset. In reality puppet will continue to work perfectly but it should be trying to connect to the master on port 22 and failing. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Steve Traylen updated an issue Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Steve Traylen Summary: agent command line options ignored running under systemd Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-4196) agent command line options ignored running systemd
Title: Message Title Steve Traylen created an issue Puppet / PUP-4196 agent command line options ignored running systemd Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Kylo Ginsberg Components: Client Created: 2015/03/13 4:37 AM Environment: CentOS 7 puppet 3.7.4 ruby 2.0.0p353 Labels: systemd Priority: Normal Reporter: Steve Traylen
Jira (PUP-4091) puppet apply does not recognize arguments when called not-interactively
Title: Message Title Michael Wodniok updated an issue Puppet / PUP-4091 puppet apply does not recognize arguments when called not-interactively Change By: Michael Wodniok When puppet apply is called via script no started by a user, the output is for example following:Error: Could not parse application options: invalid option: --detailed-exitcodesThis is not the case when the same script is executed from a lerminal on same host.The puppet call for upper output is "puppet apply --detailed-exitcodes". EDIT: The first execution works perfectly. But second execution gives me an interresting output:Fact file /etc/facter/facts.d/wn_location.rb was parsed but returned an empty data setwn_location.rb is a fact that is deployed via puppet. When deleting the corresponding file, puppet runs normally. That makes it understandible why puppet runs once fine. So the bug is caused somewhere in the fact-parsing part of puppet or maybe facter. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PUP-1719) package needs to allow holding and ensuring a particular version at the same time
Title: Message Title Matt Comben commented on PUP-1719 Re: package needs to allow holding and ensuring a particular version at the same time This seems to be related, if not a duplicate of, PUP-1541 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
