Jira (PUP-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title
Michal Bryx commented on an issue
Re: mode attribute of file type doesn't behave like chmod when given X
New PR was created.
Add Comment
Puppet / PUP-2583
mode attribute of file type doesn't behave like chmod when given X
{code} file { '/tmp/permtest': ensure = 'present', mode = '0600' } {code} behaves as expected creating file '/permtest' with given permissions changing to {code} file { '/tmp/permtest': ensure = 'present', mode = 'g+rX' } {code} doesn't behave as expected. Changes permissions from 0600 to 0650. The permissions should be '0640' since /permtes...
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-2717) Unable to confine NetworkDevice using facter values
Title: Message Title Gavin Williams created an issue Puppet / PUP-2717 Unable to confine NetworkDevice using facter values Issue Type: Bug Affects Versions: 3.5.1 Assignee: Andy Parker Components: Server Created: 03/Jun/14 1:24 AM Priority: Major Reporter: Gavin Williams Currently, it appears that it is impossible to use confine with facter values when running against a NetworkDevice, as discussed here[1]. [1] https://groups.google.com/forum/#!topic/puppet-dev/_DXOY8UrDXs Add Comment
Jira (PUP-2717) Unable to confine NetworkDevice using facter values
Title: Message Title Brice Figureau commented on an issue Re: Unable to confine NetworkDevice using facter values The problem is that the Fact based confiner directly calls Facter instead of using the indirector. Add Comment Puppet / PUP-2717 Unable to confine NetworkDevice using facter values Currently, it appears that it is impossible to use _confine_ with facter values when running against a NetworkDevice, as discussed here[1]. [1] https://groups.google.com/forum/#!topic/puppet-dev/_DXOY8UrDXs 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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-1100
create_resources auto importing a manifest with a syntax error produce a bad error message
Change By:
Felix Frank
Givenamodulewiththisstructure: pre {noformat} x└──manifests├──init.pp└──y.pp/preinit.pp:preclassx{$r={one={foo=bar}}create_resources(x::y,$r)} /pre {noformat} andy.ppwhichhasanobvioussyntaxerror: pre {code} definex::y{obviouserrorshouldbeobvious} /pre {code} Igetthefollowingerror: pre {noformat} %puppetapply--modulepath=`pwd`-e'includex'Error:exceptionobjectexpectedat/home/rip/temp/x/manifests/init.pp:4onnodedevco.netWrappedexception:exceptionobjectexpectedError:exceptionobjectexpectedat/home/rip/temp/x/manifests/init.pp:4onnodedevco.net /pre {noformat} What'shappeninghereisthey.pponlygetsimportedduringtheprocessingofcreate_resourcesandinsidecreate_resourcestheparseerrorisincorrectlyhandled.Inthiscasethefollowingcode: pre {code} beginresource.safeevaluate(self)rescuePuppet::ParseError=internal_errorraiseinternal_error.originalend /pre {code} hasanilfororiginalintheinternal_errorobjectandsoitfails.
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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-1100
create_resources auto importing a manifest with a syntax error produce a bad error message
Change By:
Felix Frank
Givenamodulewiththisstructure:{noformat}x└──manifests├──init.pp└──y.pp /pre {noformat} init.pp: pre {noformat} classx{$r={one={foo=bar}}create_resources(x::y,$r)}{noformat}andy.ppwhichhasanobvioussyntaxerror:{code}definex::y{obviouserrorshouldbeobvious}{code}Igetthefollowingerror:{noformat}%puppetapply--modulepath=`pwd`-e'includex'Error:exceptionobjectexpectedat/home/rip/temp/x/manifests/init.pp:4onnodedevco.netWrappedexception:exceptionobjectexpectedError:exceptionobjectexpectedat/home/rip/temp/x/manifests/init.pp:4onnodedevco.net{noformat}What'shappeninghereisthey.pponlygetsimportedduringtheprocessingofcreate_resourcesandinsidecreate_resourcestheparseerrorisincorrectlyhandled.Inthiscasethefollowingcode:{code}beginresource.safeevaluate(self)rescuePuppet::ParseError=internal_errorraiseinternal_error.originalend{code}hasanilfororiginalintheinternal_errorobjectandsoitfails.
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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-1100 create_resources auto importing a manifest with a syntax error produce a bad error message Change By: Felix Frank Assignee: FelixFrank 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-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title
Felix Frank created an issue
Puppet / PUP-2718
Prefetching is prone to fail for eval_generated resources
Issue Type:
Improvement
Affects Versions:
3.x
Assignee:
Kylo Ginsberg
Components:
Catalog Application
Created:
03/Jun/14 3:50 AM
Priority:
Minor
Reporter:
Felix Frank
When the User type implemented purging of ssh_authorized_keys using the eval_generate hook, it became apparent that the following manifest
package { 'coreutils': before = User[root] } user { 'root': purge_ssh_keys = '/tmp/keyfile' }
would not purge any keys from /tmp/keyfile.
The reason is that prefetching of the keys fails in the following fashion:
When Transaction#evaluate starts traversing the graph, no ssh_authorized_key resources are yet part of the graph
each resource has a pre_process hook that invokes #prefetch_if_necessary
Jira (PUP-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2718
Prefetching is prone to fail for eval_generated resources
Change By:
Felix Frank
Whenthe{{User}}typeimplementedpurgingof{{ssh_authorized_keys}}usingthe{{eval_generate}}hook,itbecameapparentthatthefollowingmanifest{code} package{'coreutils':before=User[root]}user{'root':purge_ssh_keys='/tmp/keyfile'} {code}wouldnotpurgeanykeysfrom{{/tmp/keyfile}}.Thereasonisthatprefetchingofthekeysfailsinthefollowingfashion:#When{{Transaction#evaluate}}startstraversingthegraph,no{{ssh_authorized_key}}resourcesareyetpartofthegraph#eachresourcehasa{{pre_process}}hookthatinvokes{{#prefetch_if_necessary}}#thishappensforthe{{package}}resourcefist,and{{prefetch_if_necessary}}invokes{{resources_by_provider}},whichcachesahashofallresourcesinthegraph#duringitsevaluation,the{{user}}resourcegenerates{{ssh_authorized_key}}resourcesforpurging#thesekeysalsoinvoke{{prefetch_if_necesary}},buttheresultfrom{{resources_by_provider}}iscachedandlackstheirreferences#noresourcesarepassedtotheprovider's{{prefetch}}method,theproviderconsiderstheentitiestobeunmanagedandtheresourcesarefalselydeterminedtobealreadyabsentAworkaroundmaycompriseawaytoinvalidatethecacheofthe{{Transaction#resources_by_provider}}methodupon{{eval_generate}ingresources.Thisneedsadecision,though.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2718
Prefetching is prone to fail for eval_generated resources
Change By:
Felix Frank
Whenthe{{User}}typeimplementedpurgingof{{ssh_authorized_keys}}usingthe{{eval_generate}}hook,itbecameapparentthatthefollowingmanifest{code}package{'coreutils':before=User[root]}user{'root':purge_ssh_keys='/tmp/keyfile'}{code}wouldnotpurgeanykeysfrom{{/tmp/keyfile}}.Thereasonisthatprefetchingofthekeysfailsinthefollowingfashion:#When{{Transaction#evaluate}}startstraversingthegraph,no{{ssh_authorized_key}}resourcesareyetpartofthegraph#eachresourcehasa{{pre_process}}hookthatinvokes{{#prefetch_if_necessary}}#thishappensforthe{{package}}resourcefirst,and{{prefetch_if_necessary}}invokes{{resources_by_provider}},whichcachesahashofallresourcesinthegraph#duringitsevaluation,the{{user}}resourcegenerates{{ssh_authorized_key}}resourcesforpurging#thesekeysalsoinvoke{{prefetch_if_necesary}},buttheresultfrom{{resources_by_provider}}iscachedandlackstheirreferences#noresourcesarepassedtotheprovider's{{prefetch}}method,theproviderconsiderstheentitiestobeunmanagedandtheresourcesarefalselydeterminedtobealreadyabsentAworkaroundmaycompriseawaytoinvalidatethecacheofthe{{Transaction#resources_by_provider}}methodupon{{eval_generate} } ingresources.Thisneedsadecision,though.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2718
Prefetching is prone to fail for eval_generated resources
Change By:
Felix Frank
Whenthe{{User}}typeimplementedpurgingof{{ssh_authorized_keys}}usingthe{{eval_generate}}hook,itbecameapparentthatthefollowingmanifest{code}package{'coreutils':before=User[root]}user{'root':purge_ssh_keys='/tmp/keyfile'}{code}wouldnotpurgeanykeysfrom{{/tmp/keyfile}}.Thereasonisthatprefetchingofthekeysfailsinthefollowingfashion:#When{{Transaction#evaluate}}startstraversingthegraph,no{{ssh_authorized_key}}resourcesareyetpartofthegraph#eachresourcehasa{{pre_process}}hookthatinvokes{{#prefetch_if_necessary}}#thishappensforthe{{package}}resource fist first ,and{{prefetch_if_necessary}}invokes{{resources_by_provider}},whichcachesahashofallresourcesinthegraph#duringitsevaluation,the{{user}}resourcegenerates{{ssh_authorized_key}}resourcesforpurging#thesekeysalsoinvoke{{prefetch_if_necesary}},buttheresultfrom{{resources_by_provider}}iscachedandlackstheirreferences#noresourcesarepassedtotheprovider's{{prefetch}}method,theproviderconsiderstheentitiestobeunmanagedandtheresourcesarefalselydeterminedtobealreadyabsentAworkaroundmaycompriseawaytoinvalidatethecacheofthe{{Transaction#resources_by_provider}}methodupon{{eval_generate}ingresources.Thisneedsadecision,though.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2718
Prefetching is prone to fail for eval_generated resources
Change By:
Felix Frank
Whenthe{{User}}typeimplementedpurgingof{{ssh_authorized_keys}}usingthe{{eval_generate}}hook,itbecameapparentthatthefollowingmanifest{code}package{'coreutils':before=User[root]}user{'root':purge_ssh_keys='/tmp/keyfile'}{code}wouldnotpurgeanykeysfrom{{/tmp/keyfile}}.Thereasonisthatprefetchingofthekeysfailsinthefollowingfashion:#When{{Transaction#evaluate}}startstraversingthegraph,no{{ssh_authorized_key}}resourcesareyetpartofthegraph#eachresourcehasa{{pre_process}}hookthatinvokes{{#prefetch_if_necessary}}#thishappensforthe{{package}}resourcefirst,and{{prefetch_if_necessary}}invokes{{resources_by_provider}},whichcachesahashofallresourcesinthegraph#duringitsevaluation,the{{user}}resourcegenerates{{ssh_authorized_key}}resourcesforpurging#thesekeysalsoinvoke{{prefetch_if_necesary}},buttheresultfrom{{resources_by_provider}}iscachedandlackstheirreferences#noresourcesarepassedtotheprovider's{{prefetch}}method,theproviderconsiderstheentitiestobeunmanagedandtheresourcesarefalselydeterminedtobealreadyabsentAworkaroundmaycompriseawaytoinvalidatethecacheofthe{{Transaction#resources_by_provider}}methodupon{{eval_generate}} - ingresources.Thisneedsadecision,though.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PDB-699) Ability to have different puppetdb servers for agent vs master
Title: Message Title Erik Daln created an issue PuppetDB / PDB-699 Ability to have different puppetdb servers for agent vs master Issue Type: New Feature Assignee: Unassigned Created: 03/Jun/14 4:46 AM Priority: Normal Reporter: Erik Daln It should be possible to specify different puppetdb config files for the agent, apply and master applications. Atm all of them will read puppetdb.conf from the confdir, and the confdir is tricky to configure in the puppet config file. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 Pull request Allow configurable url prefix has been closed. Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds commented on an issue Re: Windows mount provider (smb/cifs) Joshua Cooper - did we ever implement this? Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds commented on an issue Re: Windows mount provider (smb/cifs) Travis Fields perhaps it is better to have this in MODULES? Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2719) Windows mount provider (smb/cifs)
Title: Message Title redmine.exporter created an issue Puppet / PUP-2719 Windows mount provider (smb/cifs) Issue Type: New Feature Assignee: Unassigned Created: 03/Jun/14 7:34 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. Add Comment
Jira (PUP-2719) Windows mount provider (smb/cifs)
Title: Message Title Paul Ttterman updated an issue Puppet / PUP-2719 Windows mount provider (smb/cifs) Apologies for removing the gist. I no longer remembered why it was there, and I've given up on this approach anyway. Here's something that won't disappear. Change By: Paul Ttterman Attachment: mapped_drive.rb 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Paul Ttterman commented on an issue Re: Windows mount provider (smb/cifs) As an aside, I'm not using this because it turns out that while puppet doesn't support UNC paths (or didn't when this ticket was originally opened), the msiexec call made by the package provider can just be passed an UNC path and it works nicely. So no need to map network drives in order to install packages from shares. Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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
Jira (PUP-2720) Add acceptance test for PMT changes command
Title: Message Title John Duarte created an issue Puppet / PUP-2720 Add acceptance test for PMT changes command Issue Type: Task Assignee: Unassigned Created: 03/Jun/14 8:15 AM Priority: Normal Reporter: John Duarte 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-2720) Add acceptance test for PMT changes command
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2720 Add acceptance test for PMT changes command Change By: John Duarte Assignee: JohnDuarte 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds commented on an issue Re: Windows mount provider (smb/cifs) I added notes for an implementation that would create a persisted drive at https://ask.puppetlabs.com/question/10026/best-way-to-map-a-drive-on-windows/ Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds commented on an issue Re: Windows mount provider (smb/cifs) Paul Ttterman thanks for providing that. Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds commented on an issue Re: Windows mount provider (smb/cifs) Paul Ttterman - we fixed UNC support for file resources in 3.4.0 - see https://projects.puppetlabs.com/issues/8657 Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2689) A node can't always collect its own exported resources
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2689 A node can't always collect its own exported resources Change By: Andy Parker Assignee: 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-514) Add optional type to parameters
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-514 Add optional type to parameters Change By: Andy Parker Assignee: AndyParker 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Adrien Thebo Assignee: AdrienThebo 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-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title Peter Huene updated an issue Puppet / PUP-2583 mode attribute of file type doesn't behave like chmod when given X 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo commented on an issue Re: 3.6.1 issues warning message for deprecation Functional review steps: Ensure that running `puppet resource package --disable_warnings deprecations` on platforms that have the `allow_virtual` parameter do not emit deprecation warnings. The following should also work: └ bexec puppet apply -e 'notice(hi)' --disable_warnings deprecations --catalog_format loldeprecated Notice: Scope(Class[main]): hi Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds Notice: Finished catalog run in 0.10 seconds └ bexec puppet apply -e 'notice(hi)' --catalog_format loldeprecated Warning: Setting 'catalog_format' is deprecated; use 'preferred_serialization_format' instead. (at /home/adrien/eng/projects/platform/puppet/lib/puppet/settings.rb:1296:in `set') Notice: Scope(Class[main]): hi Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds Notice: Finished catalog run in 0.10 seconds (The --disable_warnings deprecations must be before the deprecated setting to ensure it can be set in time to disable the warnings for the other setting) Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in...
Jira (FACT-459) MTU interface facts not being reported on Archlinux.
Title: Message Title
Kurt Wall commented on an issue
Re: MTU interface facts not being reported on Archlinux.
Verified in stable at SHA=29a0a0cdd143aafe3cafe0ec787b48b381a9583a. Well, I verified it didn't break existing functionality. Lacking an arch linux system, that's what we get:
$ bundle exec facter | grep mtu_
mtu_bridge0 = 1500
mtu_en0 = 1500
mtu_en2 = 1500
mtu_en3 = 1500
mtu_en4 = 1500
mtu_fw0 = 4078
mtu_gif0 = 1280
mtu_lo0 = 16384
mtu_p2p0 = 2304
mtu_stf0 = 1280
Add Comment
Facter / FACT-459
MTU interface facts not being reported on Archlinux.
On Archlinux, the mtu_interface facts are not being returned by facter. This is because the regex being used is: {code} /MTU:(\d+)/ {code} When it should be: {code} /MTU:?\s*(\d+)/i {code} Given that ifconfig outputs mtu 1500, for example.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to
Jira (PUP-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title
Peter Huene commented on an issue
Re: mode attribute of file type doesn't behave like chmod when given X
The fix has been merged to master with 1c4e536c26.
Add Comment
Puppet / PUP-2583
mode attribute of file type doesn't behave like chmod when given X
{code} file { '/tmp/permtest': ensure = 'present', mode = '0600' } {code} behaves as expected creating file '/permtest' with given permissions changing to {code} file { '/tmp/permtest': ensure = 'present', mode = 'g+rX' } {code} doesn't behave as expected. Changes permissions from 0600 to 0650. The permissions should be '0640' since /permtes...
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-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Kurt Wall Assignee: KurtWall 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-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title Peter Huene updated an issue Puppet / PUP-2583 mode attribute of file type doesn't behave like chmod when given X Change By: Peter Huene 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-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title Peter Huene updated an issue Puppet / PUP-2583 mode attribute of file type doesn't behave like chmod when given X Change By: Peter Huene Sprint: Week2014-5-28to2014-6-4 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-2281) Publish Azure VM update that use external FQDN for MCO / simplified install
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2281 Publish Azure VM update that use external FQDN for MCO / simplified install Change By: Ethan Brown Summary: PublishAzureVMupdate thatuseexternalFQDN for PE3.2.3 MCO/simplifiedinstall 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-2281) Publish Azure VM update for PE 3.2.3
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2281 Publish Azure VM update for PE 3.2.3 Change By: Ethan Brown Summary: PublishAzureVMupdateforPE3.2. 2/AddressMCOandsimplifiedinstallbugs 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-1238) tag metaparam not working
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-1238
tag metaparam not working
Change By:
Andy Parker
Givenamanifest: pre {code} classtest{tag(bob)file{/tmp/test:ensure=present,content=template('/tmp/filet'),tag=files,}}includetest /pre {code} Withthetemplate: pre {code} %tags.eachdo|tag|-%Thetag%=tag%ispartofthecurrentscope%end-%%all_tags.eachdo|tag|-%Thetag%=tag%isdefined%end-% /pre {code} WhenIruneither: pre {noformat} puppet--tagsfiles/tmp/file.pp /pre {noformat} or: pre {noformat} puppet/tmp/file.pp /pre {noformat} Iget: pre {noformat} ThetagclassispartofthecurrentscopeThetagtestispartofthecurrentscopeThetagbobispartofthecurrentscopeThetagsettingsisdefinedThetagclassisdefinedThetagtestisdefined /pre {noformat} Nosignofthetagfilesanywhere.
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-1238) tag metaparam not working
Title: Message Title
Andy Parker commented on an issue
Re: tag metaparam not working
This is completely expected. The files tag hasn't been created anywhere yet at the point the template is evaluated. The template is evaluated on the master while it is determining how to construct the file resource to put into the catalog. Until the file resource is there the files tag doesn't exist.
Add Comment
Puppet / PUP-1238
tag metaparam not working
Given a manifest: {code} class test {tag(bob) file { /tmp/test: ensure = present, content = template('/tmp/filet'), tag = files, } } include test {code} With the template: {code} % tags.each do |tag| -% The tag %= tag % is part of the current scope % end -% % all_tags.eac...
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,
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2650 3.6.1 issues warning message for deprecation 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-2381) Tags should issue an error when they are invalid
Title: Message Title
Andy Parker commented on an issue
Re: Tags should issue an error when they are invalid
While working on another issue (PUP-2689) I came across this issue, as well. After some investigation there are a lot of other cases where tags don't seem to validate in the way I would expect. See a comment on a commits that was part of the work.
I'll recreate the gist of it here:
The commit changed it to make the tag ab produce an error because it would create an empty string tag.
I talked this over with @jpartlow and he agreed that the error message is confusing. After a bit of testing it out it also turns out that it doesn't actually catch a lot of cases. For example, notify { hi: tag = [a::] } is valid, but notify { hi: tag = [::a] } is now an error. It also turns out that notify { hi: tag = [undef] } or notify { hi: tag = [$bar] } (where $bar is not defined) also work, but notify { hi: tag = [] } doesn't work. Likewise notify { hi: tag = [ ] } fails because of an invalid tag, but notify { hi: tag = [a:: ::b] } succeeds.
We eventually came to the decision to leave out this extra error checking so as to not break any existing manifests and stop it from being even more inconsistent
I'll put some commits on top of this PR before merging it in to fix up this issue.
Add Comment
Puppet / PUP-2381
Tags should issue an error when they are invalid
The docs ( http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#tags ) state ( emphasis added) that tags names *should* confirm to {noformat}\A[a-z0-9_][a-z0-9_:\.\-]*\Z{noformat} and also: {quote} Tags *must* begin with a lowercase letter, number, or underscore, and can include: - Lowercase letters - Numbers -
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title
Andy Parker commented on an issue
Re: A node can't always collect its own exported resources
Merged into stable in 9d6b05.
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
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-2722) Puppet logs sensitive data to log files
Title: Message Title Greg Swift created an issue Puppet / PUP-2722 Puppet logs sensitive data to log files Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 03/Jun/14 1:00 PM Labels: security logging Priority: Normal Reporter: Greg Swift As a standard port of puppet's behaviour it logs changes to files. This is known and expected. However storing secrets in a log that might get centralized to a system is not necessarily a great idea. Would be nice if there was a way to still log that X changed without logging what it changed to. Example: (/Stage[main]/Profile_serviceA/ServiceA::Config::Auth[aPassword]/ServiceA::Config[auth-aPassword]/Ini_setting[/etc/auth.properties:aPassword]/value) value changed 'changeme' to 'realpassword' Could be: (/Stage[main]/Profile_serviceA/ServiceA::Config::Auth[aPassword]/ServiceA::Config[auth-aPassword]/Ini_setting[/etc/auth.properties:aPassword]/value) value changed. And (/Stage[main]/Monitor::Agent/File[/etc/monitor_agent.conf]/content) #012--- /etc/monitor_agent.conf#0112014-04-02 22:13:42.0 #012 ++
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2692 Puppet master passenger processes keep growing Change By: Kurt Wall Assignee: KurtWall 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-2723) Better logging around ENC timeouts
Title: Message Title Zachary Stern created an issue Puppet / PUP-2723 Better logging around ENC timeouts Issue Type: Bug Assignee: Unassigned Created: 03/Jun/14 1:09 PM Priority: Normal Reporter: Zachary Stern When there's a timeout of the ENC script, an error shows up on the agent side, but nothing on the master. By putting in an ENC script that just waits for 500 seconds, I was able to produce this: ``` [root@pe-313-master ~]# puppet agent --test Error: Failed to apply catalog: Timeout::Error ``` However, there was no corresponding error in the master logs. If the master tries to run the ENC script, but times out, shouldn't there be an error of some kind logged on the master side? Add Comment This
Jira (PUP-2723) Better logging around ENC timeouts
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-2723
Better logging around ENC timeouts
Change By:
Zachary Stern
Whenthere'satimeoutoftheENCscript,anerrorshowsupontheagentside,butnothingonthemaster.ByputtinginanENCscriptthatjustwaitsfor500seconds,Iwasabletoproducethis: ``` {code} [root@pe-313-master~]#puppetagent--testError:Failedtoapplycatalog:Timeout::Error ``` {code} However,therewasnocorrespondingerrorinthemasterlogs.IfthemastertriestoruntheENCscript,buttimesout,shouldn'ttherebeanerrorofsomekindloggedonthemasterside?
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-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2710 Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+) 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-514) Add optional type to parameters
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-514 Add optional type to parameters Change By: Andy Parker Assignee: 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-514) Add optional type to parameters
Title: Message Title Andy Parker updated an issue Puppet / PUP-514 Add optional type to parameters Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title Peter Huene updated an issue Puppet / PUP-2583 mode attribute of file type doesn't behave like chmod when given X Change By: Peter Huene Component/s: TypesandProviders 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-2692) Puppet master passenger processes keep growing
Title: Message Title Kurt Wall commented on an issue Re: Puppet master passenger processes keep growing I ran a pathological loop that called puppet agent --test 100 times while monitoring master passenger memory usage with GNOME System Monitor. RSS size grew from 66.8 MiB (at the beginning) to 83.2 MiB (around the 40th iteration), then seemed to plateau at the larger value. Killing the puppet master and restarting freed the memory, of course. Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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-2692) Puppet master passenger processes keep growing
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2692 Puppet master passenger processes keep growing Change By: Kurt Wall Assignee: KurtWall 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-2360) Yumrepo type allows invalid values
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2360 Yumrepo type allows invalid values Change By: Kurt Wall Assignee: KurtWall 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Ashwanth Fernando commented on an issue Re: Services should support 'reload' in addition to 'restart' When can this be fixed?. Reload needs to be supported. Services such as nGinx support a reload in addition to a restart which will load the new configuration without interrupting TCP connections that are inflight. Add Comment Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter ser... 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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Adrien Thebo
Labels:
service trivial
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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo commented on an issue
Re: Validation for `enable` in service{} is lacking.
Unassigning from myself since this isn't in an upcoming sprint.
Add Comment
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
[root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running Error: The systemd provider can not handle attribute enable Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable I discovered this while breaking Postgresql. It happily passes a value of running...
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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo commented on an issue
Re: Validation for `enable` in service{} is lacking.
Fixing this should be a matter of ensuring that the `enable` field in the service type (https://github.com/puppetlabs/puppet/blob/3.6.1/lib/puppet/type/service.rb#L67-L70) is a valid value.
Add Comment
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
[root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running Error: The systemd provider can not handle attribute enable Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable I discovered this while breaking Postgresql. It happily passes a value of running...
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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Adrien Thebo
Assignee:
AdrienThebo 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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Joshua Cooper
{noformat} [root@ccoifar9r5c1giypostgresql]#puppetresourceservicepostgresqlenable=runningError:ThesystemdprovidercannothandleattributeenableError:/Service[postgresql]/enable:changefromtruetorunningfailed:Thesystemdprovidercannothandleattributeenable {noformat} IdiscoveredthiswhilebreakingPostgresql.Ithappilypassesavalueofrunningintotheproviderswhichthenexplode.
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-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Joshua Cooper commented on an issue Re: puppet module generate should produce a skeleton spec test Pieter van de Bruggen I was not able to get the skeleton spec test to work correctly. Can you take a look at this? Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. 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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Joshua Cooper
Component/s:
Trivial
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-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Joshua Cooper Assignee: JoshuaCooper PietervandeBruggen 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-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo commented on an issue
Re: Validation for `enable` in service{} is lacking.
Moving from Ready for Engineering to open since we're not actively planning to work on this in the next few months.
Add Comment
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
{noformat} [root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=running Error: The systemd provider can not handle attribute enable Error: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable {noformat} I discovered this while breaking Postgresql. It happily p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2512) Validation for `enable` in service{} is lacking.
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-2512
Validation for `enable` in service{} is lacking.
Change By:
Adrien Thebo
Labels:
service trivial
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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Joshua Cooper Assignee: PietervandeBruggen 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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title
Joshua Cooper commented on an issue
Re: Allow excluding content from Puppet module tool built packages
Pieter van de Bruggen This looks like a module tool PR, please take a look
Add Comment
Puppet / PUP-2040
Allow excluding content from Puppet module tool built packages
Puppet module tool only excludes some files from built tarball {{.\*, ~\*, pkg, ...}} The result is that module tarballs could have spec files, fixtures, and any temporary files created during build It should allow excluding content with {{puppet module build --exclude PATTERN1,PATTERN2,...}}
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-2423) Filebucket server should warn, not fail, if checksum type is not supported
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2423 Filebucket server should warn, not fail, if checksum type is not supported Change By: Joshua Cooper Component/s: Trivial 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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Joshua Cooper commented on an issue Re: Puppet package acceptance is sufficient for a smoke test Kurt Wall Do you have any idea when this can be done? Add Comment Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test The current version of the package acceptance test jobs for Puppet does not sufficiently cover what we have been checking for smoke tests. Looking at the list of tests from PP-364, the points we are missing are: * The ability to test the msi packages on vcloud windows templates * A Beaker that uses the service scripts for starting and stopping pupp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-927) puppet apply on Windows always uses *nix style newlines from templates
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-927 puppet apply on Windows always uses *nix style newlines from templates Change By: Joshua Cooper Component/s: Trivial 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-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1270 PR (2200) 'pkg' package provider does not understand IPS package versions properly Change By: Adrien Thebo Labels: redmine solaris 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-1042) Puppet apply runmode should write classes.txt file
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1042 Puppet apply runmode should write classes.txt file Change By: Joshua Cooper 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-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-1270
PR (2200) 'pkg' package provider does not understand IPS package versions properly
Change By:
Joshua Cooper
Itwouldseemthe'pkg'provider(forillumos/Solaris/OpenSolarisIPS)doesnotdotherightthingwithIPSpackageversions.We'rerunningOmniOSandseeingthis: {noformat} kekkonen~%pfexecpuppetapply-e'package{mdb:ensure=latest}'Notice:Compiledcatalogforkekkonen.niksula.hut.fiinenvironmentproductionin1.17secondsNotice:Finishedcatalogrunin6.39secondskekkonen~%pfexecpkgupdate-nvmdbPackagestoupdate:1Estimatedspaceavailable:14.11TBEstimatedspacetobeconsumed:24.61MBCreatebootenvironment:NoCreatebackupbootenvironment:YesRebuildbootarchive:NoChangedpackages:omniosdeveloper/debug/mdb0.5.11,5.11-0.151006:20130731T194820Z-0.5.11,5.11-0.151006:20131019T183740Z {noformat} Sopuppetthinkstherearenoupdates,butpkgcorrectlynoticesthatanupdateisavailable(onlythetimestamphaschanged,nottheversion,buildrelease,orbranchnumbers).puppetresourceprovidessomeinsightintothis: {noformat} kekkonen~%puppetresourcepackagemdbpackage{'mdb':ensure='0.5.11-0.151006',} {noformat} Thisversionnumberisnotcorrect,it'smissingthebuildrelease(5.11)andtimestamp.
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-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1270 PR (2200) 'pkg' package provider does not understand IPS package versions properly Change By: Adrien Thebo Component/s: TypesandProviders 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-1700) Update Puppet Package Acceptance tests to make use of the new package_build_url parameter for tracing pipeline errors.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1700 Update Puppet Package Acceptance tests to make use of the new package_build_url parameter for tracing pipeline errors. Change By: Kylo Ginsberg Assignee: RogerIgnazio 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-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-41 Puppet returns different result non-existent services on EL and Debian Change By: Kylo Ginsberg Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Puppet returns different result non-existent services on EL and Debian
Backlog grooming: Marking this as Open and removing Fix Version. If this is still a PE priority, please comment in the ticket.
Add Comment
Puppet / PUP-41
Puppet returns different result non-existent services on EL and Debian
EL and Debian have different results for service resources that don't exist. On EL, `puppet resource service abcdefg` will return service { 'abcdefg': ensure = 'stopped', enable = 'false', } On Debian, this will return Error: Could not run: Could not find init script for 'abcdefg' While what is returned by puppet on EL is te...
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-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Joshua Cooper commented on an issue Re: Hiera stable acceptance tests use dynamically provisioned vcloud templates. Kurt Wall Any update when this might happen? Add Comment Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Scott Schneider has already merged in changes to master which allow the Hiera Acceptance (master) Jenkins job to run against current puppet acceptance with dynamically provisioned vcloud templates. These templates do not exhibit the sporadic networking issues which have plagued the older templates. We need to get these changes merged down into stable an... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Change By: Kylo Ginsberg Fix Version/s: future 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-2243) Using a prefix of a setting on the CLI doesn't work nor fail
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2243 Using a prefix of a setting on the CLI doesn't work nor fail Change By: Adrien Thebo Fix Version/s: future 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-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter Change By: Joshua Cooper 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-147) Add validation to the ZFS type
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-147 Add validation to the ZFS type Change By: Adrien Thebo Fix Version/s: 4.0.0 Fix Version/s: future 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-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Adrien Thebo commented on an issue Re: Puppet needs to delegate all fact loading to Facter This will probably tie into PUP-2104. Add Comment Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter 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-24) (#7643) Add WMI Operating System facts
Title: Message Title Adrien Thebo commented on an issue Re: (#7643) Add WMI Operating System facts Rob Reynolds structurable? Add Comment Facter / FACT-24 (#7643) Add WMI Operating System facts Figure out which facts from WMI OperatingSystem would make sense to include in facter, e.g. caption, country code, etc. Also which of them match existing facts, and which would be new facts. 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 Joshua Cooper updated an issue Puppet / PUP-575 Split windows wix files into respective repositories Change By: Joshua Cooper Fix Version/s: future 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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall commented on an issue Re: Puppet package acceptance is sufficient for a smoke test Josh I'll sit down with Justin Stoller this week to understand and scope the work. Add Comment Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test The current version of the package acceptance test jobs for Puppet does not sufficiently cover what we have been checking for smoke tests. Looking at the list of tests from PP-364, the points we are missing are: * The ability to test the msi packages on vcloud windows templates * A Beaker that uses the service scripts for starting and stopping pupp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance tests use dynamically provisioned vcloud templates. Josh RSN probably isn't the right answer. I'll sit down with Justin Stoller and sort it out. Answer by Thursday. Add Comment Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Scott Schneider has already merged in changes to master which allow the Hiera Acceptance (master) Jenkins job to run against current puppet acceptance with dynamically provisioned vcloud templates. These templates do not exhibit the sporadic networking issues which have plagued the older templates. We need to get these changes merged down into stable an... 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-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2659 Puppet stops working with error 'Attempted to pop, but already at root of the context stack.' Change By: Kurt Wall Assignee: KurtWall 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-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2710 Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+) 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 (FACT-24) (#7643) Add WMI Operating System facts
Title: Message Title Rob Reynolds commented on an issue Re: (#7643) Add WMI Operating System facts Adrien Thebo Add Comment Facter / FACT-24 (#7643) Add WMI Operating System facts Figure out which facts from WMI OperatingSystem would make sense to include in facter, e.g. caption, country code, etc. Also which of them match existing facts, and which would be new facts. 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-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Peter Huene updated an issue Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Change By: Peter Huene Component/s: TypesandProviders Affects Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Peter Huene updated an issue Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD 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-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Peter Huene commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD Hi Jasper Lievisse Adriaanse. I went ahead and fixed up your original PR after not hearing back from you. I've submitted it as GH-2736. Thanks! Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. 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-514) Add optional type to parameters
Title: Message Title
Andy Parker commented on an issue
Re: Add optional type to parameters
The type parameters are for classes, defines, and lambdas. The current implementation handles classes and defines, but the lambdas got left out in the cold. Working through that right now.
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x, Integ...
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-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Henrik Lindberg 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-1931) mount provider improvement when options property is not specified
Title: Message Title
Mark Bainter commented on an issue
Re: mount provider improvement when options property is not specified
I did some work on this but I'm not sure of the best path forward, so some feedback would be welcome. It is easy enough to detect in the provider when (as in the example) a device is not actually a block device, and then verify that loop is set. However, there are exceptions where this might be the case (such as using a swapfile) so there is a somewhat open-ended list of exceptions that might need to be handled on that approach.
It seems to me like the larger concern here is that the options field is empty and the fstab is updated prior to mount, so when the mount fails there's no rollback. We could add options to the required list, but that would be a significant change for existing use, and would result in a lot of needless data entry. It seems to me that a standard default for the Linux platform of 'defaults' would do the trick here. So I propose the following change:
Mount Type Changes
diff --git a/lib/puppet/type/mount.rb b/lib/puppet/type/mount.rb
index 8111a0d..74f2e9d 100644
--- a/lib/puppet/type/mount.rb
+++ b/lib/puppet/type/mount.rb
@@ -171,6 +171,14 @@ module Puppet
desc Mount options for the mounts, as they would
appear in the fstab.
+ defaultto do
+if Facter.value(:kernel) == 'Linux'
+ 'defaults'
+else
+ nil
+end
+ end
+
validate do |value|
raise Puppet::Error, option must not contain whitespace: #{value} if value =~ /\s/
end
With this patch in place, the error still occurs:
...
Error: /Stage[main]/Main/Mount[/mnt/loop]: Could not evaluate: Execution of '/bin/mount /mnt/loop' returned 32: mount: /root/1m is not a block device (maybe try `-o loop'?)
...
but the fstab file is correct:
...
proc /proc proc defaults 0 0
/root/1m /mnt/loop ext2 defaults 0 0
Since this only partially addresses the originally reported issue, I'd appreciate some feedback on this proposed solution.
Add Comment
