Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section

2017-08-29 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-4755 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet config set --section main foo bar does not set or respect an empty [main] section  
 
 
 
 
 
 
 
 
 
 
Considering it already has a PR up, probably. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section

2017-08-29 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer commented on  PUP-4755 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet config set --section main foo bar does not set or respect an empty [main] section  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer Is this small enough for the 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 (HI-579) Begin hardcoding hiera version into gemspec

2017-08-29 Thread Past Haus (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Past Haus created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-579 
 
 
 
  Begin hardcoding hiera version into gemspec  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/29 3:49 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Past Haus 
 
 
 
 
 
 
 
 
 
 
In https://github.com/puppetlabs/r10k/issues/760, users noticed warnings indicating stack too deep when using r10k with puppet-agent and having more than one version of a dependency of r10k installed. As noted in https://github.com/puppetlabs/r10k/issues/760#issuecomment-325825267, it is because of how rubygems behaves when doing version selection, and also because of how the version of the hiera and puppet gems are declared in their gemspecs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256f

Jira (PUP-7889) Begin hardcoding puppet version into gemspec

2017-08-29 Thread Past Haus (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Past Haus created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7889 
 
 
 
  Begin hardcoding puppet version into gemspec  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/29 3:49 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Past Haus 
 
 
 
 
 
 
 
 
 
 
In https://github.com/puppetlabs/r10k/issues/760, users noticed warnings indicating stack too deep when using r10k with puppet-agent and having more than one version of a dependency of r10k installed. As noted in https://github.com/puppetlabs/r10k/issues/760#issuecomment-325825267, it is because of how rubygems behaves when doing version selection, and also because of how the version of the hiera and puppet gems are declared in their gemspecs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae

Jira (PUP-7882) lookup() function: set a kind of default value which is merged

2017-08-29 Thread Francois Lafont (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francois Lafont commented on  PUP-7882 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: lookup() function: set a kind of default value which is merged  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg, it's probably possible to do the transformation via a function (for instance) but it seems to me not so easy in the case of a deep merging for instance (in fact the case of the deep merge seems to me very complex, am I wrong?). Furthermore, it seems to me quiet relevant to use directly the code of the lookup() function, to match exactly with the merge policy of the current parameter. 
The possibility to use a kind of default_merged_value option in lookup seems to me very convenient, even if, from my point of view, it should be an option to use... sparingly (in fact, the only case I see is the case I have tried to explain in my previous messages). 
That being said, maybe I'm wrong. As I said, feel free to close the ticket if you think it's not a good idea.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-775) Facter changes name of VLAN interface (name with dot)

2017-08-29 Thread Peter Meier (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter changes name of VLAN interface (name with dot)  
 
 
 
 
 
 
 
 
 
 
I can definitely confirm this bug, also in the latest release: 
Here is a node with multiple vlans on an interface and it is broken. This used to be fine in facter-2.4.6-1.el7.x86_64. 
 
 
 
 
 
 
# ip a show dev enp1s0.10 
 
 
 
 
6: enp1s0.10@enp1s0:  mtu 1500 qdisc noqueue state UP qlen 1000 
 
 
 
 
link/ether 00:0d:de:ad:be:ef brd ff:ff:ff:ff:ff:ff 
 
 
 
 
inet 10.12.34.1/24 brd 10.12.34.255 scope global enp1s0.10 
 
 
 
 
   valid_lft forever preferred_lft forever 
 
 
 
 
facter -p --show-legacy | grep -E '(enp1s0.10|operatingsystem|facterversion)' 
 
 
 
 
facterversion => 3.8.0 
 
 
 
 
interfaces => enp1s0,enp1s0.10,enp1s0.958,enp2s0,enp3s0,lo 
 
 
 
 
ipaddress6_enp1s0.10 => 10.12.34.1 
 
 
 
 
   

Jira (PUP-7888) Pluginsync modules with deep directories fail on Windows

2017-08-29 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7888 
 
 
 
  Pluginsync modules with deep directories fail on Windows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 5.1.0, PUP 4.7.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2017/08/29 2:17 PM 
 
 
 

Environment:
 
 
Node: Windows 2012R2 Master: Using 2016.4.2 but it is not master dependant Puppet 4.7.1 but will affect Puppet 5.1.0 too 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
After updating the Windows DSC module with the latest resources, the acceptance tests were failing setup due to plugin cache failing to synchronise files with deep directories 
 
 
 
 
 
 
$ puppet agent -t --trace 
   

Jira (FACT-1742) Add a new "hypervisors" fact using (optional) libwhereami

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1742 
 
 
 
  Add a new "hypervisors" fact using (optional) libwhereami  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Casey Williams 
 
 
 

Created:
 

 2017/08/29 2:13 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Casey Williams 
 
 
 
 
 
 
 
 
 
 
We'd like to start integrating libwhereami into facter as a source of hypervisor information. Add a new hypervisors fact that reports hypervisors detected by libwhereami and their metadata. The whereami dependency should be optional. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
  

Jira (PDB-3647) (maint) Update to ezbake 1.1.11

2017-08-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3647 
 
 
 
  (maint) Update to ezbake 1.1.11  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/29 12:04 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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/opto

Jira (FACT-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1741 
 
 
 
  Ensure facts are reported correctly on EL 7 (AArch64)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 * Platform has been added to case switch statement in Facter tests.* Facter tests are passing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2017-08-29 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1741 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure facts are reported correctly on EL 7 (AArch64)  
 
 
 
 
 
 
 
 
 
 
On x86, the processor fact looks something like this: 
 
 
 
 
 
 
{ 
 
 
 
 
  count => 4, 
 
 
 
 
  isa => "x86_64", 
 
 
 
 
  models => [ 
 
 
 
 
"Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz", 
 
 
 
 
"Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz", 
 
 
 
 
"Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz", 
 
 
 
 
"Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz" 
 
 
 
 
  ], 
 
 
 
 
  physicalcount => 1, 
 
 
 
 
  speed => "3.50 GHz" 
  

Jira (FACT-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1741 
 
 
 
  Ensure facts are reported correctly on EL 7 (AArch64)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Platform OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1741 
 
 
 
  Ensure facts are reported correctly on EL 7 (AArch64)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Summary:
 
 Ensure facts are reported correctly on EL 7 ( Aarch64 AArch64 ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1741) Ensure facts are reported correctly on EL 7 (Aarch64)

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1741 
 
 
 
  Ensure facts are reported correctly on EL 7 (Aarch64)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/29 11:21 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Nichols 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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:

Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1642 
 
 
 
  facter should understand cpu model on Power for the processors.model fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

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 (FACT-1642) facter should understand cpu model on Power for the processors.model fact

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1642 
 
 
 
  facter should understand cpu model on Power for the processors.model fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Platform OS  Grooming  2017-09-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1642) facter should understand cpu model on Power for the processors.model fact

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1642 
 
 
 
  facter should understand cpu model on Power for the processors.model fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 The 'processors.model' fact is correct on Power. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7846) I18N LANG setting not honored when running puppet on redhat 7.3 on power8

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7846 
 
 
 
  I18N LANG setting not honored when running puppet on redhat 7.3 on power8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7846) I18N LANG setting not honored when running puppet on redhat 7.3 on power8

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7846 
 
 
 
  I18N LANG setting not honored when running puppet on redhat 7.3 on power8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 Translations work on EL7 Power builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7842) language for SLES 11.3 service not being set correctly during boot

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7842 
 
 
 
  language for SLES 11.3 service not being set correctly during boot  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 Puppet uses configured language when puppet service is started at system boot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7842) language for SLES 11.3 service not being set correctly during boot

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7842 
 
 
 
  language for SLES 11.3 service not being set correctly during boot  
 
 
 
 
 
 
 
 
 

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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7887 
 
 
 
  Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 The current Cisco testing pipeline requires frequent manual reconfiguration because :- There's no passed parameter that controls what branch and SHA in [cisco-network-puppet-module] we want to run from.- We frequently jump back and forth between puppet agent version 5.0.x and 1.10.x.I want to add the following ENV variables/parameters to the Cisco pipeline :- cisco-network-puppet-module branch- cisco-network-puppet-module SHA (default HEAD)- cisco-network-node-utils branch (defaults to the branch name of cisco-network-puppet-module)- cisco-network-node-utils SHA (default HEAD) Scope of this ticket includes the JJB work needed to add these parameters, and some presuite work needed to take the cisco-network-node-utils branch and SHA, build the gem and load it to puppet master and switch under test. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7887 
 
 
 
  Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 The current Cisco testing pipeline requires frequent manual reconfiguration because :- There's no passed parameter that controls what branch and SHA in [cisco-network-puppet-module] we want to run from.- We frequently jump back and forth between puppet agent version 5.0.x and 1.10.x.I want to  have  add  the  following ENV variables/parameters to the  Cisco pipeline  reconfigured so that  :-  We can pass a parameter that controls what branch  cisco-network-puppet-module  builds from  branch -  We have two cells / configurations, one based on  cisco-network-  puppet  agent 5.0.x, one on 1.10.x. -module SHA (default HEAD)  Sometimes we need - cisco-network-node-utils branch (defaults  to  pick  the branch  and sha  name  of  cisco_node_utils.  cisco-network-puppet-module)    - cisco-network-node-utils SHA (default HEAD) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7887 
 
 
 
  Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 The current Cisco testing pipeline requires frequent manual reconfiguration because :- There's no passed parameter that controls what branch  and SHA  in [cisco-network-puppet-module] we want to run from.- We frequently jump back and forth between puppet agent version 5.0.x and 1.10.x.I want to have the Cisco pipeline reconfigured so that :- We can pass a parameter that controls what branch  [ cisco-network-puppet-module ]  builds from- We have two cells / configurations, one based on puppet agent 5.0.x, one on 1.10.x.Sometimes we need to pick the branch and sha of cisco_node_utils.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7887 
 
 
 
  Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 The current Cisco testing pipeline requires frequent manual reconfiguration because :- There's no passed parameter that controls what branch in  [  cisco-network-puppet-module ]  we want to run from.- We frequently jump back and forth between puppet agent version 5.0.x and 1.10.x.I want to have the Cisco pipeline reconfigured so that :- We can pass a parameter that controls what branch  [  cisco-network-puppet-module ]  builds from- We have two cells / configurations, one based on puppet agent 5.0.x, one on 1.10.x.Sometimes we need to pick the branch and sha of cisco_node_utils.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher commented on  PUP-7887 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 
 
I moved this from the CISCO project to the PUP project because it's an issue internal to puppet, and because the work will be done by the Platform OS team. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7887) Cisco Pipeline Reorg

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7887 
 
 
 
  Cisco Pipeline Reorg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

Team:
 
 Platform OS 
 
 
 

Workflow:
 
 Puppet Supported Program Scrum Team  Workflow 
 
 
 

Key:
 
 CISCO PUP - 57 7887 
 
 
 

Project:
 
 Cisco Network Devices Puppet 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1658) Add support for rhev virtualization detection

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1658 
 
 
 
  Add support for rhev virtualization detection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Casey Williams 
 
 
 

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 (FACT-1669) Add support for zlinux virtualization detection

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1669 
 
 
 
  Add support for zlinux virtualization detection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Casey Williams 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1659) Add support for ovirt virtualization detection

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1659 
 
 
 
  Add support for ovirt virtualization detection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Casey Williams 
 
 
 

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 (FACT-1662) Add support for vserver virtualization detection

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1662 
 
 
 
  Add support for vserver virtualization detection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Casey Williams 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1657) Add support for bochs virtualization detection

