Jira (FACT-804) cfpropertylist is a missing dependency
Title: Message Title Geoff Williams commented on FACT-804 Re: cfpropertylist is a missing dependency I ran into this today while trying to test a module with Puppet-Rspec. I ended up with the Following Gemfile to workaround the problem: source ENV['GEM_SOURCE'] || 'https://rubygems.org' case RUBY_PLATFORM when /darwin/ gem 'CFPropertyList' end gem 'puppet', '4.9.0' gem 'facter', '2.4.6' gem 'rubocop', '0.47.1' Perhaps this will be useful to someone else...
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. same issue: Debug: importing '/etc/puppetlabs/code/environments/hiera3_custom_backend_tq3nh067/modules/some_mod/manifests/init.pp' in environment hiera3_custom_backend_tq3nh067 Debug: Automatically imported some_mod from some_mod into hiera3_custom_backend_tq3nh067 Debug: ModuleLoader: module 'some_mod' has unknown dependencies - it will have all other modules visible Debug: Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Test" Unable to load backend 'custom': cannot load such file -- hiera/backend/custom_backend
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. I assume that you're using a puppetserver? If so, is there any difference if you just run a plain puppet master instead (that's what I did)? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. supposedly loaded, but: 2017-01-31 17:42:11,435 DEBUG [qtp666317422-24] [puppetserver] Puppet importing '/etc/puppetlabs/code/environments/hiera3_custom_backend_tq3nh067/modules/some_mod/manifests/init.pp' in environment hiera3_custom_backend_tq3nh067 2017-01-31 17:42:11,444 DEBUG [qtp666317422-24] [puppetserver] Puppet Automatically imported some_mod from some_mod into hiera3_custom_backend_tq3nh067 2017-01-31 17:42:11,447 DEBUG [qtp666317422-24] [puppetserver] Puppet ModuleLoader: module 'some_mod' has unknown dependencies - it will have all other modules visible 2017-01-31 17:42:11,544 DEBUG [qtp666317422-24] [puppetserver] Puppet Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Test" Unable to load backend 'custom': no such file to load --
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Rob Reynolds Labels: gem package provider windows Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Eric Thompson, never mind. I misread that quote. Puppet really do load things beneath lib. I tried your example. It works OK for me, both using the command line and with puppet agent -t. Can you run the master with --debug enabled? It would be helpful because it will output a full lookup explanation in the master log. When I do that, I get this output: Debug: Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/home/thhal/puppet_fixture/etc/puppet/hiera.yaml" Hierarchy entry "Custom" Found key: "lookup_options" value: nil Searching for "anykey" Global Data Provider (hiera configuration version 5) Using configuration "/home/thhal/puppet_fixture/etc/puppet/hiera.yaml"
Jira (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Henrik Lindberg commented on PUP-7102 Re: Insufficient logging when encountering 'permission denied' on environmentpath Thomas Hallgren Acceptance criteria updated. The rationale is that the big problem here is errors (other than "not found") are swallowed. It should simply stop and report that. Warnings etc. still lead to bad behavior, and you would need to know that you must look in the logs. Warnings are not propagated to the user in most scenarios (they are in the apply case since you are seeing the log output, but not in an agent -t run against the master). It is especially troublesome if there is a "production" env with permission error as the system now takes that as "not found" and it goes of to create the default production environment. That in turn can lead to horrible effects with nodes getting empty catalogs, or strange catalogs. Hence - it should simply error out. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Henrik Lindberg Acceptance Criteria: When multiple paths are specified for resolution of an environment name to path takes place and the effective user does not have access to a configuration option like ' path included in the environmentpath ', puppet should raise an error when the access is denied because of permissions. The rationale for this is that it is impossible to tell if the environment is missing or not in the expected location. Therefore a decision that a) it did not exist, or b) a directory found later in the environmentpath should be easy used are wrong because it is inconclusive.Therefore:If puppet can sudo to determine which path was picked during check the actual existence without an agent run auth error it should do so to allow the search to continue past a bona fide "not found" , and why. Specifically, in this case, that with lowered access rights would look like a permission denied message should error. (i.e. make it into an inconclusive error conclusive if possible).Only a bona fide "file not found" should mean that the puppetserver logs search continues . Only if the search ends error free and with "production" not found should an attempt be made to create that environment. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it,
Jira (FACT-1544) Facter leaves behind cached facts if you enable fact TTLs in facter.conf and then remove those TTLs
Title: Message Title Martin Jackson commented on FACT-1544 Re: Facter leaves behind cached facts if you enable fact TTLs in facter.conf and then remove those TTLs That's completely fair. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7114) Re-vendor semantic_puppet gem
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-7114 Re-vendor semantic_puppet gem Change By: Joshua Partlow Summary: Re-vendor semantic_pupppet semantic_puppet gem Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. To answer my own question. I found this in the docs (last link in Eric's comment above): When using Hiera with Puppet, you can load backends from the lib directory of a Puppet module; however, these backends won’t be loaded when you run Hiera from the command line unless you specify that directory in your RUBYLIB environment variable. @erict, is the RUBYLIB environment variable set on the master when you execute the agent run? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. @erict, any Hiera backend can provide lookup_options. It gives the user the ability to declare lookup_options close to data and works with Puppet lookup using a classic Hiera 3 too. Regarding the failure, is everything present under modules/some_mod/lib added to the Ruby load path? I wouldn't expect that to happen. Do we have some example of a backend for classic Hiera that is made accessible this way? My expectation would be that such backends must to be installed as gems to be available to Hiera but I might be wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7152) AIX user provider should specify passwd file encoding explicitly
Title: Message Title Ethan Brown created an issue Puppet / PUP-7152 AIX user provider should specify passwd file encoding explicitly Issue Type: Improvement Affects Versions: PUP 4.9.0 Assignee: Unassigned Created: 2017/01/31 3:16 PM Priority: Normal Reporter: Ethan Brown The call to read /etc/security/passwd on AIX does not specify an encoding, meaning that it defaults to Encoding.default_external. This may be accurate, but it might be better to read the raw bytes as BINARY for the sake of its usage. Will need to investigate encodings more on AIX to understand. Add Comment
Jira (PUP-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Ethan Brown created an issue Puppet / PUP-7151 selmodule type should explicitly specify encoding when reading selmodversion_file Issue Type: Improvement Assignee: Unassigned Created: 2017/01/31 3:04 PM Priority: Normal Reporter: Ethan Brown This is just a minor improvement to be more explicit when reading the selmodversion_file at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/selmodule/semodule.rb#L86 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7150) on cisco_ios_xr-6-x86_64: File resource drift correction fails on file named with utf-8 characters
Title: Message Title Sean Griffin updated an issue Puppet / PUP-7150 on cisco_ios_xr-6-x86_64: File resource drift correction fails on file named with utf-8 characters Change By: Sean Griffin Summary: os on cisco_ios_xr-6-x86_64: File resource drift correction fails on file named with utf-8 characters Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7150) os cisco_ios_xr-6-x86_64: File resource drift correction fails on file named with utf-8 characters
Title: Message Title Sean Griffin moved an issue Puppet / PUP-7150 os cisco_ios_xr-6-x86_64: File resource drift correction fails on file named with utf-8 characters Change By: Sean Griffin Key: MODULES PUP - 4366 7150 Project: Forge Modules Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3286) Add job_uuid to reports and catalogs
Title: Message Title Alex Dreyer updated an issue PuppetDB / PDB-3286 Add job_uuid to reports and catalogs Change By: Alex Dreyer Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file
Title: Message Title Nolan Gibb commented on PUP-6697 Re: Allow full downloaded CA bundle to be stored to agent's localcacert file Having this fixed would solve a big headache. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3286) Add job_uuid to reports and catalogs
Title: Message Title Alex Dreyer created an issue PuppetDB / PDB-3286 Add job_uuid to reports and catalogs Issue Type: New Feature Assignee: Unassigned Created: 2017/01/31 2:38 PM Priority: Normal Reporter: Alex Dreyer Reports and catalogs submitted with PUP-7149 will include a job_id. This should be stored in a nullable column of the database and queryable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7149) Puppet should include job_uuid in reports and catalogs
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-7149 Puppet should include job_uuid in reports and catalogs Change By: Alex Dreyer Puppet should add a job_uuid to reports and catalogs similiar to transaction_uuid. This should be nil unless it set intentionally in a similiar similar fashion to how PUP-6642 allows transaction_uuid to be set . The job_uuid should be included when reports and catalogs are sent to puppetdb Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7149) Puppet should include job_uuid in reports and catalogs
Title: Message Title Alex Dreyer created an issue Puppet / PUP-7149 Puppet should include job_uuid in reports and catalogs Issue Type: New Feature Assignee: Unassigned Created: 2017/01/31 2:35 PM Priority: Normal Reporter: Alex Dreyer Puppet should add a job_uuid to reports and catalogs similiar to transaction_uuid. This should be nil unless it set intentionally in a similiar fashion to how PUP-6642 allows transaction_uuid to be set Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. also, it was a bit surprising to me, as the user that i had to screen on lookup_options in my custom_backend. this makes perfect sense based on my own knowledge of data in modules and hiera5. my custom_backend is exceedingly dumb as well, compared to one that would be used in production, checking for actual keys and returning nil for non-existent keys. Lindsey Smith, others: thoughts? documentation additions? existing docs: https://docs.puppet.com/puppet/latest/lookup_quick.html#setting-lookupoptions-in-data https://docs.puppet.com/hiera/3.2/custom_backends.html Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. now i can get this to work with puppet lookup but not in an agent run: [root@uqxwu2rlejmodoo hiera3_custom_backend_7pe0glhq]# find . . ./manifests ./manifests/site.pp ./modules ./modules/some_mod ./modules/some_mod/lib ./modules/some_mod/lib/hiera ./modules/some_mod/lib/hiera/backend ./modules/some_mod/lib/hiera/backend/custom_backend.rb
Jira (PUP-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Stan Duffy assigned an issue to Stan Duffy Puppet / PUP-7143 CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR Change By: Stan Duffy Assignee: Eric Delaney Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Stan Duffy commented on PUP-7143 Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR Question sent to Mike at Cisco. awaiting response. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Kurt Wall
QA Risk Assessment Reason:
Low risk of downtime, data loss
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Kurt Wall
QA Risk Assessment:
Needs Assessment
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Kurt Wall
QA Risk Assessment:
Needs Assessment No Action
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-5475) Windows Service provider should use something better than net.exe - perhaps direct FFI access
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-5475 Windows Service provider should use something better than net.exe - perhaps direct FFI access Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Stan Duffy commented on PUP-7143 Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR Moses Mendoza No idea. But we can ask our friends at Cisco. I have a Sync up with them shortly. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Nick Walker commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Yes, one possible way to achieve this would be to allow agents access to update their own facts and only their own facts directly via the puppetdb API. However, I'm not sure that's desirable in more locked down architectures and it may still make sense to have an API on the master that forwards the facts to PuppetDB. In addition to submitting facts after a puppet run, you should be able to submit facts on whatever interval you prefer. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3273) Timeout during pull-changes sync test
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3273 Timeout during pull-changes sync test Change By: Rob Browning Fix Version/s: PDB 4.2.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3282) threadpool-test/exec-from-channel-test failed in CI
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3282 threadpool-test/exec-from-channel-test failed in CI Change By: Rob Browning Fix Version/s: PDB 4.2.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3217) (maint) Update beaker to ~3.4, unpin from 2.43.0
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3217 (maint) Update beaker to ~3.4, unpin from 2.43.0 Change By: Rob Browning Fix Version/s: PDB 4.2.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3274) (maint) Backport default-timeout-ms (for tests) from stable
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3274 (maint) Backport default-timeout-ms (for tests) from stable Change By: Rob Browning Fix Version/s: PDB 4.2.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3207) Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3207 Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release Change By: Rob Browning Fix Version/s: PDB 4.2.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-4692) Puppet has no designated default user or group providers for Linux
Title: Message Title Eric Sorenson commented on PUP-4692 Re: Puppet has no designated default user or group providers for Linux Charlie Sharpsteen sure, but how is it that this hasn't hit nearly anyone in years and years...? I'd probably take a patch that changed it but I don't think I'd prioritize in the backlog. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Sam Woods commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Patrick Carlisle Are you able to answer Eric Thompson's question? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7148) acceptance: logging 'permission denied' on environmentpath; others
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7148 acceptance: logging 'permission denied' on environmentpath; others Change By: Eric Thompson Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7148) acceptance: logging 'permission denied' on environmentpath; others
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7148 acceptance: logging 'permission denied' on environmentpath; others Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7132) acceptance: lookup subcommand can take multiple arguments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7132 acceptance: lookup subcommand can take multiple arguments Change By: Eric Thompson QA Risk Assessment: No Action Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7132) acceptance: lookup subcommand can take multiple arguments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7132 acceptance: lookup subcommand can take multiple arguments Change By: Eric Thompson Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7132) acceptance: lookup subcommand can take multiple arguments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7132 acceptance: lookup subcommand can take multiple arguments Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Moses Mendoza commented on PUP-7143 Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR ping Stan Duffy - do you have any idea why we might see a "flaky" segfault on cisco? It seems that about 50% of the time this test fails on cisco: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/utf8_user_comments.rb#L74-L84 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title
Eric Delaney commented on PUP-7143
Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
So I set up the tests from the latest puppet source and started a loop of tests. It failed on the first 2 tests runs
SHA=a4c3c47838c0dd14c7f491403e81063fc8f9e6d2 SUITE_VERION=1.8.3.496.ga4c3c47 TEST_TARGET=ciscoxr-64a bundle exec rake ci:test:aio
local_options.rb:
{:tests=>
["tests/resource/user/utf8_user_comments.rb"],
:log_level=>"debug",
:color=>true}
output.1.log:
^[[00;00m^[[00;34mlocalhost $ scp /tmp/beaker20170131-9972-51hin4 ciscoxr-64-1:/tmp/apply_manifest.pp.cupTKi {:ignore => }
^[[00;00m^[[00;37m
c67lu28zyl6vphp.delivery.puppetlabs.net (ciscoxr-64-1) 18:44:57$ source /etc/profile; env LANG="en_US.ISO8859-1" puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest.pp.cupTKi
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Eric Thompson commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Sam Woods do you know, or know who would know, what puppet api code NC is using to assign/check environments? i could try to reproduce that way so we could have a test, if required in puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7130) Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7130 Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler. Change By: Eric Thompson Acceptance Criteria: * existing tests pass Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7130) Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7130 Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler. Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7130) Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7130 Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler. Change By: Eric Thompson QA Risk Assessment Reason: covered by existing tests Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted:https://github.com/puppetlabs/puppet/pull/5559 (merge this first)https://github.com/puppetlabs/puppet/pull/5561https://github.com/puppetlabs/puppet/pull/5562https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567https://github.com/puppetlabs/puppet/pull/5568https://github.com/puppetlabs/puppet/pull/5569https://github.com/puppetlabs/puppet/pull/5570https://github.com/puppetlabs/puppet/pull/5571https://github.com/puppetlabs/puppet/pull/5572https://github.com/puppetlabs/puppet/pull/5573https://github.com/puppetlabs/puppet/pull/5574https://github.com/puppetlabs/puppet/pull/5575https://github.com/puppetlabs/puppet/pull/5576https://github.com/puppetlabs/puppet/pull/5577https://github.com/puppetlabs/puppet/pull/5579https://github.com/puppetlabs/puppet/pull/5580https://github.com/puppetlabs/puppet/pull/5581https://github.com/puppetlabs/puppet/pull/5582https://github.com/puppetlabs/puppet/pull/5583https://github.com/puppetlabs/puppet/pull/5584https://github.com/puppetlabs/puppet/pull/5585https://github.com/puppetlabs/puppet/pull/5586https://github.com/puppetlabs/puppet/pull/5587 https://github.com/puppetlabs/puppet/pull/5588https://github.com/puppetlabs/puppet/pull/5589https://github.com/puppetlabs/puppet/pull/5590https://github.com/puppetlabs/puppet/pull/5591https://github.com/puppetlabs/puppet/pull/5592 Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Ben Ford commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Eric Thompson Sure. Delete an existing environment but don't edit classification in the Console. (the console won't allow you to assign to a nonexistent env). Restart the master or clear its cache. Run the agent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7148) acceptance: logging 'permission denied' on environmentpath; others
Title: Message Title Eric Thompson created an issue Puppet / PUP-7148 acceptance: logging 'permission denied' on environmentpath; others Issue Type: Sub-task Assignee: Unassigned Created: 2017/01/31 10:58 AM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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
Jira (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Eric Thompson QA Risk Assessment Reason: not covered by unit tests; automate, medium priority Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3170) Cap integer and float sizes
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3170 Cap integer and float sizes Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; error message Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3170) Cap integer and float sizes
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3170 Cap integer and float sizes Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6373 SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6367) Semantic::VersionRange creates incorrect range for exact version
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6367 Semantic::VersionRange creates incorrect range for exact version Change By: Eric Thompson QA Risk Assessment Reason: closed: duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6367) Semantic::VersionRange creates incorrect range for exact version
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6367 Semantic::VersionRange creates incorrect range for exact version Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6373 SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7100) Add a Hiera 5 eyaml lookup_key function
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-7100 Add a Hiera 5 eyaml lookup_key function Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Reid Vandewiele commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Eric Sorenson my understanding is there is no longer an API endpoint on puppetserver to accept facts independent of a catalog request, even if you were inclined to modify the face or agent code to send them. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3255) Update to i18n 0.5.1 and add i18n-clj job to CI pipeline
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-3255 Update to i18n 0.5.1 and add i18n-clj job to CI pipeline Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted:https://github.com/puppetlabs/puppet/pull/5559 (merge this first)https://github.com/puppetlabs/puppet/pull/5561https://github.com/puppetlabs/puppet/pull/5562https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567https://github.com/puppetlabs/puppet/pull/5568https://github.com/puppetlabs/puppet/pull/5569https://github.com/puppetlabs/puppet/pull/5570https://github.com/puppetlabs/puppet/pull/5571https://github.com/puppetlabs/puppet/pull/5572https://github.com/puppetlabs/puppet/pull/5573https://github.com/puppetlabs/puppet/pull/5574https://github.com/puppetlabs/puppet/pull/5575https://github.com/puppetlabs/puppet/pull/5576https://github.com/puppetlabs/puppet/pull/5577 https://github.com/puppetlabs/puppet/pull/5579https://github.com/puppetlabs/puppet/pull/5580https://github.com/puppetlabs/puppet/pull/5581https://github.com/puppetlabs/puppet/pull/5582https://github.com/puppetlabs/puppet/pull/5583https://github.com/puppetlabs/puppet/pull/5584https://github.com/puppetlabs/puppet/pull/5585https://github.com/puppetlabs/puppet/pull/5586https://github.com/puppetlabs/puppet/pull/5587 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-4933) Remove cfacter setting
Title: Message Title William Hopper updated an issue Puppet / PUP-4933 Remove cfacter setting Change By: William Hopper Release Notes Summary: This change removes the old cfacter feature, which has been obsolete since the Puppet 4.x series. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3670) Remove Facts#strip_internal method
Title: Message Title William Hopper updated an issue Puppet / PUP-3670 Remove Facts#strip_internal method Change By: William Hopper Release Notes Summary: This change removes the strip_internal method from the Puppet::Node::Facts class. This method has been deprecated since Puppet 4.0.0. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6219) Remove req_bits setting
Title: Message Title William Hopper updated an issue Puppet / PUP-6219 Remove req_bits setting Change By: William Hopper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Eric Thompson Release Notes Summary: Before this, if a class was defined more than once their bodies would be merged. The output of a warning or error was under the control of the --strict flag.Now, this is always an error except for the top scope class named '' (a.k.a 'main'). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Eric Thompson Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Eric Sorenson commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Well, that sucks. [root@cloudline repros]# puppet help facts save USAGE: puppet facts save [--terminus TERMINUS] [--extra HASH] API only: create or overwrite an object. As the Faces framework does not currently accept data from STDIN, save actions cannot currently be invoked from the command line. Add Comment
Jira (PUP-4933) Remove cfacter setting
Title: Message Title Eric Thompson commented on PUP-4933 Re: Remove cfacter setting William Hopper can you add release notes on this, if needed, please? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6219) Remove req_bits setting
Title: Message Title Eric Thompson commented on PUP-6219 Re: Remove req_bits setting William Hopper can you add release notes on this, if needed, please? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3670) Remove Facts#strip_internal method
Title: Message Title Eric Thompson commented on PUP-3670 Re: Remove Facts#strip_internal method William Hopper can you add release notes for this, please? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Nick Walker commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Eric Sorenson puppet facts upload no longer exists. In past versions of puppet the agent would upload it's facts to the master before compiling a catalog and then those facts were used to compile the catalog. Now you have to submit facts with a request to compile a catalog and there is no way to submit facts outside of the request to compile a catalog ( or so that is my understanding). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6860) puppet on solaris 11 should support exists? for services
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-6860
puppet on solaris 11 should support exists? for services
Change By:
Moses Mendoza
The smf provider for solaris is currently incapable of removing a service or understanding that a service does not exist.This means puppet cannot distinguish between a service that exists and is stopped/disabled from a nonexistent service. Ie. this (current output):{code}-bash-4.1# puppet resource service fooservice { 'foo': ensure => 'stopped', enable => 'false',}{code}Should be this (desired output):{code}-bash-4.1# puppet resource service fooservice { 'foo': ensure => 'absent',}{code}I should be able to do this, but can't:{code}-bash-4.1# puppet resource service foo ensure=absentError: Could not run: Parameter ensure failed on Service[foo]: Invalid value "absent". Valid values are stopped, running.{code} *Update** Per comment below, it does not make sense to ensure => absent on a service with SMF* Instead, just going with correcting the output for a non-existent service, so now it returns "ensure => absent" instead of "ensure => stopped"
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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
Jira (PUP-6860) puppet on solaris 11 should support exists? for services
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6860 puppet on solaris 11 should support exists? for services Change By: Moses Mendoza Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7143 CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR Change By: Eric Delaney Assignee: Moses Mendoza Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3269) Assuming we include large_value_hash, add some specific tests
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3269 Assuming we include large_value_hash, add some specific tests Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7147) cumulus-vx-25-x86_64: File resource drift correction fails on file named with utf-8 characters
Title: Message Title Sean Griffin created an issue Puppet / PUP-7147 cumulus-vx-25-x86_64: File resource drift correction fails on file named with utf-8 characters Issue Type: Bug Assignee: Unassigned Created: 2017/01/31 9:27 AM Priority: Normal Reporter: Sean Griffin See PUP-7146, PUP-6983. A manifest specifying one file resource whose filename includes a UTF-8 character is applied, successfully creating the desired file. Modifying that file (e.g. emptying it), and re-applying the manifest does not result in correcting the file. On this platform, the environment variable, LANG is set by default to "en_US-UTF-8", which fixes the issue on Ubuntu (PUP-6983). Setting the LANG variable to "POSIX" also does not fix the problem. Add Comment
Jira (PUP-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7073 Comparisons between SELinux file categories should always translate to the numeric version Change By: Kenn Hussey Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Kurt Wall QA Risk Assessment Reason: Build and infra changes not risk-assessed QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7073 Comparisons between SELinux file categories should always translate to the numeric version Change By: Kurt Wall QA Risk Assessment Reason: Build and infra changes not risk-assessed QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6721) Implicit produces/consumes mappings will read variables from topscope
Title: Message Title David Kramer assigned an issue to Ryan Coleman Puppet / PUP-6721 Implicit produces/consumes mappings will read variables from topscope Change By: David Kramer Assignee: Ryan Coleman Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7146) on arista-4-i386: File resource drift correction fails on file named with utf-8 characters
Title: Message Title
Sean Griffin created an issue
Puppet / PUP-7146
on arista-4-i386: File resource drift correction fails on file named with utf-8 characters
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/01/31 9:02 AM
Priority:
Normal
Reporter:
Sean Griffin
This bug is similar to PUP-6983, except that 1. In this case the system is arista-4-i386 and 2. Setting the LANG environment variable to "en_US.UTF-8" does not fix the problem as it did in the Ubuntu-16 case.
To reproduce: 1. apply this manifest:
-bash-4.1# cat manifest
file { "/tmp/file_utf8_title_€" :
ensure => file,
mode => "0644",
Jira (PUP-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Ethan Brown
Story Points:
2
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Ethan Brown commented on PUP-6783
Re: Update all built-in resources to specify {{apply_to_all}} when appropriate
Merged to master in https://github.com/puppetlabs/puppet/commit/9fccfc7374e25795171bdaf6f34f3b207ad582e8
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Ethan Brown assigned an issue to Ethan Brown
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Ethan Brown
Assignee:
Kylo Ginsberg Ethan Brown
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
Ethan Brown
Sprint:
AP 2017-02-08
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you 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-7143) CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR
Title: Message Title Eric Delaney commented on PUP-7143 Re: CI failure: tests/resource/user.utf8_user_comments.rb CiscoXR I ran the tests again last night on the CiscoXR and this time it passed without issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7145) Puppet ensure=>latest doesn't work in case of dots in package name
Title: Message Title
Iaroslav Pleten updated an issue
Puppet / PUP-7145
Puppet ensure=>latest doesn't work in case of dots in package name
Change By:
Iaroslav Pleten
On Amazon linux I tried to {noformat}class test { package { 'java':ensure => 'latest',name=> 'java-1.8.0-openjdk', }}class {"test":}{noformat}And nothing is installed.{noformat}/opt/puppetlabs/puppet/bin/puppet apply ./test.pp --testInfo: Loading factsInfo: Loading factsInfo: Loading factsNotice: Compiled catalog for host.test in environment production in 0.08 secondsInfo: Applying configuration version '1485878170'Notice: Applied catalog in 0.86 seconds{noformat}Meanwhile:{noformat}# /opt/puppetlabs/puppet/bin/puppet resource package javapackage { 'java': ensure => '1:1.7.0.121-2.6.8.1.69.amzn1',}# /opt/puppetlabs/puppet/bin/puppet resource package java-1.8.0-openjdkpackage { 'java-1.8.0-openjdk': ensure => '1:1.8.0.111-1.b15.25.amzn1',} # yum check-updatesLoaded plugins: priorities, s3, update-motd, upgrade-helperamzn-main/latest | 2.1 kB 00:00 amzn-updates/latest | 2.3 kB 00:00 13 packages excluded due to repository priority protectionsjava-1.8.0-openjdk.x86_641:1.8.0.121-0.b13.29.amzn1 amzn-updates java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.29.amzn1 amzn-updates puppet-bootstrap-test.noarch 1.0-29 bootstrap-artifactsSecurity: kernel-4.4.41-36.55.amzn1.x86_64 is an installed security updateSecurity: kernel-4.4.35-33.55.amzn1.x86_64 is the currently running version{noformat}Traced problem to:https://github.com/puppetlabs/puppet/blame/master/lib/puppet/provider/package/yum.rb#L109Here is a my copy/paste of code for IRB:dataset for testing:{noformat}a='''Loaded plugins: priorities, s3, update-motd, upgrade-helperamzn-main/latest | 2.1 kB 00:00 amzn-main/latest/group| 35 kB 00:00 amzn-main/latest/primary_db | 3.5 MB 00:00 amzn-updates/latest
Jira (PUP-7145) Puppet ensure=>latest doesn't work in case of dots in package name
Title: Message Title Iaroslav Pleten moved an issue Puppet / PUP-7145 Puppet ensure=>latest doesn't work in case of dots in package name Change By: Iaroslav Pleten Component/s: Community Component/s: Community Key: FACT PUP - 1563 7145 Project: Facter Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-1563) Puppet ensure=>latest doesn't work in case of dots in package name
Title: Message Title
Iaroslav Pleten created an issue
Facter / FACT-1563
Puppet ensure=>latest doesn't work in case of dots in package name
Issue Type:
Bug
Assignee:
Unassigned
Components:
Community
Created:
2017/01/31 8:10 AM
Environment:
puppet 4.8.0 puppet 4.8.2
Priority:
Normal
Reporter:
Iaroslav Pleten
On Amazon linux I tried to
class test {
package { 'java':
Jira (PUP-6553) Environment compiler and app_management language need to support hiera lookups
Title: Message Title Alex Dreyer commented on PUP-6553 Re: Environment compiler and app_management language need to support hiera lookups If we set up fake facts for environment compilation they may be used. This would run a high risk of compiling a different application graph for each node and breaking dependencies. I think a better path forward for this problem is to allow users to configure an "application_manifest" in environment.conf and not load the main manifest at all. This is separate from the discussion of how we should load data during environment compilation but either way we'll want a different set of variables and data then is generally used for nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-6) Hiera needs to validate the structure of its config file
Title: Message Title Eric Thompson commented on HI-6 Re: Hiera needs to validate the structure of its config file we haven't tested for edge cases in config structure specifically. we could probably get more bang in unit tests for stuff like that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title Vadym Chepkov commented on PUP-3451 Re: Puppet generates metrics that extend past 6 decimal places under some circumstances It was isolated incident 2 years ago, we haven't seen this problem since, vcsrepo was coming back with six digits Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-5587) Unnecessary amount of dns requests with SRV records
Title: Message Title Thomas Mueller commented on PUP-5587 Re: Unnecessary amount of dns requests with SRV records I created a PR: https://github.com/puppetlabs/puppet/pull/5578 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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-3368) nagios_contact no longer is able to parse utf-8 from nagios config files
Title: Message Title Matthias Saou commented on PUP-3368 Re: nagios_contact no longer is able to parse utf-8 from nagios config files I have the exact same problem on a RHEL6 client node (nagios server). Previously working environment : Puppet master : RHEL6 with puppet-3.7.5 and ruby-1.8.7.374, puppetserver-1.0.8. Client node : RHEL6 with puppet-3.7.5 and ruby-1.8.7.374. New non-working environment : Puppet master : RHEL7 with puppet-agent-1.8.3, puppetserver-2.7.2 (Completely new node) Client node : RHEL6 with puppet-agent-1.8.3 (OS unchanged) The puppet-agent includes its own ruby 2.1.0 from what I can see. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you 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.
