Jira (FACT-3200) Facter throws ``Error while resolving custom fact fact=''``

2023-05-04 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3200  
 
 
  Facter throws ``Error while resolving custom fact fact=''``   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 
 
Assignee: 
 Josh Cooper  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Open Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





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

Jira (FACT-3200) Facter throws ``Error while resolving custom fact fact=''``

2023-05-04 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen commented on  FACT-3200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter throws ``Error while resolving custom fact fact=''``   
 

  
 
 
 
 

 
 Hi Josh Cooper. You're absolutely right...sorry for the false alarm here. I didn't realize that this module had a custom fact that was expecting the presence of ``/etc/puppetlabs/puppet/ssl/private_keys/# {Puppet.settings[:certname]} .pem'``. Once the File.exists?() check was added then the error went away.  
 
 
 
 
 require 'puppet'  
 
 
 require 'yaml'  
 
 
 require 'net/ssh'  
 
 
    
 
 
 Facter.add(:usage, type: :aggregate) do  
 
 
   chunk(:sshkey) do  
 
 
 private_key_file = File.join('/etc/puppetlabs/puppet/ssl/private_keys', Puppet.settings[:certname] + '.pem')  
 
 
 identifier = Puppet.settings[:certname]  
 
 
    
 
 
 if File.exists?(private_key_file)  
 
 
   key = OpenSSL::PKey::RSA.new(File.read(private_key_file))  
 
 
   type = key.ssh_type

Jira (FACT-3200) Facter throws ``Error while resolving custom fact fact=''``

