Jira (PUP-6860) puppet on solaris 11 cannot distinguish between non-existent and stopped services

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6860 
 
 
 
  puppet on solaris 11 cannot distinguish between non-existent and stopped services  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Summary:
 
 puppet on solaris 11  services  cannot  ensure => absent  distinguish between non-existent and stopped services 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6860) solaris 11 services cannot ensure => absent

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6860 
 
 
 
  solaris 11 services cannot ensure => absent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 5:01 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
The smf provider for solaris is currently incapable of removing a service or understanding that a service does not exist. 
This means puppet cannot distinguish between a service that exists and is stopped/disabled from a nonexistent service.  
Ie. this (current output): 
 
 
 
 
 
 
-bash-4.1# puppet resource service foo 
 
 
 
 
service { 'foo': 
 
 
 
 
  ensure => 'stopped', 
 
 
 
 
  enable => 'false', 
 

Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1394 
 
 
 
  Warning printed when 'ip route show' output contains "linkdown"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1394) Warning printed when 'ip route show' output contains "linkdown"

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1394 
 
 
 
  Warning printed when 'ip route show' output contains "linkdown"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1523) (SPIKE) Explore viability of a Facter 3 rubygem

[Geoff Nichols (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1523 
 
 
 
  (SPIKE) Explore viability of a Facter 3 rubygem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2016-11- 16 30 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3150) [Spike] Investigate and estimate solutions to the "big structure fact" problem

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3150 
 
 
 
  [Spike] Investigate and estimate solutions to the "big structure fact" problem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Summary:
 
 [Spike] Investigate and estimate solutions to the "big structure fact" problem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3159) I'd like to access the performance dashboard over https

[Nick Walker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3159 
 
 
 
  I'd like to access the performance dashboard over https  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 3:19 PM 
 
 
 

Labels:
 

 tcse 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
Currently the only way to get to the performance dashboard is to open up the http listen address which means anyone could query the puppetdb API over http as well.  
I'd prefer to simply load the performance dashboard over HTTPS.  
I could see allowing it to load without permissions at all or in PE allowing it to load when passing in a token generated from RBAC. Something like: 
 
 
 
 
 
 

Jira (PDB-3158) puppet query gives rust error when piped to a program that doesn't read its output

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3158 
 
 
 
  puppet query gives rust error when piped to a program that doesn't read its output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 MCO-776 is adding the ability to pipe output from {{puppet query}} to mco, so you can do things like{code}puppet query "inventory { facts.os.name = 'CentOS' }"| mco  rpc  puppet runonce{code} However, when  I  do I  get  the same thing if I pipe it through {{less}} and then quit (without reading the full stream).While testing that, I discovered that {{puppet query}} gives  an error  if all output isn't read, such as when piping through less but exiting before reading the full output {code} Finished processing 70 / 70 hosts in 373 $ puppet query "inventory { facts . 08 ms os.name = 'CentOS' }" | less  ...q thread 'main' panicked at 'failed to write response', ../src/libcore/option.rs:699stack backtrace:   1: 0x7ff351fbc1af - std::sys::backtrace::tracing::imp::write::h46e546df6e4e4fe6   2: 0x7ff351fbf04b - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::h077deeda8b799591   3: 0x7ff351fbeccf - std::panicking::default_hook::heb8b6fd640571a4f   4: 0x7ff351fb0c8e - std::panicking::rust_panic_with_hook::hd7b83626099d3416   5: 0x7ff351fbf291 - std::panicking::begin_panic::h941ea76fc945d925   6: 0x7ff351fb182a - std::panicking::begin_panic_fmt::h30280d4dd3f149f5   7: 0x7ff351fbf22e - rust_begin_unwind   8: 0x7ff351ff4aef - core::panicking::panic_fmt::h2d3cc8234dde51b4   9: 0x7ff351ff9cc4 - core::option::expect_failed::ha6269a58a5455f37  10: 0x7ff351d095c7 - _::expect::h84ad3d2881fe7a71at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/obj/../src/libcore/option.rs:293  11: 0x7ff351cfd652 - puppet_query::main::h60fe3698131a6d38at /var/tmp/tmp.Wlsa2DmVQo/puppetdb-cli/src/query.rs:79  12: 0x7ff351fbe908 - std::panicking::try::call::hca715a47aa047c49  13: 0x7ff351fc68ab - __rust_try  14: 0x7ff351fc684e - __rust_maybe_catch_panic  15: 0x7ff351fbe3ae - std::rt::lang_start::h162055cb2e4b9fe7  16: 0x7ff351d0a4a9 - main  17: 0x7ff350a49b14 - __libc_start_main  18: 0x7ff351cfccc8 -   19:0x0 - {code} I get the same thing if I pipe it through {{less}} and then quit (without reading the full stream). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

Jira (PDB-3158) puppet query gives rust error when piped to a program that doesn't read its output

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3158 
 
 
 
  puppet query gives rust error when piped to a program that doesn't read its output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Summary:
 
 puppet query gives rust error when piped to  mco  a program that doesn't read its output 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PDOC-124) JSON: Inconsistent naming of function parameters

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-124 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSON: Inconsistent naming of function parameters  
 
 
 
 
 
 
 
 
 
 
After discussing with Nick, we decided that this is acceptable behavior. We'll just document that this is the way the signature and param name references work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3158) puppet query gives rust error when piped to mco

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3158 
 
 
 
  puppet query gives rust error when piped to mco  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 3:02 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
MCO-776 is adding the ability to pipe output from puppet query to mco, so you can do things like 
 
 
 
 
 
 
puppet query "inventory { facts.os.name = 'CentOS' }"| mco puppet runonce 
 
 
 
 
 
 
However, when I do I get an error 
 
 
 
 
 
 
Finished processing 70 / 70 hosts in 373.08 ms 
 
 
 
 
thread 'main' panicked at 'failed to write response', ../src/libcore/option.rs:699 
   

Jira (PDB-3154) Add some "stockpile guidance" docs for the release

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning commented on  PDB-3154 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add some "stockpile guidance" docs for the release  
 
 
 
 
 
 
 
 
 
 
No idea. I put it there because it's a FOSS release we're doing as the PDB team, and I happened to be up for it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-453) selinux fact fails on centos/lxc

