Jira (PUP-9101) PE agent installation fails on newly released Solaris 11.4

2018-09-04 Thread Halim Wijaya (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9101  
 
 
  PE agent installation fails on newly released Solaris 11.4   
 

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 

  
 
 
 
 

 
 *Puppet Version: 5.5.4* *Puppet Server Version: 2018.1.2* *OS Name/Version: Solaris 11.4*Installation of the puppet agent using the curl | bash method fails on Solaris 11.4, which was released last week.  {code:java} curl -k  [ https:// \ {Master FQDN}:8140/packages/current/install.bash |https://puppetmaster.unix.anz:8140/packages/current/install.bash]  | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 25740 100 25740 0 0 447k 0 - - : -- :--  -- : -- :--  -- : -- :- -  523k This method of agent installation is not supported for solaris-11.4-sparc in Puppet Enterprise v2018.1.2 {code}   This seems to happen because in Solaris 11.4, is now an  *_  /etc/os- release release_*  file. An example file follows: {code:java}  #  cat /etc/os-release NAME="Oracle Solaris" PRETTY_NAME="Oracle Solaris 11.4" CPE_NAME="cpe:/o:oracle:solaris:11:4" ID=solaris VERSION=11.4 VERSION_ID=11.4 BUILD_ID=11.4.0.0.1.3.0 HOME_URL=" [ https://www.oracle.com/solaris/ ] " SUPPORT_URL=" [ https://support.oracle.com/ ] " {code}   The presence of this file causes install.bash to resolve the platform tag to solaris-11.4-sparc, where on previous Solaris releases it would be solaris-11-sparc. This in turn causes the t_supported_platform_regex to not match.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 

Jira (PUP-9101) PE agent installation fails on newly released Solaris 11.4

2018-09-04 Thread Halim Wijaya (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Halim Wijaya created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9101  
 
 
  PE agent installation fails on newly released Solaris 11.4   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/09/04 6:54 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Halim Wijaya  
 

  
 
 
 
 

 
 Puppet Version: 5.5.4 Puppet Server Version: 2018.1.2 OS Name/Version: Solaris 11.4 Installation of the puppet agent using the curl | bash method fails on Solaris 11.4, which was released last week.  curl -k https://{Master FQDN}:8140/packages/current/install.bash | bash  % Total % Received % Xferd Average Speed Time Time Time Current  Dload Upload Total Spent Left Speed  100 25740 100 25740 0 0 447k 0 -::- -::- -::- 523k  This method of agent installation is not supported for solaris-11.4-sparc in Puppet Enterprise v2018.1.2 This seems to happen because in Solaris 11.4, is now an /etc/os-release file. An example file follows: 
 
cat /etc/os-release  NAME="Oracle Solaris"  PRETTY_NAME="Oracle Solaris 11.4"  CPE_NAME="cpe:/o:oracle:solaris:11:4"  ID=solaris  VERSION=11.4  VERSION_ID=11.4  BUILD_ID=11.4.0.0.1.3.0  HOME_URL="https://www.oracle.com/solaris/"  SUPPORT_URL="https://support.oracle.com/" 
 The presence of this file causes install.bash to resolve the platform tag to solaris-11.4-sparc, where on previous Solaris releases it would be solaris-11-sparc. This in turn causes the t_supported_platform_regex to not match.    
 

  
 
 
 
 

 
 
 

 
   

Jira (PUP-9100) Values in Puppet Jobs

2018-09-04 Thread Anne Rachelle Maulawin (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anne Rachelle Maulawin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9100  
 
 
  Values in Puppet Jobs
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-09-05-10-26-51-635.png  
 
 
Components: 
 Settings  
 
 
Created: 
 2018/09/04 5:41 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Anne Rachelle Maulawin  
 

  
 
 
 
 

 
 Puppet Version: 5.5.4 Puppet Server Version: PE-2018.1.3.1 OS Name/Version: Centos 7.5 This is a cosmetic issue. The cell width of the Task field in the Jobs table is fixed, hence the cell contents of the Task Name is not properly shown and has overlapped the text of the next cell. Desired Behavior:  The table cell content of the Task should be displayed properly in the table. Actual Behavior: The value of the Task name is not readable as it overlaps the text of the next cell. Step By Step Procedure: 
 
Go to Puppet Console. 
Click Jobs -> Task to view all in progress and completed jobs 
     
 

  
 
 
 
 

 
 
 

 
   

Jira (PUP-8987) add resource_api gem to puppet gemspec

2018-09-04 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan commented on  PUP-8987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add resource_api gem to puppet gemspec   
 

  
 
 
 
 

 
 Kenn Hussey Yes, I see it as a dependency in the puppet-agent here: https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/rubygem-puppet-resource_api.json. I wasn't involved with any of the work for the resource api gem though. Branan Riley was the most involved, so he might know more (including whether we may need it as a dependency for Puppet).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9068) Windows admin? check should consider group membership

2018-09-04 Thread Erick Banks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erick Banks assigned an issue to Ethan Brown  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9068  
 
 
  Windows admin? check should consider group membership   
 

  
 
 
 
 

 
Change By: 
 Erick Banks  
 
 
Assignee: 
 Ethan Brown  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9068) Windows admin? check should consider group membership

2018-09-04 Thread Erick Banks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erick Banks updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9068  
 
 
  Windows admin? check should consider group membership   
 

  
 
 
 
 

 
Change By: 
 Erick Banks  
 
 
Sprint: 
 Windows  Grooming  Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4289) user type doesn't support Full Name on Windows

2018-09-04 Thread Erick Banks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erick Banks commented on  PUP-4289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: user type doesn't support Full Name on Windows   
 

  
 
 
 
 

 
 Hi Dima, thanks for raising this. We feel puppetlabs-dsc and puppetlabs-dsc_lite modules provide the functionality you're asking for and we feel the issue has been addresed by dsc/dsc_lite puppet-supported modules. If you feel otherwise please do not hesitate to re-open this ticket and provide more information as to why this may still be a valid issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4290) Group type doesn't support description/comment field on Windows

2018-09-04 Thread Erick Banks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erick Banks commented on  PUP-4290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Group type doesn't support description/comment field on Windows   
 

  
 
 
 
 

 
 Hi Dima, thanks for raising this. We feel puppetlabs-dsc and puppetlabs-dsc_lite modules provide the functionality you're asking for and we feel the issue has been addresed by dsc/dsc_lite puppet-supported modules. If you feel otherwise please do not hesitate to re-open this ticket and provide more information as to why this may still be a valid issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8733) File type redefined when required in code

2018-09-04 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8733  
 
 
  File type redefined when required in code   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 Fix an issue running in JRuby where we didn't store autoloaded paths in the same way that the JRuby implementation did, leading to a bug where a type or provider could get loaded more than once.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8591) Actually delete webrick

2018-09-04 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8591  
 
 
  Actually delete webrick   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Release Notes Summary: 
 Webrick support (previous deprecated) has been removed. This means that the `puppet master` command no longer exists. To run puppet as a server you must use puppetserver.  
 
 
Release Notes: 
 Deprecation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3947) Remove activemq entirely

2018-09-04 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3947  
 
 
  Remove activemq entirely   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes Summary: 
 Initial This initial  draft  is already  in release_notes.markdown :[upgrade_policy]: . /versioning_policy.html#upgrades## 6.0.0## Upgrading-  Support for ActiveMQ has been completely removed, meaning that PuppetDB can no longer convert an existing queue to the new format when upgrading from versions older than 4.3.0, but since PuppetDB's [upgrade policy][upgrade_policy] forbids skipping major versions, this should not present a problem since any version 5 release will perform the conversion at startup.As a result of the removal, these ActiveMQ specific configuration options have been retired: `store-usage`, `temp-usage`, `memory-usage`, and `max-frame-size`,  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 

Jira (PDB-3993) Add --upgrade-and-quit or similar for unattended multi-version upgrades

2018-09-04 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3993  
 
 
  Add --upgrade-and-quit or similar for unattended multi-version upgrades   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes Summary: 
 [versioning]: ./versioning_policy.html#upgrades[multiple-major-upgrades]: ./upgrade.html#upgrading-across-multiple-major-versions## 5.2.?### New features- An `upgrade` subcommand has been added that should be useful for cases where you want to upgrade across multiple major versions without skipping major versions (as per the [versioning policy][versioning]).  See [these notes [multiple-major-upgrades] for additional information.([PDB-3993](https://tickets.puppetlabs.com/browse/PDB-3993))  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 

Jira (PDB-3993) Add --upgrade-and-quit or similar for unattended multi-version upgrades

2018-09-04 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3993  
 
 
  Add --upgrade-and-quit or similar for unattended multi-version upgrades   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 5.2.z  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9099) Convert run times from seconds to minutes and seconds

