Jira (PUP-10945) Change the master -> server in Server used http code

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10945  
 
 
  Change the master -> server in Server used http code   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389566.1614715872000.159010.1614991740090%40Atlassian.JIRA.


Jira (PUP-10945) Change the master -> server in Server used http code

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10945  
 
 
  Change the master -> server in Server used http code   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Fix Version/s: 
 PUP 7.5.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389566.1614715872000.159009.1614991740045%40Atlassian.JIRA.


Jira (PUP-10945) Change the master -> server in Server used http code

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-10945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Change the master -> server in Server used http code   
 

  
 
 
 
 

 
 The changes in the 7.x stream associated with this ticket mark the minimum version of the agent that we can allow to be installed with puppetserver in 8, when we switch over to using those new constants. So the version constrainthttps://github.com/puppetlabs/puppetserver/blob/5e19f473ecb05976cadda7fb960899333fc840d6/resources/ext/ezbake.conf#L10 will need to be updated when we do that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389566.1614715872000.159008.1614991680088%40Atlassian.JIRA.


Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts

2021-03-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  FACT-2956  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter should ensure core facts are resolved before loading custom facts   
 

  
 
 
 
 

 
 I think the issue Kevin and Charlie are concerned about is actually fixed in FACT-2937. The problem isn't that core facts aren't available when the custom fact is evaluated. It's that the init provider uses a legacy fact to confine its suitability and facter was filtering out the custom fact, even when requested via Facter.value. This is true for both facter -p and puppet facts show:  
 
 
 
 
 [root@jerky-luxury ~]# puppet --version  
 
 
 7.4.1  
 
 
 [root@jerky-luxury ~]# cat /opt/puppetlabs/puppet/cache/lib/facter/boom.rb  
 
 
 require 'puppet'  
 
 
 Puppet::Type.type(:service).new(:name => 'something')  
 
 
 [root@jerky-luxury ~]# facter -p | head -1  
 
 
 [2021-03-06 00:19:30.893599 ] ERROR Facter - error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/boom.rb Could not autoload puppet/type/service: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass  
 
 
 aio_agent_version => 7.4.1  
 
 
 # puppet facts show | head -1  
 
 
 Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass  
 
 
 

Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts

2021-03-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2956  
 
 
  Facter should ensure core facts are resolved before loading custom facts   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Attachment: 
 these-are-not-the-droids-youre-looking-for.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389854.1614799263000.158982.1614989880053%40Atlassian.JIRA.


Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts

2021-03-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2956  
 
 
  Facter should ensure core facts are resolved before loading custom facts   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Facter 4 calls {{Kernel.load}} on all custom ruby facts before core facts have been resolved. If the custom ruby facts has code outside a {{setcode}} block, then it's possible for core facts like {{Facter.value(:operatingsystem)}} to return nil, like FACT-2880.It is true that custom facts shouldn't misbehave that way, but a single misbehaving custom fact can prevent PE from managing itself. We also don't have tooling/validation to warn or prevent users from doing this, so there are many examples of it in practice.We should be more defensive about this. One way would be to ensure core facts are resolved before custom facts are loaded. It would still be possible for a custom fact with a higher weight to override the core fact, but at least the core fact would never have a nil value.Facter 3 didn't have this issue because core facts were implemented in C++ and evaluated before loading custom ruby facts.Due to this issue, puppet may not be able to manage services, because puppet selects {{base}} as the default service provider instead of {{systemd}}:{noformat}change from 'stopped' to 'running' failed: Services must specify a start command or a binary (corrective){noformat} I believe this This  issue  is only  can be  triggered when running {{ puppet facts show}}:{noformat}# mkdir -p /etc/puppetlabs/code/environments/production/modules/badfact/lib/ facter # cat < /etc/puppetlabs/code/environments/production/modules/badfact/lib/facter/service.rbrequire 'puppet'Puppet::Type.type(:service).new(:name => 'something')END# rm  - - rf /opt/puppetlabs/ puppet /cache/lib/# puppet facts showError: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/type/service: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/environments/production/modules/badfact/lib/facter/service.rb Could not autoload puppet/type/service: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat } If the agent has pluginsynced, then {{facter -p } } will also trigger the issue:{noformat}# facter -p[2021-03-05 20:03:49 .  It can happen when running 595880 ] ERROR Facter - error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/service.rb Could not autoload puppet/type/service: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass  { noformat}However, { puppet agent {facter  - t p  }}  if there is 

Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts

2021-03-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2956  
 
 
  Facter should ensure core facts are resolved before loading custom facts   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Facter 4 calls {{Kernel.load}} on all custom ruby facts before core facts have been resolved. If the custom ruby facts has code outside a {{setcode}} block, then it's possible for core facts like {{Facter.value(:operatingsystem)}} to return nil, like FACT-2880.It is true that custom facts shouldn't misbehave that way, but a single misbehaving custom fact can prevent PE from managing itself. We also don't have tooling/validation to warn or prevent users from doing this, so there are many examples of it in practice.We should be more defensive about this. One way would be to ensure core facts are resolved before custom facts are loaded. It would still be possible for a custom fact with a higher weight to override the core fact, but at least the core fact would never have a nil value.Facter 3 didn't have this issue because core facts were implemented in C++ and evaluated before loading custom ruby facts.Due to this issue, puppet may not be able to manage services, because puppet selects {{base}} as the default service provider instead of {{systemd}}:{noformat}change from 'stopped' to 'running' failed: Services must specify a start command or a binary (corrective){noformat} I believe this issue is only triggered when running {{facter --puppet}}. It can happen when running {{puppet agent -t}} if there is a custom or external fact that shells out to {{facter --puppet}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

Jira (PUP-5735) Remove usage of win32-security gem

2021-03-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-5735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove usage of win32-security gem   
 

  
 
 
 
 

 
 Valentyna the dependency on win32-security was removed in version 3.2.1 of the puppetlabs-acl module, see https://github.com/puppetlabs/puppetlabs-acl/commit/0aa45cba8eb89cc90879b3c53b854f0f64e482b9. Please update your acl module to 3.2.1 or greater.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.113210.1453399346000.158594.1614968100033%40Atlassian.JIRA.


Jira (PDB-5056) Document proper pagination for the various entities

2021-03-05 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5056  
 
 
  Document proper pagination for the various entities   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/03/05 10:08 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 https://www.depesz.com/2007/08/29/better-results-paging-in-postgresql-82/ https://www.depesz.com/2011/05/20/pagination-with-fixed-order/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
   

Jira (PUP-10952) Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10952  
 
 
  Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Sprint: 
 Froyo - 03/10/2021  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390083.1614901848000.158483.1614961320061%40Atlassian.JIRA.


Jira (PUP-10952) Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer assigned an issue to Maggie Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10952  
 
 
  Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Assignee: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390083.1614901848000.158485.1614961320147%40Atlassian.JIRA.


Jira (PUP-10952) Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10952  
 
 
  Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Method Found: 
 Needs Assessment Manual Test  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390083.1614901848000.158484.1614961320104%40Atlassian.JIRA.


Jira (PUP-10952) Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode

2021-03-05 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10952  
 
 
  Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390083.1614901848000.158482.1614961260093%40Atlassian.JIRA.


Jira (PUP-10950) unless should support sensitive data for any type

2021-03-05 Thread David Schmitt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt commented on  PUP-10950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unless should support sensitive data for any type   
 

  
 
 
 
 

 
 This issue is affecting customers deploying the recent security-related postgresql release (see https://github.com/puppetlabs/puppetlabs-postgresql/pull/1249 for details).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389976.1614881718000.158343.1614951480079%40Atlassian.JIRA.


Jira (PUP-10954) .gemspec doesn't fulfill its stated goal

2021-03-05 Thread David Schmitt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10954  
 
 
  .gemspec doesn't fulfill its stated goal   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.21.1, PUP 7.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/03/05 5:19 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 David Schmitt  
 

  
 
 
 
 

 
 Puppet Version: git repo, main and 6.x branch The .gemspec file claims it is "intended for use with bundler when Puppet is a dependency of another project", but is not reflecting the correct gem dependencies as uploaded to rubygems. Desired Behavior: Referencing the puppet repository in a Gemfile pulls all gems required by puppet and packaged in the agent. Actual Behavior: Referencing the puppet repository in a Gemfile doesn't pull in the win32-* dependencies that https://rubygems.org/gems/puppet/versions/6.21.1-x64-mingw32 has. Context: This was found during the analysis of MODULES-10963.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

Jira (PUP-10929) Syntax error in previously valid puppet code due to removal of application orchestration keywords

2021-03-05 Thread Ciprian Badescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ciprian Badescu assigned an issue to Ciprian Badescu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10929  
 
 
  Syntax error in previously valid puppet code due to removal of application orchestration keywords   
 

  
 
 
 
 

 
Change By: 
 Ciprian Badescu  
 
 
Assignee: 
 Ciprian Badescu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388276.1614006941000.158310.1614946740032%40Atlassian.JIRA.


Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces

2021-03-05 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2951  
 
 
  Facter 3 bad network for VirtualBox or VPN network interfaces   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
Labels: 
 known-issue-added knownissue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.158279.1614941340119%40Atlassian.JIRA.


Jira (PUP-10953) Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security

2021-03-05 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau commented on  PUP-10953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security   
 

  
 
 
 
 

 
 Valentyna looks like the dependency on win32/security was removed in this PR: https://github.com/puppetlabs/puppetlabs-acl/pull/208 and released as part of version 3.2.1 of the puppetlabs-acl module: https://github.com/puppetlabs/puppetlabs-acl/blob/main/CHANGELOG.md  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390117.1614936436000.158265.1614937620072%40Atlassian.JIRA.


Jira (PUP-10953) Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security

2021-03-05 Thread Valentyna (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentyna commented on  PUP-10953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security   
 

  
 
 
 
 

 
 Fixed by puppet module upgrade puppetlabs-acl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390117.1614936436000.158263.1614937560031%40Atlassian.JIRA.


Jira (PUP-10953) Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security

2021-03-05 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10953  
 
 
   Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Labels: 
 acl  community  provider windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390117.1614936436000.158258.1614936840120%40Atlassian.JIRA.


Jira (PUP-10953) Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security

2021-03-05 Thread Valentyna (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentyna updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10953  
 
 
   Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security   
 

  
 
 
 
 

 
Change By: 
 Valentyna  
 
 
Summary: 
 {brief summary of issue}  Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390117.1614936436000.158253.1614936480105%40Atlassian.JIRA.


Jira (PUP-10953) {brief summary of issue}

2021-03-05 Thread Valentyna (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentyna created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10953  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/03/05 1:27 AM  
 
 
Environment: 
 Production  
 
 
Labels: 
 windows acl provider  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Valentyna  
 

  
 
 
 
 

 
 Puppet Version: 7.4.1 Puppet Server Version: 7.0.3 OS Name/Version: Windows 10 I found in puppet/provider/acl/windows/base.rb require 'win32/security'. Puppet: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security Puppet: Could not autoload puppet/type/acl: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security Puppet: Failed to apply catalog: Could not autoload puppet/type/acl: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security. As I have read this should be removed.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

Jira (PUP-5735) Remove usage of win32-security gem

2021-03-05 Thread Valentyna (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentyna updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5735  
 
 
  Remove usage of win32-security gem   
 

  
 
 
 
 

 
Change By: 
 Valentyna  
 
 
Priority: 
 Normal High  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.113210.1453399346000.158248.161493630%40Atlassian.JIRA.


Jira (PUP-5735) Remove usage of win32-security gem

2021-03-05 Thread Valentyna (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentyna commented on  PUP-5735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove usage of win32-security gem   
 

  
 
 
 
 

 
 The problem exists in puppet/provider/acl/windows/base.rb, which require 'win32/security'. It gets me an error on my Winows 10: Puppet: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security Puppet: Could not autoload puppet/type/acl: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security Puppet: Failed to apply catalog: Could not autoload puppet/type/acl: Could not autoload puppet/provider/acl/windows: cannot load such file – win32/security  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.113210.1453399346000.158247.1614935940028%40Atlassian.JIRA.


Jira (HI-621) Need some help of call same hiera variable from multiple hiera files

2021-03-05 Thread Karthik Keshav M (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karthik Keshav M commented on  HI-621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need some help of call same hiera variable from multiple hiera files   
 

  
 
 
 
 

 
 Can you please provide me the instruction on how to get into the puppet's slack channel?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389949.1614876617000.158233.1614934080025%40Atlassian.JIRA.


Jira (PUP-10947) Revist the exclude_list for puppet facts diff command

2021-03-05 Thread Luchian Nemes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes assigned an issue to Luchian Nemes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10947  
 
 
  Revist the exclude_list for puppet facts diff command   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Assignee: 
 Luchian Nemes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389694.1614756311000.158221.1614932160047%40Atlassian.JIRA.