2017-08-29 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1657 
 
 
 
  Add support for bochs virtualization detection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Casey Williams 
 
 
 

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-7886) Several AAA and TACACS failures in Cisco pipeline

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher assigned an issue to Erik Dasher 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7886 
 
 
 
  Several AAA and TACACS failures in Cisco pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

Assignee:
 
 Erik Dasher 
 
 
 

Team:
 
 Platform OS 
 
 
 

Method Found:
 
 Needs Assessment Automated Test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7886) Several AAA and TACACS failures in Cisco pipeline

2017-08-29 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7886 
 
 
 
  Several AAA and TACACS failures in Cisco pipeline  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/29 10:24 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 
During the investigation around CISCO-56, I found several tacacs and AAA test failures in both 5.1.x and 1.10.x. We need to resolve these issues to get to green. 
FAILED: tests/beaker_tests/cisco_tacacs_server/tacacsserver_provider_negatives.rb ERRORED: 01 tests/beaker_tests/cisco_aaa_group_tacacs/test_aaa_group_tacacs.rb  02 tests/beaker_tests/cisco_aaa_login_cfg_svc/test_aaalogincfgsvc_nondefaults.rb 03 tests/beaker_tests/cisco_aaa_login_exec_svc/test_aaaloginexecsvc_nondefaults.rb 04 tests/beaker_tests/cisco_hsrp/test_interface_hsrp_group.rb 05 tests/beaker_tests/cisco_object_group/test_object_group.rb 06 tests/beaker_tests/cisco_tacacs_server/tacacsserver_provider_defaults.rb 07 tests/beaker_tests/cisco_tacacs_server/tacacsserver_provider_nondefaults.rb 08 tests/beaker_tests/cisco_tacacs_server_host/tacacsserverhost_provider_defaults.rb 09 tests/beaker_tests/cisco_tacacs_server_host/tacacsserverhost_provider_nondefaults.rb 10 tests/beaker_tests/file_service_package/test_package.rb 11 tests/beaker_tests/tacacs/tacacs_provider_defaults.rb 12 tests/beaker_tests/tacacs_global/tacacs_global_provider_defaults.rb 13 tests/beaker_tests/tacacs_server/tacacs_server_provider_defaults.rb  14 tests/beaker_tests/tacacs_server_group/tacacs_server_group_provider_defaults.rb 
 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (FACT-1720) regression on overidding external facts (shell)