2023-05-04 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3200  
 
 
  Facter throws ``Error while resolving custom fact fact=''``   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2023/05/04 1:00 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
 When I run a plan against nodes on GCP, I always see the following non-fatal error:  
 
 
 
 
 Facter throws ``Error while resolving custom fact fact=''`
  
 
 
 
  See replication and workaround in Description section. Desired Behaviour  
 
 
 
 
   Notice: /Stage[main]/Main/Notify[Hello, world!]/message: defined 'message' as 'Hello, world!'  
 
 
   changed: 1, failed: 0, unchanged: 0 skipped: 0, noop: 0
  
 
 
 
  Actual Behaviour

Jira (FACT-3192) ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``

2023-03-29 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen commented on  FACT-3192  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``   
 

  
 
 
 
 

 
 Hi Josh Cooper. Can you tell me a rough ETA on this so I can pass this onto the customer at ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





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

Jira (FACT-3192) ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``

2023-03-23 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3192  
 
 
  ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 
 
Summary: 
 Custom fact fails to appear when using some options like ``facter  - p - - no-external-facts `` causes ``ERROR Facter::OptionsValidator``  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





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

Jira (FACT-3192) Custom fact fails to appear when using some options like --json

2023-03-17 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3192  
 
 
  Custom fact fails to appear when using some options like --json   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
 A customer is seeing some unexpected behaviours when using facter as follows: * Using``{*}-p-{*}`` and ``{*}-no-external-facts{*}`` together produces an error ``{*}ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one{*}`` and no facts are returned * Other variations of facter options fail to return the expected custom factI have been able to replicate what the customer is seeing on my lab of   {code}root@pe-server-238c28-1 development (development)$ facter --version  4.2.14root@pe-server-238c28-1 development (development)$   {code} More detail of my lab setup:  * I  have a custom fact defined on my PE, e.g., my environment containse the custom fact here *site-modules/bigbird/lib/facter/bigbird.rb* * I  can see my ``bigbird`` custom fact as expected: {code}root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p bigbird{  role => "role::replica",  sshkey => {    identifier => "pe-server-238c28-1.us-west1-b.c.customer-support-scratchpad.internal",    key => "LONGLONGLONGPUBLICKEY",    type => "ssh-rsa"  }}root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p | grep bigbirdbigbird => {root@pe-server-238c28-1 pe_curl_requests (development)$ {code}  * However, when I introduce other flags I see expected results: {code}# these workroot@pe-server-238c28-1 development (development)$ facter -p --json | grep -E "(oslogin|[^/]bigbird)"  "bigbird": {    "oslogin": {root@pe-server-238c28-1 development (development)$ facter -p bigbird --json | grep -E "(oslogin|[^/]bigbird)"  "bigbird": {root@pe-server-238c28-1 development (development)$ # these don't work# custom fact 'bigbird' is not returned unexpectedlyroot@pe-server-238c28-1 development (development)$ facter --json | grep -E "(oslogin|[^/]bigbird)"    "oslogin": {root@pe-server-238c28-1 development (development)$ # no facts returned AND an error is thrownroot@pe-server-238c28-1 development (development)$ facter -p --no-external-facts | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:08.334765 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:15.077332 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:21.438824 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:28.317694 ] ERROR Facter::OptionsValidator - no-exte

Jira (FACT-3192) Custom fact fails to appear when using some options like --json

2023-03-17 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3192  
 
 
  Custom fact fails to appear when using some options like --json   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
    * I can see my ``bigbird`` custom fact as expected:   {code}  root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p bigbird  { }}}{{{}{{}}}{{    role => "role::replica", }}{{{}    sshkey =>{ }}}{{{}{       identifier => "pe-server-238c28-1.us-west1-b.c.customer-support-scratchpad.internal",       key => "LONGLONGLONGPUBLICKEY",       type => "ssh-rsa"     } {}}}{{{}}{}}}  {{{ }  root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p | grep bigbird {}}}{{{}  bigbird => { {}}}{{{}  root@pe-server-238c28-1 pe_curl_requests (development)${ }}}{ code}    * However, when I introduce other flags I see expected results:   {code}   # these work  root@pe-server-238c28-1 development (development)$ facter -p --json | grep -E "(oslogin|[^/]bigbird)"    "bigbird": {      "oslogin": {  root@pe-server-238c28-1 development (development)$ facter -p bigbird --json | grep -E "(oslogin|[^/]bigbird)"    "bigbird": {  root@pe-server-238c28-1 development (development)$        # these don't work   # custom fact 'bigbird' is not returned unexpectedly  root@pe-server-238c28-1 development (development)$ facter --json | grep -E "(oslogin|[^/]bigbird)"      "oslogin": {  root@pe-server-238c28-1 development (development)$        # no facts returned AND an error is thrown  root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts | grep -E "(oslogin|[^/]bigbird)"  [2023-03-17 13:28:08.334765 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one   root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"  [2023-03-17 13:28:15.077332 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one   root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts | grep -E "(oslogin|[^/]bigbird)"  [2023-03-17 13:28:21.438824 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one   root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"  [2023-03-17 13:28:28.317694 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one   root@pe-server-238c28-1 development (development)$   {code}   

Jira (FACT-3192) Custom fact fails to appear when using some options like --json

2023-03-17 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3192  
 
 
  Custom fact fails to appear when using some options like --json   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
     * I can see my ``bigbird`` custom fact as expected:  ``` {code}   root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p bigbird  {  }}}{{{}{{}}}{{   role => "role::replica",  }}{{{}   sshkey => {  }}}{{{}{     identifier => "pe-server-238c28-1.us-west1-b.c.customer-support-scratchpad.internal",      key => "LONGLONGLONGPUBLICKEY",      type => "ssh-rsa"    }  { } }}{{{}}{}}}    {{{} root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p | grep bigbird  {}}}{{{} bigbird => {  {}}}{{{} root@pe-server-238c28-1 pe_curl_requests (development)$ {}}}  {code}  ```      * However, when I introduce other flags I see expected results:  ```bash {code}   # these workroot@pe-server-238c28-1 development (development)$ facter -p --json | grep -E "(oslogin|[^/]bigbird)"  "bigbird": {    "oslogin": {root@pe-server-238c28-1 development (development)$ facter -p bigbird --json | grep -E "(oslogin|[^/]bigbird)"  "bigbird": {root@pe-server-238c28-1 development (development)$     # these don't work# custom fact 'bigbird' is not returned unexpectedlyroot@pe-server-238c28-1 development (development)$ facter --json | grep -E "(oslogin|[^/]bigbird)"    "oslogin": {root@pe-server-238c28-1 development (development)$     # no facts returned AND an error is thrownroot@pe-server-238c28-1 development (development)$ facter -p --no-external-facts | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:08.334765 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:15.077332 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:21.438824 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:28.317694 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$  {code}  ```    

Jira (FACT-3192) Custom fact fails to appear when using some options like --json

2023-03-17 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3192  
 
 
  Custom fact fails to appear when using some options like --json   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2023/03/17 6:42 AM  
 
 
Labels: 
 jira_escalated  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
     
 
I can see my ``bigbird`` custom fact as expected: 
   ``` root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p bigbird {   role => "role::replica",   sshkey =>  {     identifier => "pe-server-238c28-1.us-west1-b.c.customer-support-scratchpad.internal",     key => "LONGLONGLONGPUBLICKEY",     type => "ssh-rsa"   } }   root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p | grep bigbird bigbird => { root@pe-server-238c28-1 pe_curl_requests (development)$ ```   
 
However, when I introduce other flags I see expected results: 
   ```bash 
 
these work 
 root@pe-server-238c28-1 development (development)$ facter -p --json | grep -E "(oslogin|[^/]bigbird)"   "bigbird": {     "oslogin": { root@pe-server-238c28-1 development (development)$ facter -p bigbird --json | grep -E "(oslogin|[^/]bigbird)"   "bigbird": { root@pe-server-238c28-1 development (development)$      
 
these don't work 
 
 
cus

Jira (PUP-11715) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC

2023-01-16 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen commented on  PUP-11715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC   
 

  
 
 
 
 

 
 I was unable to get a vmpooler Solaris instance running to do any tests against, e.g.,     {{➜ my_vmpooler_setup git:(development) ✗ be floaty get solaris-11-x86_64 --trace  + bundle exec floaty get solaris-11-x86_64 --trace bundler: failed to load command: floaty (/Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/bin/floaty) Traceback (most recent call last): 26: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/bin/bundle:23:in `' 25: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/bin/bundle:23:in `load' 24: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/exe/bundle:36:in `' 23: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/friendly_errors.rb:120:in `with_friendly_errors' 22: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/exe/bundle:48:in `block in ' 21: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli.rb:25:in `start' 20: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start' 19: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli.rb:31:in `dispatch' 18: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch' 17: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' 16: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' 15: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli.rb:486:in `exec' 14: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli/exec.rb:23:in `run' 13: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli/exec.rb:58:in `kernel_load' 12: from /Users/gavin.didrichsen/.gem/ruby/2.7.5/gems/bundler-2.3.24/lib/bundler/cli/exec.rb:58:in `load' 11: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/bin/floaty:23:in `' 10: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/bin/floaty:23:in `load' 9: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/vmfloaty-1.7.0/bin/floaty:8:in `' 8: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/vmfloaty-1.7.0/lib/vmfloaty.rb:582:in `run' 7: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!' 6: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:58:in `run!' 5: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command' 4: from /Users/gavin.didrichsen/@REFERENCES/github/app/parent/environments/cloud/vmpooler/my_vmpooler_setup/.direnv/ruby/gems/ruby/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run' 3: from /Users/gavin.didrichsen/@REFER

Jira (PUP-11715) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC

2023-01-16 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11715  
 
 
  Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 
 
Zendesk Ticket Count: 
 1  
 
 
Zendesk Ticket IDs: 
 50697  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





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

Jira (PUP-11715) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC

2023-01-16 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11715  
 
 
  Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC   
 

  
 
 
 
 

 
Change By: 
 Gavin Didrichsen  
 
 
Summary: 
 {brief summary of issue} Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





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

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

2023-01-16 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11715  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2023/01/16 9:03 AM  
 
 
Labels: 
 escalation  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
 puppet-team-phoenix-public   A Swisscom customer 50697 claims that on their Solaris server facter is failing to return expected results. 12 replies 
 For example: With Facter 4.2.5 (PE 2021.x), we face the following bug: Accessing fact ldom is OK: (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom  { domainchassis => "1249BDYDE1", domaincontrol => "oc-master-02-cd", domainname => "vdcf-mgmt-gd", domainrole =>  { control => "false", impl => "LDoms", io => "false", root => "false", service => "false" } , domainuuid => "edad1f61-ec07-efd1-f7da-fda1a9f35547" } Accessing ldom.domainrole is also OK: (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole { control => "false", impl => "LDoms", io => "false", root => "false", service => "false" }   However, Accessing subitems of ldom.control do not work: (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl (0)MGMT(gDom)root@vdcf-mgmt-gd:~#  However, when running the same command in debug mode, we see the value was successfully resolved to LDoms: (130)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl --debug [2023-01-11 18:38:00.437408 ] INFO Facter - executed with command line: ldom.domainrole.impl --debug  [2023-01-11 18:38:00.437982 ] DEBUG Facter - Facter version: 4.2.5  [2023-01-11 18:38:00.442361 ] DEBUG Facter::FactManager - Resolving facts sequentially  [2023-01-11 18:38:00.442909 ] DEBUG Facter::FactLoader - Loading all internal facts  [2023-01-11 18:38:00.443405 ] DEBUG Facter::FactLoader - Loading custom facts  [2023-01-11 18:38:00.447715 ] DEBUG Facter::FactLoader - Loading external facts  [2023-01-11 18:38:00.448624 ] DEBUG LegacyFacter::Util::DirectoryLoader - Fact file /opt/puppetlabs/facter/facts.d/application.txt was pars

Jira (PUP-11686) Windows Alteryx package resource causing fact failure

2022-12-05 Thread Gavin Didrichsen (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Didrichsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11686  
 
 
  Windows Alteryx package resource causing fact failure   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2022/12/05 8:18 AM  
 
 
Labels: 
 jira_escalated  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Gavin Didrichsen  
 

  
 
 
 
 

 
 Puppet Version: Puppet Server Version: OS Name/Version: facter on windows servers returns non-UTF characters {{msi_info:}}   "Alteryx 2020.2 x64 Server (Remove only)\0e\0\0\0\x11":  version: 2020.2.3.27789  vendor: Alteryx installdate: '' {{...}} {} The short-term workaround is to disable package inventory collection on these nodes or remove this package. Please open a Jira ticket for this issue. Desired Behavior: 
 
Windows fact gathering should work stripping out troublesome non-UTF characters 
 Actual Behavior: 
 
Windows facts are failing to insert into puppetdb with errors: 
   ``` 2022-11-21T01:47:08.618Z ERROR [p.p.command] [842,189,640] [replace facts] Exceeded max attempts (5) for hkwvadapp436.zone1.scbdev.net [Ljava.lang.Throwable;@7f2a2006 2022-11-21T01:49:07.293Z ERROR [p.p.command] [842,262,475] [replace facts] Retrying after attempt 4 for hkwvadapp436.zone1.scbdev.net, due to: org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 [Ljava.lang.Throwable;@7f2a2006 2022-11-21T02:21:21.094Z ERROR [p.p.command] [842,370,208] [replace facts] Retrying after attempt 3 for hkwvadapp436.zone1.scbdev.net, due to: org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 [Ljava.lang.Throwable;@7f2a2006 2022-11-21T02:29:53.884Z ERROR [p.p.command] [842,457,322] [replace facts] Ret