[Klavs Klavsen (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Klavs Klavsen commented on  FACT-453 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: selinux fact fails on centos/lxc  
 
 
 
 
 
 
 
 
 
 
it is resolved in facter 3 - with latest puppet-agent atleast  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6859) PMT does not display forge json errors when installing

[Ruth Linehan (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Linehan moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6859 
 
 
 
  PMT does not display forge json errors when installing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Linehan 
 
 
 

Key:
 
 CODEMGMT PUP - 66 6859 
 
 
 

Project:
 
 Code Management 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 (PUP-6859) PMT does not display forge json errors when installing

[Ruth Linehan (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Linehan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6859 
 
 
 
  PMT does not display forge json errors when installing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Linehan 
 
 
 

Component/s:
 
 PMT 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6858) Standardize module names vs module directory names for PMT.

[Ruth Linehan (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Linehan moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6858 
 
 
 
  Standardize module names vs module directory names for PMT.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Linehan 
 
 
 

Component/s:
 
 pmt 
 
 
 

Component/s:
 
 PMT 
 
 
 

Key:
 
 CODEMGMT PUP - 67 6858 
 
 
 

Project:
 
 Code Management 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-1530) Update Networking tests for eccentric platforms

[Stan Duffy (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1530 
 
 
 
  Update Networking tests for eccentric platforms  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 

Created:
 

 2016/11/01 12:55 PM 
 
 
 

Environment:
 
 
Puppet Agent Manual CI Pipeline 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
We need to update the test 'tests/facts/networking_facts.rb' to support the "lesser used" platforms: Cisco XR, Huawei & s390x Redhat 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian 

Jira (FACT-1054) Investigate OSX facter.jar problems

[Matthaus Owens (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1054 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Investigate OSX facter.jar problems  
 
 
 
 
 
 
 
 
 
 
Michael Smith Would you prefer a new ticket or if i simply move this one? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1054) Investigate OSX facter.jar problems

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1054 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Investigate OSX facter.jar problems  
 
 
 
 
 
 
 
 
 
 
Agreed, this is still an issue because we should be able to build JARs on OS X. However, it should probably be a PA ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1054) Investigate OSX facter.jar problems

[Matthaus Owens (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1054 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Investigate OSX facter.jar problems  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer As Michael Smith noted, actually creating facter.jar on osx is desireable for running puppet-server from source for developers. So while 

FACT-1053
 stopped the build errors, it won't help with the other thing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1388) virtual fact is wrong sometimes when nested (vmware + lxc)

[Maggie Dreyer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1388 
 
 
 
  virtual fact is wrong sometimes when nested (vmware + lxc)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Labels:
 
 virtualization 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-633) Puppet loads ZFS module on FreeBSD when ZFS is not enabled

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-633 
 
 
 
  Puppet loads ZFS module on FreeBSD when ZFS is not enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-633) Puppet loads ZFS module on FreeBSD when ZFS is not enabled

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-633 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet loads ZFS module on FreeBSD when ZFS is not enabled  
 
 
 
 
 
 
 
 
 
 
It looks like we're still doing this the same way in Facter 3. Remko Catersels's solution should be much easier to implement in the new C++ codebase than in the older ruby one, as well. 
I'd like confirmation from someone using FreeBSD that this is still a problem before I dive in and start rewriting it, though. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-454) virtual on OpenVZ returns value openvz instead of openvzve

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-454 
 
 
 
  virtual on OpenVZ returns value openvz instead of openvzve  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 maintenance redmine virtualization 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-454) virtual on OpenVZ returns value openvz instead of openvzve

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-454 
 
 
 
  virtual on OpenVZ returns value openvz instead of openvzve  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-454) virtual on OpenVZ returns value openvz instead of openvzve

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-454 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: virtual on OpenVZ returns value openvz instead of openvzve  
 
 
 
 
 
 
 
 
 
 
We should check if this is still behaving weirdly in Facter 3 (I bet it is, since we still have virt-what and non-virt-what codepaths) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-453) selinux fact fails on centos/lxc

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-453 
 
 
 
  selinux fact fails on centos/lxc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-454) virtual on OpenVZ returns value openvz instead of openvzve

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-454 
 
 
 
  virtual on OpenVZ returns value openvz instead of openvzve  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 redmine  virtualization 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1521) Kstat code is invalid on modern compilers

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1521 
 
 
 
  Kstat code is invalid on modern compilers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1521) Kstat code is invalid on modern compilers

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1521 
 
 
 
  Kstat code is invalid on modern compilers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 This blocks shipping Facter 3.x on Solaris [~branan] says this is/has always been broken and needs to be refactored I can't get this example code cleanhttps://gist.github.com/shawnferry/3067ab3be19312ee4f8281c05aaec9d8{ { code}  template<>long k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_LONG, attrib)->value.l;}template<>int32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT32, attrib)->value.i32;}template<>uint32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_UINT32, attrib)->value.ui32;}template<>int64_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT64, attrib)->value.i64;} {code } }      { { code} root@puppet4-x86:/build-x86/facter/release# make[  2%] Built target facter-jruby[  3%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o/build-x86/facter/lib/src/util/solaris/k_stat.cc:143:13: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ int64_t k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:125:10: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here long k_stat_entry::value(const std::string& attrib) const  ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:149:14: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ uint64_t k_stat_entry::value(const std::string& attrib) const  ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:119:13: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here ulong_t k_stat_entry::value(const std::string& attrib) const ^*** Error code 1The following command caused the error:cd /build-x86/facter/release/lib && /usr/bin/c++   -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DPROJECT_DIR=\"/build-x86/facter/release\" -DPROJECT_NAME=\"FACTER\" -DUSE_CPPHOCON -DUSE_JRUBY_SUPPORT -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/build-x86/facter/lib/inc -I/build-x86/facter/vendor/rapidjson-0.11/include -I/build-x86/facter/../vendor/nowide/include -I/usr/java/include -I/usr/java/include/solaris -I/build-x86/i386-gcc/include -I/build-x86/i386-gcc/include/leatherman/vendor -Wno-maybe-uninitialized -pthreads -Wno-deprecated-declarations -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -O3 -DNDEBUG -fPIC -o CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o -c 

Jira (FACT-1529) Facter fails to compile: 'convert_newlines' is not a member of 'leatherman::execution::execution_options'

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1529 
 
 
 
  Facter fails to compile: 'convert_newlines' is not a member of 'leatherman::execution::execution_options'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 2 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6857) Puppet language specification doesn't call out use of metadata.json

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6857 
 
 
 
  Puppet language specification doesn't call out use of metadata.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Team:
 
 Puppet Developer Support 
 
 
 

Sprint:
 
 PDS Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6857) Puppet language specification doesn't call out use of metadata.json