2017-08-29 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  FACT-1720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regression on overidding external facts (shell)  
 
 
 
 
 
 
 
 
 
 
FYI Branan Riley: I put up a PR for an acceptance test that verifies this behavior associated with this ticket that you can use to test the implementation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1720) regression on overidding external facts (shell)

2017-08-29 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regression on overidding external facts (shell)  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2017-08-29 10:00:01.793854 DEBUG puppetlabs.facter - resolving facts from executable file "/home/branan/proj/pl/facter/build/external/test_fact.sh". 
 
 
 
 
2017-08-29 10:00:01.793933 DEBUG leatherman.execution:92 - executing command: /home/branan/proj/pl/facter/build/external/test_fact.sh 
 
 
 
 
2017-08-29 10:00:01.795439 DEBUG | - test_fact=foo 
 
 
 
 
2017-08-29 10:00:01.795705 DEBUG leatherman.execution:556 - process exited with status code 0. 
 
 
 
 
2017-08-29 10:00:01.796266 DEBUG puppetlabs.facter - fact "test_fact" has resolved to "foo". 
 
 
 
 
2017-08-29 10:00:01.796452 DEBUG puppetlabs.facter - completed resolving facts from executable file "/home/branan/proj/pl/facter/build/external/test_fact.sh". 
 
 
 
 
2017-08-29 10:00:01.796608 DEBUG puppetlabs.facter - setting fact "test_fact" based on the value of environment variable "FACTER_test_fact". 
 
 
 
 
2017-08-29 10:00:01.796810 DEBUG puppetlabs.facter - fact "test_fact" has changed from "foo" to "bar". 
 
 
 
 
foo
 
 
  

