Jira (PUP-918) Optionally include catalog compilation warnings with report
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-918 Optionally include catalog compilation warnings with report Change By: Owen Rodabaugh CS Priority: Minor Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-167) Query for deactivated nodes
Title: Message Title Nick Walker commented on PDB-167 Re: Query for deactivated nodes Seems like you could do report-timestamp node-ttl, however, I think all queries might remove deactivated nodes by default. https://docs.puppetlabs.com/puppetdb/2.3/api/query/v4/nodes.html https://docs.puppetlabs.com/puppetdb/latest/configure.html#node-ttl Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Owen Rodabaugh updated an issue Hiera / HI-46 Hiera should support alternate environments Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4665 Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname\}}}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4638) AIO Upgrade Module name mis-fits Puppet paradigm
Title: Message Title Eric Sorenson commented on PUP-4638 Re: AIO Upgrade Module name mis-fits Puppet paradigm It seems like the question is, is this code suitable (even if it apparently wasn't specifically intended) to be the basis for the future manage-puppet-agents-with-puppet module? We certainly need something like that, and there's been enough work in here that — Pre-AIO to AIO specific code aside — it makes a certain amount of sense to keep building on it towards that end rather than scrap it and start over. I also agree that the classify them, upgrade, then de-classify is not an ideal workflow, but it's not terrible, and IIRC it evolved from the workflow for the Catalog Preview module, on which we had widespread discussion and agreement. I haven't worked extensively with this module myself other than observing a demo, so I can't really speak to that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname\} _ }}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname\} _ #x007D; }}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4638) AIO Upgrade Module name mis-fits Puppet paradigm
Title: Message Title Kylo Ginsberg commented on PUP-4638 Re: AIO Upgrade Module name mis-fits Puppet paradigm I propose: we rename it to puppetlabs-puppet_agent don't change anything in the SG plans, i.e. the workflow for SG timeframe is still classify/apply/de-classify in the future this module can evolve into puppet managing puppet but none of that is planned out at this time Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname \} #x007D;}}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4638) AIO Upgrade Module name mis-fits Puppet paradigm
Title: Message Title Eric Sorenson commented on PUP-4638 Re: AIO Upgrade Module name mis-fits Puppet paradigm +1 to Kylo, makes sense. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
The hiera command does not understand anything about variables that are available when hiera is used from inside puppet. You must explicitly set them on the command line. (And do not use :: when doing so).
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-4479) Extend upgrade module to windows
Title: Message Title Michelle Johansen commented on PUP-4479 Re: Extend upgrade module to windows Thank you all! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title John Duarte commented on PDB-1300 Re: Make acceptance tests compatible with Puppet 4.0 Kenneth Barber, the embedded matrix looks good. I have added a PR to add a beaker options file for testing with postgres and puppetserver. Please feel free to review PR-1424 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4665 Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Change By: Henrik Lindberg Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4667) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4667
datadir in hiera.yaml not interpolating %{::environment}
Change By:
Henrik Lindberg
Hi,Usingtheenvironmentvariableorr10k_environmentfactinthedatadirfieldinhiera.yamldoesn'twork.{ quote code }$cat/etc/puppetlabs/code/hiera.yaml---:backends:-yaml:hierarchy:-nodes/%{::fqdn}-environment/%{::environment}-global:yaml::datadir:/etc/puppetlabs/code/hieradata/%{::environment}$hiera-aclasses-dDEBUG:2015-05-2821:02:54+:HieraYAMLbackendstartingDEBUG:2015-05-2821:02:54+:LookingupclassesinYAMLbackendDEBUG:2015-05-2821:02:54+:LookingfordatasourceglobalDEBUG:2015-05-2821:02:54+:Cannotfinddatafile/etc/puppetlabs/code/hieradata/global.yaml,skippingnil{ quote code }
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-376
datadir in hiera.yaml not interpolating %{::environment}
Change By:
Henrik Lindberg
Priority:
Critical Normal
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg assigned an issue to Sivakalyan Chintakana
Hiera / HI-376
datadir in hiera.yaml not interpolating %{::environment}
Change By:
Henrik Lindberg
Assignee:
SivakalyanChintakana
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-4530) FreeBSD specific Service provider fix
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4530 FreeBSD specific Service provider fix Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-69) CLI inventory service lookup doesn't work with Puppet 3
Title: Message Title Owen Rodabaugh updated an issue Hiera / HI-69 CLI inventory service lookup doesn't work with Puppet 3 Change By: Owen Rodabaugh CS Priority: Reviewed Normal Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Ben Ford updated an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Ben Ford Component/s: BreakingChange Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Ben Ford moved an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Ben Ford Key: ENTERPRISE PUP - 690 4668 Project: Puppet Enterprise Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4667) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana created an issue
Puppet / PUP-4667
datadir in hiera.yaml not interpolating %{::environment}
Issue Type:
Bug
Affects Versions:
PUP 4.1.0
Assignee:
Unassigned
Components:
Puppet Server
Created:
2015/05/28 2:05 PM
Environment:
CentOS 7 Openstack VM R10k 1.3.2
Fix Versions:
PUP 4.1.0
Priority:
Critical
Reporter:
Sivakalyan Chintakana
Hi,
Using the environment variable or r10k_environment fact in the datadir field in hiera.yaml doesn't work.
$ cat /etc/puppetlabs/code/hiera.yaml — :backends:
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Please try dropping the :: in front of the names - hiera only interpolates top scope variables anyway.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera.yaml to reflect current best practices and defaults
Title: Message Title Eric Sorenson updated an issue Hiera / HI-374 Update hiera.yaml to reflect current best practices and defaults Change By: Eric Sorenson Fix Version/s: HI3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4659) environment_scenario test failures when master has agent role
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-4659 environment_scenario test failures when master has agent role Change By: Josh Cooper Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-167) Query for deactivated nodes
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-167 Query for deactivated nodes Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1550) PR (1422): (maint) don't activate the node when it's already active - wkalt
Title: Message Title gepetto-bot commented on PDB-1550 Re: PR (1422): (maint) don't activate the node when it's already active - wkalt ajroetker commented: :+1: Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Removed the :: in front of environment variable and restarted puppet server. Same issue persists.
$ cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{::fqdn}
- environment/%{::environment}
- global
:yaml:
:datadir: /etc/puppetlabs/code/hieradata/%{environment}
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices( no'global', just a {{certname/%{certname}}} ' node' and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot , ' then{{/code/environments/%{ environment ' }/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint , butwithoutanyrealdownside)triggersanothersemvermajor and 'common' thereforewillbereleasedasHiera3.0.0. ---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Kylo Ginsberg Fix Version/s: PUP3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera.yaml to reflect current best practices and defaults
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera.yaml to reflect current best practices and defaults Rob Reynolds Are you saying that these defaults are wrong? https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36 They are at least what is stated in the documentation. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg moved an issue
Hiera / HI-376
datadir in hiera.yaml not interpolating %{::environment}
Change By:
Henrik Lindberg
Fix Version/s:
PUP4.1.0
Component/s:
PuppetServer
Affects Version/s:
PUP4.1.0
Key:
PUP HI - 4667 376
Project:
Puppet Hiera
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Sorenson Summary: Updatehiera .yaml defaults toreflectcurrentbestpractices anddefaults Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Sorenson *Updatedtoreflectactionplan*The hiera.yaml config thathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation. Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(no'global',justa'node','environment',and'common' ---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{ { certname/%{certname} }} and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then {{ /code/environments/%{environment}/hieradata }} This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Rob Reynolds updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Rob Reynolds
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname\}}}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Rob Reynolds updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Rob Reynolds
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%\{certname\}}}and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%\{environment\}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-69) CLI inventory service lookup doesn't work with Puppet 3
Title: Message Title Owen Rodabaugh updated an issue Hiera / HI-69 CLI inventory service lookup doesn't work with Puppet 3 Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-129) Make puppet node clean --unexport work with PuppetDB
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-129 Make puppet node clean --unexport work with PuppetDB Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1555) PR (182): (maint) Allow database_validation to be false - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1555 PR (182): (maint) Allow database_validation to be false - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/05/28 1:48 PM Labels: github module Priority: Normal Reporter: gepetto-bot (maint) Allow database_validation to be false Author: Andrew Roetker Company: Puppet Labs Github ID: ajroetker Pull Request 182 Discussion Pull Request 182 File Diff Pull Request Description This commit fixes a bug where if a user tried to turn off database validation there would be a `before` statement requiring an absent validation resource.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Henrik Lindberg commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
oh, this is via the hiera command - does it work when used with puppet? i.e. in a puppet manifest?
Suspect you have to provide all the variables that should be set, or get them as stored facts for a node - which is broken in some versions of hiera/puppet. (The hiera command line app is not the greates).
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{{certname/%{certname}}} ' and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then{{/code/environments/%{environment}/hieradata}}This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updatedtoreflectactionplan*Theconfigthathierashipswithisprettyout-of-dateandhasn'tbeenupdatedtoreflectthewaymosthieradeploymentswork.Weshouldupdatethistoeliminatesetupfrictionsothatitworksimmediatelyafterinstallation.Therearetwopartstothechange:1.updatethedefaulthierarchyinhiera.yamltoincorporatecurrentbestpractices(just{ { certname/% \ {certname \ } }} and{{common}}levels.2.updatethehelpermethodsin[Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36]toreflecttheAIOpathingchangesthatpointtotheOS-specificroot,then {{ /code/environments/% \ {environment \ }/hieradata }} This(somewhatunfortunatelyfromatimingstandpoint,butwithoutanyrealdownside)triggersanothersemvermajorandthereforewillbereleasedasHiera3.0.0.---*Originaldescription*Presently,hieraisnotconfiguredtoworkoutoftheboxwithpuppetforseveralreasons:-hierashouldbemaintainedasastandaloneproject-hierarequiresaconfigfiletobeinplacetostart-weincludetheconfigfilefromthehieraprojectinthepuppetpackageLeadingtothefollowingunfortunateresults:-theconfigfileusedbyhieraafterthepuppetpackageisinstalledisnotusefulforconfiguringpuppet,requiringupfronteffortfromusers(peorfoss).ThisalsobecomesaCSburden.-persistenceofhiera.yamlcustomizationiscomplicatedbyoverwritesofhiera.yamlonpackageinstallationApotentialtwopartsolutionwouldsolvetheproblemsabove:-[~josh]proposedamodificationtohieratoallowittorunwithoutaconfigfile.-wecouldpackageausablehiera.yaml.examplefilethatcouldserveasarealworldexampleforhiera-onlyusersandaspringboardforusersofhierawithpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-967) Add AIX operating_system_resolver.cc
Title: Message Title William Hopper commented on FACT-967 Re: Add AIX operating_system_resolver.cc From UX feedback, it sounds like we want to preserve the base level, technology level, and service pack number. I've spent some time digging through oslevel to determine how these are generated. What I've found is that oslevel uses the AIX fix database to identify the ML (maintenance level) information. It is found in: /tmp/.oslevel.datafiles/.oslevel.rml.cache. As far as I know, we can expect this file to always be in place (as long as oslevel has been run on the system at some point in its life). However, the oslevel script itself sometimes does rebuild the cache. Option 1: I believe it would be safe for us to parse /tmp/.oslevel.datafiles/.oslevel.rml.cache ourselves the same way oslevel does, but we should probably be prepared to fall back to calling oslevel if the cache doesn't exist. The cache would then be regenerated during that Facter run. Also, some digging around on the net tells me that /tmp is not typically cleared in AIX, except during OS upgrades. Thus, the cache would not be blown away upon reboots. Via shell, we can acquire the correct line by doing: cat oslevel.rml.cache| grep 'Service Pack' | sort -n -r -t . | uniq | head -n1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Henrik Lindberg I haven't used it in a manifest yet. However, I use it in the hierarchy and works fine when I have the full path in the :datadir.
$ cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{::fqdn}
- environment/%{::environment}
- global
:yaml:
Jira (PDB-1548) PR (1420): (maint) Cleanup benchmarking tool clojure syntax - ajroetker
Title: Message Title gepetto-bot commented on PDB-1548 Re: PR (1420): (maint) Cleanup benchmarking tool clojure syntax - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1325/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Kylo Ginsberg commented on PUP-2728 Re: zypper should always be the default package provider for Suse osfamily Closing this. On review, this PR couldn't be merged to 3.x because it would be a breaking change for rug users. Note the fix is still available in puppet 4. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1537) Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1537 Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1537) Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1537 Add redirect from `/` to `/pdb/dashboard/index.html` if PuppetDB is alone in JVM Change By: Wyatt Alt Sprint: PuppetDB2015-06- 17 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera.yaml to reflect current best practices and defaults
Title: Message Title Rob Reynolds commented on HI-374 Re: Update hiera.yaml to reflect current best practices and defaults There is possibly a longer term solution that Josh mentioned, but I think making that simple change in the code base to change the default location will meet the need for most folks who use hiera. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4482) Add support for PE platforms/repos/paths
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-4482 Add support for PE platforms/repos/paths Change By: Michelle Johansen Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4479) Extend upgrade module to windows
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-4479 Extend upgrade module to windows Change By: Michelle Johansen Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Preben Ingvaldsen created an issue Puppet / PUP-4665 Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Issue Type: Bug Affects Versions: PUP 4.1.0, PUP 3.8.1 Assignee: Preben Ingvaldsen Created: 2015/05/28 11:57 AM Fix Versions: PUP 3.8.2 Priority: Normal Reporter: Preben Ingvaldsen Recently, SERVER-556 was filed against Puppet Server. After some investigation, it seems that when an error is thrown in Puppet's template function, Ruby will call inspect on the top-level scope object, but not use the returned string. However, since the Puppet::Parser::Scope class has no inspect method of its own, inspecting the scope object causes an absolutely massive string to be produced and never used. The more code the user has in their environment, the larger the string. This string can grow so large that it can cause an OOM error when running Puppet Server due to the restrictions placed on the heap size. We need to add an inspect method to the Puppet::Parser::Scope class that returns something simple to avoid this.
Jira (PUP-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Erik Dasher updated an issue Puppet / PUP-4665 Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Change By: Erik Dasher QA Risk Severity: High QA Risk Probability: High QA Risk Assessment: High QA Contact: ErikDasher QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PUP-4479) Extend upgrade module to windows
Title: Message Title Michelle Johansen commented on PUP-4479 Re: Extend upgrade module to windows Alexander Johnson and Heidi Pio Is anyone available from the Windows team to assist with this? We are looking for near term support to help complete the module for the handoff to PE. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4666) build_ignore_module_file fails if '/tmp/test' already exists
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-4666 build_ignore_module_file fails if '/tmp/test' already exists Change By: Jeremy Barlow Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4666) build_ignore_module_file fails if '/tmp/test' already exists
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-4666 build_ignore_module_file fails if '/tmp/test' already exists Issue Type: Bug Assignee: Jeremy Barlow Created: 2015/05/28 12:39 PM Priority: Normal Reporter: Jeremy Barlow In the Puppet Server acceptance test pipeline, we've seen the build_ignore_module_file_test Puppet acceptance test fail if a directory named /tmp/test exists when the test is run. The test expects to be able to create a directory with that name and so fails when it is pre-existing. I'm not exactly sure what it is during the job execution which creates that directory. I think it would be safer, though, if the test just created its own unique tmpdir on the master rather than relying upon a hard-coded one. Add Comment This message was
Jira (PUP-4664) The output of {{puppet describe ssh_authorized_key}} is not valid
Title: Message Title
Johnson Earls created an issue
Puppet / PUP-4664
The output of {{puppet describe ssh_authorized_key}} is not valid
Issue Type:
Bug
Affects Versions:
PUP 4.0.0, PUP 3.8.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2015/05/28 10:27 AM
Priority:
Normal
Reporter:
Johnson Earls
The output from puppet describe ssh_authorized_key is messed up:
$ puppet describe ssh_authorized_key -s | head -30
Jira (PUP-2400) Add acceptance tests for mount type
Title: Message Title John Duarte commented on PUP-2400 Re: Add acceptance tests for mount type Michael Smith, this is due to the loop kernel module not being loaded on this platform. I will submit a PR to make sure this step is added in the tests. cc: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2400 Add acceptance tests for mount type Change By: John Duarte Assignee: JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2400 Add acceptance tests for mount type Change By: Kurt Wall Assignee: EricThompson KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1551) PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker
Title: Message Title gepetto-bot commented on PDB-1551 Re: PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1321/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2400 Add acceptance tests for mount type Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4479) Extend upgrade module to windows
Title: Message Title Alexander Johnson commented on PUP-4479 Re: Extend upgrade module to windows Travis Fields Is going to take a look at this. We'll get back with plans. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1551) PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker
Title: Message Title gepetto-bot commented on PDB-1551 Re: PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker wkalt commented: +1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Yeah agreed that managing stringify_facts in this module is too late. It's one of the prerequisites for this module. Managing that setting could be done in a variety of ways, e.g. the inifile module, etc, and there may be demand for improving that experience, but that's a different topic than this epic for this module. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Archana Sridhar commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Preben Ingvaldsen- it looks like the soonest release will be 3.8.1 slated for June 15th ish- and in order to make that we need to be ready by end of this week? Confirming with Michael Stahnke. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2400 Add acceptance tests for mount type Change By: Eric Thompson Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2400 Add acceptance tests for mount type Change By: Eric Thompson Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields commented on PUP-4479 Re: Extend upgrade module to windows Rob Reynolds what service pack did powershell get included into 2003 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4479) Extend upgrade module to windows
Title: Message Title Rob Reynolds commented on PUP-4479 Re: Extend upgrade module to windows I believe you are required to upgrade to Service Pack 2, and then install it manually. Not sure and would need to verify that. It's installed by default on all of the other systems we support. Anything we create would need to be POSH v2 compatible, because that is what you can get back there and what is default on Win 7/2008/2008 R2. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1550) PR (1422): (maint) don't activate the node when it's already active - wkalt
Title: Message Title gepetto-bot commented on PDB-1550 Re: PR (1422): (maint) don't activate the node when it's already active - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1323/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2400) Add acceptance tests for mount type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2400 Add acceptance tests for mount type Change By: Eric Thompson Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Archana Sridhar commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced sorry I take that back. the 3.8.1 I referred to is for PE and we need PUP3.8.2. will continue to track for PUP 3.8.2 and check on the dates for that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-982) Warnings about not being able to resolve custom facts with --no-custom-facts
Title: Message Title Kurt Wall updated an issue Facter / FACT-982 Warnings about not being able to resolve custom facts with --no-custom-facts Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-982) Warnings about not being able to resolve custom facts with --no-custom-facts
Title: Message Title Kurt Wall updated an issue Facter / FACT-982 Warnings about not being able to resolve custom facts with --no-custom-facts Change By: Kurt Wall QA Risk Assessment Reason: Justawarning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-982) Warnings about not being able to resolve custom facts with --no-custom-facts
Title: Message Title Kurt Wall updated an issue Facter / FACT-982 Warnings about not being able to resolve custom facts with --no-custom-facts Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Eric Thompson QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4431) Service with 'hasstatus = false' fails
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4431 Service with 'hasstatus = false' fails Change By: Eric Thompson QA Highest Test Level Reason: notestchangeinthePR QA Risk Severity: Medium QA Risk Probability: Low QA Risk Assessment: Medium QA Risk Probability Reason: mosthavestatuscommand QA Highest Test Level: Unit QA Status: Reviewed Add Comment
Jira (PUP-4534) Specify EPP templating language
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4534 Specify EPP templating language Change By: Nicholas Fagerlund Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4668
cannot create a define named something that starts with 'class'
Change By:
Henrik Lindberg
{code}[master/etc/puppetlabs/puppet/modules/classroom]#catmanifests/boo.ppdefineclassroom::boo{notify{$name:}}[master/etc/puppetlabs/puppet/modules/classroom]#cattests/wtf.ppclassroom::boo{'whatthe':}notify{'test':require=Classroom::Boo['whatthe'],}[master/etc/puppetlabs/puppet/modules/classroom]#puppetapplytests/wtf.ppNotice:Compiledcatalogformaster.puppetlabs.vminenvironmentproductionin0.47secondsError:CouldnotfinddependencyClass[Whatthe]forNotify[test]at/etc/puppetlabs/puppet/modules/classroom/tests/wtf.pp:3{code} WORDAROUNDEXISTS---Thiscanbeworkedaroundbygivingthereferenceasastringinsteadofasatype:{code:puppet}requireClassroom[whatthe]{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title John Duarte commented on PDB-1300 Re: Make acceptance tests compatible with Puppet 4.0 Kenneth Barber, I have amended PR-1424 to consolidate the beaker options files to include conditionals for AIO as per your suggestion. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4665) Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced
Title: Message Title Kenn Hussey commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Michael Stahnke if PE 3.8.1 is picking up PUP 3.8.2, I need to change the filter for the board to include PUP 3.8.2. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1551) PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker
Title: Message Title gepetto-bot commented on PDB-1551 Re: PR (1423): (maint) Remove `paged_results.*` wrapper around generated sql - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1329/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4653) The filebucket client uses v1 API URLs internally
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4653 The filebucket client uses v1 API URLs internally Change By: Kylo Ginsberg Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Kylo Ginsberg Fix Version/s: PUP4.2.0 Fix Version/s: PUP4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kurt Wall QA Risk Severity: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Henrik Lindberg commented on PUP-4668 Re: cannot create a define named something that starts with 'class' PR available Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Ben Ford updated an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Ben Ford Labels: future-parser Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf Change By: Kurt Wall QA Risk Assessment Reason: N/Aforaddingspectests Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-4638 Rename module to puppetlabs-puppet_agent Change By: Kylo Ginsberg Assignee: KyloGinsberg Sprint: Client2015-06-10 Scrum Team: ClientPlatform Story Points: 1 Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-4668) cannot create a define named something that starts with 'class'
Title: Message Title Henrik Lindberg commented on PUP-4668 Re: cannot create a define named something that starts with 'class' The problem is in runtime3_converter.rb on line 143: 143 if type_name =~ /^(::)?[Cc]lass/ since this regexp will find a class anywhere in the word except since it is not anchored with a $ at the end. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4668) cannot create a define named something that starts with 'class'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4668 cannot create a define named something that starts with 'class' Change By: Henrik Lindberg Fix Version/s: PUP3.8.2 Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4638) Rename module to puppetlabs-puppet_agent
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4638 Rename module to puppetlabs-puppet_agent Change By: Kylo Ginsberg Summary: AIOUpgradeModulenamemis Renamemoduletopuppetlabs - fitsPuppetparadigm puppet_agent Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1556) PR (1425): (maint) Remove unneccesary querying macro to improve streaming syntax - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1556 PR (1425): (maint) Remove unneccesary querying macro to improve streaming syntax - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/05/28 4:33 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Remove unneccesary querying macro to improve streaming syntax Author: Andrew Roetker Company: Puppet Labs Github ID: ajroetker Pull Request 1425 Discussion Pull Request 1425 File Diff Pull Request Description This commit removes the `with-query-results-cursor` macro, as it was functionally unused. The macro wrapped `with-query-results-cursor*` with a different interface, but the only thing that used the macro was
Jira (PUP-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kurt Wall QA Risk Assessment Reason: Mostlyanuisance,kindacornercase,butweneedseamlessinteropbetweenWindowsandLinux Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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.
