Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Change By: Pieter van de Bruggen Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: Pieter van de Bruggen Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2452) Refreshable feature on package type
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2452 Refreshable feature on package type Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Adrien Thebo updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Adrien Thebo updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Adrien Thebo Affects Version/s: 1.7.4 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Pieter van de Bruggen Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2802) add slot support for packages in portage.rb
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2802 add slot support for packages in portage.rb Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2654 label provider for class/define should capitalize all segments Change By: Henrik Lindberg Component/s: DSL Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2654
label provider for class/define should capitalize all segments
Change By:
Henrik Lindberg
Whenthelabelproviderproducesalabelforadefine/classetc.allsegmentsofthenameshouldbecapitalized.Thelabelisshowninerrormessages. Reproduce bydefining with:{code}definefoo::bar::fee{}$ a resourcetype,andsetitstitletonumeric.Thereportednameshouldhaveallsegmentscapitalized. =with()||{foo::bar::fee{x:}}notice$a{code}Whichdisplays:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2654
label provider for class/define should capitalize all segments
Change By:
Henrik Lindberg
Whenthelabelproviderproducesalabelforadefine/classetc.allsegmentsofthenameshouldbecapitalized.Thelabelisshowninerrormessages.Reproducewith:{code}definefoo::bar::fee{}$a=with()||{foo::bar::fee{x:}}notice$a{code}Whichdisplays:{code} [Type[Foo::bar::fee['1']]]{code}whenitshouldhavebeen[Type[Foo::Bar::Fee['1']]]
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2654
label provider for class/define should capitalize all segments
Change By:
Henrik Lindberg
Whenthelabelproviderproducesalabelforadefine/classetc.allsegmentsofthenameshouldbecapitalized.Thelabelisshowninerrormessages.Reproducewith:{code}definefoo::bar::fee{}$a=with()||{foo::bar::fee{x:}}notice$a{code}Whichdisplays:{code}[Type[Foo::bar::fee['1']]]{code}whenitshouldhavebeen {code} [Type[Foo::Bar::Fee['1']]] {code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2654
label provider for class/define should capitalize all segments
Change By:
Henrik Lindberg
Whenthelabelproviderproducesalabelforadefine/classetc.allsegmentsofthenameshouldbecapitalized.Thelabelisshowninerrormessages.Reproducewith:{code} definefoo noticeType[Foo :: bar Bar :: fee{} Fee] $a=with()|| { foo::bar::fee{x:}}notice$a{ code}Whichdisplays:{code}[Type[Foo::bar::fee ['1' ] ]] {code}whenitshouldhavebeen{code}[Type[Foo::Bar::Fee ['1' ] ]] {code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-709) PR (2048): (maint) Allow code to verify SSL connections post factum - adaburrows
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-709 PR (2048): (maint) Allow code to verify SSL connections post factum - adaburrows Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-674) PR (2035): (#23085) Ensure old puppet agents get properly stopped when upgrading from 2.6 or early to 2.7 or later - skottler
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-674 PR (2035): (#23085) Ensure old puppet agents get properly stopped when upgrading from 2.6 or early to 2.7 or later - skottler Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-638) PR (198): Modify pick() to always return a value. - DavidS
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-638 PR (198): Modify pick() to always return a value. - DavidS Change By: Adrien Thebo Fix Version/s: M Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-621) Pull Request (2014): [#22992] Correction of wrong exit code when testing state.yaml
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-621 Pull Request (2014): [#22992] Correction of wrong exit code when testing state.yaml Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-632) PR (197): fix typo in pick error message
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-632 PR (197): fix typo in pick error message Change By: Adrien Thebo Fix Version/s: M Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-616) Pull Request (1996): (#22858) note official ruby 2.0 support in README
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-616 Pull Request (1996): (#22858) note official ruby 2.0 support in README Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-624) Pull Request (189): (#20200) Add a recursive merge function.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-624 Pull Request (189): (#20200) Add a recursive merge function. Change By: Adrien Thebo Fix Version/s: M Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-613) Pull Request (1984): (maint) Remove shebangs from *.rb files in lib
Title: Message Title Adrien Thebo commented on an issue Re: Pull Request (1984): (maint) Remove shebangs from *.rb files in lib Merged in cd65a30. Add Comment Puppet / PUP-613 Pull Request (1984): (maint) Remove shebangs from *.rb files in lib h2. (maint) Remove shebangs from *.rb files in lib * Author: John-John Tedro johnjohn.te...@gmail.com * Company: Spotify AB * Github ID: [udoprog|https://github.com/udoprog] * [Pull Request 1984 Discussion|https://github.com/puppetlabs/puppet/pull/1984] * [Pull Request 1984 File Diff|https://github.com/puppetlabs/puppet/pull/1984/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-615) Pull Request (1994): Let OpenBSD use gtar too.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-615 Pull Request (1994): Let OpenBSD use gtar too. Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-619) Pull Request (2008): improve tag performance
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-619 Pull Request (2008): improve tag performance Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-612) Pull Request (1983): (maint) Remove executable permission from *.rb files in lib
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-612 Pull Request (1983): (maint) Remove executable permission from *.rb files in lib Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-593) Pull Request (2016): (#22938) test and document symbolic file modes
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-593 Pull Request (2016): (#22938) test and document symbolic file modes Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2802) add slot support for packages in portage.rb
Title: Message Title Proneet Verma assigned an issue to Proneet Verma Puppet / PUP-2802 add slot support for packages in portage.rb Change By: Proneet Verma Assignee: ProneetVerma Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-442) (PR) (22617) In Augeas onlyif, compare number strings numerically
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-442 (PR) (22617) In Augeas onlyif, compare number strings numerically Change By: Adrien Thebo Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-87) PR (554): Cherry-pick aix memory fixes - haus
Title: Message Title Adrien Thebo updated an issue Facter / FACT-87 PR (554): Cherry-pick aix memory fixes - haus Change By: Adrien Thebo Fix Version/s: 1.7.4 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Change By: Adrien Thebo Fix Version/s: M Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1553) PR (2312): Fix error message in reduce function - dalen
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1553 PR (2312): Fix error message in reduce function - dalen Change By: Adrien Thebo Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1958) Puppet Ticketing System Should Support Puppet Markup
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1958 Puppet Ticketing System Should Support Puppet Markup Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2358) puppet apply throws SELinux errors if $HOME is mounted via NFS
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2358 puppet apply throws SELinux errors if $HOME is mounted via NFS Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-479) Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-479
Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Change By:
Adrien Thebo
Ihavearubycustomfactthatwhenqueriedwith'facter-pmysite'onAIX6.1/7.1displaysasexpected(egTX),butifIdo'facter-p|grepmysite'itshowsuplike[TX].Itwillshowupthiswrongwaywhenitgoestopuppetdb.Thefacterversionis1.7.5withpuppet3.4.3,bothinstalledviagems,onAIXwithruby2.0.0p353.Thebuilt-infactsdonothavethissameissue.Thecustomrubyfactcodeissomethinglike: {code} Facter.add(mysite)dosetcodedocaseFacter.value(:ipaddress)when/^10\.1\.91\.|^10\.1\.92\.|^10\.1\.93\./TXwhen/^13\.1\.1\.|^13\.1\.2\./CAendendend {code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title
Henrik Lindberg commented on an issue
Re: Complete handling of undef/nil
We currently have the following in the implementation:
CALL BY POSITION
calling 3x function API, undef is transformed to empty string (or functions will generally blow up). We do this transformation deeply (arrays, and hashes / nested)
calling 4x function API, undef is passed through (as nil for computational results, and :undef when it is entered as a literal).
# gets :undef, notices true
with($y) |$x| { notice $x =~ Undef }
# gets nil, notices true
with($y) |undef| { notice $x =~ Undef }
# gets nil, notices true
with({}[x]) |$x| { notice $x =~ Undef }
The semantics are the same when calling a lambda, an undef/nil parameter is a value, and it does not trigger the use of the default value
# prints false (it does not get the default)
with(undef) |$x=10| { notice $x =~ Integer }
# prints true, (it gets the default)
with(undef) |$x=10| { notice $x =~ Integer }
CALL BY NAME
In call by name (passing parameters to classes, and defines) passing nil or undef is the same as not passing it at all (defaults will be used)
In call by name to EPP, the given hash is not transformed, and it behaves as a lambda
TYPE SYSTEM In the type system, Any accepts undef/nil, Scalar does not, and Optional must be used to accept undef/nil value. The Data type accepts undef (Data is equivalent to the stuff 3x passes around - a mix or Scalar, Undef, and with restrictions on keys and values)
LOGIC All values except Boolean false and an Undef value are truthy (i.e. empty string is now thruthy).
LEFT TO DISCUSS Should literal :undef's be passed to functions, or be transformed to nil? This poses potential problems, as the transformation may have to be made when the call takes place because the given data is used in several situations (transformation to 3x resources where empty string is expected) etc. (This needs to be investigated). (It is not good that :undef leaks into the functions).
Jira (FACT-479) Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Title: Message Title Adrien Thebo updated an issue Facter / FACT-479 Custom facts with facter 1.7.5 on AIX display facts as [fact value] Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-479) Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Title: Message Title
Adrien Thebo commented on an issue
Re: Custom facts with facter 1.7.5 on AIX display facts as [fact value]
The description of this issue indicates that the value in your custom fact is returning an array of values rather than a single value. Facter handles single values separately from multiple values; single values are printed with `puts` but multiple values are interpolated as a string. See https://github.com/puppetlabs/facter/blob/1.7.5/lib/facter/application.rb#L68-L76 for more information.
I was able to reproduce this with the following:
[1] pry(main) value = [TX]
[2] pry(main) puts value
TX
[3] pry(main) puts mysite = #{value}
mysite = [TX]
[4] pry(main) puts [foo, bar]
foo
bar
This is intended behavior on the part of Ruby; when outputting an array each element of the array is put on a separate line so when an array has one element it displays like a single value. Returning multiple values demonstrates that each value is on a different line.
Since this is a bug in the custom fact and not a bug in Facter I'm closing this issue. To resolve this on your end, make sure that your custom fact is returning a string and not an array of strings.
Add Comment
Facter / FACT-479
Custom facts with facter 1.7.5 on AIX display facts as [fact value]
I have a ruby custom fact that when queried with 'facter -p mysite' on AIX 6.1/7.1 displays as expected (eg TX), but if I do 'facter -p | grep mysite' it shows up like [TX]. It will show up this wrong way when it goes to puppetdb. The facter version is 1.7.5 with puppet 3.4.3, both installed via gems, on AIX with ruby 2.0.0p353. The built-in facts do...
Jira (PUP-2842) Limit platforms on which Gemfile tries to install ruby-prof
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2842 Limit platforms on which Gemfile tries to install ruby-prof Change By: Josh Cooper Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1270 PR (2200) 'pkg' package provider does not understand IPS package versions properly Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2842) Limit platforms on which Gemfile tries to install ruby-prof
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2842 Limit platforms on which Gemfile tries to install ruby-prof Change By: Josh Cooper Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1541) PR (2309): Separate out hold state into a separate property - lollipopman
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1541 PR (2309): Separate out hold state into a separate property - lollipopman Change By: Adrien Thebo Fix Version/s: future Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2842) Limit platforms on which Gemfile tries to install ruby-prof
Title: Message Title Josh Cooper commented on an issue Re: Limit platforms on which Gemfile tries to install ruby-prof Merged in 47425cba to master, verified bundle install --path .bundle worked on mac and windows, and both continued to install ruby-prof Add Comment Puppet / PUP-2842 Limit platforms on which Gemfile tries to install ruby-prof The ruby-prof gem is not applicable on all platforms (e.g., jruby). However, the Gemfile attempts to install it unconditionally. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title
Andy Parker commented on an issue
Re: parameter lookup produces screwy result for default values
Here is an example of how weird things can get when you access the values on virtual resources.
@notify { m: message = hi }
Notify || { message = bye }
define a () {
notice(Notify[m][message])
}
notice(Notify[m][message])
a { m: }
The output is:
be puppet apply t.pp --parser future
Notice: hi
Notice: bye
Notice: Compiled catalog for aparker.corp.puppetlabs.net in environment production in 0.49 seconds
Notice: bye
Notice: /Stage[main]/Main/Notify[m]/message: defined 'message' as 'bye'
Notice: Finished catalog run in 0.06 seconds
Add Comment
Puppet / PUP-2532
parameter lookup produces screwy result for default values
When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the lookup resource parameter scope/context, and not the context...
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2682) Trailing commas should be allowed in node definitions
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2682 Trailing commas should be allowed in node definitions Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-624) Pull Request (189): (#20200) Add a recursive merge function.
Title: Message Title Henrik Lindberg commented on an issue Re: Pull Request (189): (#20200) Add a recursive merge function. hm, do we now have three different deep merge behaviors? hiera deep, hiera deeper, and now this? The next request will be to support the deep merge gem, because simple deep merging is most often not enough. Why does this have to be in stdlib? Add Comment Puppet / PUP-624 Pull Request (189): (#20200) Add a recursive merge function. h2. (#20200) Add a recursive merge function. * Author: Justin Burnham * Company: * Github ID: [jburnham|https://github.com/jburnham] * [Pull Request 189 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/189] * [Pull Request 189 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/189/files] h2. Pull Request Description -... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Peter Huene commented on an issue Re: Make puppet able to configure a facter implementation to use Success! Required some refactoring of defaults.rb in Puppet and a version bump with a patched cfacter (it errors if the version is 0.1.0): $ puppet apply --facter=cfacter -e 'notice $::cfacterversion' Notice: Scope(Class[main]): 0.1.1 Notice: Compiled catalog for peterhu-osx.sd.cox.net in environment production in 0.02 seconds Notice: Finished catalog run in 0.01 seconds Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Peter Huene commented on an issue Re: Make puppet able to configure a facter implementation to use Structured facts come through just fine too: $ puppet apply --facter=cfacter --no-stringify_facts -e 'notice $::dhcp_servers[system]' Notice: Scope(Class[main]): 192.168.1.1 Notice: Compiled catalog for peterhu-osx.sd.cox.net in environment production in 0.02 seconds Notice: Finished catalog run in 0.01 seconds Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Peter Huene commented on an issue Re: Make puppet able to configure a facter implementation to use Structured facts come through just fine too: $ puppet apply --facter=cfacter --no-stringify_facts -e 'notice $::dhcp_servers[system]' Notice: Scope(Class[main]): 192.168.1.1 Notice: Compiled catalog for peterhu-osx.sd.cox.net in environment production in 0.02 seconds Notice: Finished catalog run in 0.02 seconds Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title garrett honeycutt commented on an issue Re: Puppet 3.6.1 issue with Forge API v3 This seems to be an issue with compiling the dependency graph. I've not had any modules that use ghoneycutt-generic in years, but it is showing up here. Add Comment Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Getting this error on RHEL5 and RHEL6 when trying to install ghoneycutt/puppet. Broken on 3.6.0 and 3.6.1 but downgrading to 3.5.1 fixed the issue. [root@sbox09 ~]# puppet module install ghoneycutt/puppet --verbose --debug Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Debug: HT... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-392
Validate win32 gems on x86 and x64
Change By:
Josh Cooper
Someofthewin32gemsthatweusecontainnativecodeandarenotportabletox64.Thecompletelistofgemsthatwecurrentlyvendoris:https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications{noformat}bigdecimal-1.1.0deep_merge-1.0.0ffi-1.9.0-x86-mingw32io-console-0.3json-1.5.5minitar-0.5.4minitest-2.5.1rake-0.9.2.2rdoc-3.9.5rgen-0.6.5stomp-1.2.9sys-admin-1.5.6-x86-mingw32win32-api-1.4.8-x86-mingw32win32-dir-0.4.3win32-eventlog-0.5.3win32-process-0.6.5win32-security-0.1.4win32-service-0.7.2-x86-mingw32win32-taskscheduler-0.2.2win32console-1.3.2-x86-mingw32windows-api-0.4.2windows-pr-1.2.2{noformat}Foreachgem,weneedtodetermineifitneedstobeupdated.Ifagemneedsupdating,itmustbedoneinthefollowingpuppet-win32-rubybranches.Notesomegemscontainplatformspecificcode,e.g.ffi-1.9.3-x86,andwillneedtomatchthetargetbranch:{noformat}puppet-win32-ruby#1.9.3-x86puppet-win32-ruby#2.0.0-x64{noformat}Additionally,wemayneedtoupdateversionconstraintsinthefollowinglocations:{noformat}Gemfileext/project_data.yaml{noformat}Forexample,win32-security0.2.4isknowntohaveabug,soweneedtorequire~0.2.5Someofthegemslistedabovehaveknownissues,soseparateticketshavealreadybeencreated:{noformat}win32consolewin32-securitywin32-service{noformat}Theremainingsetofgemsshouldbeverifiedaspartofthistickete.g.trytomanagethattypeofresource,trytowritetotheeventlog,etcunderbothx86andx64ruby.Ifagemdoesn'twork,updateit.Thisshouldmainlyaffectwindowsgemsthatarenotffi'ed,e.g.win32-eventlog.Onethesegemshavebeenvalidatedandupdated,weshouldbeinagoodpositiontorunacceptancetests.Thiswillalsoprepareusforremovingourdependencyonwindows-prwin32-apigems. Wealsowanttoremovesys-admingem.Itisreferencedin{{ext/project_data.yaml}},{{install.rb}},etcbutneverused.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1548) Facter deliver wrong architecture to puppet
Title: Message Title
Bjoern commented on an issue
Re: Facter deliver wrong architecture to puppet
No
root@PC3214ub:~# facter architecture amd64 root@PC3214ub:~# facter -p architecture amd64
Add Comment
Puppet / PUP-1548
Facter deliver wrong architecture to puppet
I got this params.pp {noformat} case $::operatingsystem{ 'Debian', 'Ubuntu': { $package_name = SnareLinux-3.0.0-2_$::architecture.deb $provider = 'dpkg' $install_name = 'snarelinux' } {noformat} On Ubuntu Client puppet says: {noformat} root@PC3214ub:~# puppet agent -t info: Retrieving plugin ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-604) Fact domainname does hostname no-op call on windows
Title: Message Title Walter Doekes created an issue Facter / FACT-604 Fact domainname does hostname no-op call on windows Issue Type: Bug Assignee: Eric Sorenson Created: 25/Jun/14 1:43 AM Priority: Minor Reporter: Walter Doekes 67e57de4fb9314382b950a7e016fd46046aa40a1 (branch facter-2) lib/facter/domain.rb: windows_hostname = 'hostname NUL' That outputs nothing. Should be 2 NUL but that might change existing behaviour now. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2836) Incorrect lockfile placemen
Title: Message Title Ivan created an issue Puppet / PUP-2836 Incorrect lockfile placemen Issue Type: Bug Affects Versions: 3.6.0 Assignee: Kylo Ginsberg Components: Client Created: 25/Jun/14 1:49 AM Environment: Debian stable Priority: Normal Reporter: Ivan Currently agent places its lockfile in /var/lib/puppet/state/agent_catalog_run.lock. according to man hier this file survives any reboot, so when my machine reboots abruptly or affected by reset button or oom_killed on the supervisor node or (...thousand other reasons...), puppet agent sees this file at reboot and never runs again. However, it is common in linux systems to place such lockfiles in /run or /run/lock : theese locations are cleaned up at boot and after abrupt reboot or something like that outdated lockfiles do not take effect.
Jira (PUP-2837) alter parser to throw an error on use of an undefined, unquoted, variable.
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2837
alter parser to throw an error on use of an undefined, unquoted, variable.
Issue Type:
New Feature
Assignee:
Unassigned
Created:
25/Jun/14 3:13 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
Currently, the parser treats the following cases as equivalent:
pre
file {/tmp/testfile: content = $content }
file {/tmp/testfile: content = $content }
/pre
I think it would be beneficial to throw a compile error in the first case if $content is not defined, eg fail('Attempt to use unquoted, undefined variable $content'). This would sensibly catch many cases where I have:
typo'd on variable names,
misjudged scoping,
forgotten to define a variable that I am using in a defined type,
broken a facter fact.
The second form
Jira (PUP-2837) alter parser to throw an error on use of an undefined, unquoted, variable.
Title: Message Title
Henrik Lindberg commented on an issue
Re: alter parser to throw an error on use of an undefined, unquoted, variable.
In the 3x future parser, undefined variables all have the value undef and this value renders as an empty string when interpolated. Since (IIRC 3.5.0) it is possible to turn on --strict_variables and get an error whenever an undefined variable (one that has never been initialized, not even to undef). The intent is to keep this as optional behavior also in Puppet 4.0 simply because changing this would cause breaking a lot of code.
We are hoping to be able to enforce --strict_variables in Puppet 5.0.
The mixed undefined variables can be interpolated-mode would just make everything even more confusing, and this is not something that we have considered implementing.
We already have a ticket for Make variables strict by default, so I am closing this as a duplicate.
Add Comment
Puppet / PUP-2837
alter parser to throw an error on use of an undefined, unquoted, variable.
Currently, the parser treats the following cases as equivalent: pre file {/tmp/testfile: content = $content } file {/tmp/testfile: content = $content } /pre I think it would be beneficial to throw a compile error in the first case if $content is not defined, eg fail('Attempt to use unquoted, undefined variable $conte...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2838 Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names Issue Type: Bug Affects Versions: 3.6.2, 3.6.1 Assignee: Unassigned Attachments: graph_fail.png Created: 25/Jun/14 5:30 AM Priority: Normal Reporter: Tristan Helmich Puppet generates invalid .dot files. If a resource name contains a quoted string the name is not escaped in the .dot file. Example content generated by puppet: Postgresql_psql[GRANT ALL ON DATABASE puppetdb TO puppetdb] [ fontsize = 8, label = Postgresql_psql[GRANT ALL ON DATABASE puppetdb TO puppetdb] ] resulting in something like this: The behavior has been reproduced with Puppet 3.6.1 and 3.6.2
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title
Tristan Helmich updated an issue
Puppet / PUP-2838
Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Change By:
Tristan Helmich
Puppetgeneratesinvalid.dotfiles.Ifaresourcenamecontainsaquotedstringthenameisnotescapedinthe.dotfile.Examplecontentgeneratedbypuppet:{code}Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb]]{code} resultinginsomethinglikethis:!graph_fail.png|thumbnail! Correctlyescapeditwouldlooklikethis:{code}Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\]]{code} resultinginsomethinglikethis: !graph_fail.png|thumbnail! ThebehaviorhasbeenreproducedwithPuppet3.6.1and3.6.2
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title
Tristan Helmich updated an issue
Puppet / PUP-2838
Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Change By:
Tristan Helmich
Puppetgeneratesinvalid.dotfiles.Ifaresourcenamecontainsaquotedstringthenameisnotescapedinthe.dotfile.Examplecontentgeneratedbypuppet:{code}Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb]]{code} Correctlyescapeditwouldlooklikethis:{code}Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\]]{code} resultinginsomethinglikethis:!graph_fail.png|thumbnail!ThebehaviorhasbeenreproducedwithPuppet3.6.1and3.6.2
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
Josh Cooper You would think we vendored json but it is not actually in https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/gems
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
Some of this work was already done in the creation of the ruby 2.0 branch (
PUP-2389
). I reinstalled all dependencies based on looking at where we were going with facter, hiera, mco, and puppet. So those will just need to be validated as correct in this ticket.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
One thing to watch out for is files that are installed to bin as part of the gem install may contain a full path to ruby that is undesirable. So those will need to be edited or those lines reverted as part of the updates.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options,
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Issue Type: Bug Affects Versions: 3.6.2, 3.6.1, 3.6.0 Assignee: Andy Parker Components: DSL Created: 25/Jun/14 7:33 AM Labels: 3.6.0 future-parser Priority: Critical Reporter: Tristan Helmich In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): puppet apply --graph --modulepath /vagrant/modules/ --parser future futureparser_dependency_cycle.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /root//puppet/lib/puppet/settings.rb:1069:in `each') Notice: Compiled catalog for
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Robin Gloster assigned an issue to Robin Gloster Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Change By: Robin Gloster Assignee: AndyParker RobinGloster Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Robin Gloster updated an issue Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Change By: Robin Gloster Assignee: RobinGloster AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2840) PropertyList returns true when asked if nil is insync
Title: Message Title
Charlie Sharpsteen created an issue
Puppet / PUP-2840
PropertyList returns true when asked if nil is insync
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
25/Jun/14 9:12 AM
Labels:
customer
Priority:
Normal
Reporter:
Charlie Sharpsteen
The insync method for PropertyList starts with the following guard clause:
def insync?(is)
return true unless is
...
Nil values frequently occur when resources are transitioning from :absent to a managed state as the property hash for an absent resource usually takes the following form:
{
ensure = :absent
}
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Andy Parker updated an issue Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Change By: Andy Parker Fix Version/s: 3.6.3 Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Andy Parker commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
I think what is happening here is that somehow that change has caused (See https://github.com/fadenb/puppet_futureparser_depency_cycle_bug/blob/master/modules/component/manifests/example.pp)
anchor { 'component::example::begin': } -
class { '::example': } -
anchor { 'component::example::end': }
to end up referring to Class component::example instead of ::example.
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg This looks like a pretty serious issue. I marked it with 3.6.3 since I think we should take a very serious look at whether this is bad enough to warrant a new 3.6 release. Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-723) PR (997): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (997): (RE-1497) Remove quantal from build_defaults - clantant pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-723 PR (997): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 997 Discussion|https://github.com/puppetlabs/puppetdb/pull/997] * [Pull Request 997 File Diff|https://github.com/puppetlabs/puppetdb/pull/997/files] h2. Pull Request Descriptio... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-723) PR (997): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-723 PR (997): (RE-1497) Remove quantal from build_defaults - clantant Issue Type: Task Assignee: Unassigned Created: 25/Jun/14 9:42 AM Labels: github Priority: Normal Reporter: gepetto-bot (RE-1497) Remove quantal from build_defaults Author: Eric Timmerman eet1...@gmail.com Company: Github ID: clantant Pull Request 997 Discussion Pull Request 997 File Diff Pull Request Description This commit removes quantal from all build defaults because it is end of life. It removes the defaults from the build_defaults yaml. (webhooks-id: 0b738690f7b4629ef0785791c1b3dc64)
Jira (PDB-723) PR (997): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (997): (RE-1497) Remove quantal from build_defaults - clantant pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-723 PR (997): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 997 Discussion|https://github.com/puppetlabs/puppetdb/pull/997] * [Pull Request 997 File Diff|https://github.com/puppetlabs/puppetdb/pull/997/files] h2. Pull Request Descriptio... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
The change pointed out makes defaults that previously was not triggered (as they should) to now take effect. The bug was in place from 3.5.0 when the new evaluator was introduced. Afikt, there are no resource defaults in the gist Andy referred to so have a very hard time coming up with a scenario where the blamed commit is causing a problem in that case. For the reported case, I would also look at resource defaults.
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Ethan Brown updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Ethan Brown Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Ethan Brown Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run Facter specs against windows ruby 2.0 x64
Title: Message Title Ethan Brown updated an issue Facter / FACT-568 Run Facter specs against windows ruby 2.0 x64 Change By: Ethan Brown Summary: Run Facter specsagainstwindowsruby2.0x64 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-723) PR (997): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (997): (RE-1497) Remove quantal from build_defaults - clantant Pull request (RE-1497) Remove quantal from build_defaults has been closed. Add Comment PuppetDB / PDB-723 PR (997): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 997 Discussion|https://github.com/puppetlabs/puppetdb/pull/997] * [Pull Request 997 File Diff|https://github.com/puppetlabs/puppetdb/pull/997/files] h2. Pull Request Descriptio... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Franz Pletz commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
Henrik Lindberg Resource defaults are actually used right here: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug/blob/master/modules/component/manifests/example.pp#L6-9
But manually requiring the class in resource definitions without using resource defaults also fails! This is a major bug!
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-723) PR (997): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-723 PR (997): (RE-1497) Remove quantal from build_defaults - clantant Change By: Kenneth Barber Sprint: 20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-722) PuppetDB response hanging on select-nodes subquery
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-722 PuppetDB response hanging on select-nodes subquery Change By: Kenneth Barber Affects Version/s: 2.1.0 Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1638) Puppet 3.4.2 broken in OpenBSD
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet 3.4.2 broken in OpenBSD
Jasper Lievisse Adriaanse: How do I view the patches made against a specific build of a BSD port? For example, pkg_add puppet is giving me Puppet 3.4.2, how do I grab the source + patches that produced that binary? The CSV history browser doesn't seem to support this use case very well.
Basically, I'm looking for the equivalent of apt-get source, yumdownloader --source, gem unpack, etc.
Add Comment
Puppet / PUP-1638
Puppet 3.4.2 broken in OpenBSD
When running puppet agent -t --debug --trace I get the following error: {quote} Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=/etc/puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}' Debug: Failed to load library 'shadow' f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send
Jira (PUP-2841) Have pupet client and master setup and communicationg.
Title: Message Title Gary created an issue Puppet / PUP-2841 Have pupet client and master setup and communicationg. Issue Type: Task Assignee: Unassigned Created: 25/Jun/14 10:20 AM Priority: Normal Reporter: Gary Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1638) Puppet 3.4.2 broken in OpenBSD
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Puppet 3.4.2 broken in OpenBSD
If you get Puppet 3.4.2 you're using OpenBSD 5.5 (release), right? If you upgrade to -current you'll have Puppet 3.6.2.
Anyways, CVSweb is indeed sub-optimal, or heck, cvs in general even...however if you checkout the `OPENBSD_5_5` tag, you'll have the sources that built the 3.4.2 package for OpenBSD 5.5. If you're tracking -current then you can omit checking out a specific tag and just look at the REVISION in the Makefile if that matches the 'pN' part of the package name.
Add Comment
Puppet / PUP-1638
Puppet 3.4.2 broken in OpenBSD
When running puppet agent -t --debug --trace I get the following error: {quote} Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=/etc/puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}' Debug: Failed to load library 'shadow' f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2841) Node not receiving a simple custom motd from master
Title: Message Title Gary updated an issue Puppet / PUP-2841 Node not receiving a simple custom motd from master Any help or documentation would be appreciated. Change By: Gary Priority: Normal Major Environment: Centos6.5StaticIPaddress.Hostfiledefined.SSLsuccessfullyattainedandsigned. Summary: Havepupetclientand Nodenotreceivingasimplecustommotdfrom master setupandcommunicationg. Ihaveclientandmaster.Theycommunicateandsslisworking.Iamtryingtotestoutasendofacustommotdinitially.Itisfailingwiththefollowing.=[snippet]Error:/Stage[main]/Main/Node[default]/File[motd]:Couldnotevauluate:Couldnotretrieveinformationfromenvironmentproductionsourcesfile:/files/motd=[snippet]CanyoupointmetoappthatIcanuseandcustomizetoyuminstallandapplicationandthenmodifytheconfigofthatapplication?Thanks.Shark Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2841) Node not receiving a simple custom motd from master
Title: Message Title
Gary updated an issue
Puppet / PUP-2841
Node not receiving a simple custom motd from master
Change By:
Gary
Ihaveclientandmaster.Theycommunicateandsslisworking.Iamtryingtotestoutasendofacustommotdinitially.Itisfailingwiththefollowing.=[snippet]Error:/Stage[main]/Main/Node[default]/File[motd]:Couldnotevauluate:Couldnotretrieveinformationfromenvironmentproductionsourcesfile:/files/motd=[snippet] site.ppnodedefault{file{'motd'path=/tmp/motd,ensure='file'source='/files/motd',}} CanyoupointmetoappthatIcanuseandcustomizetoyuminstallandapplicationandthenmodifytheconfigofthatapplication?Thanks.Shark
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2822) Description of disable_warnings setting is incomplete
Title: Message Title
Adrien Thebo commented on an issue
Re: Description of disable_warnings setting is incomplete
Merged in b3c6f5b.
Add Comment
Puppet / PUP-2822
Description of disable_warnings setting is incomplete
The description currently reads: {quote} A list of warning types to disable. Currently the only warning type that can be disabled are deprecations, but more warning types may be added later. {quote} This needs a clearly labeled list of keywords; right now, the user has to guess. It could also use some context about why you would want to do this.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2822) Description of disable_warnings setting is incomplete
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2822 Description of disable_warnings setting is incomplete Change By: Adrien Thebo Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-839) FFI Puppet::Util::Windows::Security module
Title: Message Title
Josh Cooper commented on an issue
Re: FFI Puppet::Util::Windows::Security module
This can be moved to resolved after clearing CI. Puppet acceptance master passed on 2003r2, 2008r2, and all 2012 with commit ae0161423a09c3aed5a5d02b69680ec4ad71d309 in https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Acceptance-Windows-master-vcloud-and-github/357/
Add Comment
Puppet / PUP-839
FFI Puppet::Util::Windows::Security module
Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. CreateFileW. Also don't do things like: {code} def supports_acl?(path) flags = 0.chr * 4 {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2663) Allow string to numeric conversion to start with + or -
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-2663 Allow string to numeric conversion to start with + or - Change By: Peter Huene Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Josh Cooper commented on an issue Re: Support pinning puppet-win32-ruby version for Puppet This can be moved to Resolved after CI passes. Commit ae0161423a09c3aed5a5d02b69680ec4ad71d309 passed in https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Acceptance-Windows-master-vcloud-and-github/357/ Add Comment Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Presently Windows acceptance tests simply clone the https://github.com/puppetlabs/puppet-win32-ruby from the local internal mirror without specifying a revision. As we start to build Ruby 2 x64 on Windows, we're going to need to pin different jobs at different Ruby architecture / patch / gemsets for the sake of acceptance. This is a stopgap solution... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-488) Change wire formats to include timestamp from producer side
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-488 Change wire formats to include timestamp from producer side Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title
Josh Cooper commented on an issue
Re: 'puppet module generate' create not compatible metadata.json with forge
This can be moved to Resolved after clearing CI. Created a module, published to the forge, verified the dependencies as displayed on the forge are listed as puppetlabs-stdlib (= 1.0.0)
Add Comment
Puppet / PUP-2781
'puppet module generate' create not compatible metadata.json with forge
When one generate module by puppet it automaticlly adds version_range instead of version_requirement which is required to publish module {code} dependencies: [ { name: puppetlabs-stdlib, version_range: = 1.0.0 } ] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Ethan Brown Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-335) Functions that require the future parser should be concretely identifiable
Title: Message Title Nicholas Fagerlund commented on an issue Re: Functions that require the future parser should be concretely identifiable After our conversations earlier this month, I'm fine with closing this as won't fix. Add Comment Puppet / PUP-335 Functions that require the future parser should be concretely identifiable Take a look at the function reference: http://docs.puppetlabs.com/references/3.latest/function.html There are a bunch of functions in there that will just plain explode on a stock Puppet 3.x install. (each, collect, etc.) This is because there’s no indication in these functions' code that they require the future parser. We need an indication of this ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2842) Limit platforms on which Gemfile tries to install ruby-prof
Title: Message Title Christopher Price created an issue Puppet / PUP-2842 Limit platforms on which Gemfile tries to install ruby-prof Issue Type: Bug Assignee: Christopher Price Created: 25/Jun/14 11:49 AM Priority: Normal Reporter: Christopher Price The ruby-prof gem is not applicable on all platforms (e.g., jruby). However, the Gemfile attempts to install it unconditionally. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
yeah, I was reading too quickly... there are defaults there... (sorry)
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