Jira (PUP-7882) lookup() function: set a kind of default value which is merged

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7882 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: lookup() function: set a kind of default value which is merged  
 
 
 
 
 
 
 
 
 
 
I don't understand why this has to be an option to the lookup function. Since you have to call lookup explicitly you can just as well do the transformation you require (say as a function). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7163) regression - systemd provider does not honor documented enabled states

2017-08-29 Thread R S (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R S commented on  PUP-7163 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regression - systemd provider does not honor documented enabled states  
 
 
 
 
 
 
 
 
 
 
For what it's worth, after some considerable effort toward this problem in the context of the Ansible project, I've filed a bug with the systemd project asking them for better stdout return values for systemctl is-enabled, better accounting for Units that have an Also= line in their 'Install' section. 
As far as I can tell, it is (currently) impossible by command line to accurately determine the state of Units (and all Units alongside, indicated with Also=) using systemctl is-enabled, such that executing systemctl (dis|en)able will product a predictable result. The bug I've filed: https://github.com/systemd/systemd/issues/6681 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1720) regression on overidding external facts (shell)

2017-08-29 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regression on overidding external facts (shell)  
 
 
 
 
 
 
 
 
 
 
Ugh, yup. I think I tested my change with a custom fact. Digging into this now 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1740) Facter tests failing on AIX 6.1 with size_bytes from facter to be positive for /aha. 01:53:35 Expected -512 to be >= 0.>

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols commented on  FACT-1740 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter tests failing on AIX 6.1 with size_bytes from facter to be positive for /aha. 01:53:35 Expected -512 to be >= 0.>  
 
 
 
 
 
 
 
 
 
 
Merged to facter#3.6.x at https://github.com/puppetlabs/facter/commit/406d8f874cfeb3d03880277a8f2c827ebb2cf0f9. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-08-29 Thread Verne Lindner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Verne Lindner commented on  PUP-7779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 
 