2018-09-04 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9099  
 
 
  Convert run times from seconds to minutes and seconds   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9099) Convert run times from seconds to minutes and seconds

2018-09-04 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9099  
 
 
  Convert run times from seconds to minutes and seconds   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Key: 
 PA PUP - 2159 9099  
 
 
Project: 
 Puppet  Agent  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1879) Duplicate facts without weight should emit a warning

2018-09-04 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1879  
 
 
  Duplicate facts without weight should emit a warning   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Labels: 
 maintenance  triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1879) Duplicate facts without weight should emit a warning

2018-09-04 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1879  
 
 
  Duplicate facts without weight should emit a warning   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Team: 
 Platform OS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9012) SELinux bindings not found.

2018-09-04 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9012  
 
 
  SELinux bindings not found.   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Labels: 
 customer packaging redhat redhat7 selinux  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-645) Support puppet device modules in a manifest block

2018-09-04 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-645  
 
 
  Support puppet device modules in a manifest block   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Summary: 
 Spike: use Support  puppet device modules in a manifest block  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9020) Give a deprecation error when top level constructs are found in modules

2018-09-04 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9020  
 
 
  Give a deprecation error when top level constructs are found in modules   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Release Notes Summary: 
 A deprecation warning will be given during puppet code validation when toplevel constructs that are not defines are found in autoloaded module files.  
 
 
