Jira (PUP-7425) Refactor Gemfile to consume .gemspec
Title: Message Title Josh Cooper commented on PUP-7425 Re: Refactor Gemfile to consume .gemspec Passed CI in 4ccdc198 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-7425) Refactor Gemfile to consume .gemspec
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7425 Refactor Gemfile to consume .gemspec Change By: Josh Cooper QA Risk Assessment: No Action 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-7437) Make `pkgng` default package provider for dragonfly bsd
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7437 Make `pkgng` default package provider for dragonfly bsd Change By: Josh Cooper QA Risk Assessment: No Action 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-7437) Make `pkgng` default package provider for dragonfly bsd
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7437 Make `pkgng` default package provider for dragonfly bsd Change By: Josh Cooper Release Notes Summary: Changes DragonFly BSD to use the pkgng package provider by default Release Notes: Bug Fix 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-7437) Make `pkgng` default package provider for dragonfly bsd
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-7437 Make `pkgng` default package provider for dragonfly bsd Change By: Josh Cooper Status: Ready for CI Test Assignee: Moses Mendoza 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 (FACT-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style
Title: Message Title Josh Cooper commented on FACT-1600 Re: Update the last of the options tests for facter with TestRail numbers, risk tags, code style Merged to facter#stable https://github.com/puppetlabs/facter/commit/d794b9b6198c054ecbc1e9930c7a5287779a1884 and merged to master in https://github.com/puppetlabs/facter/commit/d06046d7e960deeab60db313efdf533e676a187d 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-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style
Title: Message Title Josh Cooper updated an issue Facter / FACT-1600 Update the last of the options tests for facter with TestRail numbers, risk tags, code style Change By: Josh Cooper Fix Version/s: FACT 3.6.z 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-1601) Add test for fact cache clean-up
Title: Message Title Josh Cooper updated an issue Facter / FACT-1601 Add test for fact cache clean-up Change By: Josh Cooper 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 (FACT-1601) Add test for fact cache clean-up
Title: Message Title Josh Cooper updated an issue Facter / FACT-1601 Add test for fact cache clean-up Change By: Josh Cooper Fix Version/s: FACT 3.y 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-1601) Add test for fact cache clean-up
Title: Message Title Josh Cooper commented on FACT-1601 Re: Add test for fact cache clean-up Merged to facter#master in https://github.com/puppetlabs/facter/commit/e3d080c90f0e8bf716d2a5c221b25399764c96ef 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-7442) Puppet acceptance fails trying to install epel repos oń redhat 5
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7442 Puppet acceptance fails trying to install epel repos oń redhat 5 Change By: Josh Cooper QA Risk Assessment: No Action 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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Josh Cooper commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Had to dig around to remember the details, summarizing here: Nicholas Fagerlund filed the allow_ip issue in https://projects.puppetlabs.com/issues/16686, migrated to PUP-1237 . If you have a default auth.conf which grants everyone access to the prefix /puppet/v3/file, and an allow_ip in fileserver.conf, then puppet would raise an exception. And that combination hasn't worked since before 3.0. So removing support for allow_ip in fileserver.conf is not controversial. The workaround was to add the allow_ip statement to auth.conf so that we never triggered the incorrect behavior in fileserver.conf. We closed PUP-1237 , as won't fix, since allow/deny in fileserver.conf is deprecated. All inbound REST requests go through an authorization check (based on auth.conf) before calling any terminii. The authorization check is either handled in puppet's ruby code or in puppetserver depending on use-legacy-auth-conf. Puppet delegates to each terminus to apply *additional* authorization checks, if the terminus wants to. NOTE: the default auth.conf grants everyone access for all terminus methods (find, search, save, delete), but the fileserver is hardcoded to only allow find and search. This means we can't stop calling the fileserver's authorized? method, since it's effectively part of the authz policy. I'm thinking we should roll this out in phases: Update the default auth.conf to only allow find/search for file_content and file_metadata, and find/search/save for file_bucket_file. Probably don't want to grant delete since file_bucket_file doesn't implement that method. Issue deprecation warnings if we encounter allow/deny in fileserver.conf Issue warnings if the auth.conf allows save or delete to file_content/file_metadata to all users. Ideally we could differentiate when a user has a default auth.conf (possibly upgraded from an old version) vs explicitly granted all access, possibly across
Jira (PUP-7450) undefined method `argument_mismatch'
Title: Message Title Julian created an issue Puppet / PUP-7450 undefined method `argument_mismatch' Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: Breaking Change Created: 2017/04/13 9:13 PM Environment: debian jessie Labels: puppet-agent Priority: Blocker Reporter: Julian after a while i run `puppet agent --test` on my server and got a:
Jira (PUP-2915) Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux
Title: Message Title Ethan Brown commented on PUP-2915 Re: Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux net-ssh is already in the puppet-agent packaging, but its not part of the (rake generated) .gemspec used in the Puppet gem since it doesn't appear in ext/project_data.yaml. We'd like to add it there, but the situation is currently complicated by the need to satisfy other dependencies (i.e. Beaker) and ruby versions. We're considering how to move forward, but PUP-7425 and PA-1077 are good places to look for more info. 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-7332) add ability to lookup "below" in hierarchy
Title: Message Title Eric Sorenson commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Is this truly necessary? Has anyone asked for it? It seems like in practice it could lead to a great deal of complexity. 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-7416) Create acceptance test for PUP-6091
Title: Message Title Eric Thompson commented on PUP-7416 Re: Create acceptance test for PUP-6091 FYI, this is pretty well covered by unit tests and some acceptance (that we probably don't need): https://github.com/puppetlabs/puppet/blob/master/spec/unit/functions/hiera_spec.rb#L86 https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/lookup/config5_interpolation.rb#L22 the dotted key lookup covers this one loosely (in acceptance) as it's for a hiera array subkey. 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-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Geoff Nichols Sprint: Agent 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 (FACT-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols commented on FACT-1508 Re: End-to-end POC for string externalization in Facter This is being addressed as part of other i18n work in flight, especially PA-1023 and LTH-135. 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-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Geoff Nichols Team/s: Agent Epic Status: To Do Epic Name: End-to-end POC for string externalization in Facter Workflow: Engineering Epic Scrum Team Workflow Issue Type: Epic Task 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
Jira (FACT-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Geoff Nichols Fix Version/s: FACT 4.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 (FACT-620) windows facter $::osfamily and $::kernel output inconsistent vs other platforms
Title: Message Title Geoff Nichols updated an issue Facter / FACT-620 windows facter $::osfamily and $::kernel output inconsistent vs other platforms Change By: Geoff Nichols 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 (FACT-1501) timezone contains wrong value
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1501 timezone contains wrong value Change By: Geoff Nichols Sprint: Agent Ready for Engineering 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-1501) timezone contains wrong value
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1501 timezone contains wrong value Change By: Geoff Nichols Acceptance Criteria: * The timezone fact should return the "Timezone ID" instead of the "StandardName" or "DaylightName" (as presented here: http://zonetime.azurewebsites.net ).* If there is some specific reason why the timezone-fact is not returning the "Timezone ID", then we should have a new fact called eg. timezoneid fact with the Timezone ID". 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-1501) timezone contains wrong value
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1501 timezone contains wrong value Change By: Geoff Nichols 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-7440) Pattern can't allow empty string but block newlines
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7440 Re: Pattern can't allow empty string but block newlines Oops hah, thanks! 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-5889) Add a --strict flag to Puppet
Title: Message Title Chris Denneen commented on PUP-5889 Re: Add a --strict flag to Puppet Henrik Lindberg I know this is old issue but just recently I added the following to my spec testing: if Puppet::Util::Package.versioncmp(Puppet.version, '4.5.0') >= 0 RSpec.configure do |c| c.before :each do Puppet.settings[:strict] = :warning end end end and if I have multiple _spec.rb it seems to work for the first one just the rest it seems to default back to :error If I run the same tests with STRICT_VARIABLES=no they all pass Is there something that would revert this upon subsequent test? Add Comment
Jira (PUP-7315) acceptance: add test for hiera interpolated options
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-7315 acceptance: add test for hiera interpolated options Change By: Kurt Wall Assignee: Kurt Wall 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-7358) acceptance: add test of 'puppet module list' while in code page 65001
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-7358 acceptance: add test of 'puppet module list' while in code page 65001 Change By: Kurt Wall Assignee: Kurt Wall 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-7416) Create acceptance test for PUP-6091
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7416 Create acceptance test for PUP-6091 Change By: Kurt Wall Story Points: 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-7444) Regex match integer silently fails
Title: Message Title
Henrik Lindberg commented on PUP-7444
Re: Regex match integer silently fails
A regexp match fails if performed using = or !. When it comes to case or selector expressions, it is unreasonable to error as case options can be of many different types and equality / matching would then error on those. They are specified to work that way.
Note that the code in question is quite inefficient - all the regular expressions are designed to match complete strings. In 4.x the same can be written like this using case:
$some_id = 1
$json_file = case "${some_id}" {
'1', '2', '3', '4' , '5', '8', '9', '10', '14' : { "${some_id}.json" }
default : { "fallback-b${some_id}.json" }
}
notice $json_file
If you really don't know if the user has given the id as a String or a Numeric value you may want to test against both. If that is the case, then you can write a function that returns an array with values of both types. It would be much better if you enforce the data type of the input - then none of the contortions would be necessary.
Here are some examples:
function mymodule::expand(Numeric *$values) {
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Kenn Hussey Team: Foundational Features Systems Engineering 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Susan McNerney commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error We've pushed 4.2.3.2 release out to 18th to give best chance of this releasing. 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Susan McNerney Priority: Normal Critical 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-3459) PQL Query with large fact-value match causes stack overflow
Title: Message Title
Jonathan Newman created an issue
PuppetDB / PDB-3459
PQL Query with large fact-value match causes stack overflow
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/04/13 7:35 AM
Priority:
Normal
Reporter:
Jonathan Newman
If the following pql query is made against PDB, a stack overflow is generated:
inventory[certname] { facts.os.name = "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum facilisis dolor ut est egestas elementum. In bibendum, turpis et lacinia rhoncus, nunc arcu congue lacus, sit amet consequat quam urna sit amet tortor. Proin sed velit scelerisque tortor sagittis imperdiet. Vestibulum volutpat sem sed lectus tempor porttitor nec in nisi. Integer nisi dui, laoreet sit amet egestas sed, laoreet ut nunc. Donec vitae ligula ac purus consectetur aliquam. Quisque quis urna in felis lobortis imperdiet quis ut ligula. Quisque quis euismod felis. Nulla quis lorem non turpis interdum ultricies eu feugiat nunc. Morbi quis efficitur est. Phasellus dapibus pharetra augue. Suspendisse eu interdum ante. Duis rhoncus pulvinar libero, in mattis felis aliquam eget. Suspendisse sodales auctor ultricies. Ut pulvinar non nulla vitae faucibus. Sed rutrum et nulla et iaculis. Nunc pretium tincidunt ex eget commodo. Cras pellentesque accumsan odio, placerat semper nunc fermentum non. Maecenas ut massa ut lorem placerat aliquet egestas id lacus. Fusce placerat fringilla nulla. Ut arcu magna, semper at rhoncus ac, dapibus sed tortor. Pellentesque suscipit lorem ligula, eget fringilla sem egestas vel. Quisque ut eros volutpat, vulputate dolor vel, lacinia eros. Proin vestibulum gravida
Jira (PUP-7444) Regex match integer silently fails
Title: Message Title
Tom De Vylder commented on PUP-7444
Re: Regex match integer silently fails
Referring to d): it's quite the contrary. It doesn't match at all if the input is Numeric or if it's not converted to a String.
Took me a while to find it but at least it's documented: https://docs.puppet.com/puppet/4.9/lang_updating_manifests.html#regular-expressions-against-non-strings
According to said documentation it shoud raise an error: "Matching a value that is not a string with a regular _expression_ now raises an error.". However it doesn't raise anything at all.
This fails silently and goes straight to default:
$some_id = 1
$json_file = $some_id ? {
/^1$|^2$|^3$|^4$|^5$|^8$|^9$|^10$|^14$/ => ${some_id}.json",
default => "fallback-b${some_id}.json"
}
Result: fallback-b1.json, user expected it to have been 1.json but should have raised an error instead.
Albeit very ugly this works fine:
$some_id = 1
$json_file = "${some_id}" ? {
Jira (PUP-7444) Regex match integer silently fails
Title: Message Title Henrik Lindberg commented on PUP-7444 Re: Regex match integer silently fails The best I can think of is a) if the evaluator is running in --debug mode, and b) a match for one option fails and c) one of the operands is Numeric and the other is a String and d) the String would have matched the Numeric if it had been in numeric form, THEN a debug message could be issued "would have matched if it had been Numeric". Not sure how valuable this is. Ping Charlie Sharpsteen - what do you think? Is this a common problem worth doing something about? 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-3311) Improve error message on "index row size" exceptions
Title: Message Title Ryan Senior commented on PDB-3311 Re: Improve error message on "index row size" exceptions Adam Bottchen Tim Purkerson You should add votes/watchers for this ticket, I think it'd be useful too. 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-7449) sshkey uses name instead of title for duplication check
Title: Message Title russ created an issue Puppet / PUP-7449 sshkey uses name instead of title for duplication check Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Unassigned Components: Language Created: 2017/04/13 6:13 AM Environment: server centos-6.8 (updated on Mar 01, 2017) puppetserver-2.7.2-1.el6.noarch (2.7.2) agent centos-6.9 (current) puppet-agent-1.9.3-1.el6.x86_64 (4.9.4) Priority: Normal Reporter: russ With 2 resources named pxe-example.com and dhcp-example.com I get duplicate definition error. The target and title are different in both. The rest is the same.
Jira (PUP-7448) Unmount dependencies give problems
Title: Message Title Ewoud Herregat created an issue Puppet / PUP-7448 Unmount dependencies give problems Issue Type: Bug Assignee: Unassigned Components: Modules Created: 2017/04/13 5:16 AM Labels: module mount resources Priority: Normal Reporter: Ewoud Herregat In my companies filesystem there are a few parent and child mounts. Puppet autorequires the child mounts when using the native mount resource. When, however, I try to unmount these parent and child directories, puppet seems to be using the exact same order, which is causing errors since you can't unmount a parentmount without first unmounting the child mounts. Is this intended or is there anyway to fix this problem? Thanks.
Jira (PUP-4927) Add logfile option to exec
Title: Message Title Jeff Sparrow commented on PUP-4927 Re: Add logfile option to exec not sure what else this needs? feel free to close this. its been 2 years with no movement. 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-567) Variables not interpolated when value also includes an eyaml encrypted value
Title: Message Title Geoff Nichols commented on HI-567 Re: Variables not interpolated when value also includes an eyaml encrypted value Great! Thanks for the report and the follow-up Roland Kool! 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-567) Variables not interpolated when value also includes an eyaml encrypted value
Title: Message Title Roland Kool commented on HI-567 Re: Variables not interpolated when value also includes an eyaml encrypted value This is indeed fixed with 4.10 that includes a patch for PUP-7359 Ticket can be closed. 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-2915) Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux
Title: Message Title Josh Cooper commented on PUP-2915 Re: Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux Ethan Brown and I were just working on adding the missing net/ssh dependency to puppet's Gemfile and puppet-agent packaging. 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.