+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-4039) package resource doesn't find new packages in yum repo

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4039 
 
 
 
  package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Client 2016-05-04, Platform OS  Grooming  Community 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1526) Package type should support environment variables

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1526 
 
 
 
  Package type should support environment variables  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Platform OS  Grooming  Community 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1737) Disks & partitions for FreeBSD

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1737 
 
 
 
  Disks & partitions for FreeBSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Platform OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1737) Disks & partitions for FreeBSD

2017-08-29 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1737 
 
 
 
  Disks & partitions for FreeBSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Platform OS Community 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7517) Add logic for restarting hung catalog application

2017-08-29 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7517 
 
 
 
  Add logic for restarting hung catalog application  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Fix Version/s:
 
 PUP 4.10.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators

2017-08-29 Thread Jarret Lavallee (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jarret Lavallee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6729 
 
 
 
  NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jarret Lavallee 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators

2017-08-29 Thread Chris Denneen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Denneen commented on  PUP-6729 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators  
 
 
 
 
 
 
 
 
 
 
Definitely running into same issue when running via Services, Orchestrator, or even via Cloudformation steps the ACL get's too restrictive that logging in as local Administrator doesn't have permissions to apply/agent run properly.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7885) Enum accepts arguments that are not strings

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7885 
 
 
 
  Enum accepts arguments that are not strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 It was in some circumstances possible to create an illegal specification of an Enum data type by giving in numeric entries instead of string entries - for example {{Enum\[blue, 42]}}. This illegal Enum type would then either cause an error when attempting to use it, or would have undefined matching behavior. This is now corrected so that an error is raised where this illegal specification was earlier accepted. 
 
 
 

Team:
 
 Platform Core 
 
 
 

Sprint:
 
 Platform Core 2017-09-05 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 

Jira (PUP-7885) Enum accepts arguments that are not strings

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7885 
 
 
 
  Enum accepts arguments that are not strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 5.2.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 (FACT-1732) Facter core dump on large integers

2017-08-29 Thread Trevor Vaughan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Trevor Vaughan commented on  FACT-1732 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter core dump on large integers  
 
 
 
 
 
 
 
 
 
 
Branan Riley I get not wanting to handle bignum values, but you don't really get to pick what people stuff into Facter facts and if you start talking about things over 4 Petabytes in Bytes, you're going to have a bad time since Ruby's max Fixnum on a 64 bit infrastructure is 2**62 - 1. This is not unreasonable on large systems even with the native facts. 
You might just want to bring in libgmp and call it a day. Alternatively, I guess you could treat them all as strings and mark them with something that says to translate to Integer (or whatever) before you shove it over the wire. Not precise, and more work, but 100% safe. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7848) Capitals in variable names in EPP templates hang threads forever

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7848 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Capitals in variable names in EPP templates hang threads forever  
 
 
 
 
 
 
 
 
 
 
If we had a green CI status the last 5 days, yes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6764) Add PO files with translated strings to Puppet repo

2017-08-29 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6764 
 
 
 
  Add PO files with translated strings to Puppet repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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-7880) When logging mixed encoding strings, Puppet may fail

2017-08-29 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7880 
 
 
 
  When logging mixed encoding strings, Puppet may fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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-7858) `puppet help` output contains untranslated subcommand summaries

2017-08-29 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7858 
 
 
 
  `puppet help` output contains untranslated subcommand summaries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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 (PDB-3646) PDB 5.1 Release

2017-08-29 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3646 
 
 
 
  PDB 5.1 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 Data Platform 2017-09-06 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3641) Package GC does not seem to occur

2017-08-29 Thread Mike Eller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Eller commented on  PDB-3641 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package GC does not seem to occur  
 
 
 
 
 
 
 
 
 
 
Verified that this in now working  
 
 
 
 
 
 
2017-08-29 14:42:20,571 INFO  [p.p.c.services] Starting gc packages 
 
 
 
 
2017-08-29 14:42:20,575 INFO  [p.p.c.services] Finished gc packages 
 
 
 
 
 
 
FYI - doc ticket raised: https://tickets.puppetlabs.com/browse/DOCUMENT-714 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7878) Change in Puppet type management breaks defined class checks

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7878 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change in Puppet type management breaks defined class checks  
 
 
 
 
 
 
 
 
 
 
Geoff Nichols Not sure if there is anything anyone needs to do here - see the post just before this though as we may have a packaging problem that needs to be looked at / understood (if it is a real problem). Please close as "cannot reproduce" if you think that is fine too. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7818) AIX provider prefetch will fail if any package does not have a source

