Jira (PUP-6386) Error: Failed to apply catalog: Validation of File[xxxxxxx] failed: You cannot specify a remote recursion without a source
Title: Message Title
Tom Parker created an issue
Puppet / PUP-6386
Error: Failed to apply catalog: Validation of File[xxx] failed: You cannot specify a remote recursion without a source
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Kylo Ginsberg
Components:
Client, Server
Created:
2016/06/03 11:32 PM
Priority:
Normal
Reporter:
Tom Parker
This file resource fails when catalog_terminus = static_compiler
file {'/etc/ppp/peers': ensure => directory, source => "puppet:///modules/ppp/peers", recurse => remote, sourceselect => all, require => Package[$packages], }
The error generated is: Error: Failed to apply catalog: Validation of File[/etc/ppp/peers] failed: You cannot specify a remote recursion without a source at /etc/puppetlabs/code/modules/ppp/manifests/init.pp:9
I am running puppetserver 2.4.0-1puppetlabs1 on Debian and puppet 4.5.0 on my client.
Jira (HI-416) User defined node scope variable not available in hierarchies
Title: Message Title Henrik Lindberg commented on HI-416 Re: User defined node scope variable not available in hierarchies This looks very much like: PUP-4789 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-416) User defined node scope variable not available in hierarchies
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-416 User defined node scope variable not available in hierarchies Change By: Henrik Lindberg Summary: User defined node scope variable didn't not available in hierarchies Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-416) User defined node scope variable didn't available in hierarchies
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-416
User defined node scope variable didn't available in hierarchies
Change By:
Henrik Lindberg
When put hieradata for nginx in file nodes/proxy0.example.net.yaml, it works, but put in proxy.yaml, it didn't work. {code} $ cat ../../hiera.yaml---:backends: - yaml - json:yaml: :datadir: '/etc/puppet/environments/%{::environment}/hieradata':hierarchy: - "nodes/%{::clientcert}" - "%{nodetype}" - "modules/%{calling_module}" - "%{::os_family}" - common$ cat manifests/site.ppnode default { hiera_include('classes')}node /^proxy(\d+)\.example\.net$/ { $nodetype = 'proxy' hiera_include('classes')}$ cat hieradata/proxy.yaml (this didn't work)---classes: - nginxnginx::nginx_upstreams: 'local-tomcat':ensure: 'present'members: - '127.0.0.1:8080'upstream_cfg_prepend: keepalive: '100'nginx::nginx_vhosts: '_default':server_name: - 'localhost'proxy: 'http://local-tomcat'format_log: 'main'vhost_cfg_prepend: send_timeout: '10s'location_cfg_append: proxy_http_version: '1.1' proxy_set_header: 'Connection ""'nginx::nginx_locations: 'static':location: '~* \.(js|css|png|jpg|jpeg|gif|ico)$'vhost: '_default'location_custom_cfg: root: '/var/lib/tomcat/webapps/' expires: '1d' {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email t
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Change By: Henrik Lindberg Affects Version/s: PUP 4.5.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Change By: Henrik Lindberg Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs While there is a workaround as noted by Dominic Cleal (use empty array instead of undef), the problem will potentially bite other modules. When googling for the error messages, the problem seems to have been observed by others, but it never got reported. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Change By: Henrik Lindberg Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6385
No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Change By:
Henrik Lindberg
Release Notes Summary:
In PUP- 6328 6028 error handling for attempts to form relationships with undef resources was improved. This in turn led to a problem with code using {{create_resources}} and the stdlib functions {{ensure_resource}}, {{ensure_resources}}, and {{ensure_packages}} as this combination could feed an undef resource reference into the catalog, and such are now always treated as an error.The problem manifests itself as the error message:{code}No title provided and "" is not a valid resource reference{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6385
No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Change By:
Henrik Lindberg
Story Points:
1
Release Notes Summary:
In PUP-6328 error handling for attempts to form relationships with undef resources was improved. This in turn led to a problem with code using {{create_resources}} and the stdlib functions {{ensure_resource}}, {{ensure_resources}}, and {{ensure_packages}} as this combination could feed an undef resource reference into the catalog, and such are now always treated as an error.The problem manifests itself as the error message:{code}No title provided and "" is not a valid resource reference{code}
Sprint:
Language 2016-06-15
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Dominic Cleal commented on PUP-6385 Re: No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Yep, it's quite easy to fix in the module by replacing undef with an empty array, so I'll do that. Thanks for triaging. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Change By: Henrik Lindberg Summary: No title provided and "" is not a valid resource reference - caused by create_resources does () not filter filtering out undef relationships which causes error undefs Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) create_resources does not filter out undef relationships which causes error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 create_resources does not filter out undef relationships which causes error Change By: Henrik Lindberg Summary: create_resources does not filter out undef no longer an accepted value for require/before resource metaparams relationships which causes error Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams Unfortunately no easy work around for this problem except modifying manifests to remove the undef if possible. Dominic Cleal What does the input look like, is it possible to fix the problem there? The real fix requires a new release of puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6385 undef no longer an accepted value for require/before resource metaparams Change By: Henrik Lindberg Fix Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams Well, ensure_packages does almost nothing, it delegates to ensure_resource or ensure_resources and both of those delegate to create_resources. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams The create_resources function has no protection against undef/nil parameters. It could just filter them out. I have a patch that makes that work. However, the ensure_packages should not ask for an undef require - will look at that as well. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2764) Rust CLI should accept a string in server_urls configuration
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2764 Rust CLI should accept a string in server_urls configuration Issue Type: Bug Assignee: Unassigned Created: 2016/06/03 2:52 PM Fix Versions: PDB CLI 1.1.0 Priority: Normal Reporter: Andrew Roetker Currently we only accept vectors in the Rust CLI implementation. We should also accept and parse strings like we do for the C++ code/from the command line flag. Add Comment
Jira (PDB-2763) Build man pages for Rust CLI
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2763 Build man pages for Rust CLI Issue Type: Improvement Assignee: Unassigned Created: 2016/06/03 2:48 PM Fix Versions: PDB CLI 1.1.0 Priority: Normal Reporter: Andrew Roetker We need to port the CMAKE code in leatherman for pod2man to a rust build script. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title
Dominic Cleal commented on PUP-6385
Re: undef no longer an accepted value for require/before resource metaparams
The issue in the module is still present on 4.5.1 when instantiating the resource through stdlib's ensure_packages (a create_resources wrapper), as it's not declared directly in the manifest.
I think it's doing the equivalent of this:
$ bin/puppet apply -v --noop -e '$r = undef; create_resources("Package", {"a" => {"require" => $r}})' --trace
Error: No title provided and "undef" is not a valid resource reference on node cobalt
/home/dcleal/code/puppet/puppet/lib/puppet/resource.rb:544:in `extract_type_and_title'
/home/dcleal/code/puppet/puppet/lib/puppet/resource.rb:529:in `type_and_title'
/home/dcleal/code/puppet/puppet/lib/puppet/resource/catalog.rb:353:in `resource'
/home/dcleal/code/puppet/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:34:in `block in validate_relationship'
/home/dcleal/code/puppet/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:32:in `each'
/home/dcleal/code/puppet/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:32:in `validate_relationship'
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams Do check that 4.5.1 is on the agent, IIRC the error comes from applying the catalog, not the compiler / master. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg assigned an issue to Dominic Cleal Puppet / PUP-6385 undef no longer an accepted value for require/before resource metaparams Change By: Henrik Lindberg Assignee: Dominic Cleal Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Dominic Cleal commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams You're quite right, I think the reproducer I supplied must be incorrect for the issue seen in pl-postgresql, I'll try and get a correct one. I'm testing on both 4.5.1 and master and the test failure still seems to be present. (Travis CI shows it's failing on 4.5.1 still: https://travis-ci.org/puppetlabs/puppetlabs-postgresql/jobs/134796036) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: undef no longer an accepted value for require/before resource metaparams I suspect this is a duplicate of PUP-6336 as the sample works on stable as well. Please update to Puppet 4.5.1. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6234) Puppet does not accept UTF8 on the command line
Title: Message Title Ethan Brown commented on PUP-6234 Re: Puppet does not accept UTF8 on the command line A couple of options that we have to address this: Alter the way that the Start Command Prompt with Puppet operates - we could do things like: set the font to Lucia Console chcp 65001 to establish Unicode This is something that we'd want to document in our user guide so that no one is caught off guard. In the batch files that we launch ruby based tools with (i.e. puppet.bat), we can use set RUBYOPT=-EUTF8 to establish the default external encoding. This has pretty broad consequences, so we might want to think hard about doing that. Just modifying the special Puppet command prompt may be a good stopgap solution until we can evaluate the impact of using RUBYOPT. See also PE-13721 / https://github.com/puppetlabs/puppetlabs-puppet_enterprise/pull/703/files Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this gr
Jira (PUP-6234) Puppet does not accept UTF8 on the command line
Title: Message Title Michael Smith commented on PUP-6234 Re: Puppet does not accept UTF8 on the command line Indeed. This is something we had to handle with all our C++ applications, that led to the recommendations at https://github.com/puppetlabs/cppbestpractices/blob/master/01-Getting-Started.md#handling-inputoutput. Since Ruby is C, it probably needs a patch to call Windows' CommandLineToArgvW and GetCommandLineW, or use a wmain function. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title
Henrik Lindberg commented on PUP-6385
Re: undef no longer an accepted value for require/before resource metaparams
On master:
bundle exec puppet apply -e 'notify { "a": require => undef }' --trace
Notice: Compiled catalog for henrik2 in environment production in 0.05 seconds
Notice: a
Notice: /Stage[main]/Main/Notify[a]/message: defined 'message' as 'a'
Notice: Applied catalog in 0.01 seconds
I think this is fixed in Puppet 4.5.1
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title Daniel Lu updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: Daniel Lu Sprint: Windows 2016-06- 29 15 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title Daniel Lu updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: Daniel Lu Scope Change Category: Adopted Scope Change Reason: Have bandwidth to do the work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Martin Jackson commented on FACT-1244 Re: xenu vs. xen0 difference not recognized by Puppet We also noticed this. We're using a variation of Sylvain's custom fact as a workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2762) Create docs for token access via curl
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2762 Create docs for token access via curl Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6385) undef no longer an accepted value for require/before resource metaparams
Title: Message Title Dominic Cleal created an issue Puppet / PUP-6385 undef no longer an accepted value for require/before resource metaparams Issue Type: Bug Affects Versions: PUP 4.5.0 Assignee: Unassigned Created: 2016/06/03 11:17 AM Environment: Puppet 4.5.0 Priority: Normal Reporter: Dominic Cleal Since PUP-6028 , catalog compilation now fails when a resource has the require or before metaparameters set to undef. This behaviour was relied upon in the puppetlabs-postgresql module at https://github.com/puppetlabs/puppetlabs-postgresql/blob/4.7.1/manifests/server/extension.pp#L57-L58 where the value of the metaparams is worked out in the manifest and can be undef. A simple reproducer, at commit eff7ac6 or master: $ bin/puppet apply -e 'noti
Jira (PUP-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet with agent failover logic
Change By:
William Hopper
There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? By command line? A mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for {{pluginsync}}, report submission, etc.Also, from Kylo: One thing to be careful about with this is making sure it works with and without {{use_cached_catalog}}. I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need file content? And are we restricted to that master for report submission? Edit: the answer is no, we are not restricted in this way! Also, if you're running with cached catalogs, do we fail if we can't reach the master we got that catalog from originally? Or do we failover to a different master? - Edit: once again, not restricted!
Add Comment
Jira (PUP-6378) Add failover information to the report
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6378
Add failover information to the report
Change By:
William Hopper
The report should specify both whether agent-side failover occurred and if it did, which master was successfully used. The information that needs to be conveyed:* Did failover occur?* If so, which master was successfully used?* Which masters were provided to use? (the {{server_urls}} list) From Russ:We're adding a 'producer' key to the report, to be synthesized in the puppetdb terminus, so we can tell if failover happened in a Simple HA setup. But the agent has a much better, more consistent perspective on this; something like 'failover' or 'the master I actually used' or similar could be useful.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1435) functions redeclared without dllimport attribute
Title: Message Title Michael Smith commented on FACT-1435 Re: functions redeclared without dllimport attribute Should be fixed by https://github.com/puppetlabs/facter/commit/188850aea75cb21e883158d0a8e63d32c699cff0. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1435) functions redeclared without dllimport attribute
Title: Message Title Michael Smith commented on FACT-1435 Re: functions redeclared without dllimport attribute This only happens on facter#master, with Leatherman 0.7+. We haven't merged facter#stable to master in awhile, so a fix for this wasn't merged down. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1435) functions redeclared without dllimport attribute
Title: Message Title Michal Ruzicka created an issue Facter / FACT-1435 functions redeclared without dllimport attribute Issue Type: CI Blocker Assignee: Unassigned Created: 2016/06/03 9:08 AM Priority: Normal Reporter: Michal Ruzicka Facter build fails with a number of errors like this: 06:59:53 C:\cygwin64\home\Administrator\facter\lib\src\facts\array_value.cc:13:5: error: 'facter::facts::array_value::array_value(facter::facts::array_value&&)' redeclared without dllimport attribute: previous dllimport ignored [-Werror=attributes] 06:59:53 array_value::array_value(array_value&& other) 06:59:53 ^ see https://jenkins.puppetlabs.com/job/platform_pxp-agent_
Jira (FACT-1427) identity.privileged fact is not set on zlinux based sles11
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1427 identity.privileged fact is not set on zlinux based sles11 Change By: Kenn Hussey Fix Version/s: FACT 3.1.9 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6375) Triage acceptance failures on zlinux (s390x) sles-11 and sles-12
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6375 Triage acceptance failures on zlinux (s390x) sles-11 and sles-12 Change By: Kenn Hussey Fix Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6288) Cannot upgrade package from standard to backports version
Title: Message Title
Robert Scheer updated an issue
Puppet / PUP-6288
Cannot upgrade package from standard to backports version
Change By:
Robert Scheer
There is a bug in the apt-provider that will not let you upgrade a package from the standard repo to the version from the backports repo although install_options => [ '-t', "$\{lsbdistcodename\}-backports" ] was given.As described on [http://backports.debian.org/Instructions/] all backports are disabled by default. That is: the packages are pinned to 100 (or anything between 100 and 500) which means that you have to explicitly install a backport package (apt-get install -t jessie-backports somepackage) but from then on it will be upgraded automaticallly.Please consider the following code:package {'foobar': ensure => latest, install_options => [ '-t', 'jessie-backports' ],}And consider the following situations:1. package foobar is not installed2. package foobar from the standard repo is installed but there is a newer version in backports3. package foobar from the backports repo is installed but there is a newer version in backportsPuppet will execute "apt-cache policy foobar" and parse the output to determine if the package needs updating, and "apt-get install foobar -t jessie-backports" if it thinks it does.In situation 1 apt-cache outputs: Installed: (none) Candidate: the version from the standard repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the version from backports, although Puppet expected the standard version to be installed.This case turns out correctly by accident.In situation 2 apt-cache outputs: Installed: the version from the standard repo Candidate: that same versionPuppet assumes wrongly there is no action needed because the installed version and candidate version are the same.In situation 3 apt-cache outputs: Installed: the version from the backports repo Candidate: a newer version from the backports repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the newer version from backports. This case turns out correctly more or less by accident because the installed version already was from the backports repo.Solution for all situations:What Puppet should do is recognize that -t (or --target-release or --default-release) is present in install_option and use that in the apt-cache command as well. Those options (aliases of each other) _"control the default input to the policy engine"_ according to the man-page of apt-get. They are not mentioned in the manual of apt-cache, but apt-cache handles them correctly: in situation 2 "apt-cache policy foobar -t jessie-backports" would output: Installed: the version from the standard repo Candidate: the version from the backports repoand Puppet would install the newer version from backports.
Jira (PUP-6288) Cannot upgrade package from standard to backports version
Title: Message Title
Robert Scheer updated an issue
Puppet / PUP-6288
Cannot upgrade package from standard to backports version
Change By:
Robert Scheer
There is a bug in the apt-provider that will not let you upgrade a package from the standard repo to the version from the backports repo although install_options => [ '-t', "$ \ {lsbdistcodename \ }-backports" ] was given.As described on [http://backports.debian.org/Instructions/] all backports are disabled by default. That is: the packages are pinned to 100 which means that you have to explicitly install a backport package (apt-get install -t jessie-backports somepackage) but from then on it will be upgraded automaticallly.Please consider the following code:package {'foobar': ensure => latest, install_options => [ '-t', 'jessie-backports' ],}And consider the following situations:1. package foobar is not installed2. package foobar from the standard repo is installed but there is a newer version in backports3. package foobar from the backports repo is installed but there is a newer version in backportsPuppet will execute "apt-cache policy foobar" and parse the output to determine if the package needs updating, and "apt-get install foobar -t jessie-backports" if it thinks it does.In situation 1 apt-cache outputs: Installed: (none) Candidate: the version from the standard repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the version from backports, although Puppet expected the standard version to be installed.This case turns out correctly by accident.In situation 2 apt-cache outputs: Installed: the version from the standard repo Candidate: that same versionPuppet assumes wrongly there is no action needed because the installed version and candidate version are the same.In situation 3 apt-cache outputs: Installed: the version from the backports repo Candidate: a newer version from the backports repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the newer version from backports. This case turns out correctly more or less by accident because the installed version already was from the backports repo.Solution for all situations:What Puppet should do is recognize that -t (or --target-release or --default-release) is present in install_option and use that in the apt-cache command as well. Those options (aliases of each other) _"control the default input to the policy engine"_ according to the man-page of apt-get. They are not mentioned in the manual of apt-cache, but apt-cache handles them correctly: in situation 2 "apt-cache policy foobar -t jessie-backports" would output: Installed: the version from the standard repo Candidate: the version from the backports repoand Puppet would install the newer version from backports.
Jira (PUP-6288) Cannot upgrade package from standard to backports version
Title: Message Title
Robert Scheer updated an issue
Puppet / PUP-6288
Cannot upgrade package from standard to backports version
Change By:
Robert Scheer
There is a bug in the apt-provider that will not let you upgrade a package from the standard repo to the version from the backports repo although _install_options install_options => [ '-t', "${lsbdistcodename}-backports" ] _ was given.As described on [http://backports.debian.org/Instructions/] all backports are disabled by default. That is: the packages are pinned to 100 which means that you have to explicitly install a backport package (apt-get install -t jessie-backports somepackage) but from then on it will be upgraded automaticallly.Please consider the following code:package {'foobar': ensure => latest, install_options => [ '-t', 'jessie-backports' ],}And consider the following situations:1. package foobar is not installed2. package foobar from the standard repo is installed but there is a newer version in backports3. package foobar from the backports repo is installed but there is a newer version in backportsPuppet will execute "apt-cache policy foobar" and parse the output to determine if the package needs updating, and "apt-get install foobar -t jessie-backports" if it thinks it does.In situation 1 apt-cache outputs: Installed: (none) Candidate: the version from the standard repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the version from backports, although Puppet expected the standard version to be installed.This case turns out correctly by accident.In situation 2 apt-cache outputs: Installed: the version from the standard repo Candidate: that same versionPuppet assumes wrongly there is no action needed because the installed version and candidate version are the same.In situation 3 apt-cache outputs: Installed: the version from the backports repo Candidate: a newer version from the backports repoPuppet will execute "apt-get install foobar -t jessie-backports" and the system gets the newer version from backports. This case turns out correctly more or less by accident because the installed version already was from the backports repo.Solution for all situations:What Puppet should do is recognize that -t (or --target-release or --default-release) is present in install_option and use that in the apt-cache command as well. Those options (aliases of each other) _"control the default input to the policy engine"_ according to the man-page of apt-get. They are not mentioned in the manual of apt-cache, but apt-cache handles them correctly: in situation 2 "apt-cache policy foobar -t jessie-backports" would output: Installed: the version from the standard repo Candidate: the version from the backports repoand Puppet would install the newer version from backports.
Jira (PUP-6037) File Permissions are set wrong in puppet
Title: Message Title Patrick Thyen commented on PUP-6037 Re: File Permissions are set wrong in puppet In my Case I set the permissions to 0744. So only the owner can do anything, but everyone else can only read this directory. There is no write permission bit set. In addition: When i set the mode to: mode => 'u=rwx,go=r' everything works just fine Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
