Jira (FACT-2891) Facter 4.0.46 (from puppet 7) breaks virtual flag

2020-12-07 Thread Christian Reiss (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Reiss created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2891  
 
 
  Facter 4.0.46 (from puppet 7) breaks virtual flag   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 FACT 4.0.44  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Facter 4  
 
 
Created: 
 2020/12/07 10:23 PM  
 
 
Environment: 
 
 
Tested in similar Systems running CentOS 7, 
Puppet-agent 7, 
same code, 
with above commands. 
 100% reproduceable.  
 
 
Priority: 
  High  
 
 
Reporter: 
 Christian Reiss  
 

  
 
 
 
 

 
 Hey, I am running the puppet-collection 7 with facter 4.0.46 that comes along. I have a few containers that are inside OpenVZ / Virtuozzo environment. Previously it was matched correctly as "openvz" or "openvzhe", now its just "physical":  
 
 
 
 
 [root@zen10:~] # systemd-detect-virt  
 
 
 o

Jira (PDB-4932) Sync summary queries can hang

2020-12-07 Thread zendesk.jira (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zendesk.jira updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4932  
 
 
  Sync summary queries can hang   
 

  
 
 
 
 

 
Change By: 
 zendesk.jira  
 
 
Zendesk Ticket Count: 
 1 2  
 
 
Zendesk Ticket IDs: 
 41188 ,42072  
 

  
 
 
 
 

 
 
 

 
 
 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.375125.1602801356000.93159.1607403600091%40Atlassian.JIRA.


Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults

2020-12-07 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10812  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove CA dir deprecation warning from settings defaults   
 

  
 
 
 
 

 
 Could you also delete the code that filters out that message when cleaning a node?  
 

  
 
 
 
 

 
 
 

 
 
 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.379969.1607106146000.93143.1607392800351%40Atlassian.JIRA.


Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults

2020-12-07 Thread Tony Vu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Vu assigned an issue to Tony Vu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10812  
 
 
  Remove CA dir deprecation warning from settings defaults   
 

  
 
 
 
 

 
Change By: 
 Tony Vu  
 
 
Assignee: 
 Tony Vu  
 

  
 
 
 
 

 
 
 

 
 
 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.379969.1607106146000.93088.1607388840073%40Atlassian.JIRA.


Jira (PDB-4932) Sync summary queries can hang

2020-12-07 Thread Zachary Kent (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent commented on  PDB-4932  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sync summary queries can hang   
 

  
 
 
 
 

 
 We're planning on adding additional logging and a way to capture stack traces from the sync thread automatically if we're unable to interrupt sync. This should allow us to better diagnose where sync can hang and rule out possible issues caused by the recent sync interruption changes. For now I'm moving this ticket into the suspended column but will link it to the ticket Rob Browning is planning on making for the sync interrupt logging/stack trace capture work.  
 

  
 
 
 
 

 
 
 

 
 
 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.375125.1602801356000.93065.1607388180035%40Atlassian.JIRA.


Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults

2020-12-07 Thread Cas Donoghue (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10812  
 
 
  Remove CA dir deprecation warning from settings defaults   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Sprint: 
 Froyo - 12/14/2020  
 

  
 
 
 
 

 
 
 

 
 
 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.379969.1607106146000.92959.1607384520026%40Atlassian.JIRA.


Jira (PDB-4983) PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name

2020-12-07 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PDB-4983  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name   
 

  
 
 
 
 

 
 I'm mostly interested in the networking facts like: puppet facts show fqdn hostname domain networking And the puppet.conf & puppetdb.conf files, and whether the puppet server's cert rtv-puppet01.rtv.nex.lan matches its fqdn. Also after upgrading the puppet-agent package on the server, did you restart the puppetserver and puppetdb services? We've seen some reports of strange behavior due to running with inconsistent versions of code.  
 

  
 
 
 
 

 
 
 

 
 
 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.380095.1607374764000.92917.1607383920027%40Atlassian.JIRA.


Jira (PUP-10813) Unit test error with file resource content using find_template()

2020-12-07 Thread GeorgesZ (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 GeorgesZ created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10813  
 
 
  Unit test error with file resource content using find_template()   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.17.0  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 FindTemplateBug.zip  
 
 
Created: 
 2020/12/07 3:17 PM  
 
 
Environment: 
 Windows and Linux.  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 GeorgesZ  
 

  
 
 
 
 

 
 Puppet Version: 6.17.0 Puppet Server Version: N/A OS Name/Version: Windows 10, Linux Running unit test on puppet code that uses find_template gives error during compilation of the unit test. Describe steps to reproduce: 
 
 
 
 
 
 
 pdk new module ...  
 
 
 
  
 
 
 
 

Jira (PDB-4983) PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name

2020-12-07 Thread Anne Slama (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anne Slama commented on  PDB-4983  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name   
 

  
 
 
 
 

 
 Is there something specific you need from the puppet facts show? It appears to have some keys and sensitive info, so I don't think I can send the whole thing without redacting some data.  
 

  
 
 
 
 

 
 
 

 
 
 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.380095.1607374764000.92891.1607382540088%40Atlassian.JIRA.


Jira (PDB-4983) PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name

2020-12-07 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PDB-4983  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name   
 

  
 
 
 
 

 
 Hi Anne Slama could you include /etc/puppetlabs/puppet/puppet.conf, {{ /etc/puppetlabs/puppet/puppetdb.conf}} and the output of puppet facts show? Also it's normally not necessary to specify the hostcert property, as you have to be careful that other related settings are consistent. Is there a particular reason you're setting hostcert explicitly? Also there is an issue in facter4 see (FACT-2882) which could affect how facter resolves the fqdn, though in that case the hostname is present, but the domain is missing, which seems like the opposite issue that you're seeing.  
 

  
 
 
 
 

 
 
 

 
 
 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.380095.1607374764000.92788.1607379240029%40Atlassian.JIRA.


Jira (PDB-4983) PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name

2020-12-07 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4983  
 
 
  PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 After a recent upgrade to puppetdb 7.0.0 we noticed the puppet agents were error-ing out with the following message:{code}Warning: Unable to fetch my node definition, but the agent run will continue:Warning: Error 500 on SERVER: Server Error: Could not retrieve facts for rtv-mktadm02.rtv.nex.lan: Failed to find facts from PuppetDB at  /etc/puppetlabs/puppet/ssl/certs/.rtv.nex.lan.pem (No such file or directory){code}On the puppet server (hostname is rtv-puppet01.rtv.nex.lan) the following cert exists, is valid, and was working until the puppetdb upgrade:/etc/puppetlabs/puppet/ssl/certs/rtv-puppet01.rtv.nex.lan.pemIf we do " puppet config print | grep ssl" we also seem to have this set properly:hostcert = /etc/puppetlabs/puppet/ssl/certs/rtv-puppet01.rtv.nex.lan.pemWe have noticed that if we simply rename the cert to anything without the ' \ -' it appears to work, but it seems counter-intuitive to allow hostnames with ' \ -' and not let the certname also have '-'.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (PDB-4627) Docs are unclear about supported postgres/java versions

2020-12-07 Thread Zachary Kent (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4627  
 
 
  Docs are unclear about supported postgres/java versions   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Fix Version/s: 
 PDB n/a  
 

  
 
 
 
 

 
 
 

 
 
 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.342654.1579514884000.92708.1607376720037%40Atlassian.JIRA.


Jira (PDB-4983) PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name

2020-12-07 Thread Anne Slama (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anne Slama created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4983  
 
 
  PuppetDB 7.0.0 can't find cert if puppet host has dash/hyphen in name   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/12/07 12:59 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Anne Slama  
 

  
 
 
 
 

 
 After a recent upgrade to puppetdb 7.0.0 we noticed the puppet agents were error-ing out with the following message:  
 
 
 
 
 Warning: Unable to fetch my node definition, but the agent run will continue:  
 
 
 Warning: Error 500 on SERVER: Server Error: Could not retrieve facts for rtv-mktadm02.rtv.nex.lan: Failed to find facts from PuppetDB at  /etc/puppetlabs/puppet/ssl/certs/.rtv.nex.lan.pem (No such file or directory)
  
 
 
 
  On the puppet server (hostname is rtv-puppet01.rtv.nex.lan) the following cert exists, is valid, and was working until the puppetdb upgrade: /etc/puppetlabs/puppet/ssl/certs/rtv-puppet01.rtv.nex.lan.pem If we do " puppet config print | grep ssl" we also seem to have this set properly: hostcert = /etc/puppetlabs/puppet/ssl/certs/rtv-puppet01.rtv.nex.lan.pem We have noticed that if we simply rename the cert to anything without the '' it appears to work, but it seems counter-intuitive to allow hostnames with '' and not let the certname also have '-'.  
 

  
 
  

Jira (PUP-10792) How to set token for https url when using puppet file resource

2020-12-07 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10792  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: How to set token for https url when using puppet file resource   
 

  
 
 
 
 

 
 We always recommend upgrading puppetserver/puppetdb prior to agents, see https://puppet.com/docs/puppet/latest/upgrade_minor.html About slowness, you might want to use wireshark and compare network traces of puppet vs curl. It's possible ruby's Net::HTTP does something inefficiently when handling chunked encoding, like read from the socket one byte at a time.  
 

  
 
 
 
 

 
 
 

 
 
 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.379148.1606203494000.92642.1607371980088%40Atlassian.JIRA.


Jira (PDB-4971) PDB terminus generates a warning on ruby 2.7

2020-12-07 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4971  
 
 
  PDB terminus generates a warning on ruby 2.7   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 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.378969.1605830582000.92582.1607369760091%40Atlassian.JIRA.


Jira (FACT-2833) Investigate performance for hypervisor fact

2020-12-07 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2833  
 
 
  Investigate performance for hypervisor fact   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Labels: 
 platform_7. 1 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.374205.1602078248000.92440.1607364540035%40Atlassian.JIRA.


Jira (FACT-2890) Domainname is not resolved correctly

2020-12-07 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau commented on  FACT-2890  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Domainname is not resolved correctly   
 

  
 
 
 
 

 
 This is fixed in https://github.com/puppetlabs/facter/pull/2208  
 

  
 
 
 
 

 
 
 

 
 
 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.380041.1607353807000.92405.1607362140146%40Atlassian.JIRA.


Jira (PUP-10794) Update certname description

2020-12-07 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10794  
 
 
  Update certname description   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
Sprint: 
 2020.12.08-12.18  
 
 
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.379406.1606764882000.92272.1607355300078%40Atlassian.JIRA.


Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example

2020-12-07 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10800  
 
 
  Add logonaccount and logonpassword to windows service provider example   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
Sprint: 
 Triaged tickets 2020.12.08-12.18  
 

  
 
 
 
 

 
 
 

 
 
 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.379820.1607016894000.92266.1607355120103%40Atlassian.JIRA.


Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example

2020-12-07 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10800  
 
 
  Add logonaccount and logonpassword to windows service provider example   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
Labels: 
 puppet  
 

  
 
 
 
 

 
 
 

 
 
 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.379820.1607016894000.92265.1607355120052%40Atlassian.JIRA.


Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example

2020-12-07 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10800  
 
 
  Add logonaccount and logonpassword to windows service provider example   
 

  
 
 
 
 

 
Change By: 
 Claire Cadman  
 
 
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.379820.1607016894000.92267.1607355120147%40Atlassian.JIRA.


Jira (FACT-2890) Domainname is not resolved correctly

2020-12-07 Thread Michael Wodniok (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Wodniok created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2890  
 
 
  Domainname is not resolved correctly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 FACT 4.0.46  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Facter 4  
 
 
Created: 
 2020/12/07 7:10 AM  
 
 
Environment: 
 E.g. Ubuntu hosts are defining their domain name by setting an entry in `/etc/hosts` in following scheme:  
 
 
 
 
 127.0.1.1  . 
  
 
 
 
  `hostname -d` displays the domainname correctly, `hostname -f`  also displays FQDN correctly independent of entries in `/etc/resolv.conf`. The `hostname`-switches `-f` and `-d` are available in Ubuntu, OpenSuse, CentOS and FreeBSD.  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Wodniok  
 

  
 
 
 
 

 
 The dns search-list is used instead of e.g. `hostname -d` for domainname resolution. This is causing puppet 7.0 to not detect the correct FQDN correctly und stops runs immediatly.    
 

  
 
  

Jira (FACT-2884) How to disable Querying Ec2 metadata

2020-12-07 Thread Florin Dragos (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florin Dragos assigned an issue to Florin Dragos  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2884  
 
 
  How to disable Querying Ec2 metadata   
 

  
 
 
 
 

 
Change By: 
 Florin Dragos  
 
 
Assignee: 
 Florin Dragos  
 

  
 
 
 
 

 
 
 

 
 
 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.379602.1606876774000.92255.1607353380026%40Atlassian.JIRA.


Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example

2020-12-07 Thread Darren Gipson (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darren Gipson commented on  PUP-10800  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add logonaccount and logonpassword to windows service provider example   
 

  
 
 
 
 

 
 Hi Claire, The change was added into Puppet 6.17, so please can the notes reflect this? I have it working in Puppet 6.19. Please can you also detail that logonpassword is a sensitive variable. Thanks, Darren  
 

  
 
 
 
 

 
 
 

 
 
 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.379820.1607016894000.92246.1607351580029%40Atlassian.JIRA.


Jira (FACT-2887) retrieve_default_interface uses incorrect method and doesn't work when IPv6-only

2020-12-07 Thread Sebastian Miclea (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea assigned an issue to Sebastian Miclea  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2887  
 
 
  retrieve_default_interface uses incorrect method and doesn't work when IPv6-only   
 

  
 
 
 
 

 
Change By: 
 Sebastian Miclea  
 
 
Assignee: 
 Sebastian Miclea  
 

  
 
 
 
 

 
 
 

 
 
 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.379995.1607224967000.92198.1607339280027%40Atlassian.JIRA.


Jira (FACT-2889) Can't create VLANs on Amazon 6

2020-12-07 Thread Andrei Filipovici (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Filipovici created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2889  
 
 
  Can't create VLANs on Amazon 6   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/12/07 3:02 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Andrei Filipovici  
 

  
 
 
 
 

 
 On Amazon 6 ABS image we can't create VLANs with the ip command. Running ip link add link eth0 name eth0.100 type vlan id 100 is successful but the VLAN doesn't show in the list obtained with ip a. The exact same command works on the Amazon 7 and Centos 7 ABS amazon images. It also works on a locally created Amazon 6. It seems that there's a problem with how this Amazon 6 image is configured.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact

2020-12-07 Thread David Schmitt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt commented on  FACT-2880  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: facter 4 differing output from facter 3 for service_provider fact   
 

  
 
 
 
 

 
 we have precedence of writing rubocop plugins for important issues. Theoretically this should be quite easy to detect. cc Ben Ford for prioritisation.  
 

  
 
 
 
 

 
 
 

 
 
 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.379364.1606744776000.92192.1607336820039%40Atlassian.JIRA.


Jira (PUP-10774) Long query time for AD groups

2020-12-07 Thread Luchian Nemes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10774  
 
 
  Long query time for AD groups   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Release Notes: 
 Bug Fix  
 
 
Release Notes Summary: 
 Time spent on querying the groups of a system user has been significantly improved on Linux operating systems with FFI and the `getgrouplist` method available.  
 

  
 
 
 
 

 
 
 

 
 
 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.377144.160449921.92165.1607332020191%40Atlassian.JIRA.


Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact

2020-12-07 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2880  
 
 
  facter 4 differing output from facter 3 for service_provider fact   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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.379364.1606744776000.92159.1607330820049%40Atlassian.JIRA.


Jira (FACT-2884) How to disable Querying Ec2 metadata

2020-12-07 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2884  
 
 
  How to disable Querying Ec2 metadata   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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.379602.1606876774000.92160.1607330820108%40Atlassian.JIRA.