Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Henrik Lindberg commented on PUP-1334 Re: Empty clientbucket files produce errors Ping Kylo Ginsberg and Chris Price - this seems to have a long story, and is not owned by a team. 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-1334) Empty clientbucket files produce errors
Title: Message Title
Stefan Lasiewski commented on PUP-1334
Re: Empty clientbucket files produce errors
This also happens in Puppet 3.8.7 on RHEL6.
Our manifest for this file is pretty simple:
# $datacenter is a custom fact
file { "/etc/resolv.conf":
owner => 'root',
group => 'root',
mode => 0644,
source => [
"puppet:///modules/MODULE/resolv.conf.$datacenter",
'puppet:///modules/MODULE/resolv.conf.default',
]
}
Jira (PUP-6150) Don't include IP address in returned error messages
Title: Message Title Erik Dasher updated an issue Puppet / PUP-6150 Don't include IP address in returned error messages Change By: Erik Dasher QA Risk Assessment Reason: Modification to logging. QA Risk Assessment: Low QA Status: Reviewed QA Contact: Erik Dasher 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-6323) Support tdnf package provider for VMware PhotonOS
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6323 Support tdnf package provider for VMware PhotonOS Change By: Steve Barlow Story Points: 3 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 (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Steve Barlow updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: Planning mess up. Added more or less during planning. 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 (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Steve Barlow updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Steve Barlow Sprint: Client 2016-06-15 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 (FACT-1422) Facter should detect PhotonOS
Title: Message Title Steve Barlow updated an issue Facter / FACT-1422 Facter should detect PhotonOS Change By: Steve Barlow Story Points: 2 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 (FACT-1422) Facter should detect PhotonOS
Title: Message Title Steve Barlow updated an issue Facter / FACT-1422 Facter should detect PhotonOS Change By: Steve Barlow Story Points: 2 3 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 (FACT-1422) Facter should detect PhotonOS
Title: Message Title Steve Barlow updated an issue Facter / FACT-1422 Facter should detect PhotonOS Change By: Steve Barlow Sprint: Client 2016-06-29 (client fail 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-6323) Support tdnf package provider for VMware PhotonOS
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6323 Support tdnf package provider for VMware PhotonOS Change By: Steve Barlow Sprint: Client 2016-06-29 (client fail 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-6376) Add `server_urls` option to puppet and agent failover logic
Title: Message Title William Hopper updated an issue Puppet / PUP-6376 Add `server_urls` option to puppet and agent failover logic Change By: William Hopper Summary: Add `server_urls` option to puppet and agent failover logic 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-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title William Hopper updated an issue Puppet / PUP-6376 Add `server_urls` option to puppet with agent failover logic Change By: William Hopper Summary: Add `server_urls` option to puppet and with agent failover logic 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-6378) Add failover information to the report
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6378 Add failover information to the report Change By: Steve Barlow Sprint: Client 2016-06-29 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-6376) Add `server_urls` option to puppet
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6376 Add `server_urls` option to puppet Change By: Steve Barlow Sprint: Client 2016-06-29 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-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6377 Deprecate the `server` option (if we decide to actually deprecate it) Change By: Steve Barlow Sprint: Client 2016-06-29 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 (PDB-2757) Remove Ubuntu 10.04 LTS Lucid (i386, amd64) from puppetdb pipelines
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols PuppetDB / PDB-2757 Remove Ubuntu 10.04 LTS Lucid (i386, amd64) from puppetdb pipelines Change By: Geoff Nichols Assignee: Geoff Nichols 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 (PDB-2758) Remove Ubuntu 15.10 Wily (i386, amd64) from puppetdb pipelines
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols PuppetDB / PDB-2758 Remove Ubuntu 15.10 Wily (i386, amd64) from puppetdb pipelines Change By: Geoff Nichols Assignee: Geoff Nichols 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-4971) augeas on Windows
Title: Message Title Michael Smith commented on PUP-4971 Re: augeas on Windows I believe the Windows puppet-agent builds may include most of the packages required by augeas, as part of the work to build Ruby. The next step would be investigating building Augeas as part of that project. 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-4971) augeas on Windows
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-4971 augeas on Windows Change By: Michael Smith Assignee: Michael Smith 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-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Steve Barlow Sprint: Client 2015-12-02, Client 2016-05-18, Client 2016-06-01 , Client 2016-06-15 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 (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title Steve Barlow updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: Steve Barlow Sprint: Client 2016-06-01 , Client 2016-06-15 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-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? By command line? A mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for {{ pluginsync }} , report submission, etc.Also, from Kylo: One thing to be careful about with this is making sure it works with and without {{ use_cached_catalog }} . I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need file content? And are we restricted to that master for report submission?Also, if you're running with cached catalogs, do we fail if we can't reach the master we got that catalog from originally? Or do we failover to a different master?
Add Comment
This message was sent by
Jira (PUP-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352: There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline By command line ? a A mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for pluginsync, report submission, etc.Also, from Kylo: One thing to be careful about with this is making sure it works with and without use_cached_catalog. I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need file content? And are we restricted to that master for report submission?Also, if you're running with cached catalogs, do we fail if we can't reach the master we got that catalog from originally? Or do we failover to a different master?
Add Comment
Jira (PUP-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6377
Deprecate the `server` option (if we decide to actually deprecate it)
Change By:
William Hopper
Deprecate the `server` option in favor of the new `server_urls` option. Note that this is still under discussion.We need to consider how this will interact with the `server_urls` option is also specified.We should also consult with UX / CS about the impact this will have. Using {{--server}} seems like a very common workflow and we probably don't want to disrupt it if not completely necessary.If we decide to move forward with the deprecation, a number of puppet acceptance tests will need to be updated, as many use {{--server}} in conjunction with the {{--test}} option currently. See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context and discussion.
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-6378) Add failover information to the report
Title: Message Title William Hopper updated an issue Puppet / PUP-6378 Add failover information to the report Change By: William Hopper The report should specify both whether agent-side failover occurred and if it did, which master was successfully used.From Russ:We're adding a 'producer' key to the report, to be synthesized in the puppetdb terminus, so we can tell if failover happened in a Simple HA setup. But the agent has a much better, more consistent perspective on this; something like 'failover' or 'the master I actually used' or similar could be useful. (See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing) 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-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352:There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline? a mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately. See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context. Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for pluginsync, report submission, etc.Also, from Kylo: One thing to be careful about with this is making sure it works with and without use_cached_catalog. I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need file content? And are we restricted to that master for report submission?Also, if you're running with cached catalogs, do we fail if we can't reach the master we got that catalog from originally? Or do we failover to a different master?
Add Comment
Jira (PUP-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title Henrik Lindberg commented on PUP-6211 Re: Bad behavior of getvar() from stdlib when strict_variables is set to true Some confusion here it seems. The name Undef is the name of the type of the undef value in the puppet type system. In the Ruby runtime undef equates to Ruby nil in future parser / 4.x, and to Ruby Symbol :undef or Ruby value nil in 3.x function return. Returning the String "Undef" or "undef" would not be a good choice. Returning the error String seems to be a completely unintended bug in the implementation of getvar(). 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-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352:There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline? a mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context.Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for pluginsync, report submission, etc.Also, from Kylo: One thing to be careful about with this is making sure it works with and without use_cached_catalog. I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need a new file content? And are we restricted to that master for report submission?Also, if you're running with cached catalogs, do we fail if we can't reach the master we got that catalog from originally ? Or do we failover to a different master?
Add Comment
Jira (PUP-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352:There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline? a mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context.Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for pluginsync, report submission, etc. Also, from Kylo: One thing to be careful about with this is making sure it works with and without use_cached_catalog. I mention this because that setting may change what the first endpoint the agent will hit during a given agent run (and thus the code and the context in which it might failover).When failing over, are we restricted to only using the master which the cached catalog came from if we need a new catalog?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352:There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline? a mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately.See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context. Also to consider: we need to keep track of which server was successfully failed over to so we make sure to hit the correct master for pluginsync, report submission, etc.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You
Jira (PUP-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title Chris Tessmer commented on PUP-6211 Re: Bad behavior of getvar() from stdlib when strict_variables is set to true I'd like to add a +1 to returning Undef instead of the Error String. It could easily end up as the content of a class parameter without detection (unless you start validate_re()-ing your String parameters against '^Warning: Undefined variable', which feels even more wrong). Undef makes much more intuitive sense as a return value when the target variable is not defined (it is literally called "Undef"), even in strict mode. 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-6376) Add `server_urls` option to puppet
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6376
Add `server_urls` option to puppet
Change By:
William Hopper
From the main puppet HA ticket, PUP-6352:There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run.We'll need to add a {{server_urls}} option to puppet which accepts an array. Other considerations include:* Interaction with the old {{server}} option: what happens when both are specified in config? by commandline? a mix?* The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one.* Logging: from [~kylo]: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we want to leave bread crumbs for people debugging funky failovers, and we want those breadcrumbs on by default. The report element will be ticketed separately. See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context.
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
Jira (PUP-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6377
Deprecate the `server` option (if we decide to actually deprecate it)
Change By:
William Hopper
Deprecate the `server` option in favor of the new `server_urls` option. Note that this is still under discussion.We need to consider how this will interact with the `server_urls` option is also specified.We should also consult with UX / CS about the impact this will have. Using {{--server}} seems like a very common workflow and we probably don't want to disrupt it if not completely necessary.If we decide to move forward with the deprecation, a number of puppet acceptance tests will need to be updated, as many use {{--server}} in conjunction with the {{--test}} option currently. See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing for additional context and discussion.
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-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6358 Set strict_variables = true, if strict = error is set Change By: Steve Barlow Sprint: Language 2016-06-15 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-6378) Add failover information to the report
Title: Message Title William Hopper updated an issue Puppet / PUP-6378 Add failover information to the report Change By: William Hopper The report should specify both whether agent-side failover occurred and if it did, which master was successfully used.From Russ:We're adding a 'producer' key to the report, to be synthesized in the puppetdb terminus, so we can tell if failover happened in a Simple HA setup. But the agent has a much better, more consistent perspective on this; something like 'failover' or 'the master I actually used' or similar could be useful. (See https://docs.google.com/a/puppet.com/document/d/11XaOE5lbYTcRx5rG9ic8PNjKerqzcdoF7J_sew0zgiI/edit?usp=sharing) 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-6354) Enum entries are not unique.
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6354 Enum entries are not unique. Change By: Steve Barlow Sprint: Language 2016-06-15 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 (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Steve Barlow Sprint: Language 2016-06-01, Language 2016-06- 15 29 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 (NPUP-44) Review the Puppet 4.0 checker and port requisite logic to validate native ASTs
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-44 Review the Puppet 4.0 checker and port requisite logic to validate native ASTs Change By: Steve Barlow Sprint: Language 2016-06- 15 29 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-6378) Add failover information to the report
Title: Message Title William Hopper updated an issue Puppet / PUP-6378 Add failover information to the report Change By: William Hopper The report should specify both whether agent-side failover occurred and if it did, which master was successfully used. From Russ:We're adding a 'producer' key to the report, to be synthesized in the puppetdb terminus, so we can tell if failover happened in a Simple HA setup. But the agent has a much better, more consistent perspective on this; something like 'failover' or 'the master I actually used' or similar could be useful. 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-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6377
Deprecate the `server` option (if we decide to actually deprecate it)
Change By:
William Hopper
Deprecate the `server` option in favor of the new `server_urls` option. Note that this is still under discussion.We need to consider how this will interact with the `server_urls` option is also specified.We should also consult with UX / CS about the impact this will have. Using {{--server}} seems like a very common workflow and we may not probably don't want to disrupt it if not completely necessary.If we decide to move forward with the deprecation, a number of puppet acceptance tests will need to be updated, as many use {{--server}} in conjunction with the {{--test}} option currently.
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-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title William Hopper updated an issue Puppet / PUP-6377 Deprecate the `server` option (if we decide to actually deprecate it) Change By: William Hopper Summary: Deprecate the `server` option (if we decide to actually deprecate it) 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-6377) Deprecate the `server` option
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6377
Deprecate the `server` option
Change By:
William Hopper
Deprecate the `server` option in favor of the new `server_urls` option. Note that this is still under discussion.We need to consider how this will interact with the `server_urls` option is also specified. We should also consult with UX / CS about the impact this will have. Using {{--server}} seems like a very common workflow and we may not want to disrupt it if not completely necessary.If we decide to move forward with the deprecation, a number of puppet acceptance tests will need to be updated, as many use {{--server}} in conjunction with the {{--test}} option currently.
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-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6312 Load XPP instead of .pp if present and feature flag is on Change By: Steve Barlow Sprint: Language 2016-06- 15 29 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-6378) Add failover information to the report
Title: Message Title William Hopper updated an issue Puppet / PUP-6378 Add failover information to the report Change By: William Hopper Labels: ha-dep 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-6378) Add failover information to the report
Title: Message Title William Hopper created an issue Puppet / PUP-6378 Add failover information to the report Issue Type: Task Assignee: Unassigned Created: 2016/06/01 1:47 PM Fix Versions: PUP 4.6.0 Priority: Normal Reporter: William Hopper The report should specify both whether agent-side failover occurred and if it did, which master was successfully used. Add Comment This message was sent by
Jira (PUP-6376) Add `server_urls` option to puppet
Title: Message Title William Hopper updated an issue Puppet / PUP-6376 Add `server_urls` option to puppet Change By: William Hopper Labels: ha-dep 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-6377) Deprecate the `server` option
Title: Message Title William Hopper updated an issue Puppet / PUP-6377 Deprecate the `server` option Change By: William Hopper Labels: ha-dep 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-6377) Deprecate the `server` option
Title: Message Title William Hopper created an issue Puppet / PUP-6377 Deprecate the `server` option Issue Type: Task Assignee: Unassigned Created: 2016/06/01 1:44 PM Fix Versions: PUP 4.6.0 Priority: Normal Reporter: William Hopper Deprecate the `server` option in favor of the new `server_urls` option. Note that this is still under discussion. We need to consider how this will interact with the `server_urls` option is also specified. Add Comment
Jira (PUP-6376) Add `server_urls` option to puppet
Title: Message Title William Hopper created an issue Puppet / PUP-6376 Add `server_urls` option to puppet Issue Type: New Feature Assignee: Unassigned Created: 2016/06/01 1:40 PM Fix Versions: PUP 4.6.0 Priority: Normal Reporter: William Hopper From the main puppet HA ticket, PUP-6352: There will be a new capability to provide a list of hosts the agent should try to contact when initiating a run. The agent will always go down the list, in order, until it finds a master it can contact. It will use that master for the remainder of the run and stop that run if that master ceases to be available during the run. We'll need to add a server_urls option to puppet which accepts an array. Other considerations include: Interaction with the old server option: what happens when both are specified in config? by commandline? a mix? The actual failover logic - catching a failed attempt contact a master and rolling off onto the next one. Logging: from Kylo Ginsberg: I'd suggest a notice-level message for any decision point in the failover logic. It'll be easier to reason about this when we have the failover code in front of us, but I'm thinking we
Jira (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Steve Barlow updated an issue Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Steve Barlow Flagged: Impediment 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 (PDB-2760) (maint) Verify hostnames with OpenSSL
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2760 (maint) Verify hostnames with OpenSSL Issue Type: Bug Assignee: Unassigned Created: 2016/06/01 1:39 PM Priority: Normal Reporter: gepetto-bot This commit adds the openssl-verify dependency to the puppetdb-cli which adds support for verifying hostnames when connecting to PuppetDB over HTTPS. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6240) Deprecate old semantic version implementation
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6240 Deprecate old semantic version implementation Change By: Steve Barlow Sprint: Language 2016-06-01, Language 2016-06- 15 29 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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Steve Barlow updated an issue Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Steve Barlow Sprint: Language 2016-06-01, Language 2016-06- 15 29 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 (NPUP-47) Implement proper support for Unicode strings
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-47 Implement proper support for Unicode strings Change By: Peter Huene Story Points: 5 3 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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Eric Sorenson updated an issue Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs I ran strings against the lib/puppet/functions/ directory and got a spray of errors. It did produce docs but they are garbled and not many strings are rendered, see attached screenshot. I've included a tar.gz of the generated directory in case that helps anyone. Change By: Eric Sorenson Attachment: Screenshot 2016-06-01 13.19.31.png Attachment: puppet-strings-functions-4.5.0.tar.gz 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
Jira (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-6279) Cannot call type() function using postfix notation e.g 1.type()
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6279 Cannot call type() function using postfix notation e.g 1.type() Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-6220) Add TypeSet type to the Puppet Type System
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6220 Add TypeSet type to the Puppet Type System Change By: Steve Barlow Sprint: Language 2016-05-04, Language 2016-06-01 , Language 2016-06-15 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 (NPUP-7) Do not allow expressions with side effects in parameter default values
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-7 Do not allow expressions with side effects in parameter default values Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-6311) Define where XPP files should be written, and how resolution works
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6311 Define where XPP files should be written, and how resolution works Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Steve Barlow updated an issue Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-6240) Deprecate old semantic version implementation
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6240 Deprecate old semantic version implementation Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-4904) puppet describe -s ssh_authorized_key output is really bad
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4904 puppet describe -s ssh_authorized_key output is really bad Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Steve Barlow Sprint: Language 2016-06-01 , Language 2016-06-15 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 (FACT-1409) Facter should continue without locales instead of aborting if they are unavailable
Title: Message Title Stan Duffy commented on FACT-1409 Re: Facter should continue without locales instead of aborting if they are unavailable Verified against the tagged 1.5.1. build 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 (NPUP-10) Implement automatic String to Numeric conversion for arithmetic operators.
Title: Message Title Eric Thompson updated an issue Native Puppet / NPUP-10 Implement automatic String to Numeric conversion for arithmetic operators. Change By: Eric Thompson Release Notes: Not Needed 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 (NPUP-47) Implement proper support for Unicode strings
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-47 Implement proper support for Unicode strings Issue Type: Bug Assignee: Peter Huene Created: 2016/06/01 12:54 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Currently Unicode is, at best, somewhat supported in the Puppet language for strings. See here for a write-up about the issue. The fix is to implement a UTF-8 string type that internally uses ICU to handle Unicode graphemes. Add Comment
Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6361 Validate and error if a class or define is given a name starting with :: Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6312 Load XPP instead of .pp if present and feature flag is on Change By: Henrik Lindberg Fix Version/s: PUP 4.6.0 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-6310) Specify the PCore Serialization formats
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6310 Specify the PCore Serialization formats Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-6255) Add documentation for Object.new in function new
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6255 Add documentation for Object.new in function new Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-6252) reorganize documentation of function 'new'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6252 reorganize documentation of function 'new' Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-6083) Use --strict option to deprecate Class[] where begins with a capital letter.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6083 Use --strict option to deprecate Class[] where begins with a capital letter. Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3170 Cap integer and float sizes Change By: Henrik Lindberg Sprint: Language 2016-06- 15 29 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-5831) Add a Binary type and runtime object
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5831 Add a Binary type and runtime object Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (NPUP-10) Implement automatic String to Numeric conversion for arithmetic operators.
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-10 Implement automatic String to Numeric conversion for arithmetic operators. Change By: Henrik Lindberg Status: Ready for CI Test Assignee: Peter Huene qa 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 (NPUP-44) Review the Puppet 4.0 checker and port requisite logic to validate native ASTs
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-44 Review the Puppet 4.0 checker and port requisite logic to validate native ASTs Change By: Peter Huene Sprint: Language Triage 2016-06-15 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 (PDB-2759) (MAINT) Add .DS_Store to .gitignore
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2759 (MAINT) Add .DS_Store to .gitignore Issue Type: Bug Assignee: Unassigned Created: 2016/06/01 11:50 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-6150) Don't include IP address in returned error messages
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6150 Don't include IP address in returned error messages Change By: Archana Sridhar Sprint: Server Emerald 2016-06- 29 15 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-6150) Don't include IP address in returned error messages
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6150 Don't include IP address in returned error messages Change By: Archana Sridhar Sprint: Server Emerald 2016-06- 15 29 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-6375) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte created an issue Puppet / PUP-6375 Triage acceptance failures on zlinux (s390x) sles-11 Issue Type: Task Assignee: John Duarte Created: 2016/06/01 10:42 AM Priority: Normal Reporter: John Duarte The following puppet acceptance tests unexpectedly fail on sles-11 instance on zlinux s390x using puppet-agent at SHA 3af62f5c: tests/resource/service/service_enable_linux.rb tests/environment/agent_runs_pluginsync_with_proper_environment.rb tests/environment/use_enc_environment_for_files.rb tests/environment/use_enc_environment_for_pluginsync.rb tests/ssl/autosign_command.rb tests/resource/service/ticket_5024_systemd_enabling_masked_service.rb The errors are reported as follows
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title Bill Niestempski updated an issue Puppet / PUP-1796 File resource fails for root(/) directory. Change By: Bill Niestempski CS Priority: Needs Priority 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-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6188 Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Change By: Steve Barlow Sprint: Windows 2016-06- 15 29 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-3768) scheduled_task keeps reapplying
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: Steve Barlow Sprint: Windows 2016-06- 15 29 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-6374) Minitar - add public method to retrieve entries
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6374 Minitar - add public method to retrieve entries Change By: Steve Barlow Sprint: Windows 2016-06- 15 29 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 (PDB-2657) Untangle the use of facter from the 2.3.x build tasks
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-2657 Untangle the use of facter from the 2.3.x build tasks Change By: Kenn Hussey Sprint: RE Services 2016-06- 08 15 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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Archana Sridhar Sprint: Server Jade 2016-05-18, Server Jade 2016-06-01, Server Jade 2016-06- 29 15 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-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` face Change By: Archana Sridhar Sprint: Server Jade 2016-06-01, Server Jade 2016-06- 29 15 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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Karen Van der Veer Sprint: Server Jade 2016-05-18, Server Jade 2016-06-01 , Server Jade 2016-06-29 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-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` face Change By: Karen Van der Veer Sprint: Server Jade 2016-06-01 , Server Jade 2016-06-29 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-3827) Errors from indirected routes don't match error schema
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Archana Sridhar Sprint: Server Jade 2016-04-20, Server Jade 2016-05-04, Server Jade 2016-05-18, Server Jade 2016-06- 15 29 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-6295) Include agent catalog information (edges, original parameters for example) within a report
Title: Message Title Steve Quin updated an issue Puppet / PUP-6295 Include agent catalog information (edges, original parameters for example) within a report Change By: Steve Quin Sprint: CR 2016-05-18, CR 2016-06-01 , CR 2016-06-15 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 (PDB-2688) implement historical resource storage solution
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-2688 implement historical resource storage solution Change By: Steve Quin Sprint: CR 2016-05-18, CR 2016-06-01 , CR 2016-06-15 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 (PDB-2655) Create storage refactor design doc
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-2655 Create storage refactor design doc Change By: Steve Quin Sprint: CR 2016-05-18, CR 2016-06-01 , CR 2016-06-15 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 (PDB-2693) Change Reporting: Design API for reporting an event change reason/cause/remediation value
Title: Message Title Steve Quin updated an issue PuppetDB / PDB-2693 Change Reporting: Design API for reporting an event change reason/cause/remediation value Change By: Steve Quin Sprint: CR 2016-05-18, CR 2016-06-01 , CR 2016-06-15 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-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title Trevor Vaughan commented on PUP-6211 Re: Bad behavior of getvar() from stdlib when strict_variables is set to true I thought about that, but the current behavior of getvar() is: If variable defined => Return Variable If variable not defined => Return the Error String This is 100% broken and my expectation (and apparently the one of OP) is that the following would be true: If variable defined => Return Variable If variable not defined => Return Undef Then, everyone (on this thread) is happy and getvar() makes sense from regular Ruby semantics of "return me a good value or 'nil'". 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 (PDB-1345) Move PuppetDB unit tests to Jenkins for PRs
Title: Message Title Susan McNerney commented on PDB-1345 Re: Move PuppetDB unit tests to Jenkins for PRs Waiting on hardware from QEng. Need to recheck with Qeng team. 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.