[Greg Larkin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Larkin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6857 
 
 
 
  Puppet language specification doesn't call out use of metadata.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Larkin 
 
 
 
 
 
 
 
 
 
 A discussion in Slack about function loading indicated that dependency information in the metadata.json file is used by Puppet during the compilation phase. The Puppet language specification does not mention the use of the metadata.json file, and it should be clarified to do so. Reference: https://puppetcommunity.slack.com/archives/puppet/p1478021975008061 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6857) Puppet language specification doesn't call out use of metadata.json

[Greg Larkin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Larkin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6857 
 
 
 
  Puppet language specification doesn't call out use of metadata.json  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language Specification 
 
 
 

Created:
 

 2016/11/01 10:57 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Greg Larkin 
 
 
 
 
 
 
 
 
 
 
A discussion in Slack about function loading indicated that dependency information in the metadata.json file is used by Puppet during the compilation phase. The Puppet language specification does not mention the use of the metadata.json file, and it should be clarified to do so. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
  

Jira (FACT-1468) facter fails to report correct ipaddress when routing_table fails on default gateway entry

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1468 
 
 
 
  facter fails to report correct ipaddress when routing_table fails on default gateway entry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6854) OSX: Warning output when using puppet resource service

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-6854 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OSX: Warning output when using puppet resource service  
 
 
 
 
 
 
 
 
 
 
That seems to be a new property file in OS X 10.12. Thanks for reporting it. 
It's kind of unique. It doesn't look like something we should directly manage, so a fix for this might be to special-case skip it, or demote warnings about unreadable plists to info or debug level. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6855) RPM provider's install_options and uninstall_options missing query_options

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6855 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: RPM provider's install_options and uninstall_options missing query_options  
 
 
 
 
 
 
 
 
 
 
thanks for filing this Andreas Kotes  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6855) RPM provider's install_options and uninstall_options missing query_options

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6855 
 
 
 
  RPM provider's install_options and uninstall_options missing query_options  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3157) Consider gathering stockpile related information in support script

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3157 
 
 
 
  Consider gathering stockpile related information in support script  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 10:08 AM 
 
 
 

