Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-7475 A regex literal for matching backslashes causes a lexer error Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: Language Created: 2017/04/26 6:50 PM Priority: Normal Reporter: Charlie Sharpsteen Attempting to declare a regex literal for matching a single backslash results in a lexer error when the manifest is parsed. Reproduction Case Apply the following manifest which multiplies backslashes within a windows path: $win_path = "c:\\some\\path" $backslash = /\\/
Jira (PDB-3393) PQL: querying structured facts is awkward
Title: Message Title Wyatt Alt commented on PDB-3393 Re: PQL: querying structured facts is awkward Daniel Parks is it fair to call this a dupe of PDB-2634? 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-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-2634
PQL & Hashes: Provide hash projection capability for facts & resource params
Change By:
Wyatt Alt
Alongside PDB-2632, we should provide a mechanism for projection leaf values inside a hash, for example on the new `inventory` and existing `resources` endpoint we have facts, trusted and parameters. The proposal is to use the dotted notation to express this projection in PQL (and some adequate way in AST also). The deliverable here is that this kind of thing should work:{code}inventory[facts.uptime]{ facts.operatingsystem = "foo" }{code}
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-3173) PuppetDB node-purge should allow limiting the number of nodes to delete at one time
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3173 PuppetDB node-purge should allow limiting the number of nodes to delete at one time Change By: Russell Mull Sprint: Hopper 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-7357) acceptance: add tests ensuring JSON prefered over PSON
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-7357 acceptance: add tests ensuring JSON prefered over PSON 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 (FACT-1614) move and update verify fact tests into fact directory
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1614 move and update verify fact tests into fact directory Change By: Maggie Dreyer 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-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols assigned an issue to Eric Delaney Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7357) acceptance: add tests ensuring JSON prefered over PSON
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-7357 acceptance: add tests ensuring JSON prefered over PSON 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-1788) The service type should be able to use a script's default runlevels
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-1788 The service type should be able to use a script's default runlevels Change By: Adam Bottchen Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1788) The service type should be able to use a script's default runlevels
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-1788 The service type should be able to use a script's default runlevels Change By: Adam Bottchen Affects Version/s: PUP 4.9.4 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Geoff Nichols Sprint: Agent Grooming 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 (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Geoff Nichols Story Points: 5 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Geoff Nichols Acceptance Criteria: * If a HTTP request made through the Puppet::Network::HTTP library returns a 503 "Service Unavailable" or 429 "Too Many Requests" response code that includes a Retry-After header, then the agent sleeps for the number of seconds specified in the header and then retry the request. * Should be able to specify a maximum number of retries. 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Geoff Nichols Acceptance Criteria: If a HTTP request made through the Puppet::Network::HTTP library returns a 503 "Service Unavailable" or 429 "Too Many Requests" response code that includes a Retry-After header, then the agent sleeps for the number of seconds specified in the header and then retry the request. 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-7474) PuppetCA should issue certs with Subject Alternative Name containing the CN for compliance with RFC 2818
Title: Message Title Andreas Ntaflos created an issue Puppet / PUP-7474 PuppetCA should issue certs with Subject Alternative Name containing the CN for compliance with RFC 2818 Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Created: 2017/04/26 11:01 AM Priority: Normal Reporter: Andreas Ntaflos Recently Chrome 58 was released and https://www.chromestatus.com/feature/4981025180483584 states the following: RFC 2818 describes two methods to match a domain name against a certificate - using the available names within the subjectAlternativeName extension, or, in the absence of a SAN extension, falling back to the commonName. The fallback to the commonName was deprecated in RFC 2818 (published in 2000), but support still remains in a number of TLS clients, often incorrectly. Unfortunately this means that PuppetCA-issued certificates are considered invalid by Chrome 58, because by default they don't have the subjectAlternativeName extension and therefore don't include the certificate's common name (CN) as a SAN field. The implication is that many (usually internal) services that use PuppetCA-issued certificates as server certificates are now inaccessible with Chrome. Typical examples include Foreman, Puppetboard and other such services. I imagine this is also a problem for PE and its various web interfaces, but we are not PE users so I can't say for sure. In order for PuppetCA
Jira (PUP-7433) Restructure Gemfile to use different group names
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names 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-7433) Restructure Gemfile to use different group names
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Geoff Nichols Acceptance Criteria: See details in description. 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-7433) Restructure Gemfile to use different group names
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Geoff Nichols Sprint: Agent Grooming 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 (PUP-7468) scheduled_task : user attribute not working
Title: Message Title
Lucas Boisserie commented on PUP-7468
Re: scheduled_task : user attribute not working
My agent is in a windows service with System right
I have used the following manifest:
scheduled_task { 'do_backup':
command => 'C:/Program Files/marmot/backup.ps1,
trigger => {
schedule => daily,
start_time => '02:00',
},
user=> 'Administrator',
}
When i had the password, scheduled_task is created with the good user
Why is it not possible to configure the scheduled with an another local user without passing the password, please ? Is it a windows api constraint ?
Jira (PUP-7473) remove dead code in Puppet::Type::instances
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Kurt Wall QA Risk Assessment Reason: Refactor 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-7473) remove dead code in Puppet::Type::instances
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Kurt Wall QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1606) split the external_facts/fact_precedence tests into multiple files
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1606 split the external_facts/fact_precedence tests into multiple files Change By: Kenn Hussey 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-1613) Update regression ticket tests
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1613 Update regression ticket tests Change By: Kenn Hussey 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-1604) clean up facter external facts tests
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1604 clean up facter external facts tests Change By: Kenn Hussey 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-1607) split and update external fact test root_users_default_external_fact_dir
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1607 split and update external fact test root_users_default_external_fact_dir Change By: Kenn Hussey 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-1611) Update external fact stderr tests
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1611 Update external fact stderr tests Change By: Kenn Hussey Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Moses Mendoza Sprint: Agent 2017-05-03 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-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza assigned an issue to Josh Cooper Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Moses Mendoza Assignee: Josh Cooper 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-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Moses Mendoza 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-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza commented on PUP-7473 Re: remove dead code in Puppet::Type::instances found while working on review for PUP-7021 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-7473) remove dead code in Puppet::Type::instances
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7473 remove dead code in Puppet::Type::instances Issue Type: Bug Assignee: Unassigned Created: 2017/04/26 8:51 AM Priority: Normal Reporter: Moses Mendoza This block in Puppet::Type: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type.rb#L1163-L1168 iterates over all of the properties of the type, checks if the given provider supports the property, and returns an array of all the supported property names. Except we don't do anything with the result. Before commit http://github.com/puppetlabs/puppet/commit/53241a91, which was a maint commit to remove superfluous variables we never used, the result of this block was assigned to the variable `all_properties` - which was never used. The commit removed the variable, but not the associated block. I believe the intention was to filter out properties that weren't supported by the provider before we called `newattr` on them, except `newattr` https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type.rb#L769-L773 already does this filtering, and provides helpful debug output that a provider doesn't support a property so we're not managing it. The block can be removed. Add Comment
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title
Florian Klink created an issue
Puppet / PUP-7472
unable to have puppet master listen on both IPv4 and IPv6
Issue Type:
Bug
Affects Versions:
PUP 4.8.2
Assignee:
Unassigned
Created:
2017/04/26 8:36 AM
Priority:
Major
Reporter:
Florian Klink
I'd like have Puppet being dual-stacked, so I did set bindaddress = :: in my puppet.conf, as suggested in "Learning Puppet 4: A Guide to Configuration Management and Automation"/ "IPv6 Dual-Stack Puppet Master" (Page 309 in Google Books), also described here.
This should make the puppet master listen on both IPv4 and IPv6.
When running the puppet master, netstat -anl|grep 8140 shows the following: tcp6 0 0 :::8140 :::* LISTEN
I can connect via IPv6: curl -k 'https://[::]:8140/puppet/v3/' {"message":"Bad Request: The indirection name must be purely alphanumeric, not ''","issue_kind":"RUNTIME_ERROR"}
But connecting via IPv4 fails: curl -k 'https://127.0.0.1:8140/puppet/v3/' curl: (7) Failed to connect to 127.0.0.1 port 8140: Connection refused
So the socket does not seem to be listening under IPv4, contrary to the docs.
Additionally, it's not possible to bind to two different addresses (:: and 0.0.0.0), so it currently simply isn't possible to start puppet listening both on IPv4 and Ipv6.
Jira (HI-570) lookups within hiera data values break %{literal('%')}
Title: Message Title
Michael Shaw created an issue
Hiera / HI-570
lookups within hiera data values break %{literal('%')}
Issue Type:
Bug
Affects Versions:
HI 3.3.0
Assignee:
Unassigned
Components:
CLI, Community, PE
Created:
2017/04/26 8:15 AM
Priority:
Normal
Reporter:
Michael Shaw
consider the hiera data fragment:
— some_text: "% {alias('label_format')}
" label_format: "% {literal('%')}{vpc}_pub%{literal('%')} {az}" — When you lookup the value 'label_format' you correctly obtain the string "%{vpc}_pub%{az}
" as the value. However, if you lookup the value 'some_text' then the result depends on whether % {vpc}
and % {az}
have valid substitutions. Without facts or variables, the current result from the lookup is the string "_pub"
Until this bug is fixed, the utility of the % {literal('%')}
function is limited to being used in values that are only directly requested.
Jira (PDB-3484) Remove duplicate gem for beaker-abs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3484 Remove duplicate gem for beaker-abs Issue Type: Bug Assignee: Unassigned Created: 2017/04/26 7:36 AM Priority: Normal Reporter: gepetto-bot It was there on line 3 and 6 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7471) misleading error message with classname errors
Title: Message Title
David Schmitt created an issue
Puppet / PUP-7471
misleading error message with classname errors
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/04/26 7:06 AM
Priority:
Normal
Reporter:
David Schmitt
$ bundle exec puppet --version
4.10.0
$ bundle exec puppet apply -e "class 'foo' {}" --trace
Error: Could not parse for environment production: 'class' is not a valid classname at line 1:1 on node davids
Jira (PUP-996) Make relationship with empty set in the middle work as expected
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-996 Make relationship with empty set in the middle work as expected Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-3478) Remove extlookup2hiera
Title: Message Title Geoff Nichols commented on PUP-3478 Re: Remove extlookup2hiera PR #5806 was merged to puppet#master at https://github.com/puppetlabs/puppet/commit/88621c548da44acf3b76232286f461aef8c00a42. 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-6250) Remove static compiler terminus
Title: Message Title Geoff Nichols commented on PUP-6250 Re: Remove static compiler terminus PR #5809 was merged to puppet#master at https://github.com/puppetlabs/puppet/commit/1376e9ee17e7135f913dd4bf2f560b2753b55848. 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-7265) Remove file face
Title: Message Title Geoff Nichols commented on PUP-7265 Re: Remove file face PR #5808 was merged to puppet#master at https://github.com/puppetlabs/puppet/commit/944427c3b36019147941b9077eda5c4aca5950ee. 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-3483) Add disable-update-checking parameter
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3483 Add disable-update-checking parameter Issue Type: Bug Assignee: Unassigned Created: 2017/04/26 5:19 AM Priority: Normal Reporter: gepetto-bot This PR adds sort for enabling disable-update-checking. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Henrik Lindberg commented on PUP-6694 Re: The Puppet Data type should be limited to JSON types. Agree to that summary. When discussing this we concluded that in theory there is yet another data type "Serializeable" that is Any, minus Runtime. We concluded that it is an exceptional error case that serialization prevents - it is nothing a puppet developer needs to be concerned about. Thus, the type Any can (and should be used) when the restrictions imposed by Data and RichData are not wanted. 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-7447) Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack)
Title: Message Title Henrik Lindberg commented on PUP-7447 Re: Need prescriptive method for combining 'lookup' with ENCs and the Roles/Profiles pattern (aka, lookup should look up the entire stack) I would rather see that the values / bindings from ENC are mixed into the data hierarchy than wiring the compiler's scopes into the data hierarchy. I understand there are situations where you really want the "effective value of what class foo's parameter bar ended up being set to, irrespective of how it was set" and that you would like that value to be produced by a call to lookup. This because knowing the value that an APL results in for a class parameter is not enough, since the value could have been explicitly set in code, or it could, if there was no binding, and nothing was given be the result of the default value _expression_. There once was such a hiera backend; it allowed lookup in the catalog being produced. This backend was removed because of the many problems/confusing cases users ran into. The function as shown by Thomas above would essentially provide the same feature. Not sure I would want that to be part of Puppet and that we would want to promote the use of that pattern. At the same time the current state of ENC, roles/profiles, and use of APL is far from perfect - and I would really like to see that problem solved. Ping Eric Sorenson and Lindsey Smith. 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-7427) Change rich data in Catalog so that it becomes backward compatible
Title: Message Title Henrik Lindberg commented on PUP-7427 Re: Change rich data in Catalog so that it becomes backward compatible Risk is low, and the change is only for when using the experimental --rich_data support. The change made here enables that feature to function with PDB (as opposed to crashing which makes it very hard to conduct any real experiments). 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-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Thomas Hallgren commented on PUP-6694 Re: The Puppet Data type should be limited to JSON types. Based on Henrik Lindberg's last comment, can we decide on this? The current Data type is limited to what can be expressed in JSON. A new RichData type is introduced. It corresponds to the current Puppet::LookupValue. The Puppet::LookupValue becomes an alias for RichData. Worth noting is that the key of a hash in Data must be a String (JSON doesn't allow numbers as keys) ,whereas the key of RichData will be Variant[Numeric, String] (aliased as Puppet::LookupKey) 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-6242) Semantic::VersionRange does not interpret tilde ranges according to spec.
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6242 Semantic::VersionRange does not interpret tilde ranges according to spec. Change By: Thomas Hallgren Assignee: Jesse Scott 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-7436) regression: epp parameter with default expression = undef does not take
Title: Message Title Thomas Hallgren assigned an issue to qa Puppet / PUP-7436 regression: epp parameter with default _expression_ = undef does not take Change By: Thomas Hallgren Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6373 SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics Change By: Thomas Hallgren Assignee: Jesse Scott 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
