Jira (PUP-1904) Host resource type corrupts /etc/hosts
Title: Message Title Fabio Pugliese Ornellas created an issue Puppet / PUP-1904 Host resource type corrupts /etc/hosts Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 10/Mar/14 12:55 AM Environment: Linux Mint 15 / Ubuntu Raring Labels: file Priority: Critical Reporter: Fabio Pugliese Ornellas Hello, It seems when /etc/hosts has a syntax error, Puppet only reports the error, and start over with an empty file, only adding the new resource. It essentially erases all original entries to the file. When file syntax is OK, everything seems to work fine. I had problems with this situation in production systems, where, due to a human error, there was a syntax error at /etc/hosts, which made Puppet loose the whole file. I was able to recover the original file from backup, but in the meantime, my system was down. Here is an example to reproduce the error:
Jira (PUP-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Dominic Cleal created an issue Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed Issue Type: Bug Affects Versions: 3.5.0 Assignee: Dominic Cleal Created: 10/Mar/14 2:03 AM Environment: Puppet 'master' (git 545b95fc5) Priority: Normal Reporter: Dominic Cleal In Puppet 3.4 and earlier, multiple paths could be supplied with the --modulepath option, but as of PUP-1765 , there has been a regression and they no longer work. $ git co 3.4.3 Note: checking out '3.4.3'. $ bin/puppet apply --modulepath /tmp:/tmp/test/ --noop -e 'include ntp' Notice: Compiled catalog for cobalt.redhat.com in environment production in 0.76 seconds Notice: /Stage[main]/Ntp/Package[ntp]/ensure: current_value absent, should be present (noop) Notice: /Stage[main]/Ntp/File[/etc/ntp.conf]/ensure: current_value absent, should be present (noop) Notice: /Stage[main]/Ntp/File[/etc/sysconfig/ntpd]/ensure: current_value absent, should be present (noop) Notice: /Stage[main]/Ntp/Service[ntpd]/ensure: current_value stopped, should be running (noop) Notice: Class[Ntp]: Would have triggered 'refresh' from 4 events Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Jira (PUP-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Dominic Cleal assigned an issue to Dominic Cleal Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed Change By: Dominic Cleal Assignee: DominicCleal 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-1073) Common package name in two different providers
Title: Message Title
Drew Blessing commented on an issue
Re: Common package name in two different providers
This issue is being discussed on the puppet-dev list at https://groups.google.com/forum/#!msg/puppet-dev/LatVZFUkwEM/Y-EyhpLHRHsJ. So far I think the idea Pedro Crte-Real suggested both here and in the discussion is the most valid solution. I'd love to hear about the feasibility from someone at Puppet Labs.
Add Comment
Puppet / PUP-1073
Common package name in two different providers
I have a common package name, that's in two different package managers (one with yum the other with gem) package { remove-mysql: name = mysql, provider = yum, ensure = absent, } - package { gem-mysql...
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-1906) Module build with malformed type.rb fails to build or return error
Title: Message Title John McCabe moved an issue Puppet / PUP-1906 Module build with malformed type.rb fails to build or return error Change By: John McCabe Workflow: Forge Platform Workflow Key: FORGE PUP - 150 1906 Project: Puppet Forge 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-1906) Module build with malformed type.rb fails to build or return error
Title: Message Title
John McCabe commented on an issue
Re: Module build with malformed type.rb fails to build or return error
Apologies, I'd raised this against the Forge project by mistake, have moved it.
Add Comment
Puppet / PUP-1906
Module build with malformed type.rb fails to build or return error
Puppet 3.4.3-1.el6 A minor inconvenience when building modules. Running {code}puppet module build{code} on a module with a malformed custom type results in the build failing with no error returned, even if debug and verbose flags are set it just returns a failure exitcode. Took a while to pinpoint the rogue file without any feedback from the build. ...
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-1907) Puppet apply error when selinux is disabled
Title: Message Title Chris Beggio created an issue Puppet / PUP-1907 Puppet apply error when selinux is disabled Issue Type: Bug Affects Versions: 3.3.1 Assignee: Aaron Armstrong Components: PE Created: 10/Mar/14 6:32 AM Environment: /etc/redhat-release: Red Hat Enterprise Linux Server release 6.5 (Santiago) uname -a: Linux 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Dec 13 06:58:20 EST 2013 x86_64 x86_64 x86_64 GNU/Linux Priority: Normal Reporter: Chris Beggio An error involving selinux is observed consistently with the above puppet version during puppet apply operations. The error output and the contents of /etc/sysconfig/selinux are below: — [root@ modules]# puppet apply motd/tests/init.pp Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux: Invalid argument - /proc/self/attr/current Could not retrieve selinux:
Jira (PUP-1906) Module build with malformed type.rb fails to build or return error
Title: Message Title John McCabe updated an issue Puppet / PUP-1906 Module build with malformed type.rb fails to build or return error Change By: John McCabe Component/s: Modules Affects Version/s: 3.4.3 Assignee: RyanColeman AndyParker 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-1907) Puppet apply error when selinux is disabled
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-1907 Puppet apply error when selinux is disabled Change By: Aaron Armstrong Assignee: AaronArmstrong 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-1908) incorrect parsing of range after DST change
Title: Message Title Ken Geis updated an issue Puppet / PUP-1908 incorrect parsing of range after DST change Change By: Ken Geis Affects Version/s: 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1908) incorrect parsing of range after DST change
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1908
incorrect parsing of range after DST change
Issue Type:
Bug
Assignee:
Unassigned
Created:
10/Mar/14 7:38 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
After the Daylight Savings Time change this morning, range statements are not being parsed correctly.
The code: pre schedule { 'daily2am': range = 02:00 - 02:59, period = daily, repeat = 1, }
/pre
Worked just fine for the last few months. After the DST change, this error is generated:
pre err: Could not apply complete catalog: Incorrectly converted time: Sun Mar 09 03:00:23 -0700 2008: 3 vs 2 at /etc/puppet/manifests/schedules/daily2am.pp:6 /pre
This happens with versions 0.23.2 and 0.24.2
Add Comment
Jira (PUP-1909) Priority setting also given to started processes/services
Title: Message Title Steven Post created an issue Puppet / PUP-1909 Priority setting also given to started processes/services Issue Type: Bug Affects Versions: 3.4.2 Assignee: Unassigned Created: 10/Mar/14 7:50 AM Environment: RedHat Enterprise Linux 6.5 Priority: Normal Reporter: Steven Post When setting the priority level in /etc/puppet.puppet.conf, this value also affects services that are started by the agent process. Example: We manage an apache service using puppet, without configuring the priority, the httpd process show a default priority of 20 (nice 0). When setting the priority to 'low' in the 'main' section, we see the puppet agent getting priority '30' and nice level '10', but also every 'httpd' process. Clearly this isn't correct, as the httpd settings should remain with their default values. Best regards, Steven
Jira (FACT-320) PR (630): Add LXC detection to virtual and is_virtual fact - jeffmccune
Title: Message Title gepetto-bot commented on an issue Re: PR (630): Add LXC detection to virtual and is_virtual fact - jeffmccune adrienthebo commented: @jeffmccune we're currently focusing on getting the Facter 2.0.1 release stable and shipped. We're shipping 2.0.1-rc2 today and with any luck that should be the final release, so hopefully we'll be able to get this reviewed and merged in about a week. Sorry about the delay in this! Add Comment Facter / FACT-320 PR (630): Add LXC detection to virtual and is_virtual fact - jeffmccune h2. Add LXC detection to virtual and is_virtual fact * Author: Jeff McCune j...@puppetlabs.com * Company: Puppet Labs * Github ID: [jeffmccune|https://github.com/jeffmccune] * [Pull Request 630 Discussion|https://github.com/puppetlabs/facter/pull/630] * [Pull Request 630 File Diff|https://github.com/puppetlabs/facter/pull/630/files] h2. Pull Requ... 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-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Awesome, thanks for the info! I'm not sure off the top of my head what would be causing this, but I'll try to re-produce it using your class/defined type structure.
Add Comment
Puppet / PUP-1697
hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
The hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode. If a restart of the puppet agent is triggered, the changes are made. {code} Feb 11 11:17:59 node1 puppet-agent[5806]: Finished catalog run in 0.42 seconds Feb 11 11:20:59 node1 puppet-agent[5993]: Finished catalog run in 0.42 seconds Feb 11...
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
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1893 ACL module permissions are not formatted correctly Change By: Joshua Cooper Assignee: RobReynolds 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-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
I'm confused, there is no comma inside the ACE. Are you saying you want to allow for it?
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
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-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed Change By: Joshua Partlow Assignee: DominicCleal 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-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed Change By: Joshua Partlow Sprint: Week2014-3-05to2014-3-12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed Change By: Joshua Partlow Story Points: 1 Fix Version/s: 3.5.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-1909) Priority setting also given to started processes/services
Title: Message Title Joshua Cooper commented on an issue Re: Priority setting also given to started processes/services If you specify the priority for puppet, it will affect all child processes that puppet creates, e.g. exec resources. This is a POSIX thing, not a puppet thing. That said, I am surprised it is affecting your httpd service. Are you managing that with a service resource or an exec? If the former, which provider are you using? Add Comment Puppet / PUP-1909 Priority setting also given to started processes/services When setting the priority level in /etc/puppet.puppet.conf, this value also affects services that are started by the agent process. Example: We manage an apache service using puppet, without configuring the priority, the httpd process show a default priority of 20 (nice 0). When setting the priority to 'low' in the 'main' section, we see the puppet a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1909) Priority setting also given to started processes/services
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1909 Priority setting also given to started processes/services Change By: Joshua Cooper Assignee: StevenPost 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-1910) PR (231): Numerous changes to update testing gems. - apenney
Title: Message Title gepetto-bot created an issue Puppet / PUP-1910 PR (231): Numerous changes to update testing gems. - apenney Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 10/Mar/14 11:00 AM Labels: github Priority: Normal Reporter: gepetto-bot Numerous changes to update testing gems. Author: Ashley Penney ashley.pen...@puppetlabs.com Company: Puppetlabs Github ID: apenney Pull Request 231 Discussion Pull Request 231 File Diff Pull Request Description This work updates a number of
Jira (PUP-1911) Windows installer downgrade fails to start service, exits with code 1603
Title: Message Title Ethan Brown created an issue Puppet / PUP-1911 Windows installer downgrade fails to start service, exits with code 1603 Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Attachments: pe-downgrade-log.zip Created: 10/Mar/14 11:03 AM Priority: Normal Reporter: Ethan Brown A simple set of repro steps is as follows: Install PE 3.2.0 Try to install PE 3.1.2 The PE 3.1.2 installer will successfully install PE 3.2.0, and during the install of PE 3.1.2 will fail with a generic MSI installation code: ERROR_INSTALL_FAILURE 1603 Fatal error during installation If run through the UI, you can see that files are copied correctly, and a start of the pe-puppet / puppet service will be triggered. Unfortunately it appears that the installer believes that the service has failed to start (it appears from the logs that an internal count might not be correct). Complete log is attached as a zip.
Jira (PUP-1911) Windows installer downgrade fails to start service, exits with code 1603
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1911 Windows installer downgrade fails to start service, exits with code 1603 Change By: Ethan Brown Asimplesetofreprostepsisasfollows:*InstallPE3.2.0*TrytoinstallPE3.1.2ThePE3.1.2installerwillsuccessfullyinstallPE3.2.0,andduringtheinstallofPE3.1.2willfailwithagenericMSIinstallationcode:ERROR_INSTALL_FAILURE1603FatalerrorduringinstallationIfrunthroughtheUI,youcanseethatfilesarecopiedcorrectly,andastartofthepe-puppet/puppetservicewillbetriggered.Unfortunatelyitappearsthattheinstallerbelievesthattheservicehasfailedtostart (itappearsfrom .If the logsthataninternalcountmightnotbecorrect) PE3 . 1.2installerisstartedagain,theinstallcompletesandtheserviceisstarted. Completelogisattachedasazip. 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-1911) Windows installer downgrade fails to start service, exits with code 1603
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-1911
Windows installer downgrade fails to start service, exits with code 1603
Change By:
Ethan Brown
Asimplesetofreprostepsisasfollows:*InstallPE3.2.0*TrytoinstallPE3.1.2ThePE3.1.2installerwillsuccessfullyinstallPE3.2.0,andduringtheinstallofPE3.1.2willfailwithagenericMSIinstallationcode:ERROR_INSTALL_FAILURE1603FatalerrorduringinstallationIfrunthroughtheUI,youcanseethatfilesarecopiedcorrectly,andastartofthepe-puppet/puppetservicewillbetriggered.Unfortunatelyitappearsthattheinstallerbelievesthattheservicehasfailedtostart.Therelevantportionofthelogstartsatline160328oftheattachedlogfile.{code}MSI(s)(F4:78)[10:49:41: 046]:Executingop:ServiceInstall(Name=pe-puppet,DisplayName=PuppetAgent,ImagePath=c:\ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\service\daemon.bat,ServiceType=16,StartType=2,ErrorControl=32769,,Dependencies=[~],,StartName=LocalSystem,Password=**,Description=PeriodicallyfetchesandappliesconfigurationsfromaPuppetmasterserver.,,)MSI(s)(F4:78)[10:49:41:087]:Executingop:ServiceInstall(Name=pe-mcollective,DisplayName=MarionetteCollectiveServer,ImagePath=c:\ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\service\mco_daemon.bat,ServiceType=16,StartType=3,ErrorControl=32769,,Dependencies=[~],,StartName=LocalSystem,Password=**,Description=PuppetLabsserverorchestrationframework,,)MSI(s)(F4:78)[10:49:41: 094]:Executingop:ActionStart(Name=StartServices,Description=Startingservices,Template=Service:[1])MSI(s)(F4:78)[10:49:41:094]:Executingop:ProgressTotal(Total=1,Type=1,ByteEquivalent=130)MSI(s)(F4:78)[10:49:41:094]:Executingop:ServiceControl(,Name=pe-puppet,Action="" />MSI(s)(F4:78)[10:50:11:894]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:894]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1920MSI(s)(F4:78)[10:50:11:895]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:895]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1709MSI(s)(F4:78)[10:50:11:895]:Product:PuppetEnterprise--Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.MSI(s)(F4:78)[10:50:11:901]:Userpolicyvalue'DisableRollback'is0MSI(s)(F4:78)[10:50:11:901]:Machinepolicyvalue'DisableRollback'is0Actionended10:50:11:InstallFinalize.Returnvalue3.{code}IfthePE3.1.2installerisstartedagain,theinstallcompletesandtheserviceisstarted.Completelogisattachedasazip.
Add Comment
Jira (PUP-1911) Windows installer downgrade fails to start service, exits with code 1603
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-1911
Windows installer downgrade fails to start service, exits with code 1603
Change By:
Ethan Brown
Asimplesetofreprostepsisasfollows:*InstallPE3.2.0*TrytoinstallPE3.1.2ThePE3.1.2installerwillsuccessfullyinstallPE3.2.0,andduringtheinstallofPE3.1.2willfailwithagenericMSIinstallationcode:ERROR_INSTALL_FAILURE1603FatalerrorduringinstallationIfrunthroughtheUI,youcanseethatfilesarecopiedcorrectly,andastartofthepe-puppet/puppetservicewillbetriggered.Unfortunatelyitappearsthattheinstallerbelievesthattheservicehasfailedtostart. Therelevantportionofthelogstartsatline160328oftheattachedlogfile.{code}MSI(s)(F4:78)[10:49:41:094]:Executingop:ActionStart(Name=StartServices,Description=Startingservices,Template=Service:[1])MSI(s)(F4:78)[10:49:41:094]:Executingop:ProgressTotal(Total=1,Type=1,ByteEquivalent=130)MSI(s)(F4:78)[10:49:41:094]:Executingop:ServiceControl(,Name=pe-puppet,Action="" />MSI(s)(F4:78)[10:50:11:894]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:894]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1920MSI(s)(F4:78)[10:50:11:895]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:895]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1709MSI(s)(F4:78)[10:50:11:895]:Product:PuppetEnterprise--Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.MSI(s)(F4:78)[10:50:11:901]:Userpolicyvalue'DisableRollback'is0MSI(s)(F4:78)[10:50:11:901]:Machinepolicyvalue'DisableRollback'is0Actionended10:50:11:InstallFinalize.Returnvalue3.{code} IfthePE3.1.2installerisstartedagain,theinstallcompletesandtheserviceisstarted.Completelogisattachedasazip.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1911) Windows installer downgrade fails to start service, exits with code 1603
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-1911
Windows installer downgrade fails to start service, exits with code 1603
Change By:
Ethan Brown
Asimplesetofreprostepsisasfollows:*InstallPE3.2.0*TrytoinstallPE3.1.2ThePE3.1.2installerwillsuccessfullyinstallPE3.2.0,andduringtheinstallofPE3.1.2willfailwithagenericMSIinstallationcode:ERROR_INSTALL_FAILURE1603FatalerrorduringinstallationIfrunthroughtheUI,youcanseethatfilesarecopiedcorrectly,andastartofthepe-puppet/puppetservicewillbetriggered.Unfortunatelyitappearsthattheinstallerbelievesthattheservicehasfailedtostart.Therelevantportionofthelogstartsatline160328oftheattachedlogfile.{ code panel }MSI(s)(F4:78)[10:49:41:046]:Executingop:ServiceInstall(Name=pe-puppet,DisplayName=PuppetAgent,ImagePath=c:\ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\service\daemon.bat,ServiceType=16,StartType=2,ErrorControl=32769,,Dependencies=[~],,StartName=LocalSystem,Password=**,Description=PeriodicallyfetchesandappliesconfigurationsfromaPuppetmasterserver.,,)MSI(s)(F4:78)[10:49:41:087]:Executingop:ServiceInstall(Name=pe-mcollective,DisplayName=MarionetteCollectiveServer,ImagePath=c:\ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\service\mco_daemon.bat,ServiceType=16,StartType=3,ErrorControl=32769,,Dependencies=[~],,StartName=LocalSystem,Password=**,Description=PuppetLabsserverorchestrationframework,,)MSI(s)(F4:78)[10:49:41:094]:Executingop:ActionStart(Name=StartServices,Description=Startingservices,Template=Service:[1])MSI(s)(F4:78)[10:49:41:094]:Executingop:ProgressTotal(Total=1,Type=1,ByteEquivalent=130)MSI(s)(F4:78)[10:49:41:094]:Executingop:ServiceControl(,Name=pe-puppet,Action="" />MSI(s)(F4:78)[10:50:11:894]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:894]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1920MSI(s)(F4:78)[10:50:11:895]:Note:1:22052:3:ErrorMSI(s)(F4:78)[10:50:11:895]:Note:1:22282:3:Error4:SELECT`Message`FROM`Error`WHERE`Error`=1709MSI(s)(F4:78)[10:50:11:895]:Product:PuppetEnterprise--Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.Error1920.Service'PuppetAgent'(pe-puppet)failedtostart.Verifythatyouhavesufficientprivilegestostartsystemservices.MSI(s)(F4:78)[10:50:11:901]:Userpolicyvalue'DisableRollback'is0MSI(s)(F4:78)[10:50:11:901]:Machinepolicyvalue'DisableRollback'is0Actionended10:50:11:InstallFinalize.Returnvalue3.{ code panel }IfthePE3.1.2installerisstartedagain,theinstallcompletesandtheserviceisstarted.Completelogisattachedasazip.
Add Comment
Jira (PUP-1855) Defer starting the agent until enable
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-1855 Defer starting the agent until enable Change By: Ethan Brown Assignee: EthanBrown 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-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title
Joshua Partlow commented on an issue
Re: Multiple paths in --modulepath command line option not parsed
Merged to master in 3016849
Add Comment
Puppet / PUP-1905
Multiple paths in --modulepath command line option not parsed
In Puppet 3.4 and earlier, multiple paths could be supplied with the --modulepath option, but as of PUP-1765, there has been a regression and they no longer work. {noformat} $ git co 3.4.3 Note: checking out '3.4.3'. $ bin/puppet apply --modulepath /tmp:/tmp/test/ --noop -e 'include ntp' Notice: Compiled catalog for cobalt.redhat.com in environment...
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-1885) File type ignore can't convert Fixnum into String
Title: Message Title Dominic Maraglia updated an issue Puppet / PUP-1885 File type ignore can't convert Fixnum into String Change By: Dominic Maraglia Component/s: QA 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-1912) PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun
Title: Message Title gepetto-bot created an issue Puppet / PUP-1912 PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 10/Mar/14 11:56 AM Labels: github Priority: Normal Reporter: gepetto-bot This commit solves a problem with the commandline interpretation of the ... Author: Markus Hartmann Company: Github ID: aidun Pull Request 2427 Discussion Pull Request 2427 File Diff Pull Request Description
Jira (PUP-1913) Puppet user resource should read only from local databases
Title: Message Title redmine.exporter created an issue Puppet / PUP-1913 Puppet user resource should read only from local databases Issue Type: New Feature Assignee: Unassigned Created: 10/Mar/14 1:38 PM Labels: redmine customer Priority: Normal Reporter: redmine.exporter Currently, the puppet user type uses `getent` to get information about user resources. The problem with this is that `getent` will also report information from LDAP and other remote user management services that are configured in nsswitch.conf, which are not actually managed by Puppet. This can cause Puppet to think a user is in a local group, or not in a local group, when the opposite is true. This is especially problematic since we user the useradd suite of commands to actually manage the settings, which of course affect local users/groups only. Puppet's user type should have some way of examining only local users and groups, to check if something is currently true/present/etc. Add Comment
Jira (PUP-28) Add heredoc support in future parser
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-28 Add heredoc support in future parser Change By: Tony Vu Assignee: TonyVu 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-1839) Puppet device results in SSL stack too deep error
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1839 Puppet device results in SSL stack too deep error Change By: Joshua Cooper Assignee: JoshuaCooper 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-1914) PR (232): Readd location_for - apenney
Title: Message Title gepetto-bot created an issue Puppet / PUP-1914 PR (232): Readd location_for - apenney Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 10/Mar/14 2:57 PM Labels: github Priority: Normal Reporter: gepetto-bot Readd location_for Author: Ashley Penney ashley.pen...@puppetlabs.com Company: Puppetlabs Github ID: apenney Pull Request 232 Discussion Pull Request 232 File Diff Pull Request Description location_for is used in Jenkins to transform a passed in git repo into
Jira (PUP-1914) PR (232): Readd location_for - apenney
Title: Message Title gepetto-bot commented on an issue Re: PR (232): Readd location_for - apenney Pull request Readd location_for has been closed. Add Comment Puppet / PUP-1914 PR (232): Readd location_for - apenney h2. Readd location_for * Author: Ashley Penney ashley.pen...@puppetlabs.com * Company: Puppetlabs * Github ID: [apenney|https://github.com/apenney] * [Pull Request 232 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/232] * [Pull Request 232 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/232/files] h2. Pull Request ... 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-1912) PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun
Title: Message Title gepetto-bot commented on an issue Re: PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun puppetcla commented: Waiting for CLA signature by @aidun @aidun - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/ Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html Add Comment Puppet / PUP-1912 PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun h2. This commit solves a problem with the commandline interpretation of the ... * Author: Markus Hartmann * Company: * Github ID: [aidun|https://github.com/aidun] * [Pull Request 2427 Discussion|https://github.com/puppetlabs/puppet/pull/2427] * [Pull Request 2427 File Diff|https://github.com/puppetlabs/puppet/pull/2427/files] h2. Pull Request D... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Joshua Cooper Assignee: JustinStoller 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-1915) PR (233): Make sure location_for is used when installing Puppet. - apenney
Title: Message Title gepetto-bot created an issue Puppet / PUP-1915 PR (233): Make sure location_for is used when installing Puppet. - apenney Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 10/Mar/14 3:23 PM Labels: github Priority: Normal Reporter: gepetto-bot Make sure location_for is used when installing Puppet. Author: Ashley Penney ashley.pen...@puppetlabs.com Company: Puppetlabs Github ID: apenney Pull Request 233 Discussion Pull Request 233 File Diff Pull Request Description
Jira (PUP-1915) PR (233): Make sure location_for is used when installing Puppet. - apenney
Title: Message Title gepetto-bot commented on an issue Re: PR (233): Make sure location_for is used when installing Puppet. - apenney Pull request Make sure location_for is used when installing Puppet. has been closed. Add Comment Puppet / PUP-1915 PR (233): Make sure location_for is used when installing Puppet. - apenney h2. Make sure location_for is used when installing Puppet. * Author: Ashley Penney ashley.pen...@puppetlabs.com * Company: Puppetlabs * Github ID: [apenney|https://github.com/apenney] * [Pull Request 233 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/233] * [Pull Request 233 File Diff|https://github.com/puppetlabs/puppetlabs-stdli... 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-1776) acl module can't load helper code when types loaded on master
Title: Message Title
Tony Vu commented on an issue
Re: acl module can't load helper code when types loaded on master
Confirmed that the acl package installed from the master onto a windows box installs correctly; puppet resource acl C:\Windows executes correctly and returns an acl hash for that folder. Also confirmed that 'puppet/type/acl/ace' are placed into the lib.
Add Comment
Puppet / PUP-1776
acl module can't load helper code when types loaded on master
The type and provider try to {{require 'puppet/type/acl/ace'}}, etc, but this doesn't work when the module is installed on the puppetmaster, because individual module lib directories are not added to the master's LOAD_PATH. The pattern that we've followed in the past is to use a relative directory, e.g. {code} require 'pathname' require Pathname.n...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-1912) PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun
Title: Message Title gepetto-bot commented on an issue Re: PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1912 PR (2427): This commit solves a problem with the commandline interpretation of the ... - aidun h2. This commit solves a problem with the commandline interpretation of the ... * Author: Markus Hartmann * Company: * Github ID: [aidun|https://github.com/aidun] * [Pull Request 2427 Discussion|https://github.com/puppetlabs/puppet/pull/2427] * [Pull Request 2427 File Diff|https://github.com/puppetlabs/puppet/pull/2427/files] h2. Pull Request D... 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-46) Hiera should support alternate environments
Title: Message Title Zack Smith updated an issue Hiera / HI-46 Hiera should support alternate environments Change By: Zack Smith Labels: customerredmine wf001 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 (PDB-24) Support for Puppet Environments
Title: Message Title Zack Smith updated an issue PuppetDB / PDB-24 Support for Puppet Environments Change By: Zack Smith Labels: PE_3.3puppetdb wf001 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Zack Smith updated an issue Puppet / PUP-731 Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Change By: Zack Smith Labels: customerredmine wf001 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-1450) [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors
Title: Message Title Zack Smith updated an issue Puppet / PUP-1450 [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors Change By: Zack Smith Labels: 3.5.0 wf001 windows 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 (FACT-231) PR (608): Fix to Virtual Machine detection on Darwin - keeleysam
Title: Message Title Jesse Endahl commented on an issue Re: PR (608): Fix to Virtual Machine detection on Darwin - keeleysam Gary LarizzaNigel KerstenZack Smith can we get this merged? Add Comment Facter / FACT-231 PR (608): Fix to Virtual Machine detection on Darwin - keeleysam h2. Fix to Virtual Machine detection on Darwin * Author: Samuel Keeley s...@keeleysam.com * Company: * Github ID: [keeleysam|https://github.com/keeleysam] * [Pull Request 608 Discussion|https://github.com/puppetlabs/facter/pull/608] * [Pull Request 608 File Diff|https://github.com/puppetlabs/facter/pull/608/files] h2. Pull Request Description ---... 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-1846) PR (2410): File content diffing should respect loglevel - wfarr
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1846 PR (2410): File content diffing should respect loglevel - wfarr 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-1041) PR (2385) naginator not parsing blank parameters
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1041 PR (2385) naginator not parsing blank parameters The patch looks good. 3.5.0 is currently closed for merges at this time, so I'm targeting at 3.x for the moment. I'll keep an eye on this one and get it merged in when the code thaws back out. Change By: Charlie Sharpsteen Component/s: TypesandProviders Affects Version/s: 3.4.3 Fix Version/s: 3.x Assignee: CharlieSharpsteen Summary: PR(2385) naginatornotparsingblankparameters Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Peter Huene Assignee: PeterHuene 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-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Peter Huene updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Peter Huene Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Peter Huene updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Peter Huene Sprint: Week2014-3-05to2014-3-12 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Peter Huene updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Peter Huene Fix Version/s: 3.5.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.
