Jira (PUP-7440) Pattern can't allow empty string but block newlines
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-7440
Pattern can't allow empty string but block newlines
Change By:
Hunter Haugen
I'm trying to use https://docs.puppet.com/puppet/4.9/lang_data_abstract.html#pattern to validate my input, which at least should allow {{''}} but not allow {{"\n"}}Here are some examples that I tried:{code:puppet}notice('' =~ Pattern[/\A\Z/])notice("\n" !~ Pattern[/\A\Z/])notice('' =~ Pattern[/\A[^\n]*\Z/])notice("\n" !~ Pattern[/\A[^\n]*\Z/])notice('' =~ Pattern[/\A[^\n]+\Z/])notice("\n" !~ Pattern[/\A[^\n]+\Z/])notice('' =~ Pattern[/^[^\n]*$/])notice("\n" !~ Pattern[/^[^\n]*$/])notice('' =~ Pattern[/^[^\n]+$/])notice("\n" !~ Pattern[/^[^\n]+$/]){code}Also, {{Pattern[]}} allows multiple arguments, but these regexes are or'd together so it's not possible to use a combination of these either, as it will always be {{true or false}} or {{false or true}}
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 Haugen created an issue
Puppet / PUP-7440
Pattern can't allow empty string but block newlines
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/04/10 4:42 PM
Environment:
puppet 4.9
Priority:
Normal
Reporter:
Hunter Haugen
I'm trying to use https://docs.puppet.com/puppet/4.9/lang_data_abstract.html#pattern to validate my input, which at least should allow '' but not allow "\n"
Here are some examples that I tried:
notice('' =~ Pattern[/\A\Z/])
notice("\n" !~ Pattern[/\A\Z/])
notice('' =~ Pattern[/\A[^\n]*\Z/])
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Hunter Haugen commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 Here you go: https://github.com/puppetlabs/hiera/pull/48 Oh wait. 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-7103) Prefetch runs for tag-filtered providers
Title: Message Title Hunter Haugen commented on PUP-7103 Re: Prefetch runs for tag-filtered providers Specifically, the mysql_* providers are suitable because the mysql command exists, but during prefetch try to connect to a non-running daemon and fail. One proposed workaround is https://github.com/puppetlabs/puppetlabs-mysql/pull/921 though this would also mean adding similar providers to firewall, mongodb, rabbitmq, keystone, and any other provider that depends on a running service. 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-7103) Prefetch runs for tag-filtered providers
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-7103
Prefetch runs for tag-filtered providers
Issue Type:
Bug
Affects Versions:
PUP 4.8.1
Assignee:
Unassigned
Created:
2017/01/13 2:24 PM
Priority:
Normal
Reporter:
Hunter Haugen
Steps to reproduce:
# puppet apply -e 'package { "aoeu": }' --tags doesntmatchanything -d
...
Debug: Prefetching pkgdmg resources for package
Debug:
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Hunter Haugen Priority: Major 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 (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Hunter Haugen commented on PUP-3483 Re: Systemd provider doesn't scan for changed units So, this seems major if not critical, given the systemd adoption rates. 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Hunter Haugen Priority: Normal Major 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-6930) Disallow multiple case defaults.
Title: Message Title Hunter Haugen created an issue Puppet / PUP-6930 Disallow multiple case defaults. Issue Type: Bug Assignee: Unassigned Components: Language Created: 2016/11/17 9:55 AM Priority: Normal Reporter: Hunter Haugen Apparently multiple default blocks are possible: https://github.com/puppetlabs/puppetlabs-postgresql/pull/798 Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6751) Deprecate multi-block defaults (and multi-block resources)
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-6751
Deprecate multi-block defaults (and multi-block resources)
Issue Type:
Task
Assignee:
Unassigned
Created:
2016/09/28 5:37 AM
Priority:
Normal
Reporter:
Hunter Haugen
Puppet's language has long supported multi-block resources:
file {
'/etc/ssh_host_dsa_key':
mode => '0600',
owner => 'root',
group => 'root',
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title
Hunter Haugen commented on PUP-5971
Re: Define evaluation should be evaluated depth-first, not breadth-first
Ran into this again with the tomcat module. Here is a simple minimal case:
define foo {
foo::foo { $name: }
}
define foo::foo {
ensure_resource('user', 'tomcat8', { 'ensure' => 'present' })
file { '/test':
owner => 'tomcat8',
}
}
define bar {
ensure_resource('user', 'tomcat8', { 'ensure' => 'present' })
Jira (PUP-6158) puppetlabs-ntp module doesn't configure service to start at boot in AIX
Title: Message Title Hunter Haugen moved an issue Puppet / PUP-6158 puppetlabs-ntp module doesn't configure service to start at boot in AIX Change By: Hunter Haugen Affected Organization/s: Northrop_Grumman-SBIRS Key: FM PUP - 5109 6158 Project: Forge Modules [Internal] Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Hunter Haugen commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first When changing the variable lookup scope, each variable lookup would do two lookups (the new lookup and the old lookup, except it was broken for a while) and if they were different then it raised a warning. Two different compile paths on every run would introduce a lot of overhead, but perhaps the "puppet 4 future parser" could have depth-first and be under evaluation of users who attempt early migration, as the puppet 3 future parser did. Most likely the issue we'd run into is that roles and profiles would declare lots of parameterized classes, and various components include those same classes farther down. Under breadth-first search the roles & profiles would be generally evaluated first and thus the parameterized classes would be fine, but depth-first risks delving into the non-parameterized declaration of classes by defined types which then conflict with the parameterized versions later on... bummer. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Hunter Haugen commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first Keeping lazy evalutation pointers on defined() functions such that it is neither depth nor breadth evalutaion sounds like a ball of spaghetti to me, but I'd love for you to prove me wrong. In the mean time, I'll keep my eye open for sub defines that would assume the parent would be fully evaluated. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-5971
Define evaluation should be evaluated depth-first, not breadth-first
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/24 3:27 PM
Priority:
Normal
Reporter:
Hunter Haugen
For a long time, a little loop in the compiler has called evaluate_definitions after the current scope is evaluated (https://github.com/puppetlabs/puppet/blob/8a82d7d7c4d8254177e93a392607385755095cf4/lib/puppet/parser/compiler.rb#L609-L625).
This means that declaration evaluation is breadth-first instead of depth-first. However when writing manifests one often sees the pattern of if defined(Some['resource']) which depends on parse order to work. Using defined() with definitions that declare definitions such as `some::sub {'hi': }
; if defined(Some::Sub::Define['aoeu'])` when combined with the breadth-first evaluation described violates parse order, as the defined resource will not exist until after the function call as their evaluation is delayed until the end of the current scope.
If defined resources were evaluated at parse time instead of being delayed until evaluate_definitions then parse order would be maintained.
Also, I believe that this is different than collectors as collectors affect resources across the entire catalog, whereas defined resources are only evaluated a single time and will not generate additional resources on further evaluation.
Jira (PUP-5589) Type without namevar causes failures with no error
Title: Message Title Hunter Haugen created an issue Puppet / PUP-5589 Type without namevar causes failures with no error Issue Type: Bug Assignee: Unassigned Created: 2015/12/08 9:05 PM Priority: Normal Reporter: Hunter Haugen When trying to compile a catalog with a resource type that does not have a namevar specified in the type (ie, no parameter with `:namevar => true` and no `isnamevar` call) then the puppet run will exit 1 as soon as the catalog compile is finished with no back trace, error message, or any other indicator that anything is wrong. This makes it extremely difficult to debug (ie, guessing at what is missing). Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2150) Provide reusable report wire-format code
Title: Message Title Hunter Haugen commented on PDB-2150 Re: Provide reusable report wire-format code This originated from Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2150) Provide reusable report wire-format code
Title: Message Title Hunter Haugen created an issue PuppetDB / PDB-2150 Provide reusable report wire-format code Issue Type: Improvement Assignee: Unassigned Created: 2015/11/03 3:54 PM Priority: Normal Reporter: Hunter Haugen Currently the code that transforms a puppet report object into a wire-format json payload to be sent to puppetdb lives in the report processor (https://github.com/puppetlabs/puppetdb/blob/3.2.0/puppet/lib/puppet/reports/puppetdb.rb#L28-L187). As a user I want to write my own report processor and submit the reports to puppetdb in a different way. The code is not reusable as it is enclosed in a report processor and is not directly accessible from other report processors, so it needs to be moved into a generic (like lib/puppet/util/puppetdb/*) library that other report processors can access. Add Comment
Jira (PUP-4901) puppetlabs-splunk doesn't update spunk
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-4901 puppetlabs-splunk doesn't update spunk Change By: Hunter Haugen Summary: puppet puppetlabs -splunk doesn't update spunk Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1430) puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb
Title: Message Title Hunter Haugen commented on PDB-1430 Re: puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb I don't have an opinion on this actually; I just created it as a more general ticket to track the wants of PDB-1272 and PDB-1273 (linked issues). This would be for Trevor Vaughan Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5091) Add confine for arbitrary libraries (gems)
Title: Message Title Hunter Haugen created an issue Puppet / PUP-5091 Add confine for arbitrary libraries (gems) Issue Type: New Feature Assignee: Unassigned Created: 2015/08/26 11:23 AM Priority: Normal Reporter: Hunter Haugen When writing custom types and providers, it is often necessary to bring in external libraries. The readme should document which gems are needed, and the providers should have confines on those gems. One half-workaround for this currently is to confine based on a feature, and have the feature try to load the gem's library. But for libraries that are commonly used across many modules (such as faraday) the modules features will just stomp on each other. This is increasingly becoming an issue as more providers are appearing in the same space. Add Comment
Jira (PUP-5021) package name dependency no longer works
Title: Message Title Hunter Haugen created an issue Puppet / PUP-5021 package name dependency no longer works Issue Type: Bug Assignee: Unassigned Created: 2015/08/10 2:02 PM Priority: Normal Reporter: Hunter Haugen When a dependency is declared on a package name that is different from the title, the package resource is not found: [root@ngi2pj5swkzolhe tmp]# /opt/puppetlabs/bin/puppet --version 4.2.1 [root@ngi2pj5swkzolhe tmp]# cat test.pp #
Jira (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Hunter Haugen created an issue Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Issue Type: Bug Assignee: Unassigned Created: 2015/07/23 4:22 PM Environment: facter 3.0.1, sles 10 Priority: Normal Reporter: Hunter Haugen Interfaces can have multiple IP addresses of the same protocol (v4 or v6): t5yi12595vbs1v6:/etc # ip addr show lo 1: lo: LOOPBACK,UP mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Jira (PUP-531) {{puppet cert generate}} should accept {{--allow-dns-alt-names}}
Title: Message Title
Hunter Haugen commented on PUP-531
Re: {{puppet cert generate}} should accept {{--allow-dns-alt-names}}
I don't know if that actually blocks this work, though.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4691) Solaris zone resource fails with iptype = exclusive
Title: Message Title Hunter Haugen commented on PUP-4691 Re: Solaris zone resource fails with iptype = exclusive Eric Thompson Yes, https://github.com/puppetlabs/puppet/pull/4000 sorry. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3999) Cannot strip result of generate (regression)
Title: Message Title
Hunter Haugen commented on PUP-3999
Re: Cannot strip result of generate (regression)
Looks like it's been fixed at least as of puppet 4 (it was a puppet bug):
extern% puppet apply -e notice(strip(generate('/bin/date', '-u', '+%Y%m%d%H%M')))
Notice: Scope(Class[main]): 201506242337
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4709) Future parser thinks a resource has been declared twice
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-4709
Future parser thinks a resource has been declared twice
Change By:
Hunter Haugen
Ifwehave2resources wherethetitlesbegin with asimilarname.Futureparsers anidenticalstringenclosedinsquarebraces,thepuppet4parser throwsanerrorthatduplicateresourceshavebeendeclared ,eventhoughtheyaredifferent : {code}extern%PUPPET_GEM_VERSION='~4.0'bepuppetapply-e'notify{[foo]bar:};notify{[foo]baz:}'Error:EvaluationError:ErrorwhileevaluatingaResourceStatement,Duplicatedeclaration:Notify[[foo]baz]isalreadydeclaredinfile:1;cannotredeclareatline1atline1:27onnodeextern.local{code} Itworksfinewithoutthesquarebraceshowever:{code}extern%PUPPET_GEM_VERSION='~4.0'bepuppetapply-e'notify{foobar:};notify{foobaz:}'Notice:Compiledcatalogforextern.localinenvironmentproductionin0.48secondsNotice:foobarNotice:/Stage[main]/Main/Notify[foobar]/message:defined'message'as'foobar'Notice:foobazNotice:/Stage[main]/Main/Notify[foobaz]/message:defined'message'as'foobaz'Notice:Appliedcatalogin0.02seconds{code} Anexampleofaunittestfailureisinpuppetlabs-inifilewhenrunagainstPuppet4:https://travis-ci.org/puppetlabs/puppetlabs-inifile/jobs/65406398
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-4709) Square braces in title confuse puppet 4 parser
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-4709
Square braces in title confuse puppet 4 parser
Change By:
Hunter Haugen
Ifwehave 2 two resourceswherethetitlesbeginwithanidenticalstringenclosedinsquarebraces,thepuppet4parserthrowsanerrorthatduplicateresourceshavebeendeclared:{code}extern%PUPPET_GEM_VERSION='~4.0'bepuppetapply-e'notify{[foo]bar:};notify{[foo]baz:}'Error:EvaluationError:ErrorwhileevaluatingaResourceStatement,Duplicatedeclaration:Notify[[foo]baz]isalreadydeclaredinfile:1;cannotredeclareatline1atline1:27onnodeextern.local{code}Itworksfinewithoutthesquarebraceshowever:{code}extern%PUPPET_GEM_VERSION='~4.0'bepuppetapply-e'notify{foobar:};notify{foobaz:}'Notice:Compiledcatalogforextern.localinenvironmentproductionin0.48secondsNotice:foobarNotice:/Stage[main]/Main/Notify[foobar]/message:defined'message'as'foobar'Notice:foobazNotice:/Stage[main]/Main/Notify[foobaz]/message:defined'message'as'foobaz'Notice:Appliedcatalogin0.02seconds{code}Anexampleofaunittestfailureisinpuppetlabs-inifilewhenrunagainstPuppet4:https://travis-ci.org/puppetlabs/puppetlabs-inifile/jobs/65406398
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-4709) Square braces in title confuse puppet 4 parser
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-4709 Square braces in title confuse puppet 4 parser Change By: Hunter Haugen Summary: Future Squarebracesintitleconfusepuppet4 parser thinksaresourcehasbeendeclaredtwice Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4691) Solaris zone resource fails with iptype = exclusive
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-4691 Solaris zone resource fails with iptype = exclusive Change By: Hunter Haugen Story Points: 1 2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4691) Solaris zone resource fails with iptype = exclusive
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-4691 Solaris zone resource fails with iptype = exclusive Change By: Hunter Haugen Scrum Team: Modules Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4691) Solaris zone resource fails with iptype = exclusive
Title: Message Title Hunter Haugen assigned an issue to Hunter Haugen Puppet / PUP-4691 Solaris zone resource fails with iptype = exclusive Change By: Hunter Haugen Assignee: HunterHaugen Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3088) Debug logging messages can't be used by providers with a path method
Title: Message Title Hunter Haugen commented on PUP-3088 Re: Debug logging messages can't be used by providers with a path method This is primarily a concern in providers, where path/file/tags may be properties and thus get eponymous getter methods. https://github.com/puppetlabs/puppet/pull/4000 should handle that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4691) Solaris zone resource fails with iptype = exclusive
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-4691
Solaris zone resource fails with iptype = exclusive
Issue Type:
Bug
Assignee:
Hunter Haugen
Created:
2015/06/03 4:43 PM
Priority:
Normal
Reporter:
Hunter Haugen
Due to PUP-3088, the solaris zone resource will fail given the following manifest (or any manifest that has iptype = exclusive):
zone { 'test33321':
name = $fqdn,
autoboot = true,
iptype = 'exclusive',
ip = [net1],
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Hunter Haugen assigned an issue to Hunter Haugen Puppet / PUP-1628 Add mount provider for AIX Change By: Hunter Haugen Assignee: HunterHaugen Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Hunter Haugen commented on PUP-1628 Re: Add mount provider for AIX PR for review https://github.com/puppetlabs/puppet/pull/3740 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4190) CLONE - Puppet device displays credentials in plain text when run manually
Title: Message Title Hunter Haugen commented on PUP-4190 Re: CLONE - Puppet device displays credentials in plain text when run manually PR: https://github.com/puppetlabs/puppet/pull/3706 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4190) CLONE - Puppet device displays credentials in plain text when run manually
Title: Message Title Hunter Haugen moved an issue Puppet / PUP-4190 CLONE - Puppet device displays credentials in plain text when run manually Change By: Hunter Haugen Component/s: f5 Key: MODULES PUP - 1845 4190 Project: ForgeModules Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1273) -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb
Title: Message Title Hunter Haugen moved an issue PuppetDB / PDB-1273 -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb Change By: Hunter Haugen Component/s: puppetdb Key: MODULES PDB - 1812 1273 Project: ForgeModules PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1272) The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes
Title: Message Title Hunter Haugen moved an issue PuppetDB / PDB-1272 The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes Change By: Hunter Haugen Component/s: puppetdb Key: MODULES PDB - 1811 1272 Project: ForgeModules PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1272) The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes
Title: Message Title Hunter Haugen commented on PDB-1272 Re: The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes It sounds like this is relevant to the puppetdb package specifically, as the puppedb module does not manage /etc/sysconfig/puppetdb at all. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4055) Support DNF package manager (yum successor)
Title: Message Title Hunter Haugen created an issue Puppet / PUP-4055 Support DNF package manager (yum successor) Issue Type: New Feature Assignee: Unassigned Created: 2015/02/27 11:00 AM Priority: Normal Reporter: Hunter Haugen Fedora 22 is moving from yum to DNF for its package management (http://www.phoronix.com/scan.php?page=news_itempx=Fedora-22-Alpha-Features) https://github.com/rpm-software-management/dnf We should add support for this with a new package provider. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4032) puppet device always exits 0
Title: Message Title Hunter Haugen created an issue Puppet / PUP-4032 puppet device always exits 0 Issue Type: Bug Assignee: Unassigned Created: 2015/02/20 9:36 AM Priority: Normal Reporter: Hunter Haugen Compile errors, resource failures, --detailed-exitcodes... it always exits 0. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4032) puppet device always exits 0
Title: Message Title Hunter Haugen commented on PUP-4032 Re: puppet device always exits 0 https://github.com/puppetlabs/puppet/pull/3633 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4032) puppet device always exits 0
Title: Message Title Hunter Haugen assigned an issue to Kylo Ginsberg Puppet / PUP-4032 puppet device always exits 0 Change By: Hunter Haugen Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3664) Invalid metadata.json in module root causes Error 400
Title: Message Title Hunter Haugen commented on PUP-3664 Re: Invalid metadata.json in module root causes Error 400 If the module is a plugin-only module (ie, does not have manifests that are declared) then the erroneous metadata.json would not raise an error. The module will be silently ignored by pluginsync instead. The error WILL be raised for puppet module list though. It would be nice if the puppet master's pluginsync raised an error as well. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3975) puppet device should have a puppet apply equivilant
Title: Message Title Hunter Haugen commented on PUP-3975 Re: puppet device should have a puppet apply equivilant Yes yes! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3732) type validation should not run for `puppet resource`
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-3732 type validation should not run for `puppet resource` Change By: Hunter Haugen Summary: typevalidationshould rot not runfor`puppetresource` Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3732) type validation should rot run for `puppet resource`
Title: Message Title Hunter Haugen created an issue Puppet / PUP-3732 type validation should rot run for `puppet resource` Issue Type: Bug Assignee: Unassigned Created: 2014/12/03 12:41 PM Priority: Normal Reporter: Hunter Haugen tl;dr: puppet resource creates resource types without attributes, which causes the type's global validate block to fail. It should initialize the type with values from the provider so that it can be validated. Puppet types can have per-parameter or per-property validate blocks, but can also have a global validate block. Oddly, when running puppet resource whatever the per-attribute validates are not called (as no attributes are passed), but the global validate is. Validation is usually done on the resource coming from the catalog, which is self in the context of the global validate. When using puppet resource there is no true catalog per-say, but if no arguments are passed then the resource types @parameter hash is not initialized and thus validation will fail. If the @parameter hash was merged with the values from self.provider's @property_hash then the global validation block would still be validating any values that were passed on the command-line, or just the values returned by self.instances if there are no arguments. This *should* still work for normal catalog application, as a resource returned by self.instances and thus passing global validation is already configured correctly.
Jira (PUP-1793) Cleanup, reduce, and improve stdlib based on new Puppet 4 features
Title: Message Title Hunter Haugen commented on PUP-1793 Re: Cleanup, reduce, and improve stdlib based on new Puppet 4 features An update before heading off for Thanksgiving vacation: (caveat, I haven't read Henrick's 800-line write up yet, but it looks super useful and will go through it after vacation.) The high-level plan is to release a major version that drops puppet 2.7 support and adds puppet 4 support in a following minor release if not at the same time) so that we can have overlapping 3/4 support in a major revision of stdlib. Splitting 3/4 support between two modules would be a Bad Thing for our customers. This will cause some conflicting functions (ie, type()) and some gaps in functionality as mentioned, but nothing we can't cover with a few minor releases and some hacky puppet version detection (like having type.rb wrap the function declaration). The major revision after that will be a long time after and drop puppet 3 support. We would like if at all possible to avoid any other churn on major versions to keep user confidence high. I'll construct a more specific plan in the near future. Thanks for doing the footwork on this! Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title
Hunter Haugen commented on an issue
Re: Yumrepo target attribute does not work
The yumrepo resource type defines target to be a parameter 1 and so therefore it is not read from the system during self.instances as a property would be, and thus cannot be updated by itself. (Parameters are used to modify the behavior of the provider when sync'ing properties, but are not themselves sync'd.)
But it doesn't seem to be taken into account even when creating the repo... during the create, the provider calls the store class method 2 which is for a Puppet::Util::IniConfig object 3. (NB, virtual_inifile is a collection of all .repo files into one big ini structure.) The iniconfig file collection will store each ini structure in a file named after its key in the virtual_inifile object 4 which doesn't take target into account at all.
To start fixing this, it would probably require updating the description section 5 to be able to use target instead of descr if it is available, and the description is not currently one of the pre-existing sections. But that would probably also run into issues with destroying 6, among other things.
I assume we would not want to allow targets to be changed once a repo entry exists... or at least I can't imagine how puppet would handle such an operation.
Add Comment
Puppet / PUP-2782
Yumrepo target attribute does not work
Simplified example: yumrepo { 'foo-bar': descr = 'Foo Bar', target = '/tmp/foo-bar.repo' } yumrepo { 'foo-bat': descr = 'Foo Bat', target = '/tmp/foo-bar.repo' }Notice: /Stage[main]/Yum/Yumrepo[foo-bat]/ensure: created Info: changing mode of /etc/yum.repos.d/foo-bat.repo from 600 to 644 Not...
Jira (PUP-3496) Ability to set default provider or require `provider` to be set
Title: Message Title Hunter Haugen created an issue Puppet / PUP-3496 Ability to set default provider or require `provider` to be set Issue Type: New Feature Assignee: Unassigned Created: 21/Oct/14 12:16 PM Priority: Normal Reporter: Hunter Haugen When creating custom types and providers, there is no way to 1) set a globally-default provider, 2) require the user to explicitly set a provider, or 3) get rid of the Warning: Found multiple default providers for ... warning without hacky hacks. More details: 1) globally-default provider provider.rb gives the ability to set defaultfor based on availability of a :feature or on the matching of a fact, but there is no always default setting (link). The closest I've gotten is setting defaultfor :feature = :posix (link) when I don't need windows defaults, but ran into trouble when trying to defaultfor on a device because of PUP-2717 (facts don't work for devices). The next best thing was to create a puppet feature and use that to set a default (link) (private link). It's all gross. 2) Require the user to explicitly set provider From type.rb during a catalog application, self.instances (which is called before processing catalog resources) calls self.providers_by_source which calls self.defaultprovider which will randomly pick a default provider if no default is discoverable (link). It doesn't seem to care whether a resource has a provider attribute set by self.instances or in the catalog, it still prints a warning. Then the catalog resource begin their processing and validation, but at that point all types already have a default provider and we cannot tell if a user explicitly set the provider or not, and therefore cannot tell if the provider is even the right one. The hacky solution to this was to use the global default provider hack above, but with a dummy resource that just raises an error to tell the user to choose a provider (link) (except it
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-3226 Non-existent directory environments should raise a helpful error Change By: Hunter Haugen Environment: PE3.3.1( puppet3.6.2 ) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Issue Type:
Improvement
Assignee:
Unassigned
Created:
09/Sep/14 5:11 PM
Environment:
puppet 3.6.2
Priority:
Normal
Reporter:
Hunter Haugen
If in puppet.conf I have:
[main]
basemodulepath = /etc/puppet/modules
environmentpath = /etc/puppet/envs
and if /etc/puppet/modules/test/manifests/init.pp exists with class\ test { }}} in it, and if /etc/puppet/envs/production does not exist, when I run {{puppet agent -t I get Error 400 on SERVER: Could not find class test for ...
This is because if $environmentpath/$environment does not exist then the environment is considered to be non-existent. If I create /etc/puppet/envs/production (even leaving it empty) then it will work as desired.
To avoid red-herring hunts, it would probably be better UX to have the puppetmaster raise an error describing that the environment (in this case production) cannot be found in the environmentpath.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Change By:
Hunter Haugen
Ifinpuppet.confIhave:{noformat}[main]basemodulepath=/etc/ puppetlabs/ puppet/modulesenvironmentpath=/etc/ puppetlabs/ puppet/envs{noformat}andif/etc/ puppetlabs/ puppet/modules/test/manifests/init.ppexistswith{{class\test\{\}}}init,andif/etc/ puppetlabs/ puppet/envs/productiondoesnotexist,whenIrun{{puppetagent-t}}Iget{{Error400onSERVER:Couldnotfindclasstestfor...}}Thisisbecauseif{{$environmentpath/$environment}}doesnotexistthentheenvironmentisconsideredtobenon-existent.IfIcreate/etc/puppet/envs/production(evenleavingitempty)thenitwillworkasdesired.Toavoidred-herringhunts,itwouldprobablybebetterUXtohavethepuppetmasterraiseanerrordescribingthattheenvironment(inthiscaseproduction)cannotbefoundintheenvironmentpath.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Change By:
Hunter Haugen
Ifinpuppet.confIhave:{noformat}[main]basemodulepath=/etc/puppetlabs/puppet/modulesenvironmentpath=/etc/puppetlabs/puppet/envs{noformat}andif/etc/puppetlabs/puppet/modules/test/manifests/init.ppexistswith {{ ` class \ test \ { \ } }} ` init,andif/etc/puppetlabs/puppet/envs/productiondoesnotexist,whenIrun{{puppetagent-t}}Iget{{Error400onSERVER:Couldnotfindclasstestfor...}}Thisisbecauseif{{$environmentpath/$environment}}doesnotexistthentheenvironmentisconsideredtobenon-existent.IfIcreate/etc/puppet/envs/production(evenleavingitempty)thenitwillworkasdesired.Toavoidred-herringhunts,itwouldprobablybebetterUXtohavethepuppetmasterraiseanerrordescribingthattheenvironment(inthiscaseproduction)cannotbefoundintheenvironmentpath.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Hunter Haugen moved an issue Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename Change By: Hunter Haugen Workflow: Forge Platform Workflow Issue Type: Bug Improvement Key: FORGE PUP - 36 3124 Project: Puppet Forge Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Hunter Haugen commented on an issue Re: tool should generate code using the actual module name as the directory instead of username-modulename For reference, the work was accepted as part of https://github.com/puppetlabs/puppet/pull/1711 but had to be reverted due to testing issues. If anyone wants to follow up on this work they are welcome to. Add Comment Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename This is what currently happens pre [root@puppet modules]# puppet-module generate ghoneycutt-apache = Generating module at /etc/puppetlabs/puppet/modules/ghoneycutt-apache - ghoneycutt-apache ghoneycutt-apache/M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Hunter Haugen commented on an issue Re: tool should generate code using the actual module name as the directory instead of username-modulename From #puppet-dev: 14:06 +finch | electrical: I believe the failure occurred because acceptance tests were assuming that `puppet module generate` was outputting username-modulename genned modules ... 14:08 electrical | ahh okay :-) thanks. i'll make some time tomorrow and send a new PR. Add Comment Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename This is what currently happens pre [root@puppet modules]# puppet-module generate ghoneycutt-apache = Generating module at /etc/puppetlabs/puppet/modules/ghoneycutt-apache - ghoneycutt-apache ghoneycutt-apache/M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2779) Resource suitability in Puppet::Transaction.evaluate
Title: Message Title Hunter Haugen created an issue Puppet / PUP-2779 Resource suitability in Puppet::Transaction.evaluate Issue Type: Bug Assignee: Unassigned Created: 13/Jun/14 4:23 PM Environment: puppet 3.6.2 Priority: Normal Reporter: Hunter Haugen Given a resource @resource and a provider with both commands and confine, the following cases appear to happen: @resource.suitable? is true only when confine and commands are trueish @resource.provider has a provider only when commands is trueish, but ignores the state of confine I would expect @resource.provider to not return a provider unless it was suitable. This could cause issues because the Puppet::Transaction.evaluate method uses @resource.provider to evaluate suitability: https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/transaction.rb#L79 . The comment would indicate that it is evaluating suitability, in which case it should be using @resource.suitable?
Jira (PUP-2779) Resource suitability in Puppet::Transaction.evaluate
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-2779
Resource suitability in Puppet::Transaction.evaluate
Change By:
Hunter Haugen
Givenaresource{{@resource}}andaproviderwithboth{{commands}}and{{confine}},thefollowingcasesappeartohappen:-{{@resource.suitable?}}istrueonlywhen{{confine}}and{{commands}}aretrueish-{{@resource.provider}}hasaprovideronlywhen{{commands}}istrueish,butignoresthestateof{{confine}}Iwouldexpect{{@resource.provider}}tonotreturnaproviderunlessitwassuitable.Thiscouldcauseissuesbecausethe{{Puppet::Transaction.evaluate}}methoduses{{@resource.provider}}toevaluatesuitability:https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/transaction.rb#L79.The code commentwouldindicatethatitisevaluatingsuitability,inwhichcaseitshouldbeusing{{@resource.suitable?}} andavoidfalsepositiveswhereaproviderisnotsuitable(dueto{{confine}}).
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
Hunter Haugen commented on an issue
Re: Yum provider purge target runs irrespective of package installation status
Still seeing this issue, Puppet 3.6.1, CentOS 6.5, ruby 1.8.7p352
Add Comment
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; } [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: P...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Hunter Haugen assigned an issue to Hunter Haugen Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Hunter Haugen Assignee: HunterHaugen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Hunter Haugen commented on an issue Re: `puppet module build` should use `metadata.json` as input format When using ea39a3de5705020d79ae89d6ab513b37fa662ce7 With Modulefile and metadata.json: Maybe success? It appears to work as specified, preferring the contents of the metadata.json and ignoring the Modulefile, but this is backwards incompatible as it previously would merge the two (eg, if there are dependencies declared in Modulefile but not in metadata.json, then the package will have no dependencies whereas before it WOULD have dependencies). This seems to be intended though. With Modulefile but no metadata.json: Success. It works as described. With no Modulefile but with metadata.json: Success. This was not previously supported so is not backwards-incompatible, and works as described. When using current master (90aad3fff7d270ef2683f486cdf999c003510cf0): With Modulefile and metadata.json: Same as above. With Modulefile but no metadata.json: Fail? The dependency list that appears in the repo Modulefile specifies two dependencies, but the package metadata.json appears like this: dependencies: [ #Puppet::ModuleTool::Dependency:0x007fc7c4218f48, #Puppet::ModuleTool::Dependency:0x007fc7c4218ac0 ] Perhaps this is on purpose, if master branch no longer supports Modulefile With no Modulefile but with metadata.json: Same as above. Other notes: I am seeing /Users/hunner/Documents/work/git/puppet/lib/puppet/version.rb:10: warning: already initialized constant PUPPETVERSION, but I see this on 3.5.1 as well. Add Comment
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Hunter Haugen Assignee: HunterHaugen PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Hunter Haugen commented on an issue Re: `puppet module build` should use `metadata.json` as input format I failed the review because based on the backwards-incompatible nature of this change, it will currently break the packaging of all of our modules. Example:: We only declare dependencies in the Modulefile but not metadata.json. We also don't synchronize the versions in Modulefile and metadata.json because pmt prefers the Modulefile version over metadata.json invisibly. Suggestion: The pmt should merge Modulefile and metadata.json entries, preferring the entries in Modulefile for conflicts. It should warn that support for Modulefile is deprecated and it will only use metadata.json in the future. It would also be helpful if it warned about every entry that exists in Modulefile but is different or non-existent in the metadata.json Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
Change By:
Hunter Haugen
Ifyourunthepuppetlabs-ntpmodulewithparser=futureon3.5.0-rc1itwillbreakcomplainingthatitcan'tcall{{flatten {{ }} on{{nil:NilClass {{ }} inthentp.conftemplate.Thishappensbecauseforsomereason{{@restrict {{ }} andeveryothervariableinthetemplateisn'tbound,ergonil.IfIexplicitlyadda{{$restricted=$::ntp::restricted}}toconfig.ppitworks.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Common package name in two different providers
Title: Message Title
Hunter Haugen commented on an issue
Re: Common package name in two different providers
I agree with this solution also.
If the holdup is finding a solution to allow any resource to be declared with non-unique namevars then we may be thinking too hard about a solution that doesn't fit the problem. The package resource is kind of special in this regard.
Add Comment
Puppet / PUP-1073
Common package name in two different providers
I have a common package name, that's in two different package managers (one with yum the other with gem) package { remove-mysql: name = mysql, provider = yum, ensure = absent, } - package { gem-mysql...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-1692) Allow types to specify required attributes
Title: Message Title Hunter Haugen created an issue Puppet / PUP-1692 Allow types to specify required attributes Issue Type: Improvement Assignee: Unassigned Created: 13/Feb/14 4:21 PM Priority: Normal Reporter: Hunter Haugen Currently with types in puppet, a developer can set a default value or not. If a efault is unset then the default is nil. As a developer, I often want types to be able to specify required attributes that do not have a default. Currently the only way to do this is in the global validate method which leads to inconsistent messages across modules. Could we get a way to make certain type attributes required? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