Labels:
 

 maintenance 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You 

Jira (PUP-6856) data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently

[David Schmitt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6856 
 
 
 
  data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.7.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 9:14 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 David Schmitt 
 
 
 
 
 
 
 
 
 
 
When building the hierarchy for looking up data in modules, lib/puppet/data_providers/hiera_config.rb the interpolation around https://github.com/puppetlabs/puppet/blob/4.7.0/lib/puppet/data_providers/hiera_config.rb#L101 does weird things causing the whole lookup to fail, instead of 
 

ignoring that hierarchy level
 

reporting a specific error
 
 
This can easily be reproduced by adding the following code to spec/classes/test_spec.rb into https://github.com/puppetlabs/puppetlabs-ntp/tree/c4f586c8eabc879837942febbb70d30dc4d614ac and running 
 
 
 
 
 
 
bundle install --without 

Jira (PUP-5454) Bind mounts are not correctly handled by the 'mount' provider.

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5454 
 
 
 
  Bind mounts are not correctly handled by the 'mount' provider.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-5454) Bind mounts are not correctly handled by the 'mount' provider.

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5454 
 
 
 
  Bind mounts are not correctly handled by the 'mount' provider.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4681) Change From NFS to Bind Mount is Partially Unsuccessful

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-4681 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change From NFS to Bind Mount is Partially Unsuccessful  
 
 
 
 
 
 
 
 
 
 
thanks Trevor Vaughan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1043) Specifying file content by checksum should not use 'content' property

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-1043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Specifying file content by checksum should not use 'content' property  
 
 
 
 
 
 
 
 
 
 
Thanks for clarifying Josh Cooper. I wasn't entirely sure if that was the case and reviewed the latest type reference (https://docs.puppet.com/puppet/latest/reference/type.html#file-attribute-content) which no longer mentions support for checksum type/value via content. I've reopened this.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6855) RPM provider's install_options and uninstall_options missing query_options