2017-08-29 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-7818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: AIX provider prefetch will fail if any package does not have a source  
 
 
 
 
 
 
 
 
 
 
Branan Riley please add release notes for this issue, if 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-7848) Capitals in variable names in EPP templates hang threads forever

2017-08-29 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-7848 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Capitals in variable names in EPP templates hang threads forever  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg from the GitHub history it looks like this was already merged to master. So, have the changes made it through CI yet? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7885) Enum accepts arguments that are not strings

2017-08-29 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7885 
 
 
 
  Enum accepts arguments that are not strings  
 
 
 
 
 
 
 
 
 

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.


Jira (PUP-7885) Enum accepts arguments that are not strings

2017-08-29 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-7885 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enum accepts arguments that are not strings  
 
 
 
 
 
 
 
 
 
 
This bug only affects the internal type parser (used when creating functions in ruby and also by the assert_type command when the type is passed as a string). An Enum that is declared in a puppet manifest rejects strings. E.g. this fails: 
 
 
 
 
 
 
$ puppet apply -e 'notice Enum[1,3]' 
 
 
 
 
Error: Evaluation Error: Error creating type specialization of an Enum-Type, Cannot use Integer where String is expected  at line 1:17 on node localhost
 
 
 
 
 
 
 
but this succeeds: 
 
 
 
 
 
 
$ puppet apply -e 'notice Type("Enum[1,3]")' 
 
 
 
 
Notice: Scope(Class[main]): Enum[1, 3]
 
 
 
 
 
 
 
but mixing integers and strings (like in the description) never succeeds: 
 
 
 
 
 
 
$ puppet apply -e 'notice Type("Enum[foo, 1]")' 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, comparison of String with 1 failed  at line 1:8 on node localhost
 
 
 
 
  

Jira (PUP-7885) in pcore-jave Enum does not coerce numbers to strings

2017-08-29 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7885 
 
 
 
  in pcore-jave Enum does not coerce numbers to strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Method Found:
 
 Manual Test 
 
 
 

Issue Type:
 
 Task Bug 
 
 
 

Key:
 
 TASKS PUP - 41 7885 
 
 
 

Project:
 
 Puppet  Tasks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7885) Enum accepts arguments that are not strings

2017-08-29 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7885 
 
 
 
  Enum accepts arguments that are not strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Summary:
 
 in pcore-jave  Enum  does  accepts arguments that are  not  coerce numbers to  strings 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3641) Package GC does not seem to occur

2017-08-29 Thread Mike Eller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Eller assigned an issue to Mike Eller 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3641 
 
 
 
  Package GC does not seem to occur  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mike Eller 
 
 
 

Assignee:
 
 Mike Eller 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7831) Specifying a return type causes syntax error on puppet 4.7 in conflict with docs

2017-08-29 Thread Kevin Reeuwijk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Reeuwijk commented on  PUP-7831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Specifying a return type causes syntax error on puppet 4.7 in conflict with docs  
 
 
 
 
 
 
 
 
 
 
Hi Jorie Tappa, please check https://docs.puppet.com/puppet/4.7/lang_write_functions_in_puppet.html which still shows syntax that includes the return type. The docs for this version should resemble the 4.6 version where the syntax doesn't have the return type syntax. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-08-29 Thread Scott Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Walker commented on  PUP-7779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 
 
That auto-upload-after-run functionality (

PUP-5934
) would be great for Package inventory as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-08-29 Thread Jon Pugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Pugh commented on  PUP-7779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 
 
If an option on the agent to run this after each Puppet run could be added it would be very useful for those who want the functionality of https://tickets.puppetlabs.com/browse/PUP-5934 without having to implement their own method of calling the script. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-7879) Configure Language runtime

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7879 
 
 
 
  Configure Language runtime  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7879) Configure Language runtime

2017-08-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configure Language runtime  
 
 
 
 
 
 
 
 
 
 
After merge of the first PR, this should go back to 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.