Jira (PUP-1060) enablerepo and disablerepo for yum type
Title: Message Title
Darroch Royden commented on an issue
Re: enablerepo and disablerepo for yum type
Is there an active ticket for this? It looks like the install_options directive is not being passed to the yum list command on line 96 in /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yum.rb
unless @resource.allow_virtual?
yum '-d', '0', '-e', '0', '-y', :list, wanted
end
Current a work around would be to supply the --enablerepo=repo in the install_options and then include (which will cause it to skip the above check):
allow_virtual = yes,
In the package definition.
Add Comment
Puppet / PUP-1060
enablerepo and disablerepo for yum type
it would be nice to be able to enable a disabled repo for the installation on one package. for example installing facter from EPEL. something like; {noformat} package { facter: ensure = installed, enablerepo = [ epel, epel-testing ]; } {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-438) reportdir gets permissions of root owner when running puppet apply
Title: Message Title Dave McNeill commented on an issue Re: reportdir gets permissions of root owner when running puppet apply This is a problem for me as well. In development, I use vagrant to create a puppetmaster with the vagrant 'puppet apply' provisioner. Puppet apply creates the directory $vardir/reports/$hostname owned by root. Later, when the puppet master comes up on that box, running as puppet, reports cannot be written into that directory. Jul 24 10:28:12 localhost puppet-master[4333]: Report processor failed: cannot generate tempfile `/var/lib/puppet/reports/puppet/201407241028.yaml20140724-4333-1fpvxw4-9' I tried to disable reports at the puppet apply stage using various combinations of - report=true, -report true, etc, but all such attempts error and fail. Add Comment Puppet / PUP-438 reportdir gets permissions of root owner when running puppet apply If you enable the `store` report handler, then run `puppet apply file`, then the reportdir gets created as root, meaning that subsequent puppet runs fail to write out reports. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2970) warning: Found multiple default providers
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2970
warning: Found multiple default providers
Issue Type:
Bug
Assignee:
Unassigned
Created:
24/Jul/14 4:42 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Using a noop provider to work around suitability checks for commands from yet-to-be installed packages, causes a warning about multiple providers during runs when the package is actually installed. If the package is not installed before the run, there are no warnings and the package is later installed.
pre
lib/puppet/type/nova_admin.rb Puppet::Type.newtype(:nova_admin) do @doc = Manage createion/deletion of nova admin users. ensurable newparam(:name) do desc The name of the admins. end end /pre
pre
lib/puppet/provider/nova_admin/default.pp Puppet::Type.type(:nova_admin).provide(:default) do desc This is a default provider that does nothing. This allows us to install nova-manage on the same puppet run where we want to use it. def create return false end def destroy return false end def exists? fail('This is just the default provider for nova_admin, all it does is fail') end end /pre
pre
Jira (PDB-769) Deprecate pre 9.3 PostgreSQL
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-769 Deprecate pre 9.3 PostgreSQL Issue Type: Task Assignee: Unassigned Created: 24/Jul/14 4:48 AM Fix Versions: 2.2.0 Priority: Normal Reporter: Kenneth Barber With 8.4 going end of life, there is definitely no more need to support the 8.x branch. And since we want to be on the bleeding edge when it comes to features if we can, we should deprecate anything but the current PostgreSQL. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-769) Deprecate pre 9.3 PostgreSQL
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-769 Deprecate pre 9.3 PostgreSQL Change By: Kenneth Barber Sprint: 20140730to20140813 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Daniel Henninger commented on an issue Re: modulepath not being respected in multi-path setups How interesting. This issue does not happen if you use puppet apply on a client. It only appears to occur through the master. I suspect then that it is related to PUP-731 none-the-less I am still going to try to get you a very compact here's an example of it failing in case that helps something. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Tim Hartmann commented on an issue Re: changes to ordering in custom facts breaks things Any ideas, or is this our own hacktastic ruby biting us in the bum? Add Comment Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi... 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-281) Add YAML output format to CLI
Title: Message Title Ahmet Demir created an issue Hiera / HI-281 Add YAML output format to CLI Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 24/Jul/14 6:08 AM Fix Versions: 1.4.0 Priority: Normal Reporter: Ahmet Demir Author: Ahmet Demir ahmet2mir+git...@gmail.com Github ID: ahmet2mir Pull Request 198 Discussion Pull Request 198 File Diff Just add YAML output to https://tickets.puppetlabs.com/browse/HI-129 I use hiera with other tools like Salt (custom 'backend') and yes, i can directly parse from JSON. But YAML is more elegant than JSON and I can directly use safe_load with pyyaml. Adrien Thebo told me that YAML will move away from Hiera? Why not, but what Hiera will use ? Only JSON and custom backend ?
Jira (HI-281) PR (198): Add YAML output format to CLI
Title: Message Title Ahmet Demir updated an issue Hiera / HI-281 PR (198): Add YAML output format to CLI Change By: Ahmet Demir Summary: PR(198): AddYAMLoutputformattoCLI 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups You can test if this is PUP-731 by having a scenario where your modules are simple and do not contain any custom ruby code (functions, types, facts, etc). Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2963 modulepath not being respected in multi-path setups Change By: Henrik Lindberg Assignee: AndyParker DanielHenninger 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-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Change By: Henrik Lindberg Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title Henrik Lindberg commented on an issue Re: Make it possible to namespace ruby-defined custom types This is something we are working towards. In 4.0 (and available in 3.7 --parser future) there is a new loader that loads functions using the 4x function API. (This means you can namespace functions). It is our intention to use the new loader for loading all kinds of things, and we plan to have this as an experimental feature for resource types during the 4x series with the aim of making it standard in Puppet 5.0. Add Comment Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Refreshing feature request #16401 from the old issue tracker (opened 2 years ago, listed as open), it would be great from a UX standpoint if it were possible to namespace ruby-defined custom types. From the original request: When working on a module that contains a mix of types that are defined via puppet manifests and via ruby code, it would ... 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
Jira (PUP-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title Henrik Lindberg commented on an issue Re: Make it possible to namespace ruby-defined custom types Marking this as being blocked by Biff the catalog builder, since that issue is the umbrella for the new compiler (which includes a new way/API for defining custom resource types). Add Comment Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Refreshing feature request #16401 from the old issue tracker (opened 2 years ago, listed as open), it would be great from a UX standpoint if it were possible to namespace ruby-defined custom types. From the original request: When working on a module that contains a mix of types that are defined via puppet manifests and via ruby code, it would ... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Daniel Henninger commented on an issue Re: modulepath not being respected in multi-path setups Sure enough--- testing a couple of modules that have no custom stuff in them (ie are really just manifiests and files) showed up problem what-so-ever. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this 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-398) Backslashify windows paths when appropriate
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-398 Backslashify windows paths when appropriate Change By: Rob Reynolds Component/s: Community 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-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Rob Reynolds commented on an issue Re: Puppet Windows package provider warn when source =~ /\// I'm going to close this as a duplicate of PUP-398. I've already set the link to Chris Spence's PR over on that issue. Add Comment Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Package installation/upgrade in Windows will probably fail if the source attribute path contains / Not sure of all the ins and outs here, but I think warning is sufficient - it the path ends up really not existing to msiexec etc then the resource will fail, and the warning will give a hint as to the cause. 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Daniel Henninger commented on an issue Re: modulepath not being respected in multi-path setups So get this! Your comment had me test something out. So in my above scenario, we have your environment followed by the root environment followed by global modules. root is a legit environment. It's the environment you get if you don't have a specific one set up. So taking what you said above, I found myself wondering, well, what if the root modules were not in an environment but rather a separate module directory not related to an environment. After making an adjustment, I now have: your environment : core-modules : global-modules Guess what, it works like a charm! So taking the root modules out of the scope of an actual used environment seemed to do the trick. Interesting. Bizarre. But cool. I'm not going to worry with coming up with a here's an example of it not working tarball like I was going to do unless you all feel it would really help you out at this point. It sounds like I am running into exactly what PUP-731 is and I'm sure you have enough data on that already. =) That said, I'm going to leave this to you all to close or ask me for more information. I'm hoping something in here was useful. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s...
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups Ah, yes! The problem with having things in the default configured environment is that it is always used before context switching takes place to another environment. That initial environment is used to find the applications / faces that are available. And thus naturally, anything in it will win (if it contains any custom ruby things). This is something that should be pointed out in docs. Ping Nicholas Fagerlund. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2963 modulepath not being respected in multi-path setups Change By: Henrik Lindberg Assignee: DanielHenninger NicholasFagerlund 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-2354) allow duplicate certs does not work with agent/master
Title: Message Title
Brian Warsing commented on an issue
Re: allow duplicate certs does not work with agent/master
Yes, 3.6.2 still appears affected by this bug.
Is this just a dead feature?
Add Comment
Puppet / PUP-2354
allow duplicate certs does not work with agent/master
On my master, I set: {code} [main] allow_deplicate_certs = true {code} on the master, I regenerate a private key, I get the failure: {noformat} root@cygnet-2:~# puppet agent -t --ssldir=/tmp/ info: Creating a new SSL key for cygnet-2.cygnet.lab warning: peer certificate won't be verified in this SSL session info: Caching certificate for ...
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-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio updated an issue Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Roger Ignazio Assignee: QA 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-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Kylo Ginsberg it looks like 'Failed Test' in your workflow automatically assigns to QA. I re-assigned to Joshua Partlow since he was working on this fixes for this. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. 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-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Brian Warsing created an issue Facter / FACT-630 factor 2.1.0 errors out on Mavericks Issue Type: Bug Affects Versions: 2.1.0 Assignee: Eric Sorenson Components: Community Created: 24/Jul/14 9:13 AM Environment: productname = VMware7,1 hardwareisa = i386 hardwaremodel = x86_64 kernel = Darwin kernelmajversion = 13.3 kernelrelease = 13.3.0 kernelversion = 13.3.0 macosx_buildversion = 13E28 macosx_productname = Mac OS X macosx_productversion = 10.9.4 macosx_productversion_major = 10.9 macosx_productversion_minor = 4 rubyversion = 2.0.0 Priority: Normal Reporter: Brian Warsing Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/rest.rb:48: warning: already initialized constant Facter::EC2::Metadata::DEFAULT_URI /Library/Ruby/Site/facter/ec2/rest.rb:48: warning: previous definition of
Jira (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo updated an issue Hiera / HI-281 Add YAML output format to CLI Change By: Adrien Thebo Summary: PR(198): AddYAMLoutputformattoCLI 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 (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo updated an issue Hiera / HI-281 Add YAML output format to CLI Change By: Adrien Thebo Issue Type: Task NewFeature 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 (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo commented on an issue Re: Add YAML output format to CLI Merged in bf3cf75. Add Comment Hiera / HI-281 Add YAML output format to CLI * Author: Ahmet Demir ahmet2mir+git...@gmail.com * Github ID: [ahmet2mir|https://github.com/ahmet2mir] * [Pull Request 198 Discussion|https://github.com/puppetlabs/hiera/pull/198] * [Pull Request 198 File Diff|https://github.com/puppetlabs/hiera/pull/198/files] Just add YAML output to https://tickets.puppetlabs.com/browse/HI-129 I use hiera w... 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-2971) install_options no longer honored by yum provider
Title: Message Title Andy Parker created an issue Puppet / PUP-2971 install_options no longer honored by yum provider Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 24/Jul/14 9:51 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Andy Parker According to reports in PUP-1060, the enablerepo and disablerepo options are no longer working. At least one of the reports points out that the install_options is not longer passed to the yum command. Add Comment
Jira (PUP-2971) install_options no longer honored by yum provider
Title: Message Title Andy Parker updated an issue Puppet / PUP-2971 install_options no longer honored by yum provider Change By: Andy Parker Affects Version/s: 3.6.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-2971) install_options no longer honored by yum provider
Title: Message Title
Peter Huene commented on an issue
Re: install_options no longer honored by yum provider
More specifically, it's not passed to the list command that is performed to filter to real package names (when allow_virtual is false), thus it won't be able to find packages that would otherwise be found when passing --enablerepo. If the package can be found without the install_options, the install_options are still passed to yum. This was caused by my fix to allow_virtual; I forgot to pass the options down when performing the list command.
Add Comment
Puppet / PUP-2971
install_options no longer honored by yum provider
According to reports in PUP-1060, the enablerepo and disablerepo options are no longer working. At least one of the reports points out that the {{install_options}} is not longer passed to the yum command.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-2971) install_options are not passed to yum when listing packages
Title: Message Title Peter Huene updated an issue Puppet / PUP-2971 install_options are not passed to yum when listing packages Change By: Peter Huene Summary: install_options nolongerhonoredby arenotpassedto yum provider whenlistingpackages 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-2971) install_options are not passed to yum when listing packages
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-2971
install_options are not passed to yum when listing packages
Change By:
Peter Huene
AccordingtoreportsinPUP-1060,theenablerepoanddisablerepooptionsarenolongerworking.Atleastoneofthereportspointsoutthatthe{{install_options}}isnotlongerpassedtotheyumcommand.
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-2971) install_options are not passed to yum when listing packages
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-2971
install_options are not passed to yum when listing packages
Change By:
Peter Huene
AccordingtoreportsinPUP-1060,theenablerepoanddisablerepooptionsarenolongerworking.Atleastoneofthereportspointsoutthatthe{{install_options}}isnotlongerpassedtotheyumcommand thatlistspackages . Thisresultsinpackagesnotbeingfoundinenabledrepos.
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 Kurt Wall commented on an issue Re: 3.6.1 issues warning message for deprecation Gary Steven Setting disable_warnings=deprecations in puppet.conf or using puppet apply --disable_warnings deprecations ... might help. 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... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund commented on an issue Re: modulepath not being respected in multi-path setups Hi Henrik Lindberg. I don't understand the behavior being described in this ticket. The duplicate resource declaration error above looks like it should be impossible unless something very screwy is going on. It also looks like it has nothing to do with Ruby resource type plugins, and thus doesn't seem explainable by PUP-731. I don't see anything here to document. Could you please explain? Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2963 modulepath not being respected in multi-path setups Change By: Nicholas Fagerlund Assignee: NicholasFagerlund 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-2526) puppet agent retry failed http requests
Title: Message Title Marc Seeger commented on an issue Re: puppet agent retry failed http requests Here is some copypasta from the PR: I would love to see this in as well. We run thousands of machines per puppet master and see this almost on every release. Some things that caused these failures in the past: Machines being in a different region and having a bit of a flaky connection (e.g. machines from Asia calling to a US puppet master) Security groups being rewritten in EC2 and network connections just dropping network connectivity issues in AWS Running releases on too many machines in parallel and thus putting too much load on the puppet master Some of these issues can be resolved by upsizing/load balancing the instance of the puppet master, but all of the network failures are something that a user might not be able to control and it's usually network problems so it's arbitrary requests that fail (file_metadata. file_metadatas, file_content, ...) Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova...
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2963 modulepath not being respected in multi-path setups Change By: Henrik Lindberg Assignee: HenrikLindberg NicholasFagerlund 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups The problem is that they have different versions of the same modules, these modules contain custom types. The problem is that they have a configured environment that has a modulepath that contains one version, and then a context switch is made to a particular environment. Now there is a clash, because things were already loaded. What I thought would be helpful to point out in documentation was the fact that if you do have a configured environment it will be loaded as part of an apply or master run since it is needed in the very first phase, and if it contains custom types those will win over different versions of the same types in an environment that you context switch to. Thus, make sure that the default configured environment does not contain custom things to load. You still obviously will be bitten by PUP-731) if you try to switch between environments with conflicting versions, but it is mysterious to a user that you will be bitten by it when you think you are not switching. Nicholas Fagerlund if you think this is too esoteric to mention, then simply close this ticket as a duplicate of PUP-731. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s...
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund commented on an issue Re: modulepath not being respected in multi-path setups Henrik Lindberg What do you mean by configured environment? That's a new term. Do you mean the environment in an agent's puppet.conf? Or the environment in a master's puppet.conf? Or something else? Also, could you explain how a problem with a custom resource type could cause this error? It looks like a straight-up duplicate resource declaration error to me, which shouldn't have anything to do with Ruby plugins. Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate declaration: Resources[firewall] is already declared in file /srv/puppet/root/modules/ncsufirewall/manifests/base.pp:12; cannot redeclare at /srv/puppet/chass_danieltest/modules/ncsufirewall/manifests/base.pp:12 on node MYHOSTNAME-d9048e7f-80ab-4c71-83a2-cfd85ff58f7e Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s...
Jira (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 factor 2.1.0 errors out on Mavericks Change By: Adrien Thebo Component/s: Community 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-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 factor 2.1.0 errors out on Mavericks Change By: Adrien Thebo Assignee: EricSorenson BrianWarsing 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-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo commented on an issue Re: factor 2.1.0 errors out on Mavericks How did you install Facter? Is it possible you have facter installed via the .pkg as well as a gem? Add Comment Facter / FACT-630 factor 2.1.0 errors out on Mavericks Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups Yes you are right in that PUP-731 is not to blame for for the duplicate resource, it is having a complete environment on the modulepath that makes it load things it should not. I.e. if you want to share the modules of the configured environment's (the one that puppet.conf specifies for the app you are running) they should be placed somewhere where there are nothing else besides the modules (no manifests directory) and then referenced from it, and all other sharing environments. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title
Gary Steven commented on an issue
Re: 3.6.1 issues warning message for deprecation
While that might help it introduces the larger problem of blocking ALL deprecation messages which I do not want to do. How would I be aware of future changes or problems if I turn off all deprecation messages. The real issue is agent vs apply behave differently.
in site.pp if I specify Package { allow_virtual = false }
I do not see the message anymore using 'puppet agent --test' but always see it using 'puppet apply /etc/puppet.manifests/site.pp'.
One would expect these to behave the same and return the same results which they do not today.
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...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Kylo Ginsberg commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Roger Ignazio sounds good and thanks. Our Jira workflow needs some tweaks and Kenn is on that. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund commented on an issue Re: modulepath not being respected in multi-path setups I'm sorry Henrik, I still really don't understand what's happening here. If I'm to document this, I need a clearer picture or a reproducible example that I can take apart. As far as I can tell in the example above: if the environment in the puppet master's config file is named root, then the modulepath will just have the same path in it twice, which I've tested before and haven't seen any weirdness with. From the modulepath above, it looks like there AREN'T any complete environments in the modulepath; it's all just /modules directories. Could you explain where the complete environments you're talking about enter the modulepath? Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-613) Create structured processor fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Create structured processor fact Adrien Thebo fixed up the specs on windows so the initial PR has been through CI - woot! However, since I pushed the big green merge button before I noticed Peter Huene had some additional comments, let's leave this open to resolve those additional comments. Add Comment Facter / FACT-613 Create structured processor fact Currently, there are five processor based facts: Processor, ProcessorCount, PhysicalProcessorCount, ProcessorSpeed and dynamic ProcessorX facts, which are resolved depending on operating system. These are a good candidate for merging into a single structured fact. The output for this fact could appear as follows (simulated for a system that resolves ea... 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
Jira (FACT-613) Create structured processor fact
Title: Message Title Peter Huene commented on an issue Re: Create structured processor fact I'd also like to revisit the names we're using for these new facts, such as removing redundancy in things like repeating the word processor. Add Comment Facter / FACT-613 Create structured processor fact Currently, there are five processor based facts: Processor, ProcessorCount, PhysicalProcessorCount, ProcessorSpeed and dynamic ProcessorX facts, which are resolved depending on operating system. These are a good candidate for merging into a single structured fact. The output for this fact could appear as follows (simulated for a system that resolves ea... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups I think the problem is caused by having a manifests and a site.pp in the configured environment, and then pointing to that location in a module path - but I have not tested. The evidence for that is that it worked for the user when the modules in the configured environment was moved to another place and then referenced. Basically the advice would be do not use an environment root as part of a modulepath. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails
Jira (PUP-2936) PMT appears to change metadata.json after generating checksums.json
Title: Message Title Anderson Mills commented on an issue Re: PMT appears to change metadata.json after generating checksums.json Because this follows the PE ticket PE-5074, and that is now resolved, I am resolving this ticket. Add Comment Puppet / PUP-2936 PMT appears to change metadata.json after generating checksums.json This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-770) PR (1021): Allow empty arrays and hashes in structured facts - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-770 PR (1021): Allow empty arrays and hashes in structured facts - kbarber Issue Type: Task Assignee: Unassigned Created: 24/Jul/14 3:59 PM Labels: github Priority: Normal Reporter: gepetto-bot Allow empty arrays and hashes in structured facts Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 1021 Discussion Pull Request 1021 File Diff Pull Request Description We were getting validation errors in factmap-to-paths code due to the lack of proper handling for empty hashes and arrays. This patch drops those branches quickly and now moves onto the next element. Signed-off-by: Ken Barber k...@bob.sh
Jira (PUP-2972) Implementation of +=/-= is potentially confusing
Title: Message Title Justin Holguin created an issue Puppet / PUP-2972 Implementation of +=/-= is potentially confusing Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 24/Jul/14 3:58 PM Priority: Normal Reporter: Justin Holguin It seems to me that += and -= are more confusing than useful, and I would argue that they simply shouldn't exist. Right now (with --parser future), these operators implicitly create a new variable that may shadow one from an outer scope, appending/removing the RHS to the outer scope variable if it exists. If the variable has already been defined in the current scope, the operation fails. In practice, this works like a kind of temporary mutation, or else it's just regular assignment, or else causes a failure. The alternative, using +/- with =, is more intuitive, less ambiguous, and sacrifices little if anything in terms of expressiveness. I apologize in advance if there's something major that I'm missing here, but I'd like to reopen the discussion on whether it's better to just remove these operators from the language. Add Comment
Jira (PUP-2973) Is freeze_main a dead setting?
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: Is freeze_main a dead setting?
(I just tested it — puppet apply blows up, and puppet master imposes an extra restriction on files referenced with import, which like I said above doesn't really have any use going forward.)
Add Comment
Puppet / PUP-2973
Is freeze_main a dead setting?
http://docs.puppetlabs.com/references/latest/configuration.html#freezemain Testing in puppet 3.6.2 with freeze_main = false (the default), it appears that orphaned resources — that is, resources that are: * inside some {{modules/MODULE/manifests/SOMETHING.pp}} file... * ...but OUTSIDE a class or defined type definition... —will always be i...
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-2973) Is freeze_main a dead setting?
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-2973 Is freeze_main a dead setting? Issue Type: Bug Assignee: Unassigned Created: 24/Jul/14 4:03 PM Priority: Normal Reporter: Nicholas Fagerlund http://docs.puppetlabs.com/references/latest/configuration.html#freezemain Testing in puppet 3.6.2 with freeze_main = false (the default), it appears that orphaned resources — that is, resources that are: inside some modules/MODULE/manifests/SOMETHING.pp file... ...but OUTSIDE a class or defined type definition... —will always be ignored and not added to the catalog, even if that manifest file is autoloaded and evaluated due to include MODULE::SOMETHING. (The one exception: if you use the import keyword with the full path to that manifest file. But import is going away, so we can already sort of pretend it doesn't exist.) From the description of the freeze_main setting, it sounds like this default behavior is what you'd be going for if you set freeze_main = true. Which implies to me that freeze_main is a holdover from the pre-modules era, when you'd keep class and defined type definitions in random manifest files and then use import FILE to make them available to the parser — in that world, setting freeze_main = true sounds like a reasonable precaution. But now that we're not in that world anymore and the autoloader already discards rogue resources, that sounds like dead code to me.
Jira (PUP-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title Andy Parker created an issue Puppet / PUP-2974 Cannot turn off allow_virtual warning in puppet apply Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: DSL Created: 24/Jul/14 4:05 PM Priority: Normal Reporter: Andy Parker According to comments on PUP-2650 , the suggested fix for the allow_virtual warning doesn't work when puppet apply is used. Add Comment
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund commented on an issue Re: modulepath not being respected in multi-path setups You mean his /srv/puppet/root/modules directory had a site.pp in it? I can't see anything that would indicate that, but okay. If that's what was going on, I don't believe it's worth documenting, especially since it would be impossible to do with directory envs. So I'll close this issue as wontfix. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker commented on an issue Re: 3.6.1 issues warning message for deprecation Gary Steven, I've opened PUP-2974. If you could provide a reproduction case in that ticket I'll make sure that it gets looked at. 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... 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-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title
Andy Parker commented on an issue
Re: Cannot turn off allow_virtual warning in puppet apply
I tried to reproduce this myself on Centos 6 and Puppet 3.6.2, but was not able to see the problem.
The setup is puppet 3.6.2 installed from yum.puppetlabs.net running on the system ruby. The puppetlabs-apache module is installed in the default location (/etc/puppet/modules).
allow_virtual suppressed
[root@localhost ~]# cat testing.pp
Package { allow_virtual = false }
include apache
[root@localhost ~]# puppet apply testing.pp
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.corp.puppetlabs.net in environment production in 1.80 seconds
Notice: Finished catalog run in 1.09 seconds
[root@localhost ~]#
allow_virtual not suppressed
[root@localhost ~]# cat testing.pp
#Package { allow_virtual = false }
include apache
[root@localhost ~]# puppet apply testing.pp
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.corp.puppetlabs.net in environment production in 1.85 seconds
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 `set_default')
Notice: Finished catalog run in 1.10 seconds
[root@localhost ~]#
Add Comment
Puppet / PUP-2974
Cannot turn off allow_virtual warning in puppet
Jira (PUP-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title Andy Parker assigned an issue to Gary Steven Puppet / PUP-2974 Cannot turn off allow_virtual warning in puppet apply Change By: Andy Parker Assignee: AndyParker GarySteven Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-770) PR (1021): Allow empty arrays and hashes in structured facts - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1021): Allow empty arrays and hashes in structured facts - kbarber Pull request Allow empty arrays and hashes in structured facts has been closed. Add Comment PuppetDB / PDB-770 PR (1021): Allow empty arrays and hashes in structured facts - kbarber h2. Allow empty arrays and hashes in structured facts * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1021 Discussion|https://github.com/puppetlabs/puppetdb/pull/1021] * [Pull Request 1021 File Diff|https://github.com/puppetlabs/puppetdb/pull/1021/files] h2. Pull Reques... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Daniel Henninger commented on an issue Re: modulepath not being respected in multi-path setups Sorry guys I've been busy all day – just to clarify. In the original issue posting, I had a module path of: /srv/puppet/chass_danieltest:/srv/puppet/root:/srv/puppet/global-modules /srv/puppet/chass_danieltest was laid out like (this is simplified but hey): site.pp manfests modules /srv/puppet/root was laid out the same: site.pp manifests modules /srv/puppet/global-modules was just a modules directory, nothing else. After talking with Henrik, I restructured it to be: /srv/puppet/chass_danieltest:/srv/puppet/core-modules:/srv/puppet/global-modules where core-modules was structured the same as global-modules (just a modules directory) and it contained the contents of what was /srv/puppet/root/modules. I believe what Henrik was suggesting being documented is what amounts to do not add module paths that are within another environment to your environment's modulepath as it will cause unexpected results. Something along those lines. =) Either way though, thanks for the help and I enjoyed reading the discussion back and forth between you all! =) Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s...
Jira (PDB-709) /facts-something endpoint changes for querying fact paths and values
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-709 /facts-something endpoint changes for querying fact paths and values Change By: Kenneth Barber Summary: /facts -something endpointchangesfor structuredfacts queryingfactpathsandvalues Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-770) PR (1021): Allow empty arrays and hashes in structured facts - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1021): Allow empty arrays and hashes in structured facts - kbarber pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/537/ Add Comment PuppetDB / PDB-770 PR (1021): Allow empty arrays and hashes in structured facts - kbarber h2. Allow empty arrays and hashes in structured facts * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1021 Discussion|https://github.com/puppetlabs/puppetdb/pull/1021] * [Pull Request 1021 File Diff|https://github.com/puppetlabs/puppetdb/pull/1021/files] h2. Pull Reques... 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-770) PR (1021): Allow empty arrays and hashes in structured facts - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1021): Allow empty arrays and hashes in structured facts - kbarber pljenkinsro commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/538/ Add Comment PuppetDB / PDB-770 PR (1021): Allow empty arrays and hashes in structured facts - kbarber h2. Allow empty arrays and hashes in structured facts * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1021 Discussion|https://github.com/puppetlabs/puppetdb/pull/1021] * [Pull Request 1021 File Diff|https://github.com/puppetlabs/puppetdb/pull/1021/files] h2. Pull Reques... 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-2963) modulepath not being respected in multi-path setups
Title: Message Title Nicholas Fagerlund commented on an issue Re: modulepath not being respected in multi-path setups Are you sure about that? Because the modulepath in this comment doesn't match the modulepath in your original description. This: /srv/puppet/chass_danieltest:/srv/puppet/root:/srv/puppet/global-modules That: /srv/puppet/$environment/modules:/srv/puppet/root/modules:/srv/puppet/global-modules Also, Henrik said: I think the problem is caused by having a manifests and a site.pp in the configured environment, and then pointing to that location in a module path You said: I believe what Henrik was suggesting being documented is what amounts to do not add module paths that are within another environment to your environment's modulepath as it will cause unexpected results. These are describing totally different scenarios. So, I still don't know what's going on here. Anyway, thanks for coming back! I'm going to leave the ticket closed unless I get a reproducible test case that indicates a bug or misbehavior that other people are likely to run into. Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups
Jira (PUP-2963) modulepath not being respected in multi-path setups
Title: Message Title Henrik Lindberg commented on an issue Re: modulepath not being respected in multi-path setups I suspect it is because site.pp is in the root of the environment being used as the configured environment, some of the internal environment setup used to not specify anything about manifest, and ended up globbing all .pp files from the root of the environment. (This could be observed when running some of our spec tests; they always failed if you forgot to remove any .pp files in the root). This has been fixed in 3.7, the internal bootstrapping environments no longer loads any manifests. Does the problem go away if you move site.pp under ./manifests ? (and that there are no other .pp files in the directory Add Comment Puppet / PUP-2963 modulepath not being respected in multi-path setups Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the base of our Linux installs. So for example it s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2972) Implementation of +=/-= is potentially confusing
Title: Message Title
Henrik Lindberg commented on an issue
Re: Implementation of +=/-= is potentially confusing
+= exist in the current parser as well, with the same semantics as in --parser future. There is no mutation going on, += and -= creates a new variable in the scope you are in. It does not remove anything from any other scope.
The -= was added in the future parser since it was difficult to remove something (when that something can be undef).
The original rationale for adding += was that people had trouble understanding the meaning of $a = $a + something - some read this as being some kind of recursion and they have a hard time seeing that the reference to $a on the right hand side happens before the new variable is created.
It is perfectly fine to use $a = $a + something or {{$a = $a - something }}.
There are lots of usage of += out there in puppet manifests, not sure we want to break those.
For
= you may argue that the implementation should do arithmetic minus just like
= does arithmetic {
}, but it has been argued that instead, we should remove the arithmetic {
} evaluation and always treat
= and
= as array/hash operations with the meaning please give me a copy of the outer variable (empty array if it does not exist, array-ified if it is not an array) and append or delete the given values. That would however break backwards compatibility for +=.
Looking at we have currently specified (in the Puppet Language Specification for 3.7 future/4.0), there is a discrepancy with the implementation. The spec says the outer variable must be an array or hash, but the implementation does arithmetic + (but not arithmetic -).
I think we need to revisit the decisions that were made before 3.7 is released, we can:
Make arithmetic + be a deprecation warning, or error
Add arithmetic - support
Turn the operators into give me a collection with/without and optionally make them survive if the outer variable does not exist even if strict_variables is turned on. (One of the reasons strict_variables is not on by default is because of the expectancy than reference to a non existing variable in a += is the same as a straight assignment). This is more or less what is in the spec, but it is fuzzy and leaves a question regarding strict / non existence.
Remove the -= operator (it has not been part of a regular release)
Keep, but deprecate the += operator (and remove -=)
Jira (PUP-2972) Implementation of +=/-= is potentially confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2972 Implementation of +=/-= is potentially confusing Change By: Henrik Lindberg Labels: future-parser 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-2972) Implementation of +=/-= is potentially confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2972 Implementation of +=/-= is potentially confusing 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-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title Gary Steven commented on an issue Re: Cannot turn off allow_virtual warning in puppet apply I think I found the root cause of the deprecation warning appearing in my situation. I have a Puppet module which can be found at https://github.com/stankevich/puppet-python It appears there is a custom fact to hold the version of python installed. The custom fact is determined using the snippet below. If I had to guess this is caused by Facter running prior to Puppet to collect and expose all the facts to Puppet and the Package setting I have in site.pp is not being inherited at this point. pkg = Puppet::Type.type(:package).new(:name = python) While this is not a common way to collect the information for a custom fact and I should open up the issue with the module author now, it does seem odd that this can occur and maybe is part of a larger problem. Thank you for your assistance in helping to pin point the culprit. Add Comment Puppet / PUP-2974 Cannot turn off allow_virtual warning in puppet apply According to comments on PUP-2650, the suggested fix for the allow_virtual warning doesn't work when puppet apply is used.
Jira (PUP-2897) undefined method `exist?' for Puppet::FileSystem:Module
Title: Message Title Den Mat commented on an issue Re: undefined method `exist?' for Puppet::FileSystem:Module Okay, found my problem: == puppet: Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-3.4.3-1.el6' returned 1: Error: Package: puppetdb-2.1.0-1.el6.noarch (@puppetlabs-products) == puppet:Requires: puppet = 3.5.1 == puppet:Removing: puppet-3.6.2-1.el6.noarch (@puppetlabs-products) == puppet:puppet = 3.6.2-1.el6 == puppet:Downgraded By: puppet-3.4.3-1.el6.noarch (puppetlabs-products) == puppet:puppet = 3.4.3-1.el6 Puppetdb-2.1.x version pulls in = 3.5.1 puppet package, so in the normal case I would have v3.4.3 pre-installed. It tries to 'downgrade' the installed package and fails. If I run at a pre-installed = 3.5.1 puppet the package is updated to the latest. If I'm not at latest the puppet client package (doing my apply) gets ripped out and subsequent apply steps will fail the the error: == puppet: Info: /Stage[main]/Puppetdb::Server/Service[puppetdb]: Unscheduling refresh on Service[puppetdb] == puppet: Notice: /Stage[main]/Puppetmaster::Client::Linux/Package[puppet]/ensure: ensure changed '3.4.3-1.el6' to '3.6.2-1.el6' == puppet: Error: /Stage[main]/Concat::Setup/File[/var/lib/puppet/concat/bin/concatfragments.sh]: Could not evaluate: undefined method `exist?' for Puppet::FileSystem:Module Could not retrieve file metadata for puppet:///modules/concat/concatfragments.sh: undefined method `exist?' for Puppet::FileSystem:Module That make sense? Add Comment Puppet / PUP-2897 undefined method `exist?' for Puppet::FileSystem:Module