Release Notes: 
 Deprecation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7141) Refactor required string dup in 3x runtime converter

2018-09-04 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7141  
 
 
  Refactor required string dup in 3x runtime converter   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 Types and Provider implementations must not mutate the parameter values of a resource. In Puppet 6.0.0 it is more likely that the parameters of a resource will have frozen (i.e. immutable) string values and any type or provider that directly mutates a resource parameter may fail. Before Puppet 6.0.0 every resource attribute was copied to not make application break even if they did mutate. Look for use of {{gsub!}} in your modules and replace logic with non mutating version, or operate on a copy of the value. (All modules authors of modules on the forge having this problem have been notified).  
 
 
Release Notes: 
 Deprecation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, 

Jira (PUP-7141) Refactor required string dup in 3x runtime converter

2018-09-04 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-7141  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refactor required string dup in 3x runtime converter   
 

  
 
 
 
 

 
 As per the discussion in the PR a decision was made to stop duplicating frozen strings both on master side and agent. This affects some modules - and ticket PUP-9098 was logged for the modules in puppet that has affected logic. I also reached out to one forge module that has the same problem: https://github.com/thecodeteam/puppet-vnx/issues/10. This now again ready to be merged for Puppet 6.0.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9098) change of gsub! to mutate strings must change for Puppet 6.0.0

