Jira (PUP-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Britt Gresham commented on PUP-3118 Re: Run vendored library spec tests from top-level rake tasks We can close it out, if it is an actual issue we can open up another ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title Britt Gresham created an issue Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2016/07/01 3:43 PM Priority: Normal Reporter: Britt Gresham Currently the stable branch is failing because the kernel versions are no longer matching what we are expecting in facter's acceptance tests. Failing job: https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-stable/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-3567) Remove current_environment check in Puppet::Indirector::Request#environment=
Title: Message Title Britt Gresham commented on PUP-3567 Re: Remove current_environment check in Puppet::Indirector::Request#environment= I think that the idea was to not have a corner case in the environment setter as well as not look up environments by just their name but instead only allowing the environment setter to only allow environments that the agent knows about. Andy mentioned in the PR that this only shows up on an agent checking in where the environment that the master specifies for an agent is not known to the agent. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham commented on PUP-3091 Re: heredoc should trim left margin before joining lines I cherry-picked the tests over to stable and they all passed. britt at BrittMac in ~/projects/ruby/puppet on stable $ cat ./test.pp notice @(END/L) One fish,\ two fish | - END britt at BrittMac in ~/projects/ruby/puppet on stable $ be puppet apply --parser=future test.pp Notice: Scope(Class[main]): One fish, two fish Notice: Compiled catalog for brittmac.corp.puppetlabs.net in environment production in 0.33 seconds
Jira (PUP-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3091 heredoc should trim left margin before joining lines Change By: Britt Gresham Fix Version/s: PUP4.0.0 Fix Version/s: PUP3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham commented on PUP-3091 Re: heredoc should trim left margin before joining lines Retargeted toward stable branch in PR-3327. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3140) Illegal number error should include the faulty number
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3140 Illegal number error should include the faulty number Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham commented on PUP-3091 Re: heredoc should trim left margin before joining lines So I noticed that we don't have test coverage for this and I added a test to cover this case however I am not able to reproduce the behavior in my clone of Puppet. When running with future parser I cannot get the spaces to show up. notice @(END/L) Red fish,\ blue fish. | - END $ be puppet apply test.pp --parser=future Notice: Scope(Class[main]): Red fish, blue fish. Notice: Compiled catalog for brittmac.delivery.puppetlabs.net in environment production in 0.35 seconds Notice: Applied catalog in 0.01 seconds
Jira (PUP-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham commented on PUP-3091 Re: heredoc should trim left margin before joining lines PR-3326 Added Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1019) Remove ZAML
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1019 Remove ZAML Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3091) heredoc should trim left margin before joining lines
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3091 heredoc should trim left margin before joining lines Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1019) Remove ZAML
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1019 Remove ZAML Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1019) Remove ZAML
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1019 Remove ZAML Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1077) Move Nagios types and supporting from core to a module
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1077 Move Nagios types and supporting from core to a module Change By: Britt Gresham Assignee: KyloGinsberg BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3272) Remove support for yaml on the network
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3272 Remove support for yaml on the network Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1019) Remove ZAML
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1019 Remove ZAML Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1019) Remove ZAML
Title: Message Title Britt Gresham commented on PUP-1019 Re: Remove ZAML I'm a little confused as to how I should be approaching this. Is this about removing monkey patching that was done on the `to_yaml` method on native data types to replace ZAML with the built-in YAML or are we favoring something like JSON for serialization and deserialization of this data? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Fix Version/s: PUP3.7.3 Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham created an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Created: 30/Oct/14 10:33 AM Priority: Normal Reporter: Britt Gresham In the event where the agent is requesting a catalog from the master and the agent is in the wrong environment the master we grab new facts on the requesting node and send the new facts over however when the master attempts to do a plugin sync the files from the old environment are sent instead of the new environment. This would never make sense as an enc but we are using it to force the behavior to happen. On the first run the agent on the node will request a catalog for the production environment but the enc will respond saying that the node should be in the test environment causing the node to attempt to resolve the environment. enc #!/bin/bash
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title
Britt Gresham updated an issue
Puppet / PUP-3591
Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Change By:
Britt Gresham
Intheeventwheretheagentisrequestingacatalogfromthemasterandtheagentisinthewrongenvironmentthemasterwegrabnewfactsontherequestingnodeandsendthenewfactsoverhoweverwhenthemasterattemptstodoapluginsyncthefilesfromtheoldenvironmentaresentinsteadofthenewenvironment.Thiswouldnevermakesenseasanencbutweareusingittoforcethebehaviortohappen.Onthefirstruntheagentonthenodewillrequestacatalogfortheproductionenvironmentbuttheencwillrespondsayingthatthenodeshouldbeinthetestenvironmentcausingthenodetoattempttoresolvetheenvironment.{panel:title=enc}{noformat}#!/bin/bashif[-e'./enc.lock'];thencatENCenvironment:productionENCelsecatENCenvironment:testENCtouch./enc.lock/dev/nullfi{noformat}{panel}Setuptwoenvironments{panel:title=environments}{noformat}$tree~/test/ master/test/ environments/Users/britt/test/ master/test/ environments├──production│└──modules│└──test│├──lib││└──puppet││└──production_env.rb│└──manifests│└──site.pp└──test└──modules└──test├──lib│└──puppet│└──test_env.rb└──manifests└──site.pp12directories,4files{noformat}{panel}Startamasterwiththespecifiedencandenvironmentpath{noformat}$ be ./util/dev- puppet - master test -- no-daemonize--autosign=true--certname=puppetmaster-- node_terminus=exec--external_nodes= ~ / path projects / to ruby / pe-puppet/ enc--environmentpath=~/test/ master/test/ environments{noformat}Runpuppetagent{noformat}$bepuppetagent-t--server=puppetmasterWarning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmenttest,switchingagenttotest.Info:RetrievingpluginfactsInfo:RetrievingpluginNotice:/File[/Users/britt/.puppet/var/lib/puppet/test_env.rb]/ensure:definedcontentas'{md5}d41d8cd98f00b204e9800998ecf8427e'Info:Cachingcatalogforbrittmac.delivery.puppetlabs.netWarning:Localenvironment:testdoesn'tmatchserverspecifiedenvironmentproduction,restartingagentrunwithenvironmentproductionInfo:Cachingcatalogforbrittmac.delivery.puppetlabs.netInfo:Applyingconfigurationversion'1414690262'Info:Creatingstatefile/Users/britt/.puppet/var/state/state.yamlNotice:Finishedcatalogrunin0.01seconds{noformat}Youcanseethatinsteadoftheproduction_env.rbbeinginthevardirectoryinsteadthetest_env.rbfilewassyncedbeforetheenvironmentwasresolved.
Add Comment
Jira (FACT-739) Smoke test packages
Title: Message Title Britt Gresham commented on an issue Re: Smoke test packages Fedora 19 and Fedora 20 look good: https://gist.github.com/demophoon/f394ff0c8efb10cdb66b Add Comment Facter / FACT-739 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Fix Version/s: PUP3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Sprint: PlatformServer2014-11-12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Britt Gresham Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3567) Remove current_environment check in Puppet::Indirector::Request#environment=
Title: Message Title Britt Gresham created an issue Puppet / PUP-3567 Remove current_environment check in Puppet::Indirector::Request#environment= Issue Type: Bug Assignee: Andy Parker Components: Server Created: 29/Oct/14 10:26 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Britt Gresham Currently we have the environment setter in lib/puppet/indirector/request.rb set to allow the environment to be set to an environment when it is what is in `Puppet.lookup(:current_environment)`. We should only allow environments that puppet knows about in Puppet.lookup(:environments) The following lines should be removed: elsif (current_environment = Puppet.lookup(:current_environment)).name == env current_environment
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3272 Remove support for yaml on the network Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Britt Gresham commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Merged in a9bdc75
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Britt Gresham commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
I don't believe anyone is tasked with that yet.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title
Britt Gresham commented on an issue
Re: Puppet resource broken when directory environments enabled
Added PR-3198
Add Comment
Puppet / PUP-3302
Puppet resource broken when directory environments enabled
When running puppet resource, the command fails for want of a 'none' environment {quote} puppet resource file /usr/share/puppet-dashboard-mirror ensure=directory source=/usr/share/puppet-dashboard recurse=true ignore='*log*' Error: /File[/usr/share/puppet-dashboard-mirror]: Failed to generate additional resources using 'eval_generate': Could not find ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3474) Puppet Profile Blog Post
Title: Message Title Britt Gresham created an issue Puppet / PUP-3474 Puppet Profile Blog Post Issue Type: Task Assignee: Britt Gresham Components: Server Created: 15/Oct/14 1:44 PM Priority: Normal Reporter: Britt Gresham Original Estimate: 1 minute Remaining Estimate: 1 minute Write and publish blog post about the puppet profile flag and the puppet profile script so we can start collecting data from users. Add Comment
Jira (PUP-3300) Rework Puppet::Util::Checksums to not extend itself
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3300 Rework Puppet::Util::Checksums to not extend itself Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3474) Puppet Profile Blog Post
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3474 Puppet Profile Blog Post Change By: Britt Gresham Sprint: PlatformServer2014- 11 10 - 12 29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3474) Puppet Profile Blog Post
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3474 Puppet Profile Blog Post Change By: Britt Gresham Sprint: PlatformServer2014-11-12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3474) Puppet Profile Blog Post
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3474 Puppet Profile Blog Post Change By: Britt Gresham Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Britt Gresham commented on an issue Re: ENC returned environment ignored when using directory environments Actually, I was just going through my refactor of Puppet::Environments::Combined#get! and realized isn't going to do what we think it will do. Since instead of looping over all of the loaders and calling `get!` it will fail out the first time the environment is not found and it will not iterate over the rest. I've replaced that function with the version that just calls `get` on every loader and raising an error at the end if no suitable environment was found. Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the
Jira (PUP-3306) Remove deprecated Puppet::SSL::Inventory#serial method
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3306 Remove deprecated Puppet::SSL::Inventory#serial method Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3306) Remove deprecated Puppet::SSL::Inventory#serial method
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3306 Remove deprecated Puppet::SSL::Inventory#serial method Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Britt Gresham commented on an issue Re: ENC returned environment ignored when using directory environments I have some more changes that could be cherry-picked into the fix-up. Puppet::Environments::Combined#get! should be calling each loaders `get!` function instead of assuming that all of the `get!` methods work the same way. I've also added a test for directory environments with the `get!` method and did some refactors where `get!` should be used instead of `get` method Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Britt Gresham commented on an issue Re: ENC returned environment ignored when using directory environments Rob Reynolds I've cherry-picked your changes into my branch and its in PR-3182. Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3351) Puppet evaluates classes declared with parameters before classes declared without parameters
Title: Message Title Britt Gresham commented on an issue Re: Puppet evaluates classes declared with parameters before classes declared without parameters In this functional review I made sure that classes with additional params passed in were evaluated before those without params when inherited by another class and specified by an ENC. You can see below that when ran using Puppet 3.7.1 we get an error complaining that Class['one'] has already been defined as opposed to Puppet at the merge commit where puppet evaluates Class['one'] before Class['two']. The 'something' message that is shown proves that Class['one'] is evaluated before because the message emitted was not the default 'default_two' that was defined in the class definition. /Users/britt/projects/ruby/puppet/enc #!/bin/bash cat ENC classes: two: one: foo: something ENC
Jira (PUP-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3351) Puppet evaluates classes declared with parameters before classes declared without parameters
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3351 Puppet evaluates classes declared with parameters before classes declared without parameters Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham commented on an issue Re: Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Yes, this is the intended result of the ticket. The behavior should not change after the refactor. We decided that making the error messages more specific to the actual problems would have been more trouble than what it was worth and are going to keep that as a task under the internationalization epic down the road. Add Comment Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. There are various cases where an environment's final configuration may end up being invalid. One case, where an environment may have conflicting manifest settings, is already covered by a Puppet::Node::Environment#conflicting_manifest_settings? method, added in PUP-3069. Another case brought up by PUP-3162 has to do with base environment settings like e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PUP-3258) puppet apply + ENC + 3.7.x: does not read the .pp file
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3258 puppet apply + ENC + 3.7.x: does not read the .pp file Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3258) puppet apply + ENC + 3.7.x: does not read the .pp file
Title: Message Title
Britt Gresham commented on an issue
Re: puppet apply + ENC + 3.7.x: does not read the .pp file
As a part of the FR I made sure that the results on stable match those before the regressions introduced after 3.6.1.
site.pp:
notify { 'You should be able to see me': }
On Puppet 3.6.1:
britt at BrittMac in ~/projects/ruby/puppet on (detached from 3.6.1)*
$ be puppet apply ./site.pp --test
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
(at /Users/britt/projects/ruby/puppet/lib/puppet/settings.rb:1067:in `each')
Info: Loading facts in /Users/britt/Downloads/puppet-vapply-bug/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in /Users/britt/Downloads/puppet-vapply-bug/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /Users/britt/Downloads/puppet-vapply-bug/modules/stdlib/lib/facter/puppet_vardir.rb
Jira (PUP-3258) puppet apply + ENC + 3.7.x: does not read the .pp file
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3258 puppet apply + ENC + 3.7.x: does not read the .pp file Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham commented on an issue Re: Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Andy Parker After reviewing the ticket with Joshua Partlow we realized that the changes that I made were the wrong way to go about this. Instead of adding a validation method for `Puppet::Node::Environment` the error message needed to be modified for nonexistent directory environments. We stumbled upon the issue where the console logging destination was not being setup before the application exited from the Could not find a directory environment named 'nonesuch' error was raised. All of the logs that were stored were then lost. If we were to want to implement the change to enable logging earlier we would have bad side effects with every face from that point forward logging information. Unfortunately making changes to the error messages that get raised to give more detailed information requires us to add a conditional statement in each case where the Puppet::Environments::EnvironmentNotFound error is raised to check and see if $environment was in environmentpath or not. This also gets us into the situation where we'd applying the change deep inside of Puppet::Indirector::Request#environment as well as other places that would make maintaining it difficult. Warning... Brain dump below.. I'd like to see what you guys think about this ticket. I had a few thoughts while writing this and I tested a few of them that could be possible solutions to some of those problems at least on the agent side. I'll need to loop back with Joshua Partlow tomorrow to see if there is anything that can be done master side to make the error messages more helpful. One involves moving the logic that tests if $environment is in environmentpath into where we raise EnvironmentNotFound. This feels dirty. The other is to setup a console logger just before we raise the error for not finding the environment we specified in lib/puppet/application.rb. This also feels a little dirty, but I think it is better than the other solution since I'd like to see the console logger setup much earlier. The downside to that is that it is a partial fix since it only covers the agent and not the master, at least if I am understanding things correctly. Add Comment Puppet / PUP-3239
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Britt Gresham commented on an issue Re: ENC returned environment ignored when using directory environments Added PR-3146 Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Britt Gresham Assignee: AndyParker BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3245) Function calls no longer showing up in profile data
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3245 Function calls no longer showing up in profile data Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3244 ENC returned environment ignored when using directory environments Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham commented on an issue Re: Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Added PR-3117 Add Comment Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. There are various cases where an environment's final configuration may end up being invalid. One case, where an environment may have conflicting manifest settings, is already covered by a Puppet::Node::Environment#conflicting_manifest_settings? method, added in PUP-3069. Another case brought up by PUP-3162 has to do with base environment settings like e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3245) Function calls no longer showing up in profile data
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3245 Function calls no longer showing up in profile data Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3284) Write scripts to compile profile data
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3284 Write scripts to compile profile data Change By: Britt Gresham Sprint: Platform2014-10-01 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-289) automate basic functionality acceptance tests
Title: Message Title Britt Gresham commented on an issue Re: automate basic functionality acceptance tests Eric Thompson It looks like the calls to all backends till an answer is found covers if there are more than one backend. Add Comment Hiera / HI-289 automate basic functionality acceptance tests create automated acceptance tests for hiera basic functionality. high priority tests. functionality not yet covered. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3278) Find ways of increasing the puppet masters capacity
Title: Message Title Britt Gresham created an issue Puppet / PUP-3278 Find ways of increasing the puppet masters capacity Issue Type: Epic Assignee: Andy Parker Components: Server Created: 17/Sep/14 2:06 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Britt Gresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3279) Gather research from puppet-dev and puppet-users.
Title: Message Title Britt Gresham created an issue Puppet / PUP-3279 Gather research from puppet-dev and puppet-users. Issue Type: Task Assignee: Andy Parker Components: Server Created: 17/Sep/14 2:10 PM Priority: Normal Reporter: Britt Gresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-3279) Gather research from puppet-dev and puppet-users.
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3279 Gather research from puppet-dev and puppet-users. Change By: Britt Gresham Sprint: Platform2014-10-01 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3279) Gather research from puppet-dev and puppet-users.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3279 Gather research from puppet-dev and puppet-users. Change By: Britt Gresham Assignee: AndyParker BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3284) Write scripts to compile profile data
Title: Message Title Britt Gresham created an issue Puppet / PUP-3284 Write scripts to compile profile data Issue Type: Task Assignee: Andy Parker Components: Server Created: 17/Sep/14 3:26 PM Priority: Normal Reporter: Britt Gresham Create/modify scripts for users to run to help gather puppet master profile data. Should be easy to run and use to get the most data from the users. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3284) Write scripts to compile profile data
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3284 Write scripts to compile profile data Change By: Britt Gresham Assignee: AndyParker BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3285) Send announcements for gathering profile data
Title: Message Title Britt Gresham created an issue Puppet / PUP-3285 Send announcements for gathering profile data Issue Type: Task Assignee: Britt Gresham Components: Server Created: 17/Sep/14 4:11 PM Priority: Normal Reporter: Britt Gresham Remove all PI Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-900 noop = true is ignored when resource is triggered by other resource Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title
Britt Gresham commented on an issue
Re: noop = true is ignored when resource is triggered by other resource
Merged.
Add Comment
Puppet / PUP-900
noop = true is ignored when resource is triggered by other resource
when running : {code} file {'/tmp/asd': content = generate('/bin/date'), notify = Exec['ttt'], }exec { 'ttt': command ='/bin/date', logoutput = true, noop = true, } {code} exec is still ran even tho it's set to noop, any notify to resource makes it ignore noop parameter: {cod...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-289) automate basic functionality acceptance tests
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Hiera / HI-289 automate basic functionality acceptance tests Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-289) automate basic functionality acceptance tests
Title: Message Title Britt Gresham commented on an issue Re: automate basic functionality acceptance tests Thanks Joshua Partlow for the additional context. I was briefed by Eric Thompson about this ticket. I started looking into the spec tests to figure out what we were actually testing in there and where everything was just to start getting familiar with it so that I can compare it to what I saw in the three new acceptance tests. Add Comment Hiera / HI-289 automate basic functionality acceptance tests create automated acceptance tests for hiera basic functionality. high priority tests. functionality not yet covered. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-289) automate basic functionality acceptance tests
Title: Message Title Britt Gresham commented on an issue Re: automate basic functionality acceptance tests Eric Thompson and I reviewed the spec tests and the acceptance tests and found that the acceptance tests that had been proposed were covered in the spec tests already. Adding in these tests looks like it duplicates the should pick data earliest source that has it for priority searches tests in the backends spec tests. Add Comment Hiera / HI-289 automate basic functionality acceptance tests create automated acceptance tests for hiera basic functionality. high priority tests. functionality not yet covered. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-289) automate basic functionality acceptance tests
Title: Message Title Britt Gresham commented on an issue Re: automate basic functionality acceptance tests I'll double check that to see if anything in the spec tests multiple values to pick the one in the correct order. Add Comment Hiera / HI-289 automate basic functionality acceptance tests create automated acceptance tests for hiera basic functionality. high priority tests. functionality not yet covered. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Britt Gresham commented on an issue Re: Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Added PR-3062 This commit will test if the production directory environment exists and if it does puppet will test if it is a symlink or not. In the event that it is a symlink puppet will ensure that the followed path is a directory instead of ensuring the symlink itself is a directory. Add Comment Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory We use puppet environments, and symlink the puppet folder of one of our git repos to /etc/puppet/environment. This is how it looks like: #:/etc/puppet/environments$ ls -l total 4 lrwxrwxrwx 1 root root 47 Jul 4 10:05 user1 - /var/lib/ops-automation.user1/puppet lrwxrwxrwx 1 root root 49 Jul 4 10:05 user2 - /var/lib/ops-automation.user2/pupp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving
Jira (PUP-2412) Remove 1.8.7 function API support
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-2412 Remove 1.8.7 function API support Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2412) Remove 1.8.7 function API support
Title: Message Title Britt Gresham updated an issue Puppet / PUP-2412 Remove 1.8.7 function API support Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Added PR-3050 Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3156) Fix /var/lib/puppet/state permissions on redhat
Title: Message Title Britt Gresham commented on an issue Re: Fix /var/lib/puppet/state permissions on redhat PUP-3154 is referenced in PR-3030 and redirects to PUP-3156 . Add Comment Puppet / PUP-3156 Fix /var/lib/puppet/state permissions on redhat On EL platforms, if the agent runs before puppetserver is started, then /var/lib/puppet/state is owned by root and we can't write reports there. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2776) Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
Title: Message Title
Britt Gresham commented on an issue
Re: Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
PR-2920 References PUP-2766 instead of referencing
PUP-2776
.
Add Comment
Puppet / PUP-2776
Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
I believe PE 3.4.x will be based on Puppet master. We have new environment tests in master which currently rely on setting --confdir in the Beaker with_puppet_running_on() :__commandline_args__ setting so that the puppet master is started with those command line arguments. PE tests can't use this setting, as we are just restarting the rack environment a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-3099) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3099 Is there a JIRA ticket targeted at the release for every commit? Change By: Britt Gresham Assignee: JoshuaPartlow BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Do we need/utilize PuppetDB in any of the acceptance tests? Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb So any opposition on using postgres on a non-PE client during the tests? Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb RabbitMQ? It also has no upstart script and only an init.d script Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb One potential candidate that matches our criteria is the postgresql package. It only has an init.d script for starting the daemon. The problem that I see with using that one is that we would have to download postgres every time we run acceptance tests (about 22.9mb). Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post
Jira (PUP-3117) Resource Expression Enhancements
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3117 Resource _expression_ Enhancements Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Kylo Ginsberg Josh and I had thought about replacing apache in the test itself since passenger relies on apache and I'm not sure if we should be testing the service that is used in other tests with a puppet master. Apache also might not have an intermediary status that can tell us that it is in the process of starting or stopping so it might be the best we can get out of this service. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Would anyone be opposed to using testing this service against ntp instead of apache? Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Britt Gresham created an issue Puppet / PUP-3118 Run vendored library spec tests from top-level rake tasks Issue Type: New Feature Assignee: Unassigned Created: 20/Aug/14 3:21 PM Priority: Minor Reporter: Britt Gresham It would be nice if there was a way to test vendored packages against multiple versions of ruby from the top-level rake tasks. It would help identify a library needed to be updated. Instead of running the tests individually you could hit all vendored packages at the same time. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-406) Deprecate stringify_fact = true
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-406 Deprecate stringify_fact = true Change By: Britt Gresham Assignee: NicholasFagerlund BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-586) Deprecate Instrumentation system
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-586 Deprecate Instrumentation system Change By: Britt Gresham Assignee: NicholasFagerlund BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
