Jira (PUP-2740) Puppet apply core dump on RedHat 6.5
Title: Message Title Aimon Bustardo updated an issue Puppet / PUP-2740 Puppet apply core dump on RedHat 6.5 Change By: Aimon Bustardo Component/s: Modules 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-2740) Puppet apply core dump on RedHat 6.5
Title: Message Title Aimon Bustardo commented on PUP-2740 Re: Puppet apply core dump on RedHat 6.5 Hi, I ran into same issue on CentOS 6.6 w/ puppet 3.7.4. Andreas Heumaier is correct. Issue in is puppet:agent. But to be more specific.. its in stdlib, the function fqdn_rand is causing it. see lines in puppet:agent: 141 $time1 = fqdn_rand($puppet_run_interval) 142 $time2 = fqdn_rand($puppet_run_interval) + 30 Change them to: 142 $time1 = $puppet_run_interval #fqdn_rand($puppet_run_interval) 143 $time2 = $puppet_run_interval + 30 #fqdn_rand($puppet_run_interval) + 30 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-866) pe-facter missing dependency on package providing lsb_release command
Title: Message Title
Geoff Williams updated an issue
Facter / FACT-866
pe-facter missing dependency on package providing lsb_release command
Change By:
Geoff Williams
h2. OverviewFactor fact {{lsbdistcodename}} does not work out of the box on minimal OS installs due to the {{pe-facter}} package not specifying a dependency on the package providing the {{lsb_release}} command.Affected platforms:* Debian (tested 8.0/Jessie -- after a forced install of PE agent)* Centos (tested 6.5 - trainingvm seteam )* _Probably more_h2. Expected result{noformat}/opt/puppet/bin/facter lsbdistcodename{noformat}Should always print the LSB release code nameh2. Actual resultCommand output is dependent on supplementary packages being installed. On a minimal OS installation a blank line is printed:{noformat}[root@master tmp]# /opt/puppet/bin/facter lsbdistcodename{noformat}h2. Packaging info*CentOS*{noformat}[root@master tmp]# rpm -q --requires pe-facter/opt/puppet/bin/ruby dmidecode pciutils pe-ruby pe-virt-what rpmlib(CompressedFileNames) <= 3.0.4-1rpmlib(FileDigests) <= 4.6.0-1rpmlib(PayloadFilesHavePrefix) <= 4.0-1rpmlib(VersionedDependencies) <= 3.0.3-1which rpmlib(PayloadIsXz) <= 5.2-1{noformat}*Debian*{noformat}geoff@jenkins:~$ dpkg -s pe-facterPackage: pe-facterStatus: install ok installedPriority: optionalSection: rubyInstalled-Size: 388Maintainer: Puppet Labs Architecture: amd64Version: 2.3.0.2-1puppet1Depends: pe-ruby, dmidecode, pe-virt-what, pciutilsDescription: Ruby module for collecting simple facts about a host operating system Some of the facts are preconfigured, such as the hostname and the operating system. Additional facts can be added through simple Ruby scripts.Homepage: http://www.puppetlabs.com{noformat}h2. Problems this causesModules that expect to have the {{$::lsbdistcodename}} fact available fail in production in mysterious ways and {{facter}} itself gives no information or warning on how to resolve things. I was only able to figure out what was broken by looking at the source code.I personally witnessed {{puppetlabs/java}} failing on Debian with a message that the operating system is not supported. This was resolved by installing the required package.h2. Condition diagnosisTo confirm you are affected by this issue, run the command:{noformat}/opt/puppet/bin/facter lsbdistcodename{noformat}If you do not see any output, you are missing the {{lsb_release}} programh2. Workaround*Debian*{noformat}apt-get install lsb_release{noformat}*CentOS/RHEL*{noformat}yum install redhat-lsb-core{noformat}After installing these packages, the fact will work although on CentOS 6.5 it just displays the word {{Final}} which is all that is available via the {{lsb_release}} command.
Jira (PDB-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/910/ 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-3796) Puppet 3.7.3 is not supported on Ruby 2.2
Title: Message Title Charlie Sharpsteen commented on PUP-3796 Re: Puppet 3.7.3 is not supported on Ruby 2.2 Kylo Ginsberg Looks like the PR was closed without a merge. Are we planning to back support for Ruby 2.2.0 to 3.7.x, or leave it as a Puppet 4 only thing? 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-3796) Puppet 3.7.3 is not supported on Ruby 2.2
Title: Message Title Charlie Sharpsteen assigned an issue to Kylo Ginsberg Puppet / PUP-3796 Puppet 3.7.3 is not supported on Ruby 2.2 Change By: Charlie Sharpsteen Assignee: Kylo Ginsberg 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-4256) Docs pushed
Title: Message Title Nicholas Fagerlund assigned an issue to Nicholas Fagerlund Puppet / PUP-4256 Docs pushed Change By: Nicholas Fagerlund Assignee: Nicholas Fagerlund 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-4256) Docs pushed
Title: Message Title Nicholas Fagerlund commented on PUP-4256 Re: Docs pushed Once we've had the go/no-go meeting, anyone involved in the release may merge https://github.com/puppetlabs/puppet-docs/pull/478. 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-4286) Atomic Puppet
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-4286 Atomic Puppet Issue Type: New Feature Affects Versions: PUP 3.7.4 Assignee: Kylo Ginsberg Components: Client Created: 2015/03/24 6:00 PM Environment: All Priority: Normal Reporter: Trevor Vaughan So, I'm going to make this a resurrection of ancient history and link to Redmine #3806. I still think this would be useful and would be something that no other tool that I can think of has. For some reason, this one wasn't migrated, so I'd like to pull it in.
Jira (PUP-4250) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4250 Prepare long form release notes and short form release story Change By: Nicholas Fagerlund Story Points: 3 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-4250) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4250 Re: Prepare long form release notes and short form release story For the announcement email, the story is basically: You can now turn on the future parser per-environment, by setting `parser = future` in environment.conf. We've updated the future parser to more closely match the early release candidates of Puppet 4.0. We've simplified the default behavior around environment caching, and simplified our advice for mature deployments. Fewer surprises for everyone. See the release notes for more details. Release notes link (once it goes live): https://docs.puppetlabs.com/puppet/3.7/reference/release_notes.html#puppet-375 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-355) Merge master into stable
Title: Message Title Kylo Ginsberg commented on HI-355 Re: Merge master into stable I updated https://jenkins.puppetlabs.com/view/Hiera/view/Stable/job/Hiera-Acceptance-stable/ to: use acceptance rather than acceptance_tests use node configs in config/nodes/.yaml rather than config/.cfg test against facter#2.x and puppet#master since that's what hiera has been testing against 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-359) Smoke test packages
Title: Message Title Melissa Stone commented on HI-359 Re: Smoke test packages packages are available at http://builds.puppetlabs.lan/hiera/2.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 (FACT-866) pe-facter missing dependency on package providing lsb_release command
Title: Message Title Geoff Williams commented on FACT-866 Re: pe-facter missing dependency on package providing lsb_release command Lindsey Smith this is helpful, for public release please 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-866) pe-facter missing dependency on package providing lsb_release command
Title: Message Title Geoff Williams created an issue Facter / FACT-866 pe-facter missing dependency on package providing lsb_release command Issue Type: Bug Affects Versions: FACT 2.3.0 Assignee: Eric Sorenson Created: 2015/03/24 4:44 PM Environment: Debian geoff@jenkins:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie
Jira (FACT-866) pe-facter missing dependency on package providing lsb_release command
Title: Message Title
Geoff Williams updated an issue
Facter / FACT-866
pe-facter missing dependency on package providing lsb_release command
Change By:
Geoff Williams
Environment:
*Debian*{noformat}geoff@jenkins:~$ lsb_release -aNo LSB modules are available.Distributor ID: DebianDescription: Debian GNU/Linux 8.0 (jessie)Release: 8.0Codename: jessiegeoff@jenkins:~$ puppet --version3.7.4 (Puppet Enterprise 3.7.2){noformat}*CentOS* {noformat} [root@master tmp]# lsb_release -aLSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarchDistributor ID: CentOSDescription: CentOS release 6.5 (Final)Release: 6.5Codename: Final[root@master tmp]# /opt/puppet/bin/puppet --version3.7.4 (Puppet Enterprise 3.8.0-rc0-281-gd05d353) {noformat}
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-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-3863
hiera('some::key', undef) returns empty string
Change By:
Nicholas Fagerlund
When using the {{hiera()}} function with a second parameter of {{undef}}, Hiera returns the empty string for the value. When using Puppet 3.7 future parser, this means that Hiera returns a truthy value when it cannot find a key.In the Puppet 3 language, this doesn't matter because {{'' == undef}} evaluates to {{true}}.A workaround for this is to specify a second parameter of {{false}} instead of {{undef}}, but that doesn't make this behavior any less confusing. *Final resolution:* In the Puppet 4 language, the hiera functions will now respect and return a default of {{undef}}, same as they do in the Puppet 3 language. ([in comment|https://tickets.puppetlabs.com/browse/PUP-3863?focusedCommentId=134708&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-134708])
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-348) Enable deep-merge options to be passed in lookup
Title: Message Title Eric Thompson commented on HI-348 Re: Enable deep-merge options to be passed in lookup see review in pup-4070 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-1121) Node regex beginning with dash results in invalid tag
Title: Message Title Zachary Stern assigned an issue to Unassigned Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: Zachary Stern Assignee: David Gwilliam 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-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 3 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-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 3 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-353) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on HI-353 Re: Is there a commit for every JIRA ticket targeted at the release? Verified with https://gist.github.com/thallgren/c7bf0c082369a1acb0e4. ALL ISSUES WERE FOUND IN GIT 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-352) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg commented on HI-352 Re: Is there a JIRA ticket targeted at the release for every commit? Verified with https://gist.github.com/thallgren/c7bf0c082369a1acb0e4. The unmarked commits are: ** UNMARKED 51bed82 Revert "(maint) Add deep_merge gem install to git and packages pre-suite" 303add3 Revert "(maint) Remove unused setup script" 5c57446 Revert "(HI-238) Remove current directory from Ruby load path." 7adfc62 Adds ignore of .idea/ directory (used by RubyMine IDE) 7c2f324 Revert "(HI-304) Make order override work with interpolation" 62ebf80 Update pooling_api everywhere 47cffbf inform the world which key caused a type mismatch 12ad2ea Update pooling_api everywhere
Jira (HI-354) Update version number in source
Title: Message Title Kylo Ginsberg commented on HI-354 Re: Update version number in source Updated in 01f0aa5c8c159bdeda272201654fc3444a034f14. 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-4282) numeric comparison error
Title: Message Title
Henrik Lindberg commented on PUP-4282
Re: numeric comparison error
Larry Orcutt I read your updated post more carefully - now it correctly tells you what is wrong - you are indeed comparing a String and a Float.
The stdlib function is_float is lying! It reports true for a String that can be converted to a Float !
Note that future parser still converts strings to numbers when arithmetic is performed on the values.
Do you have stringify facts on? (If so, all facts are strings) - turn of stringify facts to get proper data types (if you can).
Do you need your manifests to be backwards compatible or not?
If you do not care about backwards compatibility (or just for testing the example), use the type system to check types instead of the (o_O) stdlib functions. e.g. {{$value =~ Float }}. If you need to retain that facts are Strings (or if the fact in question is a numeric value in sting format), then you can most easily convert it to a number by adding 0 or 0.0 to it. Alternatively, you can use the scanf function to convert from string to value. The function assert_type is also convenient to catch type errors.
Why you got the original error (the "label provider" instead of "String", in your error message is still unanswered, but I guess it is something that was wrong in your local file system since you now were able to get the correct error message.
I am going to close this as a "won't fix" since I believe it works as intended. Feel free to ask more questions (or reopen if by using the type system instead of the is_float function you can show that the evaluator is indeed a comparison of two floats values).
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (HI-348) Enable deep-merge options to be passed in lookup
Title: Message Title Kylo Ginsberg assigned an issue to QA Hiera / HI-348 Enable deep-merge options to be passed in lookup Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: Henrik Lindberg QA 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-346) Gemfile is outdated
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-346 Gemfile is outdated Change By: Kylo Ginsberg Fix Version/s: HI 2.0.0 Fix Version/s: HI 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 (HI-351) Is the code ready for release?
Title: Message Title Kylo Ginsberg commented on HI-351 Re: Is the code ready for release? hiera#master has passed both conventional and AIO pipelines. 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-1346) PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw
Title: Message Title gepetto-bot commented on PDB-1346 Re: PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw mullr commented: This looks good. :+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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman mullr commented: @pljenkinsro retest this please 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-1182) Status: (query) Create new PE specific endpoint for status overview
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1182 Status: (query) Create new PE specific endpoint for status overview Change By: AJ Roetker Assignee: AJ Roetker 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-1346) PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw
Title: Message Title gepetto-bot commented on PDB-1346 Re: PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/905/ 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-1343) PR (1319): (maint) remove duplicated storage test - wkalt
Title: Message Title gepetto-bot commented on PDB-1343 Re: PR (1319): (maint) remove duplicated storage test - wkalt Pull request (maint) remove duplicated storage test 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 (PDB-1343) PR (1319): (maint) remove duplicated storage test - wkalt
Title: Message Title gepetto-bot commented on PDB-1343 Re: PR (1319): (maint) remove duplicated storage test - wkalt rbrw commented: LGTM 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-830) xendomains returning empty on debian hosts
Title: Message Title Melissa Stone updated an issue Facter / FACT-830 xendomains returning empty on debian hosts Change By: Melissa Stone Story Points: 3 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-830) xendomains returning empty on debian hosts
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Facter / FACT-830 xendomains returning empty on debian hosts Change By: Melissa Stone Assignee: 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 (FACT-830) xendomains returning empty on debian hosts
Title: Message Title Melissa Stone updated an issue Facter / FACT-830 xendomains returning empty on debian hosts Change By: Melissa Stone Sprint: RE 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 (HI-346) Gemfile is outdated
Title: Message Title Kylo Ginsberg commented on HI-346 Re: Gemfile is outdated IMHO this is not blocking for hiera 2.0.0. But nice cleanup to get to. 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-4190) CLONE - Puppet device displays credentials in plain text when run manually
Title: Message Title Branan Riley updated an issue Puppet / PUP-4190 CLONE - Puppet device displays credentials in plain text when run manually Change By: Branan Riley Fix Version/s: PUP 3.7.5 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-1343) PR (1319): (maint) remove duplicated storage test - wkalt
Title: Message Title gepetto-bot commented on PDB-1343 Re: PR (1319): (maint) remove duplicated storage test - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/904/ 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-4282) numeric comparison error
Title: Message Title Henrik Lindberg commented on PUP-4282 Re: numeric comparison error Yes, there should be no auto convert for comparisons as decided in PUP-3615 . The problem reported in this ticket is two-fold, it appears that two float values are not comparable, and then the error message is corrupted because it is trying to tell us that one of the compared objects is the thing that produces the label for the object (label being "Float", "String", "An if _expression_", etc) instead of the actual label. 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-3931) Upgrading Puppet package within Puppet agent run on EL7 results in bad package state
Title: Message Title Kylo Ginsberg commented on PUP-3931 Re: Upgrading Puppet package within Puppet agent run on EL7 results in bad package state Shane Madden yes this will be merged up to master before 4.0 final. 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-4282) numeric comparison error
Title: Message Title Paula Vaughan commented on PUP-4282 Re: numeric comparison error I've run the same sample code "foo.pp" on a box with puppet 3.7.2 and get the following results... Notice: Scope(Node[com]): <3833.70> less than <50> In this case, the comparison worked. (it may not look that way, but here, 50 is 50,000) Is this somewhat related to "( PUP-3615 ) Remove string to number auto convert for compare and equals"? When I look at the compare_operator code, it appears that the auto convert is occuring in the 3.7.2 code, but not in the 3.7.4 code. 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-1326) PuppetDB 2.3.1 Release
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1326 PuppetDB 2.3.1 Release Change By: Ryan Senior 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 (PDB-1282) 'extract' on 'new_value' broken
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1282 'extract' on 'new_value' broken Change By: Ryan Senior 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 (PDB-1289) Use producer_timestamp in GC query
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: Russell Mull When synchronizing two PDBs, new factsets and catalogs are inserted using the regular "replace catalog" and "replace facts" commands. These update their respective 'timestamp' fields. Since this timestamp is used to determine if a node is stale (should be automatically deactivated), it ensures GC won't happen until `node-ttl` after sync. This is compounded by cases where GC happens at different times on each node and a sync happens in between, which may cause a previously deactivated node to be re-activated with a long ttl. 1. Require NTP to run on puppet master + pdb2. Change GC query (scf.storage/stale-nodes) to use producer_timestamp3. Audit code to find other usages of factset.timestamp, catalog.timestamp in logic4. Run a synchronous GC cycle when receiving a sync command, before generating manifests. 5. Check that report GC is running against a field generated on the master 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-1289) Use producer_timestamp in GC query
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: Ryan Senior Story Points: 3 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-1289) Use producer_timestamp in GC query
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: Russell Mull When synchronizing two PDBs, new factsets and catalogs are inserted using the regular "replace catalog" and "replace facts" commands. These update their respective 'timestamp' fields. Since this timestamp is used to determine if a node is stale (should be automatically deactivated), it ensures GC won't happen until `node-ttl` after sync. This is compounded by cases where GC happens at different times on each node and a sync happens in between, which may cause a previously deactivated node to be re-activated with a long ttl. 1. Require NTP to run on puppet master + pdb 2. Change GC query (scf.storage/stale-nodes) to use producer_timestamp 3. Audit code to find other usages of factset.timestamp, catalog.timestamp in logic 4. Run a synchronous GC cycle when receiving a sync command, before generating manifests. 5. Check 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 Ryan Senior updated an issue PuppetDB / PDB-1294 Add indices to foreign key columns Change By: Ryan Senior 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 (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1292 puppetdb api docs should include concrete examples Change By: Ryan Senior 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 (PDB-1307) Bump to the next TK Jetty release 1.3.0
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1307 Bump to the next TK Jetty release 1.3.0 Change By: Ryan Senior Summary: Bump to the next TK Jetty release ( 1. 2.1 or 1. 3.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-1307) Bump to the next TK Jetty release 1.3.0
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1307 Bump to the next TK Jetty release 1.3.0 Change By: Ryan Senior 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://groups.google.com/d/optout.
Jira (PDB-1311) Run sync on an internal timer, with configuration
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1311 Run sync on an internal timer, with configuration Change By: Ryan Senior Story Points: 3 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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman anodelman commented: Failed test unrelated to patch. 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-1309) Finish happy path Clojure end-to-end tests
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1309 Finish happy path Clojure end-to-end tests Change By: Ryan Senior Story Points: 5 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-4279) Add Utopic Unicorn 14.10 and Debian 8 jessie host configurations
Title: Message Title Justin Stoller assigned an issue to Justin Stoller Puppet / PUP-4279 Add Utopic Unicorn 14.10 and Debian 8 jessie host configurations Change By: Justin Stoller Assignee: Justin Stoller 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-1308) Change to pull-based sync
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1308 Change to pull-based sync Change By: Ryan Senior Story Points: 3 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-4282) numeric comparison error
Title: Message Title
Larry Orcutt commented on PUP-4282
Re: numeric comparison error
I still seem to be seeing an issue as I go back to my original task.
[root@hpg8-03 etc]# puppet apply /tmp/foo.pp --parser future --environment production Notice: Scope(Node[com]): memorysize_mb is a float <129022.95> Error: Evaluation Error: Comparison of: String >= Integer, is not possible. Caused by 'A String is not comparable to a non String'. at /tmp/foo.pp:3:25 on node hpg8-03.fsc.fedex.com Error: Evaluation Error: Comparison of: String >= Integer, is not possible. Caused by 'A String is not comparable to a non String'. at /tmp/foo.pp:3:25 on node hpg8-03.fsc.fedex.com [root@hpg8-03 etc]# cat /tmp/foo.pp node /\.com$/ { if is_float($::memorysize_mb) { notice "memorysize_mb is a float <$::memorysize_mb>" }
if ( $::memorysize_mb >= 5 ) { notice "<$::memorysize_mb> greater or equal to <50>" }
#else { notice "<$::memorysize_mb> less than <50>" }
} [root@hpg8-03 etc]#
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-1263) Round robin support for EC2 subnets
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1263 Round robin support for EC2 subnets Change By: Ryan Senior Story Points: 8 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-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Change By: Ryan Senior Sprint: PuppetDB 2015-01-28, PuppetDB 2015- 04 05 - 08 06 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-4282) numeric comparison error
Title: Message Title Henrik Lindberg commented on PUP-4282 Re: numeric comparison error To make sure you are actually running that version, you could change line 221 to start with "XXX Comparison of...", and verify that the XXX is part of the output. (Then change it back again). I will test against 3.7.4 as well (you may want to wait for that). 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-4282) numeric comparison error
Title: Message Title Larry Orcutt commented on PUP-4282 Re: numeric comparison error Please close. Appears to be a dumb error on my part unable to see the difference between $x and $::x. Sorry about that. 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-1346) PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1346 PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw Issue Type: Task Assignee: Unassigned Created: 2015/03/24 10:40 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) applied-migrations: don't ignore exceptions Author: Rob Browning <> Company: Github ID: rbrw Pull Request 1320 Discussion Pull Request 1320 File Diff Pull Request Description Check to see if there is a schema_migrations table before querying it. This eliminates these error messages from the postgresql log: STATEMENT: SELECT version FROM schema_migrations ORDER BY version ERROR: relation "sche
Jira (PDB-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman 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/902/ 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-4285) Puppetlabs depends on ruby(selinux) but it's not present in the dependencies repository
Title: Message Title Brian Hourigan created an issue Puppet / PUP-4285 Puppetlabs depends on ruby(selinux) but it's not present in the dependencies repository Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/03/24 10:04 AM Environment: Amazon Linux 2015.03.rc* Priority: Normal Reporter: Brian Hourigan I'm attempting to install puppet on Amazon Linux 2015.03.rc-1 (ami id ami-41795471) but puppet-3.7.4-1.el6.noarch requires ruby(selinux) which is not available for any version of ruby in my configured repositories[2]. I found that a number of puppet dependencies are present in the dependency repository[1] but ruby(selinux) is not. Please consider adding it. [1] http://yum.puppetlabs.com/el/6/dependencies/x86_64/ [2] amzn-main, amzn-updates, epel
Jira (PUP-4282) numeric comparison error
Title: Message Title
Larry Orcutt commented on PUP-4282
Re: numeric comparison error
Sorry - just saw that I cut and pasted the wrong section from the file:
220 COMPARISON_NOT_POSSIBLE = hard_issue :COMPARISON_NOT_POSSIBLE, :operator, :left_value, :right_value, :detail do 221 "Comparison of: # {label(left_value)}
# {operator}
# {label(right_value)}
, is not possible. Caused by '# {detail}
'." 222 end
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-1345) Add puppetdb-sync unit test feedback to puppetdb travis-ci
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1345 Add puppetdb-sync unit test feedback to puppetdb travis-ci Issue Type: Task Assignee: Unassigned Created: 2015/03/24 9:47 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker This will just mean merging the sync repo's .travis.yml into the puppetdb .travis.yml. Add Comment This message was sent by Atlassian JIRA (v6.3.10#
Jira (PDB-1344) Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1344 Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo) Issue Type: Task Assignee: Unassigned Created: 2015/03/24 9:45 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker PDB and RE need to talk about how we are going to move from the pe-puppetdb repo to building packages for PE out of the extensions repo. Add Comment
Jira (FACT-168) Changed domain and fqdn facts
Title: Message Title James Eckersall commented on FACT-168 Re: Changed domain and fqdn facts Hi, I'm experiencing this, or at least a similar bug with CentOS 7. On a newly deployed VM (deployed via vagrant from the puppetlabs/centos-7.0-64-nocm box), the fqdn returned by facter does not really make sense. I've installed the puppetserver and puppet-agent packages from the latest nightly repo, using the below repo files. http://nightlies.puppetlabs.com/puppetserver-latest/repo_configs/rpm/pl-puppetserver-latest-el-7-x86_64.repo http://nightlies.puppetlabs.com/puppet-agent-latest/repo_configs/rpm/pl-puppet-agent-latest-el-7-x86_64.repo $ /opt/puppetlabs/bin/facter fqdn pm4.some.domain $ cat /etc/hostname pm4.je.local $ cat /etc/resolv.conf Generated by NetworkManager domain some.domain search some.domain je.local nameserver 10.0.2.3 $ hostname pm4.je.local $ hostname -a hostname: Name or service not known $ hostname -f hostname: Name or service not known [root@pm4 ~]# The true fqdn for this VM is "pm4.je.local" (as defined in the Vagrantfile), yet facter is gathering the domain from /etc/resolv.conf. On EL7, as far as I understand it, /etc/hostname should be the true fqdn for the server so I believe that should be the first source of truth for facter. I know the domain in /etc/resolv.conf is wrong, but that shouldn't be used by facter anyway if there is an /etc/hostname file. In fact, it could be argued that facter should use the binary sethostnamectl to determine the correct fqdn. $ hostnamectl Static hostname: pm4.je.local Icon name: computer-vm Chassis: vm Machine ID: c0d6e2bd95924896857707d6196220d6 Boot ID: 8ab5dfb4c46e4de785ec22b6b8fb2d8c Virtualization: oracle Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-123.20.1.el7.x86_64 Architecture: x86_64 I'd like to also point out that I see the same behaviour on CentOS 6 deployed via Vagrant/VirtualBox. I'm not sure what the correct method of determining the fqdn should be on CentOS 6. The resolv.conf file is the same on both VM's. This file is wrongly populated by VirtualBox DHCP - it inherits the domain of the host machine and I can't find an easy way to fix it. But I think this doesn't detract from the issue that facter isn't correctly picking up the fqdn. Add Comment
Jira (PUP-4282) numeric comparison error
Title: Message Title
Larry Orcutt commented on PUP-4282
Re: numeric comparison error
Looking at /usr/lib/ruby/site_ruby/1.8/puppet/pops/issues.rb on the puppet master:
228 MATCH_NOT_STRING = hard_issue :MATCH_NOT_STRING, :left_value do 229 "Left match operand must result in a String value. Got # {label.a_an(left_value)}
." 230 end
[root@vmst13 ~]# rpm -qf /usr/lib/ruby/site_ruby/1.8/puppet/pops/issues.rb puppet-3.7.4-1.el6.noarch [root@vmst13 ~]# rpm -V puppet-3.7.4-1.el6.noarch S.5T. c /etc/puppet/auth.conf S.5T. c /etc/puppet/puppet.conf .M... /var/lib/puppet/state [root@vmst13 ~]# sum /usr/lib/ruby/site_ruby/1.8/puppet/pops/issues.rb 10312 23 [root@vmst13 ~]#
The rpm information and the checksum on this file is the same on the client where I was seeing the error.
Is there anything else you needed?
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-1343) PR (1319): (maint) remove duplicated storage test - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1343 PR (1319): (maint) remove duplicated storage test - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/03/24 9:32 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) remove duplicated storage test Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1319 Discussion Pull Request 1319 File Diff Pull Request Description this removes a storage test that was mistakenly duplicated rolling up stable to master rollup. (webhooks-id: 30baa981f4eb1388f4727c5724a5c059)
Jira (PUP-4282) numeric comparison error
Title: Message Title Henrik Lindberg commented on PUP-4282 Re: numeric comparison error Larry Orcutt can you look at the other things I suggested as I cannot reproduce the problem you are seeing. 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-4282) numeric comparison error
Title: Message Title Larry Orcutt commented on PUP-4282 Re: numeric comparison error Yes, this is using future parser. 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-1342) Using facts terminus with puppetdb_apply fails on Puppet 4.0
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1342 Using facts terminus with puppetdb_apply fails on Puppet 4.0 Change By: Ryan Senior Sprint: PuppetDB 2015-04-08 Scrum Team: PuppetDB 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-4284) Puppet module install does not fully honour --target-dir
Title: Message Title Robert Scheer created an issue Puppet / PUP-4284 Puppet module install does not fully honour --target-dir Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Components: Modules Created: 2015/03/24 9:11 AM Priority: Minor Reporter: Robert Scheer The command "puppet module install" does not honour the option --install-dir during the pre-install-check. The actual installation however is done in the correct dir. ls -ld /etc/puppet/modules/apt ls: cannot access /etc/puppet/modules/apt: No such file or directory puppet module install --target-dir=/etc/puppet/modules/ puppetlabs-apt Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not install module 'puppetlabs-apt' (latest) Installation would overwrite /data/puppet/environments/production/modules/apt Use `puppet module
Jira (PUP-4120) Capture and process logs of master --preview
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4120 Capture and process logs of master --preview Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-1342) Using facts terminus with puppetdb_apply fails on Puppet 4.0
Title: Message Title John Duarte created an issue PuppetDB / PDB-1342 Using facts terminus with puppetdb_apply fails on Puppet 4.0 Issue Type: Bug Affects Versions: PDB 2.3.0 Assignee: Unassigned Created: 2015/03/24 9:08 AM Environment: Two redhat-7-x86_64 boxes, puppet software installed from packages Pupper server: Server: puppetserver-2.0.0-0.1rc3 Agent: puppet-agent-0.9.0-1 Agent/PuppetDB Server: puppetserver-2.0.0-0.1rc3 Agent: puppet-agent-0.9.0-1 PuppetDB: puppetdb-2.3.0 Labels: AIO Priority: Normal Reporter: John Duarte Performing a puppet apply using the facts terminus with a puppetdb_apply cache fails when using Puppet 4.0 # FACTE
Jira (PUP-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4283 Update PMT to use only semantic_puppet versions (not SemVer) Change By: Anderson Mills Scrum Team: Code Management 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-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4283 Update PMT to use only semantic_puppet versions (not SemVer) Change By: Anderson Mills Component/s: PMT 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-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills commented on PUP-4283 Re: Update PMT to use only semantic_puppet versions (not SemVer) Thanks for the thorough answer. I was not aiming to get this in 4.0.0. I'll retarget for 4.1.0, as I do think it needs to happen soon because of other things coming down the pipe (semantic_puppet as a library). 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-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4283 Update PMT to use only semantic_puppet versions (not SemVer) Change By: Anderson Mills Fix Version/s: PUP 4.x Fix Version/s: PUP 4.1.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-4070) Deep merge options cannot be passed as options map.
Title: Message Title Zachary Elliott updated an issue Puppet / PUP-4070 Deep merge options cannot be passed as options map. Change By: Zachary Elliott When using lookup, the merge strategy can be passed as a map with a 'strategy' key and additional options. This map is type validated and everything works fine for the 'unique' and 'hash' strategies but it fails when using the 'deep' merge strategy since it allows additional options with varying element types (booleans in particular).The reason this fails is that the type validation incorrectly uses 'infer()' on the given map (which produces a Hash type) instead of 'infer_set()' (which produces a Struct type). The assignable? then fails since it tries to verify all elements of the required type using the common element type of the inferred Hash. 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-1119) Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1119 Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo Change By: Ryan Senior Sprint: PuppetDB 2015-05-06 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-1155) PuppetDB 3.0.0 Release
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1155 PuppetDB 3.0.0 Release Change By: Ryan Senior Sprint: PuppetDB 2015-05-06 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-1228) investigate a paging solution for multi-row responses
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1228 investigate a paging solution for multi-row responses 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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1325 PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Change By: Kenneth Barber Scope Change Reason: PR from QA team related to a more global beaker/job change requirement Scope Change Category: Adopted 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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1325 PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Change By: Kenneth Barber Sprint: PuppetDB 2015-03-25 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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1325 PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Change By: Kenneth Barber Story Points: 0 Fix Version/s: PDB 2.3.x Issue Type: Task Improvement 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-1324) PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1324 Re: PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Pull request (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... 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 (PDB-1324) PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1324 Re: PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman kbarber commented: I think the PR into stable is enough, we'll roll up the change ourselves to master. 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-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman kbarber commented: @pljenkinsro test this please 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 Ryan Senior updated an issue PuppetDB / PDB-1297 Ensure acceptance tests work with Puppet 4 Change By: Ryan Senior Sprint: PuppetDB 2015-04- 08 22 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-1326) PuppetDB 2.3.1 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1326 PuppetDB 2.3.1 Release 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-1340) Push changes to pe-puppetdb branch
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1340 Push changes to pe-puppetdb branch Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/24 7:35 AM Priority: Normal Reporter: Kenneth Barber These changes will need to be pushed to the relevant branch for pe-puppetdb Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1341) Close all resolved tickets and release version in Jira
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1341 Close all resolved tickets and release version in Jira Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/24 7:35 AM Priority: Normal Reporter: Kenneth Barber Ensure all tickets that were previously resolved are marked now as closed. Ensure the version in Jira is released. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1338) Update the downloads page
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1338 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/03/24 7:35 AM Priority: Normal Reporter: Kenneth Barber Update the downloads page with the public download locations and new version information. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1337) Push tag
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1337 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/03/24 7:35 AM Priority: Normal Reporter: Kenneth Barber Push the tag made earlier up to the main public repo for the branch in question. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) --
Jira (PDB-1334) Smoke test packages
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1334 Smoke test packages Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/24 7:34 AM Priority: Normal Reporter: Kenneth Barber Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1331) Is there a bug targeted at the release for every commit?
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1331 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/24 7:34 AM Priority: Normal Reporter: Kenneth Barber Ensure that all commits in git between the last and current release have corresponding tickets pointing at this release. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1329) Update documentation indexes for new major release
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1329 Update documentation indexes for new major release Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/24 7:34 AM Priority: Normal Reporter: Kenneth Barber The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
