Jira (PUP-4294) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg commented on PUP-4294 Re: Is there a JIRA ticket targeted at the release for every commit? Verified with https://github.com/puppetlabs/ticketmatch COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF PUP 4.0.0) #21272 – Redmine ticket in Jira as PUP-3124 CODEMGMT-69 – acceptance test change PUP-1343 – Originally fixed in 3.7.4 (with a different SHA) PUP-1680 – Originally fixed in 3.7.1 (with a different SHA) PUP-2351 – Typo, actually PUP-2531 PUP-2402 – acceptance test change PUP-2702 – Won't Fix (was committed and reverted) PUP-2914 – Originally fixed in 3.7.0 (with an acceptance test followup in master) PUP-2916 – Originally fixed in 3.7.5 (with a different SHA) PUP-3057 – acceptance test change PUP-3151 – acceptance test change PUP-3157 – acceptance test change PUP-3244 – Originally fixed in 3.7.2 (with a different SHA) PUP-3277 – acceptance test change PUP-3391 – Typo, actually PUP-3591 PUP-3468
Jira (PUP-3801) HP-UX User Provider not resetting password expiration after changing password hash.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3801 HP-UX User Provider not resetting password expiration after changing password hash. Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3702) zone provider should inherit /sbin on solaris10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3702 zone provider should inherit /sbin on solaris10 Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3697) Default key to certname for find action in indirector based faces
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3697 Default key to certname for find action in indirector based faces Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3604) Puppet fails to install correct package when 'ensure => $version' is set
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3604 Puppet fails to install correct package when 'ensure => $version' is set Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3481) Regex problem with an SELinux context type with a dash
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3481 Regex problem with an SELinux context type with a dash Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2929) Optimize the (function) loader
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2929 Optimize the (function) loader Change By: Kylo Ginsberg Fix Version/s: PUP 4.1.0 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2916) yumrepo fails to honour custom reposdir
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2916 yumrepo fails to honour custom reposdir Change By: Kylo Ginsberg Fix Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2706 Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4295) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on PUP-4295 Re: Is there a commit for every JIRA ticket targeted at the release? Verified with https://github.com/puppetlabs/ticketmatch: ALL ISSUES WERE FOUND IN GIT Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4297) Merge master into stable
Title: Message Title Kylo Ginsberg commented on PUP-4297 Re: Merge master into stable N/A. This happened earlier. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2307) Solaris acceptance tests assume puppet is on the path
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2307 Solaris acceptance tests assume puppet is on the path Change By: Kylo Ginsberg Security: Internal Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-759) Can not get ec2 facter with non-root user on FreeBSD
Title: Message Title thisisnoman commented on FACT-759 Re: Can not get ec2 facter with non-root user on FreeBSD Can access http://169.254.169.254:80 with non-root , but still unable to get ec2 facter with non-root Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4381) Array operators ending in ! in .erb templates modify puppet variables
Title: Message Title
Aaron Hicks created an issue
Puppet / PUP-4381
Array operators ending in ! in .erb templates modify puppet variables
Issue Type:
Bug
Affects Versions:
PUP 3.7.4
Assignee:
Unassigned
Components:
Language
Created:
2015/04/06 9:53 PM
Environment:
all environments
Priority:
Normal
Reporter:
Aaron Hicks
If an .erb template uses an array method that modifies the array itself (i.e. one ending with !), rather than creating a new instance of a modified array, then these changes are propagated back into the variable in puppet.
For example:
subjectAltName = "<%= @aliases.collect! {|i| "
Jira (PUP-4344) Add test(s) for the File resource manage_symlinks attribute
Title: Message Title Michael Smith updated an issue Puppet / PUP-4344 Add test(s) for the File resource manage_symlinks attribute Change By: Michael Smith Summary: Add test(s) for the File resource mange_symlinks manage_symlinks attribute Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-904) Facter does not load external facts in the order of the search directories
Title: Message Title Michael Smith assigned an issue to Unassigned Facter / FACT-904 Facter does not load external facts in the order of the search directories Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title
Ryan Gard commented on PUP-1279
Re: Windows Group and User fail during deletion even though it is successful
Verified as fixed in SHA b301505df2e13204ee408a05588e225fdffeacb6 on Windows 2012 R2 x64, Windows 2008 R2 x64 and Windows 2003 R2 x64. (See above comments for work-a-round on Windows 2003)
Reproduction Steps
Install Puppet and Windows node.
Add a user with Puppet:
puppet apply -e "user { 'foobars': ensure => present, managehome => true, password => 'admin123!!' }"
Verify that user "foobars" was added via the Computer Management control panel.
Remove user with Puppet:
puppet apply -e "user { 'foobars': ensure => absent, managehome => true, password => 'admin123!!' }"
Verify that user "foobars" was removed via the Computer Management control panel.
Add a user with Puppet:
puppet apply -e "user { 'foobars': ensure => present, managehome => true, password => 'admin123!
Jira (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title
John Duarte commented on PUP-4203
Re: Add ':uninstall_options' to gem provider
Validated with a pre-release version of puppet-agent
The following session shows the installation of the rake gem along with its dependencies. Then rake is removed with the uninstall_option attribute, successfully leaving the dependencies in place.
[root@xct8v90ltnnff1f ~]# /opt/puppetlabs/bin/puppet -V
4.0.0-rc2
[root@xct8v90ltnnff1f ~]# ls /usr/lib/ruby/gems/1.8/gems/
builder-2.1.2 nokogiri-1.5.2 nokogiri-1.5.9 rbvmomi-1.5.1 trollop-1.16.2
[root@xct8v90ltnnff1f ~]# /opt/puppetlabs/bin/puppet resource package trollop
package { 'trollop':
ensure => ['1.16.2'],
}
[root@xct8v90ltnnff1f ~]# /opt/puppetlabs/bin/puppet apply -e "package{ 'rack': provider => 'gem', }"
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Eric Sorenson Business Value: 452 Epic Name: Move non-core T/P to modules Epic Status: To Do Workflow: Scrum Team Engineering Epic Workflow Issue Type: Bug Epic Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Issue Type: Bug Assignee: Unassigned Created: 2015/04/06 5:13 PM Priority: Normal Reporter: Eric Sorenson To reduce the surface area of puppet itself and increase maintainability of non-core puppet, things which can be split out from it should be. Prime examples include the Nagios types (Redmine #4146 / PUP-1077) and some of the more esoteric single-OS types/providers like solaris zpools. These could still be combined at packaging time but the puppet repository itself would not contain them. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title Kylo Ginsberg commented on PUP-4203 Re: Add ':uninstall_options' to gem provider John Duarte this was mistakenly marked as Fixed in 4.1.0 but actually is in 4.0.0. You may have already verified this in the course of verifying PUP-4237 . Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title Kylo Ginsberg assigned an issue to QA Puppet / PUP-4203 Add ':uninstall_options' to gem provider Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: Melissa Stone QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4203) Add ':uninstall_options' to gem provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4203 Add ':uninstall_options' to gem provider Change By: Kylo Ginsberg Fix Version/s: PUP 4.1.0 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-909) Speed up type inference
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-909 Speed up type inference Change By: Kylo Ginsberg Fix Version/s: PUP 4.1.0 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4366) Test FOSS upgrade from 3.x to 4.0 using packages
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4366 Test FOSS upgrade from 3.x to 4.0 using packages Change By: Eric Thompson Perform exploratory testing of upgrading from 3.x installations to 4.0.0 using packages. Someone will try this in the wild, so it will be valuable to know in a general sense what happens.[~eric.sorenson] noted that there are "post-install scripts that preserve your local config changes and certs" [~josh] later noted that this functionality will not work for GA, but that if we move the certs and configuration files (or link them?) it should work... Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Josh Cooper Rob Reynolds I have tested this against Windows 2008 R2 x64 and not seen the same issue. I'll test with Windows 2012 R2 x64 now. If it passes with 2012 then I will mark this ticket as "Ready for Review", sound reasonable? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4379) Future parser issue with hash in a variable prefixed with an underscore
Title: Message Title
Morgan Haskel created an issue
Puppet / PUP-4379
Future parser issue with hash in a variable prefixed with an underscore
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Created:
2015/04/06 4:45 PM
Priority:
Normal
Reporter:
Morgan Haskel
When a variable containing a hash has a name prefixed with an underscore:
$_foo = {
'a' => 'b',
}
notify { "${_foo['a']
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Melissa Stone updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Melissa Stone Fix Version/s: PUP 4.x Fix Version/s: PUP 4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4377) Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval
Title: Message Title Ryan Gard commented on PUP-4377 Re: Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval Rob Reynolds The task is created in the GUI, but the repeat check box is not checked. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4366) Test FOSS upgrade from 3.x to 4.0 using packages
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4366 Test FOSS upgrade from 3.x to 4.0 using packages Change By: Eric Thompson Perform exploratory testing of upgrading from 3.x installations to 4.0.0 using packages. Someone will try this in the wild, so it will be valuable to know in a general sense what happens. [~eric.sorenson] noted that there are "post-install scripts that preserve your local config changes and certs" Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4377) Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval
Title: Message Title Rob Reynolds commented on PUP-4377 Re: Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval Ryan Gard What is the result of this? As far as the GUI. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Melissa Stone commented on PUP-1931 Re: mount provider improvement when options property is not specified Though `defaults` is useful to add in, I'm not sure it's strictly necessary. It seems the fstab entry without any options specified is still a valid entry. Mount can parse it and error out just as it does when `defaults` is there. From talking this over with Branan Riley, it seems like creating an fstab entry with an empty options field is totally valid, even though it's not mountable. The error that it throws, that Kylo Ginsberg posted earlier, is the error expected from trying to mount that entry. Having the unmountable entry doesn't produce any errors during reboot, expect that one filesystem fails to mount, which is expected (at least on centos 6). Talking this over with Geoff Nichols and Rob Braden, it does seem like the expected behavior should be to have options default to `defaults` if we're on a linux kernel and nothing was specified. This should fix errors in the majority of cases except when the user specifies a mount type that requires additional options (like loop). In this case, mount will fail with errors like the one above, which are totally expected for this situation. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title
Nicholas Fagerlund commented on PUP-4378
Re: Resource collectors can be assigned to variables by abusing chaining statements
Also I have a function that goes like this:
Puppet::Parser::Functions::newfunction(:spew, :doc => "Dump an inspect of whatever we get.", :type => :rvalue) do |args|
#return args.inspect
return "#{args.inspect}\n#{args.collect {|thing| thing.class}.inspect}"
end
and if you feed $myweirdchain to THAT, it dumps basically the entire program state, afaict.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title
Nicholas Fagerlund created an issue
Puppet / PUP-4378
Resource collectors can be assigned to variables by abusing chaining statements
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Components:
Language
Created:
2015/04/06 3:53 PM
Priority:
Minor
Reporter:
Nicholas Fagerlund
The 4x parser generally refuses to produce values from resource collectors, and errors if you put one where a value is expected. But since the value of a chaining statement is just the final term of the statement (regardless of arrow direction) and they accept collectors as operands:
notify {"I go last.":}
$myweirdchain = (file {"/tmp/thing": ensure => file,}
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Rob Reynolds assigned an issue to Ryan Gard Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Rob Reynolds Assignee: Ethan Brown Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Rob Reynolds commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Ryan Gard can you verify this behavior on a non-Windows 2003 system? Note Josh's comments about expected behavior on 2003. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-933) Update CONTRIBUTING.md to talk about acceptable kinds of changes
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-933 Update CONTRIBUTING.md to talk about acceptable kinds of changes Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Josh Cooper commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful I believe the 2003 behavior is to be expected, because we don't have a way to delete the user profile on those systems. Note the user account is removed, just not the home directory, e.g. C:\Documents and Settings\foobars Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard assigned an issue to Ethan Brown Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ryan Gard Assignee: Ryan Gard Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title
Ryan Gard commented on PUP-1279
Re: Windows Group and User fail during deletion even though it is successful
Failed review on SHA b301505df2e13204ee408a05588e225fdffeacb6 running on Windows 2003 R2 x64:
ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32]
C:\Program Files (x86)\Puppet Labs\Puppet\bin>cd \
C:\>puppet apply -e "user { 'foobars': ensure => present, managehome => true, pa
ssword => 'admin123!!' }"
Notice: Compiled catalog for n3coozbsc3evgjm.delivery.puppetlabs.net in environm
ent production in 0.30 seconds
Notice: /Stage[main]/Main/User[foobars]/ensure: created
Notice: Finished catalog run in 0.73 seconds
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Kylo Ginsberg commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) This fix will be available in 4.0.0. I updated the Fix Version to note that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3829 pip package provider is broken on EL (where osfamily is RedHat) Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode
Title: Message Title Ryan Gard updated an issue Puppet / PUP-1291 scheduled_task : add support for "every X minutes or hours" mode Test manifests. Change By: Ryan Gard Attachment: scheduled_tasks_test.zip Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode
Title: Message Title Ryan Gard commented on PUP-1291 Re: scheduled_task : add support for "every X minutes or hours" mode Verified as working with SHA b301505df2e13204ee408a05588e225fdffeacb6. (Minor bug PUP-4377 found during functional review, but does not block this ticket.) Reproduction Steps Install Puppet on Windows node. Execute functional manifest: puppet apply test.pp Verify tasks created via "Scheduled Tasks" Control Panel. Execute clean-up manifest: puppet apply absent.pp Verify tasks removed via "Scheduled Tasks" Control Panel. Execute negative manifests (Starts with "fail_"): Verify that each manifest fails with a reasonable error message. (With the exception of "fail_duration_without_interval.pp" which is tracked by PUP-4377)
Jira (PDB-1348) PR (1324): (maint) Clean up BoneCP resources when finished - rbrw
Title: Message Title gepetto-bot commented on PDB-1348 Re: PR (1324): (maint) Clean up BoneCP resources when finished - rbrw pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1012/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4377) Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval
Title: Message Title Ryan Gard created an issue Puppet / PUP-4377 Creating Scheduled Task Succeeds when Specifying a Repetition Duration while Omitting Interval Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Unassigned Attachments: duration_without_interval.pp Components: Platform, Windows Created: 2015/04/06 3:05 PM Environment: Agent: Windows 2012 R2 Puppet SHA: b301505df2e13204ee408a05588e225fdffeacb6 Priority: Minor Reporter: Ryan Gard Description if a user creates a "scheduled_task" with the "minutes_duration" parameter, but omits the required "minutes_interval" parameter Puppet will successfully create the task.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Ryan Gard commented on PUP-3804 Re: User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message Kurt Wall Tag you're it! I'm swamped with r10k work and I don't have time to FR this ticket. The biggest impediment to FR for this is getting AD running, but I know Tony has some infrastructure available. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1410) Normalize release_notes.md
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1410 Normalize release_notes.md Issue Type: Improvement Assignee: Unassigned Created: 2015/04/06 2:47 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker Our release_notes.md require us to duplicate the upgrading section every time we do another z release, but by definition of a z release this section should change. It would be nice if our release notes looked more like https://docs.puppetlabs.com/release_notes/. Add Comment
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-3804 User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title
Kurt Wall commented on PUP-3804
Re: User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
I'm not sure if I've validated this or not.
# x.pp
user { "\\delivery.puppetlabs.net\\KurtWall":
ensure => present,
groups => 'Administrator',
}
C:\Program Files\Puppet Labs\Puppet\bin>puppet apply x.pp
Notice: Compiled catalog for jkoohkjkozqs1hp.delivery.puppetlabs.net in environm
ent production in 0.30 seconds
Error: Puppet is not able to create/delete domain users with the user resource.
Jira (PDB-1102) Upgrade to the latest ActiveMQ Jars
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1102 Upgrade to the latest ActiveMQ Jars Once PDB-1252 was merged, this was no longer blocked, and was easy to update/include. Change By: Rob Browning Sprint: PuppetDB 2015-01-28 , PuppetDB 2015-04-08 Scope Change Reason: Finishing PDB-1252 made it possible to finish this Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1393) PuppetDB 2.3.3 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1393 PuppetDB 2.3.3 Release Change By: Wyatt Alt Sprint: PuppetDB 2015-04-08 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Doug Rosser commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
From looking at the code of the provider at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/pip.rb, we're looking for "pip-python" and not "python-pip"
[root@rc-metrics opt]# ln -s /usr/bin/pip /usr/bin/pip-python
[root@rc-metrics opt]# pip-python --version
pip 1.5.6 from /usr/lib/python2.7/site-packages (python 2.7)
[root@rc-metrics opt]# puppet apply -e 'package {"s3cmd": ensure => installed, provider=>"pip"}'
Notice: Compiled catalog for rc-metrics.us-west-2.compute.internal in environment production in 0.26 seconds
Notice: /Stage[main]/Main/Package[s3cmd]/ensure: created
Notice: Finished catalog run in 2.15 seconds
Jira (PDB-1348) PR (1324): (maint) Clean up BoneCP resources when finished - rbrw
Title: Message Title gepetto-bot commented on PDB-1348 Re: PR (1324): (maint) Clean up BoneCP resources when finished - rbrw rbrw commented: @wkalt rebased. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Doug Rosser commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
Hrmmm. I could rely on the workaround for now, but even that doesn't seem to work...
[root@rc-metrics ~]# ls -l /usr/bin/python-pip
lrwxrwxrwx. 1 root root 12 Apr 6 20:46 /usr/bin/python-pip -> /usr/bin/pip
[root@rc-metrics ~]# puppet apply -e 'package {"s3cmd": ensure => installed, provider=>"pip"}'
Notice: Compiled catalog for rc-metrics.us-west-2.compute.internal in environment production in 0.28 seconds
Error: Could not set 'present' on ensure: Could not locate the pip command. in 1
Error: Could not set 'present' on ensure: Could not locate the pip command. in 1
Wrapped exception:
Could not locate the pip command.
Error: /Stage[main]/Main/Package[s3cmd]/ensure: change from absent to present failed: Could not set 'present' on ensure: Could not locate the pip command. in 1
Jira (PDB-1386) PR (1337): (maint) Support iterative acceptance test development - mullr
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1386 PR (1337): (maint) Support iterative acceptance test development - mullr Change By: Russell Mull Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1386) PR (1337): (maint) Support iterative acceptance test development - mullr
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1386 PR (1337): (maint) Support iterative acceptance test development - mullr Change By: Russell Mull Remaining Estimate: 4 minutes Original Estimate: 4 minutes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1386) PR (1337): (maint) Support iterative acceptance test development - mullr
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1386 PR (1337): (maint) Support iterative acceptance test development - mullr Change By: Russell Mull Remaining Estimate: 4 0 minutes Original Estimate: 4 0 minutes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Doug Rosser commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Sorry I didn't make it clear. Pip is definitely installed. [root@rc-metrics ~]# which pip /usr/bin/pip [root@rc-metrics ~]# pip --version pip 1.5.6 from /usr/lib/python2.7/site-packages (python 2.7) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, se
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Michael Stahnke commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Doug Rosser I think you still need to make sure pip is installed for the provider to work. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4237) Add puppet_gem provider for managing puppet-agent gems
Title: Message Title
John Duarte commented on PUP-4237
Re: Add puppet_gem provider for managing puppet-agent gems
Validated on centos-5-x86_64 with recent pre-release build of puppet-agent
Shell session below shows status query, install, and removal of package resource using the puppet_gem provider
[root@xct8v90ltnnff1f ~]# ls /opt/puppetlabs/puppet/lib/ruby/gems/2.1.0/gems/
deep_merge-1.0.0 net-ssh-2.1.4 rake-10.1.0 rdoc-4.1.0 stomp-1.3.3 test-unit-2.1.5.0
[root@xct8v90ltnnff1f ~]# /opt/puppetlabs/bin/puppet resource package deep_merge
package { 'deep_merge':
ensure => ['1.0.0'],
}
[root@xct8v90ltnnff1f ~]# /opt/puppetlabs/bin/puppet apply -e "package{ 'helloworld': provider => 'puppet_gem', }"
Notice: Compiled catalog for xct8v90ltnnff1f.delivery.puppetlabs.net in environment production in 0.77 seconds
Notice: /Stage[main]/Main/Package[helloworld]/ensure: created
Jira (PDB-1348) PR (1324): (maint) Clean up BoneCP resources when finished - rbrw
Title: Message Title gepetto-bot commented on PDB-1348 Re: PR (1324): (maint) Clean up BoneCP resources when finished - rbrw wkalt commented: @rbrw looks like this needs a rebase now Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4336) puppet apply --trace has stopped producing output
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4336 puppet apply --trace has stopped producing output Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4336) puppet apply --trace has stopped producing output
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4336 puppet apply --trace has stopped producing output Change By: Kurt Wall QA Contact: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Ryan Gard assigned an issue to Kurt Wall Puppet / PUP-3804 User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message Change By: Ryan Gard Assignee: Ryan Gard Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-904) Facter does not load external facts in the order of the search directories
Title: Message Title Peter Huene assigned an issue to Michael Smith Facter / FACT-904 Facter does not load external facts in the order of the search directories Change By: Peter Huene Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-904) Facter does not load external facts in the order of the search directories
Title: Message Title Peter Huene updated an issue Facter / FACT-904 Facter does not load external facts in the order of the search directories This bug was found while doing AIO work on Windows. It was minor and easily testable, so brought into the sprint to fix. Change By: Peter Huene Sprint: Client 2015-04-15 Scope Change Reason: Found during AIO work Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To po
Jira (PDB-1409) Improve updater handling
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1409 Improve updater handling Issue Type: Bug Assignee: Unassigned Created: 2015/04/06 12:41 PM Priority: Normal Reporter: Rob Browning Right now we just cancel the updater in services and move on. It might be worth at least waiting for it to finish[1], or we might want to consider using the related service[2]. [1] https://github.com/rbrw/puppetdb/commits/ticket/master/maint-always-stop-updater [2] https://github.com/puppetlabs/dujour-version-check Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1385) PR (1336): (maint) Test migration in a different schema - rbrw
Title: Message Title gepetto-bot commented on PDB-1385 Re: PR (1336): (maint) Test migration in a different schema - rbrw pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1010/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1408) Close all resolved tickets and release version in Jira
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1408 Close all resolved tickets and release version in Jira Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:31 PM Priority: Normal Reporter: Wyatt Alt Ensure all tickets that were previously resolved are marked now as closed. Ensure the version in Jira is released. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1392) PR (1340): (maint) Always stop updater, and wait for finish - rbrw
Title: Message Title gepetto-bot commented on PDB-1392 Re: PR (1340): (maint) Always stop updater, and wait for finish - rbrw Pull request (maint) Always stop updater, and wait for finish has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1407) Push changes to pe-puppetdb branch
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1407 Push changes to pe-puppetdb branch Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:30 PM Priority: Normal Reporter: Wyatt Alt These changes will need to be pushed to the relevant branch for pe-puppetdb Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1392) PR (1340): (maint) Always stop updater, and wait for finish - rbrw
Title: Message Title gepetto-bot commented on PDB-1392 Re: PR (1340): (maint) Always stop updater, and wait for finish - rbrw rbrw commented: @ajroetker ok, then I'm fine pulling this PR in favor of considering the broader issue. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1406) Send out announcements
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1406 Send out announcements Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:30 PM Priority: Normal Reporter: Wyatt Alt Send out the release notes in the release format on puppet-users, puppet-dev and puppet-announce. Obtain a bit.ly link to such a thing from marketing and twitter it out, and send a PSA message to IRC channels #puppet and #puppet-dev. Update our hipchat channel with the new link. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1405) Update the downloads page
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1405 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/04/06 12:30 PM Priority: Normal Reporter: Wyatt Alt Update the downloads page with the public download locations and new version information. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1403) Packages pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1403 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/04/06 12:29 PM Priority: Normal Reporter: Wyatt Alt Distribute the packages previously built into their public places. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received t
Jira (PDB-1404) Push tag
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1404 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/04/06 12:29 PM Priority: Normal Reporter: Wyatt Alt Push the tag made earlier up to the main public repo for the branch in question. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You rec
Jira (PDB-1402) Go/no-go meeting
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1402 Go/no-go meeting Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:29 PM Priority: Normal Reporter: Wyatt Alt Should include: dev, docs, product, qa, releng Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1401) Smoke test packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1401 Smoke test packages Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:28 PM Priority: Normal Reporter: Wyatt Alt Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1400) Tag the release and create packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1400 Tag the release and create packages Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/04/06 12:28 PM Priority: Normal Reporter: Wyatt Alt Developer provides the SHA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because
Jira (PDB-1399) Is there a commit for every bug targeted at the release?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1399 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:28 PM Priority: Normal Reporter: Wyatt Alt Ensure that all tickets targetted at this release have corresponding commits in git. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1398) Is there a bug targeted at the release for every commit?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1398 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:27 PM Priority: Normal Reporter: Wyatt Alt Ensure that all commits in git between the last and current release have corresponding tickets pointing at this release. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697{quote} # facter -v2.4.3 # cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core) & # 35; facter dhcp_serversError: NetworkManager is not running. # systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697{quote}# facter -v2.4.3# cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core)# facter dhcp_serversError: NetworkManager is not running.# systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697{quote} & # # 35; facter -v2.4.3 # cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core) # facter dhcp_serversError: NetworkManager is not running. # systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1397) Ensure tests are passing
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1397 Ensure tests are passing Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:27 PM Priority: Normal Reporter: Wyatt Alt All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1394) Is checklist current
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1394 Is checklist current Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:26 PM Priority: Normal Reporter: Wyatt Alt Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697{quote} # facter -v2.4.3 & # 35; cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core) # facter dhcp_serversError: NetworkManager is not running. & # 35; systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697{quote} # # facter -v2.4.3 # cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core) # facter dhcp_serversError: NetworkManager is not running. # systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1385) PR (1336): (maint) Test migration in a different schema - rbrw
Title: Message Title gepetto-bot commented on PDB-1385 Re: PR (1336): (maint) Test migration in a different schema - rbrw Pull request (maint) Test migration in a different schema has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1395) Update changelog/release notes
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1395 Update changelog/release notes Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:26 PM Priority: Normal Reporter: Wyatt Alt Update the changelog/release notes in documentation/changes.md Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1396) Update documentation indexes for new major release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1396 Update documentation indexes for new major release Issue Type: Sub-task Assignee: Unassigned Created: 2015/04/06 12:26 PM Priority: Normal Reporter: Wyatt Alt The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Ryan Power updated an issue
Facter / FACT-943
If NetworkManager is installed but not used facter throws a warning.
Change By:
Ryan Power
This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1.The original bug report is here:https://tickets.puppetlabs.com/browse/FACT-697 {quote} # facter -v2.4.3# cat /etc/redhat-releaseCentOS Linux release 7.1.1503 (Core)# facter dhcp_serversError: NetworkManager is not running.# systemctl status NetworkManager.serviceNetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) {quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1393) PuppetDB 2.3.3 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1393 PuppetDB 2.3.3 Release Issue Type: Task Assignee: Wyatt Alt Created: 2015/04/06 12:26 PM Priority: Normal Reporter: Wyatt Alt See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You receive
Jira (FACT-943) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title Ryan Power created an issue Facter / FACT-943 If NetworkManager is installed but not used facter throws a warning. Issue Type: Bug Affects Versions: FACT 2.4.3 Assignee: Unassigned Components: Community Created: 2015/04/06 12:23 PM Environment: CentOS 7 Priority: Normal Reporter: Ryan Power This bug appears to be reported and fixed for CentOS/RHEL 7.0, but not 7.1. The original bug report is here: https://tickets.puppetlabs.com/browse/FACT-697 facter -v 2.4.3 cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core)
Jira (PUP-4371) Smoke test mcollective on Puppet 4.0 AIO
Title: Message Title John Duarte commented on PUP-4371 Re: Smoke test mcollective on Puppet 4.0 AIO `mco ping` test fails fails to get respones on Windows 2012r2 ping statistics No responses received Ref: MCO-626 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1389) PuppetDB won't install alongside the puppet-agent on debian
Title: Message Title Michael Stahnke commented on PDB-1389 Re: PuppetDB won't install alongside the puppet-agent on debian Merged at https://github.com/puppetlabs/puppetdb/commit/ee6e9e95fba4179cea087a175d8a0d639f190932 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4336) puppet apply --trace has stopped producing output
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4336 puppet apply --trace has stopped producing output Change By: Kurt Wall Assignee: QA Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3166) Debian service provider on docker with insserv (dep boot sequencing)
Title: Message Title Eric Thompson commented on PUP-3166 Re: Debian service provider on docker with insserv (dep boot sequencing) cool. normally i'd say that if this were a regression candidate that we should write an acceptance test for this, but since we don't have docker infra, maybe not. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