[Andreas Kotes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Kotes created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6855 
 
 
 
  RPM provider's install_options and uninstall_options missing query_options  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.7.0, PUP 3.8.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 7:42 AM 
 
 
 

Environment:
 
 
RPM-based systems 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Andreas Kotes 
 
 
 
 
 
 
 
 
 
 
When working with multiple installroots / RPM roots, the following resource: 
 
 
 
 
 
 
package { 
 
 
 
 
  'foobar': 
 
 
 
 
  

Jira (PDB-3156) (maint) Start using clj-parent

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3156 
 
 
 
  (maint) Start using clj-parent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 7:07 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This switches us over to use clj-parent for managed dependencies. 
Signed-off-by: Ken Barber  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PDB-3155) (maint) Update beaker to 3.2.x, unpin from 2.30.1

[Ken Barber (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ken Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3155 
 
 
 
  (maint) Update beaker to 3.2.x, unpin from 2.30.1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ken Barber 
 
 
 

Fix Version/s:
 
 PDB 3.2.5 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3155) (maint) Update beaker to 3.2.x, unpin from 2.30.1

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3155 
 
 
 
  (maint) Update beaker to 3.2.x, unpin from 2.30.1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 6:16 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Signed-off-by: Ken Barber  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6762) (SPIKE) How and when do we get PO files from Transifex?

[Geoff Nichols (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6762 
 
 
 
  (SPIKE) How and when do we get PO files from Transifex?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Summary:
 
 [ ( SPIKE ] )  How and when do we get PO files from Transifex? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6761) (SPIKE) Find a workflow for POT file generation

[Geoff Nichols (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6761 
 
 
 
  (SPIKE) Find a workflow for POT file generation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Summary:
 
 [ ( SPIKE ] )  Find a workflow for POT file generation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6854) OSX: Warning output when using puppet resource service

[James Stocks (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Stocks created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6854 
 
 
 
  OSX: Warning output when using puppet resource service  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/01 3:47 AM 
 
 
 

Environment:
 
 
puppet-agent (master) 1.7.1.179.g4d636ee SUITE_COMMIT 4d636ee2ab6b598e10b9b19019ffa046bc66f534 TEST_TARGET osx1012-64a 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 James Stocks 
 
 
 
 
 
 
 
 
 
 
puppet resource service .* always seems to include some warning output. puppet seems to be able to query and modify services despite the warning. 
 
 
 
 
 
 
rfoie66a86vs98y:~ root# puppet resource service puppet 
 
 
 
 
Warning: The /System/Library/LaunchDaemons/com.apple.jetsamproperties.Mac.plist plist does not contain a 'label' key; Puppet is skipping it 
 
 
 
 

Jira (FACT-1468) facter fails to report correct ipaddress when routing_table fails on default gateway entry

[Diego Abelenda (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diego Abelenda commented on  FACT-1468 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter fails to report correct ipaddress when routing_table fails on default gateway entry  
 
 
 
 
 
 
 
 
 
 
Right, with puppet 4.7.1, agent 1.7.1 there is no issue anymore for this case. Thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.