Jira (PUP-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4698
Make fqdn_rand() Return A Numeric Instead of a String
Change By:
Henrik Lindberg
Whiletestingthefollowingsnippetofcodewiththepuppet4parseritwouldfailunexpectedlyononlyafewnodes.{code}$cron_minute=fqdn_rand(60)if($cron_minute='60'){fail(Variablecron_minuteinmoduleconnection_watcheris=60.Valuesmustbe60.Thecron_minutevalueis$cron_minute.)}{code}Uponfurtherresearch,Ifiguredtheissuewasbecauseofthecomparisonoftwostringsnotworkingthesamewasastwointegerswould.So,changingovertonumericforthecomparisonresolvestheissue.{code}$cron_minute=0+fqdn_rand(60)#changeastringtoanumerictypeif($cron_minute=60){fail(Variablecron_minuteinmoduleconnection_watcheris=60.Valuesmustbe60.Thecron_minutevalueis$cron_minute.)}{code}Itturnsouttheissuewiththeoriginalcodeonlyshowsupwiththevalues 6, ' 7 ' , ' 8 ' ,and ' 9 ' becausethecomparison only compares lexiographicallyandmakesadecisionon thefirsttwovalues ofthestringifthey since'7','8'and'9' are ofunequallengths '6'(thefirstcharacterin'60') .Attheendofthedayitseemsthatfqdn_randshouldjustreturnanumericasitwillalwaysbeanumberandisonlyastringforhistoricalreasons.
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
Jira (PUP-4356) Remove undocumented puppetversion key functionality in module metadata
Title: Message Title Anderson Mills commented on PUP-4356 Re: Remove undocumented puppetversion key functionality in module metadata Steve Barlow This ticket is being worked on PF-230. That ticket is in the current sprint, and is only waiting for CI to go green. 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-1591) state-overview includes deactivated nodes
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1591 state-overview includes deactivated nodes Change By: Wyatt Alt Sprint: PuppetDB2015-06-17 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-1591) state-overview includes deactivated nodes
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1591 state-overview includes deactivated nodes Change By: Wyatt Alt 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-4478) Extend upgrade module to deb platforms
Title: Message Title Justin Stoller commented on PUP-4478 Re: Extend upgrade module to deb platforms Thanks for the heads up! 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-1594) PR (1440): DO NOT MERGE - mullr
Title: Message Title gepetto-bot commented on PDB-1594 Re: PR (1440): DO NOT MERGE - mullr 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/1395/ 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-3088) Debug logging messages can't be used by providers with a path method
Title: Message Title Hunter Haugen commented on PUP-3088 Re: Debug logging messages can't be used by providers with a path method This is primarily a concern in providers, where path/file/tags may be properties and thus get eponymous getter methods. https://github.com/puppetlabs/puppet/pull/4000 should handle 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 (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC root@puppetapply:~# /opt/puppetlabs/bin/puppet config print config /etc/puppetlabs/puppet/puppet.conf root@puppetapply:~# mv /etc/puppet/puppet.conf /etc/puppetlabs/puppet/puppet.conf root@puppetapply:~# /opt/puppetlabs/bin/puppet config print modulepath /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules root@puppetapply:~# mv /etc/puppet/modules/helloworld /etc/puppetlabs/code/modules/ root@puppetapply:~# /opt/puppetlabs/bin/puppet apply -- --debug--help --verbose --version root@puppetapply:~# /opt/puppetlabs/bin/puppet apply test.pp
Jira (PUP-4478) Extend upgrade module to deb platforms
Title: Message Title Michael Smith commented on PUP-4478 Re: Extend upgrade module to deb platforms They should all be setup with EL7 masters, and testing OS agent/default. We can look at re-enabling the other RPM platforms with EL7 masters as well. 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-4700) make color output work for all users
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4700 make color output work for all users Issue Type: Improvement Assignee: Unassigned Created: 2015/06/04 5:19 PM Priority: Normal Reporter: Henrik Lindberg At one point there was no color, then messages were colored based on severity (error = red, warning = yellow, etc.). Some of the colors where not good for all users, and warning messages were made red. Then in PUP-4632 error messages were again switched back to being yellow. See PUP-4632 for what happens when yellow text appears on a bright background. (Yeah, you cannot read the text at all). We should cater to different user needs; some have issues with red/green, others (like me) have difficulty reading certain colors on a black background and prefer a bright background. And we all have a difference sense of what is easy to read and what looks aesthetically pleasing. The issue is made worse by not being consistent across commands and subprojects. In PUP-4632 there are several suggestions how to deal with this issue + other alternatives: Find colors that work on both dark/bright background (e.g. a darker/golden yellow)
Jira (PUP-4700) make color output work for all users
Title: Message Title Henrik Lindberg commented on PUP-4700 Re: make color output work for all users --color=off seems like a MVP 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-4632) puppet agent shows warning messages in red
Title: Message Title Henrik Lindberg commented on PUP-4632 Re: puppet agent shows warning messages in red I created PUP-4700 for the follow up to fix colors so they work for 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 (PUP-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Henrik Lindberg commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String with 2 replies so far, the input is that it is ok to change. This led me to look into the code. The fqdn_rand is implemented in terms of calling a unitl finction def deterministic_rand(seed,max), and this util function does to_s on the result. In order not to break 3d party code relying on this, a second deterministic_rand_int method is needed. We seem to use a securerandom gem for this if it is available. Is it ever not available? The built in Ruby srand/rand produces quite different results (esp. when given a floating point max value (which btw is not supported by fqdn_rand). 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-4478) Extend upgrade module to deb platforms
Title: Message Title Michael Smith commented on PUP-4478 Re: Extend upgrade module to deb platforms Justin Stoller once this ticket goes in, we'll want to enable Debian 6 and 7, and Ubuntu 12.04, 14.04, and 14.10 testing on Jenkins. 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-4697) Puppet service provider for SuSE should default to systemd except for version 11
Title: Message Title
Robert Munteanu created an issue
Puppet / PUP-4697
Puppet service provider for SuSE should default to systemd except for version 11
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Created:
2015/06/04 2:19 PM
Priority:
Major
Reporter:
Robert Munteanu
This is based on an issue report in the openSUSE bugzilla : Puppet is unable to manage services since it does not use systemd for Tumbleweed.
When trying to enable a service on openSUSE Tumbleweed I get an error
$ sudo puppet apply -e 'service {apache2 : enable = true }'
/usr/lib64/ruby/gems/2.2.0/gems/puppet-3.7.5/lib/puppet/defaults.rb:488: warning: duplicated key at line 489 ignored: :queue_type
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Henrik Lindberg commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC I can't say immediately what is going on here. Need to recreate and do some debugging. 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-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Owen Rodabaugh commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String Some discussions we had on this see this is as a bug we should fix rather than a new feature. While the change to comparison is documented this specific function is now returning the wrong type. It may be worth checking with puppet-dev to get their thoughts on breaking change vs bug-fix. Risks we see with not changing this until Puppet 5: 1. Code compiles under the future parser but does a lexicographical comparison, meaning successful compilation but unexpected result. 2. A risk(seen with a customer) is that their comparison with an unquoted comparator cause a compilation failure and then to solve it they quote the comparator leading to item 1 It seems preferable to fix the function to output as a number and the compilation fails, which at least indicates there is a problem 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-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4698 Make fqdn_rand() Return A Numeric Instead of a String Change By: Owen Rodabaugh CS Priority: NeedsPriority 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 (PUP-4479) Extend upgrade module to windows
Title: Message Title Michelle Johansen commented on PUP-4479 Re: Extend upgrade module to windows CC Aaron Armstrong and Rajasree Talla for tracking and time/sprint change. 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-1593) PR (1439): (maint) Fix object exists query - mullr
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1593 PR (1439): (maint) Fix object exists query - mullr Change By: Russell Mull Scope Change Category: Found 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-1594) PR (1440): DO NOT MERGE - mullr
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1594 PR (1440): DO NOT MERGE - mullr Issue Type: Task Assignee: Unassigned Created: 2015/06/04 4:23 PM Labels: github Priority: Normal Reporter: gepetto-bot DO NOT MERGE Author: Russell Mull Company: Github ID: mullr Pull Request 1440 Discussion Pull Request 1440 File Diff Pull Request Description this is a ticket for testing our ci infrastructure. please don't merge it. (webhooks-id: 0e29cae15225dbe591ba0e7f5e74174f)
Jira (PUP-4699) puppet_agent produces a syntax error when puppet.conf does not containe [master] section
Title: Message Title John Duarte created an issue Puppet / PUP-4699 puppet_agent produces a syntax error when puppet.conf does not containe [master] section Issue Type: Bug Assignee: Unassigned Created: 2015/06/04 4:40 PM Priority: Normal Reporter: John Duarte When the puppet master's puppet.conf file does not contain a `[master]` section, applying the `puppet_agent` module results in the following error. Error: Syntax error at '['; expected ']' at /etc/puppet/environments/production/modules/puppet_agent/manifests/prepare.pp:33 on node Add Comment
Jira (PDB-1595) query service does not filter deactivated nodes
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1595 query service does not filter deactivated nodes Issue Type: Bug Assignee: Unassigned Created: 2015/06/04 4:52 PM Priority: Normal Reporter: Wyatt Alt For instance, hitting the nodes endpoint over http will cut out all deactivated stuff by default. Executing the same query through the query service will not. This was causing some strange behavior in state-overview (fixed by PDB-1591), and is probably doing strange stuff wherever else we're using the service (nowhere AFAIK.) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1592) retire support for postgres 9.3
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1592 retire support for postgres 9.3 Change By: Wyatt Alt 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 (PDB-1592) retire support for postgres 9.3
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1592 retire support for postgres 9.3 Change By: Wyatt Alt Sprint: PuppetDB2015-06-17 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 So per conversation thread, 2003SP2 is oldest version to support and we are requiring the user to have PowerShell installed, as there are server core installs that do not come with PowerShell installed by default. 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-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title
Spencer Krum updated an issue
Puppet / PUP-4694
Puppet apply doesn't read manifest when using ENC
Change By:
Spencer Krum
Thisisprettysimilarbehaviourtohttps://tickets.puppetlabs.com/browse/PUP-3258soitmightjustbethatagain.Situation:Anencdefinesclassesandasite.pporpuppetapplyfoo.ppdefinesmorepuppetthings.Intheexamplecasenotifyresourcesareusedbutinproductionresourcedefaultsareset.Fromhttps://docs.puppetlabs.com/guides/external_nodes.htmlIexpecttogetallresourcesdefinedbytheENCandinfoo.ppbutwhatIactuallygetisonlyresourcesfromtheENC.Thesetup:{code}root@puppetapply:~# ruby--versionruby1.9.3p484(2013-11-22revision43786)[x86_64-linux]root@puppetapply:~# cat/etc/puppet/puppet.conf[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppetfactpath=$vardir/lib/facternode_terminus=execexternal_nodes=/usr/local/bin/puppet_node_classifier[master]#Theseareneededwhenthepuppetmasterisrunbypassenger#andcansafelyberemovedifwebrickisused.ssl_client_header=SSL_CLIENT_S_DNssl_client_verify_header=SSL_CLIENT_VERIFY{code}{code}root@puppetapply:~#cat/usr/local/bin/puppet_node_classifier#!/bin/bashcat/root/foo.yaml{code}{code}root@puppetapply:~#catfoo.yaml---classes:-helloworld#environment:devel{code}{code}root@puppetapply:~#cattest.ppnotify{derp:}nodedefault{}{code}{code}root@puppetapply:~#cat/etc/puppet/modules/helloworld/manifests/init.ppclasshelloworld{notify{SUPNERDS:}}{code}Thecorrectbehaviourisseenon3.4:{code}root@puppetapply:~#puppet--version3.4.3root@puppetapply:~#puppetapplytest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsWarning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.Notice:derpNotice:/Stage[main]/Main/Notify[derp]/message:defined'message'as'derp'Notice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.20seconds{code}Butanincorrectbehaviourisseenin3.8.1:{code}root@puppetapply:~#puppetapply--environment=develtest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsNotice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.11secondsroot@puppetapply:~#puppet--version3.8.1{code}
Add Comment
Jira (PUP-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Henrik Lindberg commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String At a minimum this should be mentioned in documentation (but where)? ping Nicholas Fagerlund 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-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4698 Make fqdn_rand() Return A Numeric Instead of a String Targeting puppet 5.0.0 since this is an API breaking change for 4.x. Change By: Henrik Lindberg Scrum Team: Language Story Points: 1 Fix Version/s: PUP5.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
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Henrik Lindberg commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC this seems related to PUP-3341 which will be fixed in puppet 4.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-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-2958 Rapid-fire puppet runs cause race condition with SSL data Change By: Owen Rodabaugh CS Priority: NeedsPriority 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-1627) Puppet agent's locking is subject to race conditions
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1627 Puppet agent's locking is subject to race conditions Change By: Owen Rodabaugh CS Priority: NeedsPriority 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 (PDB-1593) PR (1439): (maint) Fix object exists query - mullr
Title: Message Title gepetto-bot commented on PDB-1593 Re: PR (1439): (maint) Fix object exists query - mullr wkalt commented: @mullr might be worth adding a test somewhere for this behavior 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-1021) Custom facts that require 'facter' cannot be evaluated from command line facter
Title: Message Title Shaigy Nixon commented on FACT-1021 Re: Custom facts that require 'facter' cannot be evaluated from command line facter Validated on redhat-7-x86_64, win2012r2-rubyx64 and ubuntu-1404-x86_64 with puppet-agent build SHA 473b953a4f1ff9504f7541dec4b2f008f8c4838c http://builds.puppetlabs.lan/puppet-agent/473b953a4f1ff9504f7541dec4b2f008f8c4838c/ root@asxwtzqcadayryf ~]# cat foo/foo.rb require 'facter' Facter.add(:foo) do setcode do 'bar' end end [root@asxwtzqcadayryf ~]# facter --custom-dir ./foo foo
Jira (PUP-4356) Remove undocumented puppetversion key functionality in module metadata
Title: Message Title Steve Barlow commented on PUP-4356 Re: Remove undocumented puppetversion key functionality in module metadata Reading the comments, it seems like this ticket is being actively worked, and it is targeted at PUP 4.2.0, but it is not in an active sprint. Are we expecting this to be done and in PUP 4.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-4695) add acceptance testing calling all hiera functions from ERB templates
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4695 add acceptance testing calling all hiera functions from ERB templates Change By: Eric Thompson Sprint: AM Language 2015-06- 17 24 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-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title
Nick Walker created an issue
Puppet / PUP-4698
Make fqdn_rand() Return A Numeric Instead of a String
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/06/04 2:25 PM
Labels:
tcse
Priority:
Normal
Reporter:
Nick Walker
While testing the following snippet of code with the puppet 4 parser it would fail unexpectedly on only a few nodes.
$cron_minute = fqdn_rand( 60 )
if ($cron_minute = '60') {
fail (Variable cron_minute in module connection_watcher is = 60. Values must be 60. The cron_minute value is $cron_minute.)
Jira (PDB-1590) We need to support the old command versions for wireformats for upgrade purposes
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-1590 We need to support the old command versions for wireformats for upgrade purposes Change By: Ryan Senior Assignee: RyanSenior 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-1593) PR (1439): (maint) Fix object exists query - mullr
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1593 PR (1439): (maint) Fix object exists query - mullr Issue Type: Task Assignee: Unassigned Created: 2015/06/04 3:48 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Fix object exists query Author: Russell Mull Company: Github ID: mullr Pull Request 1439 Discussion Pull Request 1439 File Diff Pull Request Description The object exists query must return data even for nodes which are expired or deactivated, since the subresources it filters on are directly addressable from a search which includes deactivated and expired nodes.
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC Whats the best way to get a nightly version of 4.2? Just for testing. 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-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Henrik Lindberg commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html?_ga=1.3709938.391883926.1430771021#using-the-nightly-repos http://nightlies.puppetlabs.com/?_ga=1.3709938.391883926.1430771021 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 commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced This is stuck in Ready for CI for some time now because the ticket is on the Puppet Server board. Moving it along. 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-1592) retire support for postgres 9.3
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1592 retire support for postgres 9.3 Issue Type: Improvement Assignee: Unassigned Created: 2015/06/04 1:56 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Wyatt Alt Shallow gravy will be running 9.4, and Amazon RDS has also extended support for 9.4. This means PuppetDB should drop support for 9.3. Add Comment This message was sent by
Jira (PDB-1593) PR (1439): (maint) Fix object exists query - mullr
Title: Message Title gepetto-bot commented on PDB-1593 Re: PR (1439): (maint) Fix object exists query - mullr wkalt commented: otherwise I'm +1 though. extensions is blocking on this. 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-1593) PR (1439): (maint) Fix object exists query - mullr
Title: Message Title gepetto-bot commented on PDB-1593 Re: PR (1439): (maint) Fix object exists query - mullr 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/1392/ 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-1529) PuppetDB accepts newlines in resource titles but not relationship titles
Title: Message Title Wyatt Alt assigned an issue to Russell Mull PuppetDB / PDB-1529 PuppetDB accepts newlines in resource titles but not relationship titles Change By: Wyatt Alt Status: Resolved Closed 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-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Henrik Lindberg commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String I posted a question to puppet-dev list. 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 QA Puppet / PUP-4665 Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Change By: Henrik Lindberg Status: Readyfor Review Test 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-1592) retire support for postgres 9.3
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1592 retire support for postgres 9.3 Change By: Wyatt Alt Sprint: PuppetDB2015- 07 06 - 01 17 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-1592) retire support for postgres 9.3
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1592 retire support for postgres 9.3 Change By: Wyatt Alt Sprint: PuppetDB2015- 06 07 - 17 01 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-1591) state-overview includes deactivated nodes
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1591 state-overview includes deactivated nodes Issue Type: Bug Assignee: Unassigned Created: 2015/06/04 10:40 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Wyatt Alt we should make it not so Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4356) Remove undocumented puppetversion key functionality in module metadata
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4356 Remove undocumented puppetversion key functionality in module metadata Change By: Anderson Mills The[validate_puppet_version](https://github.com/puppetlabs/puppet/blob/04a60fbff5dbc0d2a5818c671cecc20032b0fae7/lib/puppet/module.rb#L286)methodinthePuppet::Moduleclasswilllookfor`puppetversion`inamodule'smetadata.Itwillcomparethatstring(cannotspecifyarrayorrange)againsttherunningPuppetversionandfailtoinstallthemoduleiftherunningversionandtheexpressedpuppetversiondon'tmatch.We'llneedtoremovethisfunctionality.Thisticketisthepublicreferencetothisbehavior. EDIT:Welefttheaccessorandfunctionsassociatedsoasnottomakeabreakingchange.Thisisonlymakingthecheckneverfailfornow. 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-1025) improve unit testing of using custom facts in custom facts from different files
Title: Message Title Eric Thompson created an issue Facter / FACT-1025 improve unit testing of using custom facts in custom facts from different files Issue Type: Task Assignee: Unassigned Created: 2015/06/04 10:04 AM Priority: Normal Reporter: Eric Thompson @MichaelSmith do you know of acceptance tests that verify use of custom facts in custom facts? re: https://groups.google.com/forum/#!topic/puppet-users/-OqwDy2zgNU [9:42 AM] Michael Smith: There's an integration spec in Puppet that does something like that (puppetversion)... If userblweb is coming from a module, `require 'facter'` won't have the same effect as `facter -p`. [9:43 AM] Michael Smith: Looks like the thread got to an answer. I'll take a quick look, most likely it's in unit tests. Most of the custom fact tests are at https://github.com/puppetlabs/facter/tree/master/lib/tests/fixtures/ruby [9:46 AM] Michael Smith: Hmm, looks like we might not. @peterhu ^ [9:48 AM] Peter Huene: Looks like a test hole [9:50 AM] Peter Huene: From Facter's perspective when dealing with custom facts, there is no difference requesting a built in fact or a custom fact from within a custom fact We do sort of test for this in cycle.rb, although not in two different files [10:01 AM] Michael Smith: @erict ^ so test gap, if you want to ticket something. Putting it in lib/tests/fixtures/ruby and modifying lib/tests/ruby/ruby.cc is pretty straight-forward. Add
Jira (FACT-1021) Custom facts that require 'facter' cannot be evaluated from command line facter
Title: Message Title Michael Smith commented on FACT-1021 Re: Custom facts that require 'facter' cannot be evaluated from command line facter This wasn't a problem with the cfacter binary in the stable puppet-agent packages. It only showed up on master. 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 Michael Smith assigned an issue to Michael Smith Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Michael Smith Assignee: MichaelSmith 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-4356) Remove undocumented puppetversion key functionality in module metadata
Title: Message Title Anderson Mills updated an issue Puppet / PUP-4356 Remove undocumented puppetversion key functionality in module metadata Change By: Anderson Mills Release Notes: BugFix 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
Eric Thompson commented on FACT-982
Re: Warnings about not being able to resolve custom facts with --no-custom-facts
validated on windows2012r2-rubyx64 at puppet-agent SHA: 12d6ed7d187e8f8ad8de1337e518c2e1254155b0
Administrator@sd7mn8vy1ciz292 ~
$ cmd /c facter os --no-custom-facts
2015-06-04 18:46:20.244339 WARN puppetlabs.facter - could not locate a ruby library: facts requiring Ruby will not be resolved.
{
architecture = x64,
family = windows,
hardware = x86_64,
name = windows,
release = {
full = 2012 R2,
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 commented on PUP-4665 Re: Puppet::Parser::Scope has no inspect method which is causing an extremely large string to be produced Olof Hellqvist Justin Lambert This should fix the issues you were both seeing and will go out in Puppet 4.2.0. If you want to test the fix, I've verified that it's currently present in the latest nightly build of 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 (FACT-982) Warnings about not being able to resolve custom facts with --no-custom-facts
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-982 Warnings about not being able to resolve custom facts with --no-custom-facts 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-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith commented on PUP-4658 Re: Agent migration for mco configuration should prefer new plugin location Passed CI https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/puppet_agent/view/master/job/modules_puppetlabs-puppet_agent_intn-sys_core-master-foss-stable/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-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-4658 Agent migration for mco configuration should prefer new plugin location Change By: Michael Smith Status: Readyfor CI Test Assignee: KyloGinsberg 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-4692) Puppet has no designated default user or group providers for Linux
Title: Message Title
Charlie Sharpsteen commented on PUP-4692
Re: Puppet has no designated default user or group providers for Linux
A workaround for this issue is to set resource defaults for the User and Group types in a top scope — such as in site.pp:
if $::kernel == 'Linux' {
User { provider = useradd }
Group { provider = groupadd }
}
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
Jira (PUP-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith assigned an issue to Kylo Ginsberg Puppet / PUP-4658 Agent migration for mco configuration should prefer new plugin location Change By: Michael Smith Assignee: KyloGinsberg 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-4692) Puppet has no designated default user or group providers for Linux
Title: Message Title
Charlie Sharpsteen commented on PUP-4692
Re: Puppet has no designated default user or group providers for Linux
The reason this happens is that without a designated default provider, Puppet falls back to a set of heuristics, one of which is specificity. Basically, the ancestry of each provider is evaluated:
Puppet::Type.type(:user).provider(:pw).ancestors.select { |a| a.is_a? Class }
= [Puppet::Type::User::ProviderPw,
Puppet::Provider::NameService::PW,
Puppet::Provider::NameService::ObjectAdd,
Puppet::Provider::NameService,
Puppet::Provider,
Object,
BasicObject]
Puppet::Type.type(:user).provider(:useradd).ancestors.select { |a| a.is_a? Class }
= [Puppet::Type::User::ProviderUseradd,
Jira (FACT-959) Incorrect processor counts on Windows
Title: Message Title Christopher Pisano commented on FACT-959 Re: Incorrect processor counts on Windows I am seeing this behavior (Facter only showing the CPU socket count) on all of my windows servers running Facter version 2.x. It is in a VMware environment. It seems that Facter version 1.x shows the correct processor count. 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-1590) We need to support the old command versions for wireformats for upgrade purposes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1590 We need to support the old command versions for wireformats for upgrade purposes Change By: Kenneth Barber Whenupgradingauserwillhaveolddatapotentiallyinthequeuebeforetheupgrade.AfterupgradePuppetDBwillfailonthosecommands,even1commandwillbouncearoundwithfailures.Whilethiswilleventuallyrightitself,it'sstilldataloss.Reportsmostimportantlywillgetlost,whilecatalogsfactswithouthistoricalwilleventuallycorrectthemselvesnaturally. 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-1455) Accommodate AIO (paths, etc.)
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1455 Accommodate AIO (paths, etc.) Change By: Kenneth Barber Assignee: KennethBarber 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-4695) add acceptance testing calling all hiera functions from ERB templates
Title: Message Title Eric Thompson created an issue Puppet / PUP-4695 add acceptance testing calling all hiera functions from ERB templates Issue Type: Task Assignee: Eric Sorenson Components: QA Created: 2015/06/04 9:29 AM Priority: Normal Reporter: Eric Thompson escaped and reported from outside: https://groups.google.com/forum/#!msg/puppet-users/Ht_5d2Wb6VA/v1lVtw031DkJ regressed with update to puppet 4.0? Henrik Lindberg i'd like to get your perspective on what is required here. Add Comment
Jira (PUP-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith updated an issue Puppet / PUP-4658 Agent migration for mco configuration should prefer new plugin location Change By: Michael Smith Sprint: Client2015- 07 06 - 08 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-4693) The pw provider for users and groups should be confined to BSD
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4693 The pw provider for users and groups should be confined to BSD Change By: Josh Cooper 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 (PUP-4693) The pw provider for users and groups should be confined to BSD
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4693 The pw provider for users and groups should be confined to BSD Change By: Josh Cooper Sprint: Client2015-06-24 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 (PDB-1590) We need to support the old command versions for wireformats for upgrade purposes
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1590 We need to support the old command versions for wireformats for upgrade purposes Issue Type: Bug Affects Versions: PDB 3.0.0 Assignee: Unassigned Created: 2015/06/04 9:28 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1571) Update changelog/release notes
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1571 Update changelog/release notes Change By: Wyatt Alt Fix Version/s: PDB2.3.x 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-4696) Update module for Debian 8 Jessie
Title: Message Title Michael Smith created an issue Puppet / PUP-4696 Update module for Debian 8 Jessie Issue Type: Improvement Assignee: Unassigned Created: 2015/06/04 9:55 AM Priority: Normal Reporter: Michael Smith Once the puppet-agent package is released to apt.puppetlabs.com for Debian 8, update the puppet_agent module to support it. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-984) Fix facts/debian on Debian 8
Title: Message Title Michael Smith updated an issue Facter / FACT-984 Fix facts/debian on Debian 8 Change By: Michael Smith Sprint: Client2015-06-24 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-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith updated an issue Puppet / PUP-4658 Agent migration for mco configuration should prefer new plugin location Change By: Michael Smith Scope Change Reason: puppet_agentprioritybumped Scope Change Category: Found 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-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith commented on PUP-4658 Re: Agent migration for mco configuration should prefer new plugin location Failed CI at https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/puppet_agent/view/master/job/modules_puppetlabs-puppet_agent_intn-sys_core-master-foss-stable/9/PLATFORM_CONFIG=redhat-7-64mda-inverted,SLAVE_LABEL=beaker/consoleText 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-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Eric Thompson commented on PUP-4466 Re: add acceptance: ensure functions can be written/execute in puppet language crap, i didn't notice the non-temporary environments. sorry 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-1454) document AMQ errors on master-stable downgrades
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1454 document AMQ errors on master-stable downgrades Change By: Wyatt Alt Fix Version/s: PDB2.3.x 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-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1469 puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package Change By: Wyatt Alt Fix Version/s: PDB2.3.x 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-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks commented on PDB-1589 Re: If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Kenneth Barber - as far as I can see, it's not possible to have a null value in facter; and this issue only occurs when a mistake is made while generating JSON facts for PuppetDB. Facter seems to just remove a fact with no value - I tried creating a custom fact that is set to Ruby nil; this just results in the fact not being included in the node's fact list. A fact set to Ruby empty string results in a JSON empty string. 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-1455) Accommodate AIO (paths, etc.)
Title: Message Title Kenneth Barber commented on PDB-1455 Re: Accommodate AIO (paths, etc.) Awaiting ezbake PR here: https://github.com/puppetlabs/ezbake/pull/250 And we'll probably need a release. The final PR once this is done is here: https://github.com/puppetlabs/puppetdb/pull/1436 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-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title Kenneth Barber commented on PDB-1589 Re: If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works James Stocks have you been able to reproduce this with real-life data from facter? ie. is this world-reproducible with the full stack, or just an exception if users try to do something special via the API? I see its osfamily that is a null, I didn't think this was possible in facter, since a null meant 'unknown' and usually is skipped over, perhaps facter has changed. 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-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot commented on PDB-1560 Re: PR (1427): (packaging)Update paths to AIO layout - shrug Pull request (packaging)Update paths to AIO layout has been closed. 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-1560) PR (1427): (packaging)Update paths to AIO layout - shrug
Title: Message Title gepetto-bot commented on PDB-1560 Re: PR (1427): (packaging)Update paths to AIO layout - shrug kbarber commented: I've raised a new cleaned up PR here: https://github.com/puppetlabs/puppetdb/pull/1436 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-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title Kenneth Barber commented on PDB-1589 Re: If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works James Stocks I suspected as much. Okay thanks for this. 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-1125) PuppetDB terminus fetches unstructured facts instead of structured
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1125 PuppetDB terminus fetches unstructured facts instead of structured Change By: Kenneth Barber Assignee: ErikDaln KennethBarber 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-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4466 add acceptance: ensure functions can be written/execute in puppet language Change By: Kurt Wall Assignee: 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 (PUP-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Kurt Wall commented on PUP-4466 Re: add acceptance: ensure functions can be written/execute in puppet language Running a fix through local acceptance now. 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-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks created an issue PuppetDB / PDB-1589 If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Issue Type: Bug Assignee: Unassigned Attachments: NullFact.json Components: PE Created: 2015/06/04 6:59 AM Priority: Normal Reporter: James Stocks Noticed this during QA of Puppet Enterprise... To reproduce: Send the attached JSON to replace facts v4 (note that osfamily has a JSON null value - this was due to a bug in our test data generator tool) Expected behaviour: I'm not sure. Either null should be accepted and handled
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum created an issue Puppet / PUP-4694 Puppet apply doesn't read manifest when using ENC Issue Type: Bug Assignee: Unassigned Created: 2015/06/03 11:44 PM Priority: Normal Reporter: Spencer Krum This is pretty similar behaviour to https://tickets.puppetlabs.com/browse/PUP-3258 so it might just be that again. Situation: An enc defines classes and a site.pp or puppet apply foo.pp defines more puppet things. In the example case notify resources are used but in production resource defaults are set. From https://docs.puppetlabs.com/guides/external_nodes.html I expect to get all resources defined by the ENC and in foo.pp but what I actually get is only resources from the ENC. The setup: root@puppetapply:~# cat /etc/puppet/puppet.conf [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter node_terminus = exec external_nodes = /usr/local/bin/puppet_node_classifier [master] These are needed when the puppetmaster is run by passenger and can safely be removed if webrick is used. ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY root@puppetapply:~# cat /usr/local/bin/puppet_node_classifier #!/bin/bash cat /root/foo.yaml root@puppetapply:~# cat foo.yaml — classes:
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title
William Van Hevelingen updated an issue
Puppet / PUP-4694
Puppet apply doesn't read manifest when using ENC
Change By:
William Van Hevelingen
Thisisprettysimilarbehaviourtohttps://tickets.puppetlabs.com/browse/PUP-3258soitmightjustbethatagain.Situation:Anencdefinesclassesandasite.pporpuppetapplyfoo.ppdefinesmorepuppetthings.Intheexamplecasenotifyresourcesareusedbutinproductionresourcedefaultsareset.Fromhttps://docs.puppetlabs.com/guides/external_nodes.htmlIexpecttogetallresourcesdefinedbytheENCandinfoo.ppbutwhatIactuallygetisonlyresourcesfromtheENC.Thesetup: {code} root@puppetapply:~#cat/etc/puppet/puppet.conf[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppetfactpath=$vardir/lib/facternode_terminus=execexternal_nodes=/usr/local/bin/puppet_node_classifier[master]#Theseareneededwhenthepuppetmasterisrunbypassenger#andcansafelyberemovedifwebrickisused.ssl_client_header=SSL_CLIENT_S_DNssl_client_verify_header=SSL_CLIENT_VERIFY {code} {code} root@puppetapply:~#cat/usr/local/bin/puppet_node_classifier#!/bin/bashcat/root/foo.yamlroot@puppetapply:~#catfoo.yaml---classes:-helloworld#environment:devel {code} {code} root@puppetapply:~#cattest.ppnotify{derp:}nodedefault{}root@puppetapply:~#cat/etc/puppet/modules/helloworld/manifests/init.ppclasshelloworld{notify{SUPNERDS:}} {code} Thecorrectbehaviourisseenon3.4: {code} root@puppetapply:~#puppet--version3.4.3root@puppetapply:~#puppetapplytest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsWarning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.Notice:derpNotice:/Stage[main]/Main/Notify[derp]/message:defined'message'as'derp'Notice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.20seconds {code} Butanincorrectbehaviourisseenin3.8.1: {code} root@puppetapply:~#puppetapply--environment=develtest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsNotice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.11secondsroot@puppetapply:~#puppet--version3.8.1 {code}
Add Comment
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title
William Van Hevelingen updated an issue
Puppet / PUP-4694
Puppet apply doesn't read manifest when using ENC
Change By:
William Van Hevelingen
Thisisprettysimilarbehaviourtohttps://tickets.puppetlabs.com/browse/PUP-3258soitmightjustbethatagain.Situation:Anencdefinesclassesandasite.pporpuppetapplyfoo.ppdefinesmorepuppetthings.Intheexamplecasenotifyresourcesareusedbutinproductionresourcedefaultsareset.Fromhttps://docs.puppetlabs.com/guides/external_nodes.htmlIexpecttogetallresourcesdefinedbytheENCandinfoo.ppbutwhatIactuallygetisonlyresourcesfromtheENC.Thesetup:{code}root@puppetapply:~#cat/etc/puppet/puppet.conf[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppetfactpath=$vardir/lib/facternode_terminus=execexternal_nodes=/usr/local/bin/puppet_node_classifier[master]#Theseareneededwhenthepuppetmasterisrunbypassenger#andcansafelyberemovedifwebrickisused.ssl_client_header=SSL_CLIENT_S_DNssl_client_verify_header=SSL_CLIENT_VERIFY{code}{code}root@puppetapply:~#cat/usr/local/bin/puppet_node_classifier#!/bin/bashcat/root/foo.yaml{code}{code}root@puppetapply:~#catfoo.yaml---classes:-helloworld#environment:devel{code}{code}root@puppetapply:~#cattest.ppnotify{derp:}nodedefault{} {code} {code} root@puppetapply:~#cat/etc/puppet/modules/helloworld/manifests/init.ppclasshelloworld{notify{SUPNERDS:}}{code}Thecorrectbehaviourisseenon3.4:{code}root@puppetapply:~#puppet--version3.4.3root@puppetapply:~#puppetapplytest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsWarning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.Notice:derpNotice:/Stage[main]/Main/Notify[derp]/message:defined'message'as'derp'Notice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.20seconds{code}Butanincorrectbehaviourisseenin3.8.1:{code}root@puppetapply:~#puppetapply--environment=develtest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsNotice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.11secondsroot@puppetapply:~#puppet--version3.8.1{code}
Add Comment
Jira (PDB-1577) Smoke test packages
Title: Message Title Wyatt Alt commented on PDB-1577 Re: Smoke test packages forgot to note, I followed the method here: https://confluence.puppetlabs.com/display/PP/Smoke+Testing+Guide+for+PDB+Releases 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-1577) Smoke test packages
Title: Message Title Wyatt Alt commented on PDB-1577 Re: Smoke test packages tested successfully on trusty with PC1 and main repo packages. Used this box: https://atlas.hashicorp.com/puppetlabs/boxes/ubuntu-14.04-64-nocm Other platforms are now covered by acceptance tests for both the AIO case and the non-AIO case. 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 Geoff Nichols 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: Geoff Nichols Release Notes: BugFix 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 Michael Smith assigned an issue to Unassigned Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Michael Smith Assignee: KyloGinsberg 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 Michael Smith assigned an issue to Kylo Ginsberg Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Michael Smith Assignee: MichaelSmith KyloGinsberg 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-4695) add acceptance testing calling all hiera functions from ERB templates
Title: Message Title Henrik Lindberg commented on PUP-4695 Re: add acceptance testing calling all hiera functions from ERB templates The regressions in this area were introduced because hiera functions moved to the 3x API while the old ERB template functions are still 3.x and we have not provided a mechanism to call 4.x functions from a 3.x context. Essentially, the user's ruby logic in a template is running inside of the puppet runtime - and this was something we overlooked in the transition. So, the general problem is calling 3.x and 4.x functions from a 3.x scope 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 Eric Thompson assigned an issue to Unassigned Facter / FACT-982 Warnings about not being able to resolve custom facts with --no-custom-facts 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.