2018-09-04 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9098  
 
 
  change of gsub! to mutate strings must change for Puppet 6.0.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/09/04 12:58 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 In PUP-7141 (for Puppet 6.0.0) we will stop duplicating every parameter value string. This was there to allow old types/providers to mutate their input. This is quite wasteful in terms of memory and garbage collection and in PUP 7141 values will be to a large extent now instead be the frozen original strings. The following places in our maintained modules must be updated:  
 
 
 
 
 ag 'gsub!' */lib/puppet/type/*.rb  
 
 
 darin-zypprepo-1.0.2/lib/puppet/type/zypprepo.rb  
 
 
 112:reposdir.gsub!(/[\n,]/, " ")  
 
 
 138:  reposdir.gsub!(/[\n,]/, " ")  
 
 
    
 
 
 

Jira (PDB-4059) Test merge master

2018-09-04 Thread gepetto-bot (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4059  
 
 
  Test merge master   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/09/04 12:49 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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.

Jira (PUP-7433) Restructure Gemfile to use different group names

2018-09-04 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-7433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Restructure Gemfile to use different group names   
 

  
 
 
 
 

 
 Merged into master at ddf8b76.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9050) Beaker 4.0 Compatibility

2018-09-04 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-9050  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Beaker 4.0 Compatibility   
 

  
 
 
 
 

 
 This still needs to be merged up to the other branches, and we seem to have run into some issues actually running the test suites with these changes. See BKR-1524. Reopening.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4058) Test merge 5.2.x

2018-09-04 Thread gepetto-bot (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4058  
 
 
  Test merge 5.2.x   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/09/04 10:28 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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.

Jira (FACT-1415) Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion

2018-09-04 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan assigned an issue to Enis Inan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1415  
 
 
  Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Assignee: 
 Enis Inan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-658) Validate JSON data in bolt-transport-api requests

2018-09-04 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-658  
 
 
  Validate JSON data in bolt-transport-api requests   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-9081) Include File requirements in task infoservice files responses

2018-09-04 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9081  
 
 
  Include File requirements in task infoservice files responses   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-719) Allow modulepath to include paths relative to the Boltdir

2018-09-04 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-719  
 
 
  Allow modulepath to include paths relative to the Boltdir   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-614) I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1

2018-09-04 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-614  
 
 
  I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-774) Support multiple files for tasks in bolt

2018-09-04 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-774  
 
 
  Support multiple files for tasks in bolt   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-755) Bolt should support multi-file tasks

2018-09-04 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-755  
 
 
  Bolt should support multi-file tasks   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-263) Puppet strings output on ruby functions seems incorrect

2018-09-04 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam commented on  PDOC-263  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet strings output on ruby functions seems incorrect   
 

  
 
 
 
 

 
 Alexander Fisher Geoff Williams, I'm unfortunately not actively working on Strings anymore. I would definitely say the more granular the tickets, the better, Alex. I'll see if I can get these issues in front of someone.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-791) Support running a task on a proxy node targeting a device or API with run-on

2018-09-04 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support running a task on a proxy node targeting a device or API with run-on   
 

  
 
 
 
 

 
 Yes _target will contain the Target object which has the credentials and other connection info. Yes it's just a reference to another target(including localhost) The task framework is platform agnostic so there is no single runtime environment any task can rely on*. In practice is seems reasonable to base remote tasks on the puppet agent runtime. It will make it easiest to reuse device code and the puppet agent ruby libraries are always available at least on the bolt controller. Beyond that tasks can use feature requirements in metadata combined with documentation to control their runtime environment. We'll have to sort out how implementations and feature requirements work for remote tasks. I think they're most valuable is they relate to the proxy rather then the target.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8942) Support issuing certificates with IP Address Subject Alternative Names

2018-09-04 Thread Jeffrey Clark (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeffrey Clark commented on  PUP-8942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support issuing certificates with IP Address Subject Alternative Names   
 

  
 
 
 
 

 
  
 
 
 
 
 puppet cert sign --allow-dns-alt-names XXX.XX.com   
 
 
 
  Relevant config on the agent:  
 
 
 
 
 [main]  
 
 
 dns_alt_names=DNS:XXX.XX.com,YYY.YY.com,IP:1.2.3.4  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names

2018-09-04 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-8942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support issuing certificates with IP Address Subject Alternative Names   
 

  
 
 
 
 

 
 I'll take a look at this, thanks for reporting it! What command were you using to sign the CSR from the command line?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1842) The ability to blocklist individual facts

2018-09-04 Thread Nicky Kernohan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicky Kernohan commented on  FACT-1842  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The ability to blocklist individual facts   
 

  
 
 
 
 

 
 Yep its a duplicate, closing, thanks   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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.