Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Change By: Joshua Partlow Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. also: tests/environment.use_agent_environment_when_enc_doesnt_specify.rb tests/environment.use_agent_environment_when_no_enc.rb tests/environment.use_enc_environment_for_files.rb tests/environment.use_enc_environment_for_pluginsync.rb tests/ordering.master_agent_application.rb tests/ssl.autosign_command.rb in future parser ci and tests/environment.use_enc_environment_for_files.rb tests/ssl.autosign_command.rb in windows Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 9a95498 in master should take care of the autosign_command and use_enc_environment_for_files problems. Will look at the future parser issues tomorrow morning. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-3339) Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3339 Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug Change By: Joshua Partlow Flagged: Impediment 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Flagged: Impediment 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow assigned an issue to Hailee Kenney Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Assignee: JoshuaPartlow HaileeKenney 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow commented on an issue Re: Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Confined acceptance from running this test on fedora-19; merged to stable in 6d0d7f8 and to master in cc4e3c5 Add Comment Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. This failure is showing up in the following acceptance test: acceptance/tests/config/puppet_manages_own_configuration_in_robust_manner.rb, but only on Fedora19. This test removes the puppet user/group and then confirms that the --mkusers flag allows the puppet master to recreate them. Before doing this, it records the current user/group state, and then ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3246) Puppet Module Tool Does Not Honor puppet.conf Settings unless they are in [main]
Title: Message Title Joshua Partlow commented on an issue Re: Puppet Module Tool Does Not Honor puppet.conf Settings unless they are in [main] This ticket is open pending resolution of DOC-1237 to clarify that environmentpath/basemodulepath need to be set in main if you want them to be used by other user mode faces. Just a note about what is going on in the Puppet settings: the observed behavior is because of run_mode and settings interactions. A `puppet master` executes in the 'master' run_mode, while a `puppet module` executes in the 'user' run_mode, which correspond to the [master] and [user] sections of puppet.conf respectively. By setting environmentpath/basemodulepath in the [master] section, you are effectively telling Puppet that you only want those settings applied when run as a master. Add Comment Puppet / PUP-3246 Puppet Module Tool Does Not Honor puppet.conf Settings unless they are in [main] When setting the environmentpath setting and basemodulepath setting if you place them in the [master] section of puppet.conf then `puppet module list` will not work correctly. If you place both settings in [master] then you just get the default modulepath returned from `puppet module list`. If you place just basemodulepath in [main] and environmen... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Issue Type: Bug Affects Versions: 3.7.1 Assignee: Unassigned Attachments: puppet_manages_own_configuration_in_robust_manner-error.log Created: 24/Sep/14 11:47 AM Environment: fedora19 Fix Versions: 3.7.2 Priority: Normal Reporter: Joshua Partlow This failure is showing up in the following acceptance test: acceptance/tests/config/puppet_manages_own_configuration_in_robust_manner.rb, but only on Fedora19. This test removes the puppet user/group and then confirms that the --mkusers flag allows the puppet master to recreate them. Before doing this, it records the current user/group state, and then in the final teardown step,
Jira (PUP-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title
Joshua Partlow commented on an issue
Re: Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
The following manual reproduction on Fedora19 looks pretty similar except that it is complaining about /vra/spool/mail/test not owned by test...
[root@svctsjhgq83d67w ~]# puppet resource group test ensure=present gid=53
Notice: /Group[test]/ensure: created
group { 'test':
ensure = 'present',
gid= '53',
}
[root@svctsjhgq83d67w ~]# puppet resource user test ensure=present groups=test uid=53
Notice: /User[test]/ensure: created
user { 'test':
ensure = 'present',
Jira (PUP-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Issue Type: Bug Affects Versions: 3.7.1 Assignee: Andy Parker Components: Server Created: 23/Sep/14 5:39 PM Fix Versions: 3.7.2 Priority: Normal Reporter: Joshua Partlow I haven't tracked down all the details here, but Adrien Thebo noticed that changes to a directory environment's environment.conf are not being reloaded, even when environment_timeout is 0. Add Comment
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow commented on an issue Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Hi Franois Chenais, the puppet master needs some initial environment to bootstrap from. By default this is production. For a passenger setup, you can edit your config.ru to add the debugging flag (this file should be one up from your Apache Passenger virtualhost's documentroot) Add Comment Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You 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
Jira (PUP-3248) Update PMT tests for directory environment support
Title: Message Title Joshua Partlow commented on an issue Re: Update PMT tests for directory environment support Merged to stable in 9e5b0f4 Add Comment Puppet / PUP-3248 Update PMT tests for directory environment support Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. 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-3248) Update PMT tests for directory environment support
Title: Message Title Joshua Partlow commented on an issue Re: Update PMT tests for directory environment support But I've hit some conflicts merging down to pe-puppet 3.4.x. I'm away this weekend, will need to look into it Monday morning. Add Comment Puppet / PUP-3248 Update PMT tests for directory environment support Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. 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-3277) Fix up PE Puppet Acceptance Tests
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3277 Fix up PE Puppet Acceptance Tests Change By: Joshua Partlow Assignee: JoshuaPartlow 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 Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Joshua Partlow Assignee: JoshuaPartlow 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
Joshua Partlow commented on an issue
Re: Puppet resource broken when directory environments enabled
I've reproduced this as well:
jpartlow@percival:~/work/puppet$ be puppet resource file /tmp/bar ensure=directory source=/tmp/foo recurse=true
Warning: hi
Error: /File[/tmp/bar]: Failed to generate additional resources using 'eval_generate': Could not find a directory environment named 'none' anywhere in the path: /home/jpartlow/.puppet/environments. Does the directory exist?
Error: /File[/tmp/bar]: Could not evaluate: Could not retrieve file metadata for file:/tmp/foo: Could not find a directory environment named 'none' anywhere in the path: /home/jpartlow/.puppet/environments. Does the directory exist?
Wrapped exception:
Could not find a directory environment named 'none' anywhere in the path: /home/jpartlow/.puppet/environments. Does the directory exist?
Error: Could not run: Could not retrieve file metadata for file:/tmp/foo: Could not find a directory environment named 'none' anywhere in the path: /home/jpartlow/.puppet/environments. Does the directory exist?
Wrapped exception:
Could not find a directory environment named 'none' anywhere in the path: /home/jpartlow/.puppet/environments. Does the directory exist?
A straight apply succeeds.
jpartlow@percival:~/work/puppet$ be puppet apply -e file { '/tmp/bar': ensure = directory, source = '/tmp/foo', recurse = true }
Notice: Compiled catalog for percival.corp.puppetlabs.net in environment production in 0.09 seconds
Notice: /Stage[main]/Main/File[/tmp/bar]/ensure: created
Notice: /Stage[main]/Main/File[/tmp/bar/thing.txt]/ensure: defined content as '{md5}764efa883dda1e11db47671c4a3bbd9e'
Notice: Finished catalog run in 0.12 seconds
It's failing in the Puppet::Resource.indirection.save call: https://github.com/puppetlabs/puppet/blob/stable/lib/puppet/application/resource.rb#L218 I haven't dug into the indirector to see exactly what's going on. But the 'none' environment is most likely Puppet::Node::Environment::NONE, which is the default for a Catalog.
Add Comment
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Joshua Partlow 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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Joshua Partlow Fix Version/s: 3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-252) Spec jobs should run from an artifact of checked out code rather than each one hitting Github.
Title: Message Title Joshua Partlow commented on an issue Re: Spec jobs should run from an artifact of checked out code rather than each one hitting Github. This work is not done. It could certainly be absorbed by a QENG ticket. Roger Ignazio I didn't see one for this task in particular. We could also consider just closing this, since one incentive was to minimize number of times hitting Github directly. Although, being able to run the full pipeline from a stored artifact might still be a worthwhile goal. Add Comment Puppet / PUP-252 Spec jobs should run from an artifact of checked out code rather than each one hitting Github. So, probably github should point to a jenkin's job that tar's up a single checkout, saves it as an artifact and flicks the first spec matrix job, which uses the artifact to run the tests (and then cascades on to solaris, windows...assuming those still need to be separate because of different script requirements). 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,
Jira (PUP-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3150 config_version setting in environment.conf uses relative pathing Change By: Joshua Partlow Component/s: DOCS 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-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title
Joshua Partlow commented on an issue
Re: config_version setting in environment.conf uses relative pathing
Talked with Andy about this for a bit this morning. We think the config_version should remain relative so that config_version scripts can be referenced within their environment without needing to know the absolute path to the environment. But it would make sense to update the docs for environment.conf config_version to point out that you will need to provide an absolute path to a system binary, or wrap it in a local script. Just something to help people who are trying a call like the git rev-parse mentioned in the description and are scratching their heads over why it's failing. (Though, actually, the error message is pretty straight-forward for once (Ping Nicholas Fagerlund)
Add Comment
Puppet / PUP-3150
config_version setting in environment.conf uses relative pathing
If directory environments are configured, and you create an environment.conf in an environment, and you set the config_version parameter using a command that doesn't include the full path to the binary in question, such as: {noformat} config_version = 'git --git-dir $confdir/environments/$environment/.git rev-parse HEAD' {noformat} Puppet will att...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3150 config_version setting in environment.conf uses relative pathing Change By: Joshua Partlow Fix Version/s: 3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-252) Spec jobs should run from an artifact of checked out code rather than each one hitting Github.
Title: Message Title Joshua Partlow commented on an issue Re: Spec jobs should run from an artifact of checked out code rather than each one hitting Github. Roger Ignazio Ya, I think this approach is fine given that we're cloning from an internal mirror. I will close this. Add Comment Puppet / PUP-252 Spec jobs should run from an artifact of checked out code rather than each one hitting Github. So, probably github should point to a jenkin's job that tar's up a single checkout, saves it as an artifact and flicks the first spec matrix job, which uses the artifact to run the tests (and then cascades on to solaris, windows...assuming those still need to be separate because of different script requirements). 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 (HI-289) automate basic functionality acceptance tests
Title: Message Title Joshua Partlow commented on an issue Re: automate basic functionality acceptance tests Britt Gresham This ticket was pulled into the current sprint during our meeting this morning about Hiera testing. Eric Thompson has been preparing a set of test cases for hiera in testrail: https://testrail.ops.puppetlabs.net/index.php?/suites/overview/3 One of the things we discussed was the need to review the changes in this PR with an eye towards whether they were duplicating coverage in specs, or providing new coverage or enhancing coverage from a user (rather than a component) perspective. This would be part of the initial auditing of existing hiera test coverage in the context of the above proposed testrail cases. (Please correct me as needed, Eric, I just wanted to give Britt some context 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
Jira (PUP-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:* -- OSX -- *Windows2008/2012(MSIinstallx86x64)*--Anything(Geminstall):onrhel7--Smoketestprocedure:*Start/stop/restartanagent(Windows)*Help/man(All)*Writeandrunsomemanifests(All) 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-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. Smoketestplatforms: *OSX *Windows2008/2012(MSIinstallx86x64) * -- Anything(Geminstall) :onrhel7-- Smoketestprocedure: *Start/stop/restartanagent(Windows) *Help/man(All) *Writeandrunsomemanifests(All) 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-3214) Smoke test packages
Title: Message Title
Joshua Partlow commented on an issue
Re: Smoke test packages
Gem on RHEL7 seems fine:
wget http://builds.puppetlabs.lan/puppet/3.7.1/artifacts/puppet-3.7.1.gem
gem install puppet-3.7.1.gem
puppet --version
puppet help
puppet apply -e notify { hello: }
puppet resource group puppet ensure=present
puppet resource user puppet ensure=present groups=puppet
puppet master --autosign true --certname localhost
puppet agent -t --server localhost
Add Comment
Puppet / PUP-3214
Smoke test packages
Procedure may vary by project
Jira (PUP-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Fix Version/s: 4.0.0 Fix Version/s: 3.7.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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Flagged: Impediment 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Sprint: 2014-09-17 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Kurt Wall I think you caught a case that Henrik Lindberg and I discussed, and which I forgot to record or implement. What we discussed was adding a Puppet::Node::Environment#valid? which would handle both the conflicting_manifest_settings? check and any additional 'is this environment okay' tests such as looking for $environment in base settings. This would be used in the Puppet::Parser::Compiler.compile call to halt compilation with a more informative message. The current behavior won't allow a bad agent run to happen, since it can't find the environment in the bad environmentpath. But the message is potentially confusing. We specifically decided not to halt puppet initialization for $environment interpolation, even on key settings like environmentpath/basemodulepath, because rack error messages are semi-incomprehensible. Andy has already suggested a ticket for a 3.7.2. This could be added to that or be a 4.0 enhancement. Opinions? Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin...
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 Joshua Partlow created an issue Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Issue Type: Improvement Affects Versions: 3.7.1 Assignee: Andy Parker Components: DSL Created: 12/Sep/14 1:46 PM Priority: Normal Reporter: Joshua Partlow 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 environmentpath or basemodulepath having been set with a $environment in them. This interpolation was disallowed in PUP-3162 , and we log a warning if it's encountered, but do not stop the master from initializing. As Kurt pointed out in PUP-3162
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 Joshua Partlow updated an issue Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Joshua Partlow Fix Version/s: 3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2651) Loading facts happens twice when environmentpath is in then main section of puppet.conf
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2651 Loading facts happens twice when environmentpath is in then main section of puppet.conf Change By: Joshua Partlow Fix Version/s: 3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow commented on an issue Re: Remove 1.8.7 multibyte string support in Lexer2 Merged to puppet-4 branch in 7b871c00 Add Comment Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 There is support for Ruby 1.8.7 multibyte strings in the Lexer. Since Suport for Ruby 1.8.7 is being dropped for 4.0 (PUP-1805). This logic can be removed. 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Flagged: Impediment 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-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Sprint: 2014-09-17 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-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Assignee: JoshuaPartlow 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 Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow commented on an issue Re: In Puppet Gemfile, allow env var to indicate Puppet is already on load path Merged to stable in cdd5cec Add Comment Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Additional acceptance test fix in 88a8774 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Joshua Partlow assigned an issue to Henrik Lindberg Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Joshua Partlow Assignee: JoshuaPartlow HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Change By: Joshua Partlow Assignee: BrittGresham JoshuaPartlow 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 Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Joshua Partlow Assignee: JoshuaPartlow 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 Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Merged to stable in 00f5a9a 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-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Joshua Partlow commented on an issue Re: Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory New PR-3075 rebased on stable. 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 emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title
Joshua Partlow commented on an issue
Re: each no longer supported in Puppet 3.7.0
Merged to stable in 4dd82d
Add Comment
Puppet / PUP-3190
each no longer supported in Puppet 3.7.0
After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the each keyword. It prints this in the log: {noformat} Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se {noformat} The /etc/puppet/puppet.conf on the puppetmaster host looks ...
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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Joshua Partlow Component/s: DOCS 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Talking with Andy and Henrik this morning, we're considering changing to a whitelist of settings we allow $environment to be interpolated in, rather than proscribing a few specific settings. At the moment, the only setting we can think of that you ought to be able to interpolate $environment in when using directory environments is: config_version Can anyone think of any others? Eric Sorenson Nicholas Fagerlund Any thoughts on this? We also agreed that we don't want to halt the puppetmaster on startup, because of how difficult it is to trace the error in a passenger setup (due to the html rack error response). Henrik brought up the idea of returning an invalid environment (perhaps with a single manifest that fails compilation) if the environment settings are misconfigured? Still need to think that idea through. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin...
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Nicholas Fagerlund If we go with a whitelist, then based on our current list of settings, only config_version would allow interpolation of $environment. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... 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
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Henrik Lindberg an environment name like 'what$environment' is invalid; it will be rejected both by the network routing, and will be ignored (if you had a directory 'what$environment' in your $environmentpath) by the Directories environment loader. Are there other criteria that you would consider to make an environment 'invalid' as we were discussing at standup? Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Henrik Lindberg I agree that those would be invalid environments, but I think those cases are separate from this ticket. Other than flipping to a whitelist of config_version and removing the halt on default_manifest being set with $environment in it, is there anything you think needs adding. If I made those changes, Puppet would log a warning, not interpolate but otherwise proceed for any setting that has an $environment set in it (other than config_version). Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (PUP-3225) Remove legacy and dynamic environment support.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3225 Remove legacy and dynamic environment support. Issue Type: Improvement Assignee: Andy Parker Components: DOCS, Modules Created: 09/Sep/14 4:59 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Joshua Partlow Legacy and dynamic environments are deprecated, but support has not yet been removed. We can't remove manifest/modulepath/config_version settings, because they are still parsed in environment.conf, but we should raise an error? if they are found in puppet.conf. Legacy loaders should be removed. Puppet::Node::Environment should get cleanup for code paths related to legacy environment creation. Undoubtedly other things I'm forgetting about. Andy Parker I didn't see a ticket for this when I browsed the 4.0 stack; might have missed it though. Add Comment
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Joshua Partlow commented on an issue
Re: Non-existent directory environments should raise a helpful error
I think this is a combination of special setup for PE and the default production environment having a blessed status required for bootstrapping, but will need to investigate.
Add Comment
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
If in puppet.conf I have: {noformat} [main] basemodulepath = /etc/puppetlabs/puppet/modules environmentpath = /etc/puppetlabs/puppet/envs {noformat} and if /etc/puppetlabs/puppet/modules/test/manifests/init.pp exists with `class test { }` in it, and if /etc/puppetlabs/puppet/envs/production does not exist, when I run {{puppet agent -t}} I get {{Erro...
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
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings New PR 3065 takes the whitelist approach and removes the early validation of default_manifest that would halt puppet startup in 3.7.0. Sorry for the churn on that later piece Nicholas Fagerlund; predocs have been updated. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... 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
Jira (PUP-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Joshua Partlow Assignee: JoshuaPartlow 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 Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3177) Resource titles ending with square brackets fail
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3177) Resource titles ending with square brackets fail
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3107) Go/no-go meeting
Title: Message Title Joshua Partlow commented on an issue Re: Go/no-go meeting Thumbs up Add Comment Puppet / PUP-3107 Go/no-go meeting Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: * Smoke testing 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-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Issue Type: Bug Assignee: Unassigned Created: 04/Sep/14 3:38 PM Priority: Normal Reporter: Joshua Partlow PUP-2519 changed the settings catalog to create the default directory environment. Franz Pletz noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You end up with a cryptic error message thrown back by rack, whenever a master process is started (in response to an agent run's requests, for instance): [ 2014-09-04 18:54:04.4660 11287/7f0691bfb700 Pool2/Implementation.cpp:883 ]: Could not spawn process for group /etc/puppet/rack#default: An error occured while starting up the preloader. in 'void Passenger::ApplicationPool2::SmartSpawner::handleErrorResponse(Passenger::ApplicationPool2::SmartSpawner::StartupDetails)' (SmartSpawner.h:455) in 'std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails)' (SmartSpawner.h:566) in 'void Passenger::ApplicationPool2::SmartSpawner::startPreloader()' (SmartSpawner.h:206) in 'virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options)' (SmartSpawner.h:752) in 'void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const SpawnerPtr, const Passenger::ApplicationPool2::Options, unsigned int)' (Implementation.cpp:804)
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Change By: Joshua Partlow Affects Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow commented on an issue Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. One possibility here is to further test that the first directory in environmentpath is writable? before attempting to creation the production directory environment. Add Comment Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You 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
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow commented on an issue Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. It is strange, and it should be irrelevant, but atm puppet always runs with some initial environment At the time we bootstrap the settings environment though, we don't know what run_mode we are in. Add Comment Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You 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
Jira (PUP-3047) Validate Puppet -x64-mingw32 gem dependencies on x64
Title: Message Title Joshua Partlow commented on an issue Re: Validate Puppet -x64-mingw32 gem dependencies on x64 The spec changes (the work not put off for 3.7.1) looks to have been made in 6cf22c5d16aea3c6c42b0e1bbb74d3e9990d34d1 as part of PUP-2889 . Add Comment Puppet / PUP-3047 Validate Puppet -x64-mingw32 gem dependencies on x64 Ensure that * We release a mingw x64 gem that includes appropriate dependencies * That all of the expected dependencies resolve correctly (necessary for other things that depend on puppet gem, such as current module testing) 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-3100) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Joshua Partlow commented on an issue Re: Is there a commit for every JIRA ticket targeted at the release? All issues not associated with a git commit accounted for below: ISSUES NOT FOUND IN GIT ( PUP-229 ) : Actually merged as (PUP 229) ( PUP-390 ) : puppet_for_the_win ( PUP-511 ) : puppet-specifications ( PUP-516 ) : WONTFIX ( PUP-850 ) : Deprecation epic, not specificially referenced, but all children resolved/closed (PUP-1493) : WONTFIX ( PUP-1760 ) : Win32-Security ( PUP-1773 ) : WONTFIX ( PUP-1775 ) : WONTFIX ( PUP-1782 ) : WONTFIX ( PUP-1808 ) : WONTFIX ( PUP-1874 ) : No code changes; only documentation updates ( PUP-1900 ) : DUPLICATE ( PUP-2357 ) ( PUP-2034 ) : WONTFIX ( PUP-2046 ) : WONTFIX ( PUP-2251 ) : WONTFIX ( PUP-2252 ) : WONTFIX ( PUP-2276 ) : No code changes; need for tests covered by other work ( PUP-2286 ) : DUPLICATE ( PUP-1782 ) ( PUP-2383 ) : No code changes; Windows, infra, tooling change (
Jira (PUP-3099) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3099 Is there a JIRA ticket targeted at the release for every commit? Change By: Joshua Partlow Attachment: puppet-3.7.0-github-reconcile.txt 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-3099) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Joshua Partlow commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? So only three commits need to be called out for clarification: These two are a (packaging) change for RPMS in the ext data: PR-2621 - Does not follow convention. Missing Jira Ticket. fb5bd35: Previously, RPMS built on Amazon Linux would point to the improper ruby directory, or would have improper dependencies. f1e7d2c: Changes for azn-linux This is actually PUP-2912 : PR-2854 - Mislabeled in commit. Should be PUP-2912 instead of PE-2912 2b76f86: (PE-2912) Error on symlink in module install Add Comment Puppet / PUP-3099 Is there a JIRA ticket targeted at the release for every commit?
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb PE depends on puppetdb, and runs this same suite. 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 Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Well, the test isn't confined to foss; it will run in either puppet or pe-puppet acceptance runs. I think we'll need a different package. 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
Jira (PUP-3101) Update version number in source
Title: Message Title
Joshua Partlow commented on an issue
Re: Update version number in source
Puppet stable updated to 3.7.0, merged from master in 1681684857c6e39d60d87b0b3520d8783977ceff
Add Comment
Puppet / PUP-3101
Update version number in source
Bump VERSION in lib/{#project}/version.rb to correct version. * Commit the updated version file. * e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3-rc1. * If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). * Once this is done, hand the SHA to be built to RelEng to be tag...
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-3098) Is the code ready for release?
Title: Message Title Joshua Partlow commented on an issue Re: Is the code ready for release? Still waiting for a green stable run post merge down of master. Add Comment Puppet / PUP-3098 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... 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-3102) Merge master into stable
Title: Message Title
Joshua Partlow commented on an issue
Re: Merge master into stable
Master merged to stable in 1681684. Roger is working on updating stable ci.
Add Comment
Puppet / PUP-3102
Merge master into stable
For some releases, the code base will need to be merged down to stable. *NOTE:* This is usually only during a x.y.0-rc1 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: {noformat} git fetch up...
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-3105) Tag the release and create packages
Title: Message Title Joshua Partlow commented on an issue Re: Tag the release and create packages Updated version.rb to 3.7.0 in 038d76e. Merged to stable in 1681684 Add Comment Puppet / PUP-3105 Tag the release and create packages Tag and create packages * Developer provides the SHA - [~joshua.partlow] - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb) * checkout the sha * NOTE: If this is a final release, make sure you're releasing only the code that already went through rc, so don't let any new code get into the fina... 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-3103) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3103 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Joshua Partlow ThishappensonJira-weneedtocleanupthecurrentreleaseandprepareforthenextrelease. *Marktheversionthat'sgoingoutasReleasedintheProjectAdmin-Versionspanel. *Createaversionwecantargetfutureissuesorissuesthatdidn'tmakeitintothecurrentrelease.(e.g.ifwe'rereleasingFacter1.7.4,makesurethere'sa1.7.5version(oratleast1.7.xifthere'sisn'tanotherbugreleaseplannedforthenearfuture) *Createapublicpairofqueriesforinclusioninthereleasenotes/announcement.Thesealloweasytrackingasnewbugscomeinforaparticularversionandalloweveryonetoseethelistofchangesslatedforthenextrelease(PastetheirURLsintotheReleasestoryticket): -'project=XXANDaffectedVersion='X.Y. Y Z ',SaveasIntroducedinX.Y. Y Z ,clickDetails,addpermissionforEveryone -'project=XXANDfixVersion='X.Y.Z',SaveasFixesforX.Y.Z,clickDetails,addpermissionforEveryone 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-3104) Prepare long form release notes and short form release story
Title: Message Title Joshua Partlow commented on an issue Re: Prepare long form release notes and short form release story Jira queries for bug tracking: Introduced in 3.7.0 : https://tickets.puppetlabs.com/issues/?filter=12641 Fixes in 3.7.0 : https://tickets.puppetlabs.com/issues/?filter=12643 Add Comment Puppet / PUP-3104 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release? 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
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3106 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). IfthisisafinalreleasethenthepreviousRC(whichshouldbeidenticaltowhatiscurrentlybeingreleased)willhavegonethroughthistesting.Lightertestingisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure. Example: Smoketestplatforms: * picksomeplatformssuchas*RHEL5/6/7*CentOS5/6* Windows2003/2008/2012 * Debian6/7/ OSX-dmgpackages * Ubuntu10.04/12.04/14.04 gems Smoketestprocedure: *Start/stop/restartamasterwiththeinitscripts(onDebiantrythepassengermaster) *Start/stop/restartanagent *Help/man *Writeandrunsomemanifests Dependencies: *Tagandcreatepackages *ForWindowsMSIs-Pushtag Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3106 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).IfthisisafinalreleasethenthepreviousRC(whichshouldbeidenticaltowhatiscurrentlybeingreleased)willhavegonethroughthistesting.Lightertestingisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Smoketestplatforms:* -- Windows 2008R2x64-- 2003/2008/2012 *OSX-dmgpackages*gemsSmoketestprocedure:* Start Forel / stop/restartamasterwiththeinitscripts(onDebiantrythepassengermaster) deb,weprobablyonlyneedtocheck * Start/stop/restartanagent *Help/man* Otherpackageformats(msi,dmg,gems)** WriteandrunsomemanifestsDependencies:*Tagandcreatepackages*ForWindowsMSIs-Pushtag Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3106 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).IfthisisafinalreleasethenthepreviousRC(whichshouldbeidenticaltowhatiscurrentlybeingreleased)willhavegonethroughthistesting.Lightertestingisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.* IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.* Whenallplatformspickedhavebeensmoketested,movethistickettodone.IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Smoketestplatforms:*Windows2003/2008/2012*OSX-dmgpackages*gemsSmoketestprocedure:*Forel/deb,weprobablyonlyneedtocheck**Help/man*Otherpackageformats(msi,dmg,gems)**WriteandrunsomemanifestsDependencies:*Tagandcreatepackages *ForWindowsMSIs-Pushtag 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
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Testing gem on rhel7 Add Comment Puppet / PUP-3106 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through... 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-3106) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3106 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).IfthisisafinalreleasethenthepreviousRC(whichshouldbeidenticaltowhatiscurrentlybeingreleased)willhavegonethroughthistesting.Lightertestingisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Smoketestplatforms:*--Windows2008R2x64,bothx86andx64MSIs--*--Windows2008R2,gemsforx86andx64underRuby1.9.3andRuby2.0.0respectively--*OSX-dmgpackages*gems **--gemonrhel7-- Smoketestprocedure:*Forel/deb,weprobablyonlyneedtocheck**Help/man*Otherpackageformats(msi,dmg,gems)**WriteandrunsomemanifestsDependencies:*Tagandcreatepackages 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
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Peter did a deb test on precise. Add Comment Puppet / PUP-3106 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through... 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-3106) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Kurt checked out the Apple dmg Add Comment Puppet / PUP-3106 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through... 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-3106) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3106 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).IfthisisafinalreleasethenthepreviousRC(whichshouldbeidenticaltowhatiscurrentlybeingreleased)willhavegonethroughthistesting.Lightertestingisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Smoketestplatforms:*--Windows2008R2x64,bothx86andx64MSIs--*--Windows2008R2,gemsforx86andx64underRuby1.9.3andRuby2.0.0respectively--* -- OSX-dmgpackages -- *gems**--gemonrhel7-- **--gemonsolaris11-- Smoketestprocedure:*Forel/deb,weprobablyonlyneedtocheck**Help/man*Otherpackageformats(msi,dmg,gems)**WriteandrunsomemanifestsDependencies:*Tagandcreatepackages 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
Jira (PUP-3106) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages EricT tested gem on solaris11 Add Comment Puppet / PUP-3106 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through... 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 Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Sure, I like rabbits 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 Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3032) Setting to cache `load_library` failures
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Joshua Partlow Assignee: JoshuaPartlow 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.
