Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Michael Chapman commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Following Adrien's comments on the original PR that backwards compatibility was an issue, I have attempted to add a new lookup function that preserves types and have created a new pull request with an implementation. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-1461) Exec resource not notified but onlyif check gets executed anyway
Title: Message Title
Philipp Gassmann commented on an issue
Re: Exec resource not notified but onlyif check gets executed anyway
The original request in my words:
Expected behaviour: when refreshonly = true is set, the onlyif command should only be executed when resource gets a refresh.
Current behaviour: onlyif/unless commands gets executed regardless of refresh, on every puppet run.
Issues: onlyif/unless command can be expensive. when refreshonly is true and the resource did not get a refresh, the main command won't be executed, so the onlyif command is useless.
Add Comment
Puppet / PUP-1461
Exec resource not notified but onlyif check gets executed anyway
Please have a look at this simplified example. {code} class runtimevariation { # dummy file ressources that should represent # some real software deployment file { '/tmp/software-v1': ensure = present, }file { '/tmp/software-v2': ensure = present, }file { '/tmp/software-v3': ensure = present, } ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
Jira (FACT-691) Add IPMI facts
Title: Message Title Marek Huln created an issue Facter / FACT-691 Add IPMI facts Issue Type: Improvement Assignee: Eric Sorenson Created: 28/Aug/14 2:05 AM Priority: Normal Reporter: Marek Huln Facter could report information about ipmi devices using ipmitool. A good example can be found at https://github.com/theforeman/ovirt-node-plugin-foreman/blob/master/src/discovery-facts.rb.in#L82 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received
Jira (PUP-2552) Future parser breaks concat module
Title: Message Title Nitzan Raz assigned an issue to Andy Parker I'm not sure if this is the correct action, but I solved my problem long ago and just noticed that the issue is assigned to me. Puppet / PUP-2552 Future parser breaks concat module Change By: Nitzan Raz Assignee: NitzanRaz 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 (PDB-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog Pull request (docs) Fix some spelling mistakes and one word choice. has been closed. Add Comment PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog h2. (docs) Fix some spelling mistakes and one word choice. * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 1067 Discussion|https://github.com/puppetlabs/puppetdb/pull/1067] * [Pull Request 1067 File Diff|https://github.com/puppetlabs/puppetdb/pull/1067/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 (PDB-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog kbarber commented: @kylog superb, thanks very much. Merged manually into the stable branch, so we can see this straight away. Add Comment PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog h2. (docs) Fix some spelling mistakes and one word choice. * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 1067 Discussion|https://github.com/puppetlabs/puppetdb/pull/1067] * [Pull Request 1067 File Diff|https://github.com/puppetlabs/puppetdb/pull/1067/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.
Jira (PDB-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog Change By: Kenneth Barber Sprint: 20140827to20140910 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-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog Change By: Kenneth Barber Story Points: 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-2984) MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2984 MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec Change By: Rob Reynolds Summary: MSI downgrade architecturechange fromx64tox86doesnotremovePuppetLabsfoldersinProgramFilesduetoFileSystemRedirectionwith32bitmsiexec 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-2984) MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-2984
MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Change By:
Rob Reynolds
MSI downgrade architecturechange fromx64tox86doesnotremovePuppetLabsfoldersinProgramFilesduetoFileSystemRedirectionwith32bitmsiexec.Italsodoesn'tremovetheolderpath-thisiswhatremainsafterinstallofx86AFTERx64:{{C:\ProgramFiles\PuppetLabs\Puppet\bin;C:\ProgramFiles(x86)\PuppetLabs\Puppet\bin}}anditshouldbe{{C:\ProgramFiles(x86)\PuppetLabs\Puppet\bin}}.A{{wherepuppet}}evaluatestotheprogramfilesfolderfirst,whichcouldhavesomeverybadinconsistentresultsifthisisnotcleanedup. Ifyoudowngrade(truedowngrade)from3.7.0x64-lessthan3.7.0installer,youaresubjecttowhattheolderinstallercanhandle.Weshoulddocumentthatifyouwanttogodown,youshoulduninstallfirstandthenreinstalltheolderversion.
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-2987) Puppet service hangs when attempting to stop on Windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2987 Puppet service hangs when attempting to stop on Windows Change By: Rob Reynolds 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-1689) Windows Memory Leaks
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1689 Windows Memory Leaks @ethan is this still a concern given some of the memory stuff we've added with FFI? Change By: Rob Reynolds Component/s: Client 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-266) Allow puppet to manage owner group file settings
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-266 Allow puppet to manage owner group file settings Change By: Rob Reynolds Component/s: Client 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-266) Allow puppet to manage owner group file settings
Title: Message Title Rob Reynolds commented on an issue Re: Allow puppet to manage owner group file settings Is this coming back on 4.0? Or later? Add Comment Puppet / PUP-266 Allow puppet to manage owner group file settings 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-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1688 When applying a mode of 0466 on Windows, a mode of 0666 is applied instead Change By: Rob Reynolds Component/s: Client 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-575) Split windows wix files into respective repositories
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-575 Split windows wix files into respective repositories Change By: Rob Reynolds Component/s: RE Component/s: Client 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-579) Add automated tests for Windows installer packages
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Rob Reynolds Component/s: Client 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-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Facter / FACT-690 Add manjaro linux to the operatingsystem fact Change By: Joshua Partlow Assignee: TimSpence 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 (FACT-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow updated an issue Facter / FACT-690 Add manjaro linux to the operatingsystem fact Change By: Joshua Partlow Fix Version/s: 2.3.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 (FACT-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow commented on an issue Re: Add manjaro linux to the operatingsystem fact Merged to master in 95f663f Add Comment Facter / FACT-690 Add manjaro linux to the operatingsystem fact 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-2914) Vendor RGen 0.7.0
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2914 Vendor RGen 0.7.0 Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2984) MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2984 MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec Change By: Josh Cooper Assignee: JoshCooper 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-3151) Add jetty_external_root_ca.rb acceptance test
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-3151 Add jetty_external_root_ca.rb acceptance test Issue Type: Task Assignee: Jeremy Barlow Created: 28/Aug/14 9:48 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Jeremy Barlow Introduce a new acceptance test related to running an External CA on a Jetty webserver configuration. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-2349 Deprecate non-string modes on file type 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-3152) If zone creation fails with an assigned dataset, the dataset can not be reused
Title: Message Title Rahul Gopinath created an issue Puppet / PUP-3152 If zone creation fails with an assigned dataset, the dataset can not be reused Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 28/Aug/14 10:37 AM Priority: Normal Reporter: Rahul Gopinath 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
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Rahul Gopinath commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
This behavior needs to be investigated further since we shouldn't be leaving the system in an inconsistent state. Since this behavior is unrelated to the current bug, we will track it in a separate ticket PUP-3152.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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-3152) If zone creation fails with an assigned dataset, the dataset can not be reused
Title: Message Title
Rahul Gopinath updated an issue
Puppet / PUP-3152
If zone creation fails with an assigned dataset, the dataset can not be reused
Change By:
Rahul Gopinath
SeePUP-2817fortheoriginalreport.Theappliedmanifestsare{noformat}zone{dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff'],}zone{dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff2'],}zone{dataset3:ensure=running,path=/zones/dataset3,dataset=['rpool/stuff3'],}{noformat}
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-3152) If zone creation fails with an assigned dataset, the dataset can not be reused
Title: Message Title
Rahul Gopinath updated an issue
Puppet / PUP-3152
If zone creation fails with an assigned dataset, the dataset can not be reused
Change By:
Rahul Gopinath
SeePUP-2817fortheoriginalreport.Theappliedmanifestsare{noformat}zone{dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff'],} Info:Applyingconfigurationversion'1409242942'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetinstall'Error:Couldnotinstall zone :Executionof'/usr/sbin/zoneadm-zdatasetinstall'returned1:couldnotverifyzfsdatasetzonepool:datasetdoesnotexistzoneadm:zonedatasetfailedtoverify { noformat}{noformat}zone{ dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff2'],} Info:Applyingconfigurationversion'1409243015' Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetinstall'Error:Couldnotinstall zone :Executionof'/usr/sbin/zoneadm-zdatasetinstall'returned1:couldnotverifyzfsdatasetzonepool:datasetdoesnotexistzoneadm:zonedatasetfailedtoverify { noformat}{noformat}zone{ dataset3:ensure=running,path=/zones/dataset3,dataset=['rpool/stuff3'],} Info:Applyingconfigurationversion'1409243034'Debug:Executing'/usr/sbin/zoneadm-zdataset3list-p'Debug:Executing'/usr/sbin/zonecfg-zdataset3info'Debug:Executing'/usr/sbin/zoneadm-zdataset3list-p'Debug:Executing'/usr/sbin/zonecfg-zdataset3info'Debug:Executing'/usr/sbin/zoneadm-zdataset3install'Error:Couldnotinstallzone:Executionof'/usr/sbin/zoneadm-zdataset3install'returned1:couldnotverifyzfsdatasetrpool/stuff2:datasetdoesnotexistzoneadm:zonedataset3failedtoverify {noformat} Furtherinformationinthis[[gist]|[https://gist.github.com/MikaelSmith/66952db17447f51bed45]]
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3152) If zone creation fails with an assigned dataset, the dataset can not be reused
Title: Message Title
Rahul Gopinath updated an issue
Puppet / PUP-3152
If zone creation fails with an assigned dataset, the dataset can not be reused
Change By:
Rahul Gopinath
SeePUP-2817fortheoriginalreport.Theappliedmanifestsare{noformat}zone{dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff'],}Info:Applyingconfigurationversion'1409242942'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetinstall'Error:Couldnotinstallzone:Executionof'/usr/sbin/zoneadm-zdatasetinstall'returned1:couldnotverifyzfsdatasetzonepool:datasetdoesnotexistzoneadm:zonedatasetfailedtoverify{noformat}{noformat}zone{dataset:ensure=running,path=/zones/dataset,dataset=['rpool/stuff2'],}Info:Applyingconfigurationversion'1409243015'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetlist-p'Debug:Executing'/usr/sbin/zonecfg-zdatasetinfo'Debug:Executing'/usr/sbin/zoneadm-zdatasetinstall'Error:Couldnotinstallzone:Executionof'/usr/sbin/zoneadm-zdatasetinstall'returned1:couldnotverifyzfsdatasetzonepool:datasetdoesnotexistzoneadm:zonedatasetfailedtoverify{noformat}{noformat}zone{dataset3:ensure=running,path=/zones/dataset3,dataset=['rpool/stuff3'],}Info:Applyingconfigurationversion'1409243034'Debug:Executing'/usr/sbin/zoneadm-zdataset3list-p'Debug:Executing'/usr/sbin/zonecfg-zdataset3info'Debug:Executing'/usr/sbin/zoneadm-zdataset3list-p'Debug:Executing'/usr/sbin/zonecfg-zdataset3info'Debug:Executing'/usr/sbin/zoneadm-zdataset3install'Error:Couldnotinstallzone:Executionof'/usr/sbin/zoneadm-zdataset3install'returned1:couldnotverifyzfsdatasetrpool/stuff2:datasetdoesnotexistzoneadm:zonedataset3failedtoverify{noformat}Furtherinformationinthis[[gist ] | [ https://gist.github.com/MikaelSmith/66952db17447f51bed45]]
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Steve Barlow Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
2. Test dataset property
Used examples from acceptance/tests/resource/zone/dataset.rb. Worked correctly.
4. Solaris 11 acceptance tests cover this.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
I'm going to try to do a Solaris 10 acceptance run manually (since automated runs are broken). If that passes I think that's sufficient for Functional Review.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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-1802) Puppet should execute ruby.exe not cmd.exe when running as a windows service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1802 Puppet should execute ruby.exe not cmd.exe when running as a windows service Change By: Josh Cooper Currently,whenpuppetrunsasaserviceonwindows,itexecutesabatchscript(inacmd.exeprocess),whichtheninvokesruby.exe.Thechildprocessthencallsbackintotheservicecontrolmanager,andthatcausestheservicecontrolmanagertoissueawarningintheapplicationeventlogthatadifferentprocessregisteredasaservicethantheoneitlaunched.Ideally,theservicecontrolmanagershouldlaunchruby.exedirectlyalongwithwhateverargumentsarenecessarytodoso.Ifthepuppetserviceisrunningwhenanewversionisinstalled,orexistingversionrepaired,WindowsInstallermayissuethewarning,Thesetupmustupdatefilesorservicesthatcannotbeupdatedwhilethesystemisrunning.Ifyouchoosetocontinue,arebootwillberequiredtocompletethesetup.Ibelievethisoccursbecauseruby.exeisnottheexecutableassociatedwiththeservice,sotheinstallerjustthinksthefileisinuse. Thisissuecanbetriggeredeasilybysettingruninterval=5,e.g.runpuppetevery5seconds,andthentryingtoupgrade/repair. 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-1802) Puppet should execute ruby.exe not cmd.exe when running as a windows service
Title: Message Title Josh Cooper commented on an issue Re: Puppet should execute ruby.exe not cmd.exe when running as a windows service See http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/stop-the-service-before-uninstall-tp4802789p4832837.html Add Comment Puppet / PUP-1802 Puppet should execute ruby.exe not cmd.exe when running as a windows service Currently, when puppet runs as a service on windows, it executes a batch script (in a cmd.exe process), which then invokes ruby.exe. The child process then calls back into the service control manager, and that causes the service control manager to issue a warning in the application event log that a different process registered as a service than the one it... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1802) Puppet should execute ruby.exe not cmd.exe when running as a windows service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1802 Puppet should execute ruby.exe not cmd.exe when running as a windows service Change By: Josh Cooper Currently,whenpuppetrunsasaserviceonwindows,itexecutesabatchscript(inacmd.exeprocess),whichtheninvokesruby.exe.Thechildprocessthencallsbackintotheservicecontrolmanager,andthatcausestheservicecontrolmanagertoissueawarningintheapplicationeventlogthatadifferentprocessregisteredasaservicethantheoneitlaunched.Ideally,theservicecontrolmanagershouldlaunchruby.exedirectlyalongwithwhateverargumentsarenecessarytodoso. Ifthepuppetserviceisrunningwhenanewversionisinstalled,orexistingversionrepaired,WindowsInstallermayissuethewarning,Thesetupmustupdatefilesorservicesthatcannotbeupdatedwhilethesystemisrunning.Ifyouchoosetocontinue,arebootwillberequiredtocompletethesetup.Ibelievethisoccursbecauseruby.exeisnottheexecutableassociatedwiththeservice,sotheinstallerjustthinksthefileisinuse. 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-3153) Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks
Title: Message Title Christopher Price created an issue Puppet / PUP-3153 Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks Issue Type: Bug Assignee: Christopher Price Created: 28/Aug/14 12:09 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Christopher Price in `util.rb#replace_file`, there is an `ensure` block that calls `close!` on the `Uniquefile` object. However, if an exception is thrown during the call to the constructor for `Uniquefile` (e.g., if the user does not have write permissions to the specified directory), then this attempt to call `close!` will result in a NilClass exception, which will mask the original exception. Add Comment
Jira (PUP-1802) Puppet should execute ruby.exe not cmd.exe when running as a windows service
Title: Message Title Josh Cooper commented on an issue Re: Puppet should execute ruby.exe not cmd.exe when running as a windows service If the The setup must update files or services ... error happens, you can try running msiexec /qn /i puppet.msi /l*vx install.log and look for errors like the following: MSI (s) (2C:C8) [11:36:30:332]: RESTART MANAGER: Will attempt to shut down and restart applications in no UI modes. MSI (s) (2C:C8) [11:36:30:332]: RESTART MANAGER: Detected that application with id 1984, friendly name 'ruby.exe', of type RmCritical and status 1 holds file[s] in use. MSI (s) (2C:C8) [11:36:30:332]: RESTART MANAGER: Did detect that a critical application holds file[s] in use, so a reboot will be necessary. Add Comment Puppet / PUP-1802 Puppet should execute ruby.exe not cmd.exe when running as a windows service Currently, when puppet runs as a service on windows, it executes a batch script (in a cmd.exe process), which then invokes ruby.exe. The child process then calls back into the service control manager, and that causes the service control manager to issue a warning in the application event log that a different process registered as a service than the one it... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2984) MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title
Josh Cooper commented on an issue
Re: MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
While testing this, Windows Installer was generating errors like The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a reboot will be required to complete the setup. But I can reproduce with older builds, e.g. 3.4.3 3.6.2. I believe the root cause is https://tickets.puppetlabs.com/browse/PUP-1802?focusedCommentId=94104page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-94104 which can be triggered if the puppet service is running when you attempt to upgrade/reinstall.
Add Comment
Puppet / PUP-2984
MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec. It also doesn't remove the older path - this is what remains after install of x86 AFTER x64: {{C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin}} and it should be {{C:\Progra...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Bryan York commented on an issue Re: scheduled_task : add support for every X minutes or hours mode The Gem used supports this, but the provider has not been updated to allow minutes_interval to be a valid trigger type. I'm not much of a ruby expert, but it seems trivial to allow the provider support for this flag, since the underlying module already supports it. Add Comment Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode As stated in the Puppet documentation (http://docs.puppetlabs.com/windows/writing.html#scheduledtaskscheduledtask), the scheduled_task resource type does not support repetition modes such as every X minutes. It is a pity, because such tasks are very commonly used in Windows servers (and maybe less on Windows clients), making scheduled_task not s... 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
Jira (PUP-3153) Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks
Title: Message Title Christopher Price commented on an issue Re: Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks Kylo Ginsberg Joshua Partlow Josh Cooper Just FYI, this is the bug I mentioned in chat yesterday. Just filed a PR. Add Comment Puppet / PUP-3153 Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks in `util.rb#replace_file`, there is an `ensure` block that calls `close!` on the `Uniquefile` object. However, if an exception is thrown during the call to the constructor for `Uniquefile` (e.g., if the user does not have write permissions to the specified directory), then this attempt to call `close!` will result in a NilClass exception, which will mask... 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 (FACT-683) facter id broken on solaris10 as root
Title: Message Title
Michael Smith commented on an issue
Re: facter id broken on solaris10 as root
From Rahul:
The problem is here: https://github.com/puppetlabs/facter/blob/master/lib/facter/gid.rb Uses which(id)
Should be like: https://github.com/puppetlabs/facter/blob/master/lib/facter/id.rb Uses (/usr/xpg4/bin/id -g)
Add Comment
Facter / FACT-683
facter id broken on solaris10 as root
installed from source at SHA 5994c22 {code} -bash-3.2# which facter /opt/csw/bin/facter -bash-3.2# facter /usr/bin/id: illegal option -- n Usage: id [-ap] [user] architecture = i86pc {code}
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-3035) Debian package does not create /var/run/puppet dir during install
Title: Message Title Kylo Ginsberg commented on an issue Re: Debian package does not create /var/run/puppet dir during install Targeted at 3.7 and updated state to Ready for CI. I'll also pull it into the platform sprint just so there's visibility. Add Comment Puppet / PUP-3035 Debian package does not create /var/run/puppet dir during install It looks like `/var/run/puppet` has typically been created during by the debian init script if it didn't exist already: https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init#L22 This should instead be handled by the `puppet-common.dirs` file in the `puppet-common` package. I say that it should be included in the `puppet-common` ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3035) Debian package does not create /var/run/puppet dir during install
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3035 Debian package does not create /var/run/puppet dir during install Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3035) Debian package does not create /var/run/puppet dir during install
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3035 Debian package does not create /var/run/puppet dir during install Change By: Kylo Ginsberg Sprint: 2014-09-03 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-767) Show if an event was due to a change in the catalog or not
Title: Message Title Carl Caum commented on an issue Re: Show if an event was due to a change in the catalog or not My first reaction is that a non-idempotent resource is still an unexpected change. If an exec resource runs every single Puppet run. That's likely unexpected, i.e. a bug. If it is intentional, it should probably be a cron job, not a puppet resource. I'll give it more thought, though. Add Comment PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Events should be distinguishable as having occurred due to a change in the catalog or due to a change on the system. 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-683) facter id broken on solaris10 as root
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Kylo Ginsberg Affects Version/s: 2.2.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 (FACT-683) facter id broken on solaris10 as root
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Kylo Ginsberg 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 (FACT-683) facter id broken on solaris10 as root
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Kylo Ginsberg Fix Version/s: 2.2.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 (PDB-767) Show if an event was due to a change in the catalog or not
Title: Message Title Kenneth Barber commented on an issue Re: Show if an event was due to a change in the catalog or not Carl Caum its sometimes not a change at all though, but hey - maybe this is just waffling detail. If we can't tell the difference its not the end of the world also, by alerting a user and letting them do the last haul investigation to figure it out the difference between a manual change and an idempotency bug, its still a lot better then not being able to alert them at all. If you show the history of the resource over time (in regards to events) a human can quickly see a repeat event, and thus determine its an idempotency issue. However its nicer if we can guess for them, or provide a hint. Another alternative is to collect the full RAL status periodically in PDB and use that as another source of information to help answer the question. If we ran such a report out of band from the agent run, for example. We've talked about this to aid with detecting unmanaged resources, perhaps it can come into play also for this problem. Obviously we don't do this yet, but I think it has it uses. My only gripe with such a solution is that it requires more proper well developed resources for it to be useful, and we have a terribly small library of those due to the difficulty in developing them. Also, having thought about it, the idempotency bug might still show up here, since usually the symptoms of idempt. bugs are a bad status query for a propery/resource via RAL ... lol. Shucks, it's never easy . Add Comment PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Events should be distinguishable as having occurred due to a change in the catalog or due to a change on the system.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Kylo Ginsberg Assignee: EricSorenson 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-767) Show if an event was due to a change in the catalog or not
Title: Message Title Carl Caum commented on an issue Re: Show if an event was due to a change in the catalog or not Having a full resource list in PuppetDB would ENORMOUS use cases. This is a hack I wrote over a year ago to perform resource change detection of resources not being managed by Puppet. https://confluence.puppetlabs.com/pages/viewpage.action?pageId=20611331 I would love to have something like that as a product. Add Comment PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Events should be distinguishable as having occurred due to a change in the catalog or due to a change on the system. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Trevor Vaughan commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. This looks like a good solution to me. I'll roll it in and see if it works for what I'm doing. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3116) The read_mounts function reads /proc/mounts for every file call and should instead cache.
Title: Message Title Trevor Vaughan commented on an issue Re: The read_mounts function reads /proc/mounts for every file call and should instead cache. Any love here? I'm hoping to not roll a custom version of Puppet if possible. Add Comment Puppet / PUP-3116 The read_mounts function reads /proc/mounts for every file call and should instead cache. During a puppet run, the read_mounts function in util/selinux is called for each file that it managed on the system. As currently implemented, the system will read /proc/mounts for each file. While initially being unwanted due to unnecessary file IO, certain systems that use namespacing, such as OpenShift, create potentially thousands of redundant m... 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 (PDB-767) Show if an event was due to a change in the catalog or not
Title: Message Title Kenneth Barber commented on an issue Re: Show if an event was due to a change in the catalog or not Yeah, thats a nice demo Carl Caum . I'm a fan of the RAL idea also, lak was telling me about it last time I was in PDX. I'm not sure if you've spoken to him yet about it. Anyhow ... the RAL storage may assist with this problem, but its not mandatory. Maybe we need another ticket? The story around that is 'unmanaged resources' like you say in your demo ... and thats really a good piece of work on its own. But we don't have to do both to achieve this tickets goal for now, both pieces of work could probably be done incrementally. Add Comment PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Events should be distinguishable as having occurred due to a change in the catalog or due to a change on the system. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
Jira (PDB-767) Show if an event was due to a change in the catalog or not
Title: Message Title Kenneth Barber commented on an issue Re: Show if an event was due to a change in the catalog or not Unless I come up with another solution, I feel like this is dependant on historical catalogs, so I'm going to change the epic. API Evolution is just an internal one we care about, but Historical Data is higher on the radar. Add Comment PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Events should be distinguishable as having occurred due to a change in the catalog or due to a change on the system. 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-3116) The read_mounts function reads /proc/mounts for every file call and should instead cache.
Title: Message Title Kylo Ginsberg commented on an issue Re: The read_mounts function reads /proc/mounts for every file call and should instead cache. Trevor Vaughan can you turn that patch into a PR? We can discuss at weekly PR triage. Thanks! Add Comment Puppet / PUP-3116 The read_mounts function reads /proc/mounts for every file call and should instead cache. During a puppet run, the read_mounts function in util/selinux is called for each file that it managed on the system. As currently implemented, the system will read /proc/mounts for each file. While initially being unwanted due to unnecessary file IO, certain systems that use namespacing, such as OpenShift, create potentially thousands of redundant m... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3154) CLONE - Fix /var/lib/state permissions on redhat
Title: Message Title Christopher Price moved an issue Puppet / PUP-3154 CLONE - Fix /var/lib/state permissions on redhat Change By: Christopher Price Fix Version/s: 3.4.0 Fix Version/s: 3.7.0 Workflow: PuppetEnterprise Platform Workflow Key: PE PUP - 5718 3154 Project: Puppet Enterprise[Internal] 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
Jira (PUP-3154) CLONE - Fix /var/lib/state permissions on redhat
Title: Message Title Christopher Price updated an issue Puppet / PUP-3154 CLONE - Fix /var/lib/state permissions on redhat Change By: Christopher Price Assignee: ChristopherPrice MatthausOwens 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-3155) Improve spec tests around pe puppet version
Title: Message Title
Anderson Mills created an issue
Puppet / PUP-3155
Improve spec tests around pe puppet version
Issue Type:
Bug
Assignee:
Unassigned
Created:
28/Aug/14 4:10 PM
Priority:
Normal
Reporter:
Anderson Mills
Several spec tests started to fail when run in CI because of poor isolation with the host environment.
Failures:
1) Puppet#version should be valid semver
Failure/Error: SemVer.should be_valid Puppet.version
expected valid?(3.6.2 (Puppet Enterprise 3.3.0)) to return true, got nil
# ./spec/unit/puppet_spec.rb:12:in `block (3 levels) in top (required)'
2) Puppet::Util::CommandLine#execute should print the version and exit if --version is given
Failure/Error: expect do
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
3.6.2 (Puppet Enterprise 3.3.0)
# ./spec/unit/util/command_line_spec.rb:71:in `block (4 levels) in top (required)'
3) Puppet::Util::CommandLine#execute should print the version and exit if -V is given
Failure/Error: expect do
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
3.6.2 (Puppet Enterprise 3.3.0)
# ./spec/unit/util/command_line_spec.rb:71:in `block (4 levels) in top (required)'
4) Puppet::Util::CommandLine when dealing with puppet commands when the subcommand is not implemented and an external implementation cannot be found should abort and display --version information
Failure/Error: expect {
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
Error: Unknown Puppet subcommand 'whatever'
3.6.2 (Puppet Enterprise 3.3.0)
# ./spec/unit/util/command_line_spec.rb:126:in `block (6 levels) in top (required)'
5) Puppet::Util::CommandLine when dealing with puppet commands when the subcommand is not implemented and an external implementation cannot be found should abort and display -V information
Failure/Error: expect {
expected
Jira (PUP-3155) Improve spec tests around pe puppet version
Title: Message Title Anderson Mills assigned an issue to Anderson Mills Puppet / PUP-3155 Improve spec tests around pe puppet version Change By: Anderson Mills Assignee: AndersonMills 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-3154) CLONE - Fix /var/lib/state permissions on redhat
Title: Message Title Matthaus Owens commented on an issue Re: CLONE - Fix /var/lib/state permissions on redhat We already manage the perms of this directory on debian via the puppet-common postinst. It makes sense to do something similar for redhat. Add Comment Puppet / PUP-3154 CLONE - Fix /var/lib/state permissions on redhat On EL platforms, if the agent runs before puppetserver is started, then /var/lib/puppet/state is owned by root and we can't write reports there. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3155) Improve spec tests around pe puppet version
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3155 Improve spec tests around pe puppet version Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3154) Fix /var/lib/state permissions on redhat
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3154 Fix /var/lib/state permissions on redhat Change By: Kylo Ginsberg Summary: CLONE- Fix/var/lib/statepermissionsonredhat 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-3156) Fix /var/lib/state permissions on redhat
Title: Message Title Christopher Price moved an issue Puppet / PUP-3156 Fix /var/lib/state permissions on redhat Change By: Christopher Price Fix Version/s: 3.4.0 Fix Version/s: 3.4.0 Workflow: PuppetEnterprise Platform Workflow Key: PE PUP - 5721 3156 Project: Puppet Enterprise[Internal] 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
Jira (PUP-3156) Fix /var/lib/state permissions on redhat
Title: Message Title Christopher Price updated an issue Puppet / PUP-3156 Fix /var/lib/state permissions on redhat Change By: Christopher Price Fix Version/s: 3.4.0 Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3156) Fix /var/lib/state permissions on redhat
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3156 Fix /var/lib/state permissions on redhat Change By: Kylo Ginsberg Sprint: PEAugust27 ,2014-09-03 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-1884) Move puppet dependencies on windows into the puppet repo
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1884 Move puppet dependencies on windows into the puppet repo Change By: Josh Cooper Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1884) Move puppet dependencies on windows into the puppet repo
Title: Message Title Josh Cooper commented on an issue Re: Move puppet dependencies on windows into the puppet repo On Mac, from puppet repo, ran: $ bundle exec rake pl:jenkins:uber_build COW='' MOCK='' GEM=false DMG=false Downloaded x86 MSI from http://XXX/job/puppet-msi-2014-08-28-16-17-39-ebf1592, installed: C:\Windows\system32puppet --version 3.6.2 C:\Windows\system32ruby --version ruby 1.9.3p484 (2013-11-22) [i386-mingw32] C:\Windows\system32gem list *** LOCAL GEMS *** bigdecimal (1.1.0) deep_merge (1.0.0) ffi (1.9.3 x86-mingw32) io-console (0.3) json (1.5.5) minitar (0.5.4) minitest (2.5.1) rake (0.9.2.2) rdoc (3.9.5) stomp (1.2.9) win32-dir (0.4.9) win32-eventlog (0.6.1) win32-process (0.7.4) win32-security (0.2.5) win32-service (0.8.5) win32console (1.3.2 x86-mingw32) Downloaded and installed x64 MSI: C:\Windows\system32puppet --version 3.6.2 C:\Windows\system32ruby --version ruby 2.0.0p481 (2014-05-08) [x64-mingw32] C:\Windows\system32gem list *** LOCAL GEMS *** bigdecimal (1.2.0) deep_merge (1.0.1) ffi (1.9.3 x64-mingw32) io-console (0.4.2) json (1.7.7) minitar (0.5.4) minitest (4.3.2) psych (2.0.0) rake (0.9.6) rdoc (4.0.0) stomp (1.3.2) test-unit (2.0.0.0) win32-dir (0.4.9) win32-eventlog (0.6.1) win32-process (0.7.4) win32-security (0.2.5) win32-service (0.8.5) MSI's on commit, yo! Add Comment Puppet / PUP-1884 Move puppet dependencies on windows into the puppet repo
Jira (PUP-1884) Move puppet dependencies on windows into the puppet repo
Title: Message Title
Josh Cooper commented on an issue
Re: Move puppet dependencies on windows into the puppet repo
Merged into puppet master in 6328a4b168
Add Comment
Puppet / PUP-1884
Move puppet dependencies on windows into the puppet repo
Currently the logic for puppet dependencies on Windows is kept in the jenkins job used to build the MSI. This ticket is about moving that logic into the puppet repo. As outlined in RE-876: {quote} Add ext/windows_versions.yaml to puppet repo listing dependencies on facter, hiera, puppet-win32-ruby, and MSI artifacts (icons) in puppet_for_the_win. Also...
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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title
Zack Smith commented on an issue
Re: When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
This is pretty bad as this is standard workflow and would cause code to be deployed that was meant to be noop'ed and cause and extremely unintuitive result to occur.
Add Comment
Puppet / PUP-3077
When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Steps to reproduce: - do not disable {{pe-puppet}} service - successfully compile catalog from non-Production environment using {{puppet agent -t --noop --environment manage_meta}}, catalog is cached locally - puppet master fails to compile catalog in agent's assigned environment (e.g. because a new class is assigned for testing non-Production code) ...
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
Jira (PUP-3153) Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3153 Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks Change By: Kylo Ginsberg Sprint: 2014-09-03 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-3153) Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-3153 Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks Change By: Kylo Ginsberg Assignee: KyloGinsberg 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-3151) Add jetty_external_root_ca.rb acceptance test
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3151 Add jetty_external_root_ca.rb acceptance test Change By: Jeremy Barlow Fix Version/s: 3.7.0 Fix Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3035) Debian package does not create /var/run/puppet dir during install
Title: Message Title Josh Cooper commented on an issue Re: Debian package does not create /var/run/puppet dir during install Merged to master in commit 62cd16ab Add Comment Puppet / PUP-3035 Debian package does not create /var/run/puppet dir during install It looks like `/var/run/puppet` has typically been created during by the debian init script if it didn't exist already: https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init#L22 This should instead be handled by the `puppet-common.dirs` file in the `puppet-common` package. I say that it should be included in the `puppet-common` ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3156) Fix /var/lib/state permissions on redhat
Title: Message Title Josh Cooper commented on an issue Re: Fix /var/lib/state permissions on redhat Merged to master in 1ab6030b Add Comment Puppet / PUP-3156 Fix /var/lib/state permissions on redhat On EL platforms, if the agent runs before puppetserver is started, then /var/lib/puppet/state is owned by root and we can't write reports there. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2984) MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title
Josh Cooper commented on an issue
Re: MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Merged to puppet_for_the win in c61dda25 and updated puppet dependency in 718cb2e
Add Comment
Puppet / PUP-2984
MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
MSI architecture change from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec. It also doesn't remove the older path - this is what remains after install of x86 AFTER x64: {{C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin}} and it should be {{C:\Progra...
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
Jira (PUP-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title Zack Smith updated an issue Puppet / PUP-3077 When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment Change By: Zack Smith Labels: TSE 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-3157) helpful_error_message_when_hostname_not_match_server_certificate test does not tolerate variable DNS alt name order
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-3157 helpful_error_message_when_hostname_not_match_server_certificate test does not tolerate variable DNS alt name order Issue Type: Bug Assignee: Jeremy Barlow Created: 28/Aug/14 5:47 PM Fix Versions: 3.7.1 Priority: Normal Reporter: Jeremy Barlow The `helpful_error_message_when_hostname_not_match_server_certificate.rb` test evaluates the DNS alt names which appear in the Subject Alternative Name extension from the Puppet master's server certificate. The order in which these appear in the certificate does not translate directly to the order in which these may be received at the OpenSSL layer and outputted into the agent log. If the order in which these were inserted into the certificate at signing time were to change, the test would break. The test should be altered to tolerate a variable order for the enumeration of the DNS alt names. Add Comment
Jira (PUP-3158) Improve spec tests around pe puppet version
Title: Message Title
Anderson Mills created an issue
Puppet / PUP-3158
Improve spec tests around pe puppet version
Issue Type:
Bug
Assignee:
Unassigned
Created:
28/Aug/14 6:15 PM
Fix Versions:
3.7.0
Priority:
Normal
Reporter:
Anderson Mills
Several spec tests started to fail when run in CI because of poor isolation with the host environment.
Failures:
1) Puppet#version should be valid semver
Failure/Error: SemVer.should be_valid Puppet.version
expected valid?(3.6.2 (Puppet Enterprise 3.3.0)) to return true, got nil
# ./spec/unit/puppet_spec.rb:12:in `block (3 levels) in top (required)'
2) Puppet::Util::CommandLine#execute should print the version and exit if --version is given
Failure/Error: expect do
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
3.6.2 (Puppet Enterprise 3.3.0)
# ./spec/unit/util/command_line_spec.rb:71:in `block (4 levels) in top (required)'
3) Puppet::Util::CommandLine#execute should print the version and exit if -V is given
Failure/Error: expect do
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
3.6.2 (Puppet Enterprise 3.3.0)
# ./spec/unit/util/command_line_spec.rb:71:in `block (4 levels) in top (required)'
4) Puppet::Util::CommandLine when dealing with puppet commands when the subcommand is not implemented and an external implementation cannot be found should abort and display --version information
Failure/Error: expect {
expected /^3.6.2 (Puppet Enterprise 3.3.0)$/ to be printed; got:
Error: Unknown Puppet subcommand 'whatever'
3.6.2
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests There's a PR up (linked in the ticket) that can be reviewed for the discussed functionality, including the compilation halt for manifest conflict. We're still working on some integration specs. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PDB-846) equality operator inconsistency in v2/v3 across resources and facts
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-846 equality operator inconsistency in v2/v3 across resources and facts Issue Type: Bug Affects Versions: 2.2.0 Assignee: Unassigned Created: 28/Aug/14 7:53 PM Priority: Normal Reporter: Wyatt Alt The v2/v3 API documentation says that equality queries must be predicated on matching types. It appears that this is true for resource queries (tested on the exported field) as indicated in the docs, but not for facts. In the case of facts there is even a unit test ensuring that mixed types work. This ticket is to determine correct behavior. https://docs.puppetlabs.com/puppetdb/1.6/api/query/v3/ope... https://github.com/puppetlabs/puppetdb/blob/c2b70a06f8de7de16137a96d49cd891050f50a97/test/com/puppetlabs/puppetdb/test/http/nodes.clj#L135 Add Comment
