Jira (PUP-8997) Deprecate Faces related to CA and certificate handling
Title: Message Title Tommy McNeely commented on PUP-8997 Re: Deprecate Faces related to CA and certificate handling Usually when there is a (deprecation) warning, there is something that can be done to "fix" the situation that is causing the warning. In this case, we can't do anything except to hide all deprecation warnings. I don't think that is desirable. Until there is a solution to the deprecation, it should not appear. At a minimum, it should not appear during a "puppet agent" run (as that is in the "master" section). 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-9027) Deprecate CA-related settings in puppet.conf
Title: Message Title Tommy McNeely commented on PUP-9027 Re: Deprecate CA-related settings in puppet.conf Usually when there is a (deprecation) warning, there is something that can be done to "fix" the situation that is causing the warning. In this case, we can't do anything except to hide all deprecation warnings. I don't think that is desirable. Until there is a solution to the deprecation, it should not appear. At a minimum, it should not appear during a "puppet agent" run (as that is in the "master" section). 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-7241) AIX - Errors when parsing lsuser output with special characters (#!)
Title: Message Title Tommy McNeely commented on PUP-7241 Re: AIX - Errors when parsing lsuser output with special characters (#!) It appears that the colons are escaped with "#!" in an IPv6 address. # /usr/sbin/lsuser -c -R files root #name:id:pgrp:groups:home:shell:gecos:auditclasses:login:su:rlogin:daemon:admin:sugroups:tpath:ttys:expires:auth1:auth2:umask:registry:SYSTEM:loginretries:pwdwarntime:account_locked:minage:maxage:maxexpired:minalpha:minloweralpha:minupperalpha:minother:mindigit:minspecialchar:mindiff:maxrepeats:minlen:histexpire:histsize:fsize:cpu:data:stack:core:rss:nofiles:time_last_login:time_last_unsuccessful_login:tty_last_login:tty_last_unsuccessful_login:host_last_login:host_last_unsuccessful_login:unsuccessful_login_count root:0:system:system,bin,sys,security,cron,audit,lp:/:/usr/bin/ksh:root:general:true:false:false:true:true:system:nosak:ALL:0:SYSTEM:NONE:22:files:compat:0:0:false:0:0:-1:0:0:0:0:0:0:0:8:0:0:0:-1:-1:-1:-1:-1:-1:-1:1527849270:1533085305:ssh:ssh:fd8c#!:215d#!:178e#!:12#!:290#!:fa72#!:fab2#!:882:10.10.28.247:147 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely commented on BOLT-545 Re: upload/script/task doesn't work with --run-as on AIX (and possibly others) FYI, OSX has the same chown syntax, per the man page: SYNOPSIS chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ... chown [-fhv] [-R [-H | -L | -P]] :group file ... However, it doesn't give a syntax error (like on AIX), it just doesn't do the "primary group" thing... # chown tmcneely: testfile # ls -l testfile -rw-r--r-- 1 tmcneely wheel 0 May 29 09:21 testfile Add Comment
Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely updated an issue Puppet Task Runner / BOLT-545 upload/script/task doesn't work with --run-as on AIX (and possibly others) Change By: Tommy McNeely Summary: upload/script/task don doesn 't work with --run-as on AIX (and possibly others) 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely updated an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Change By: Tommy McNeely Method Found: Needs Assessment Customer Feedback 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely commented on BOLT-546 Re: mktemp is not available on all platform (AIX specifically) Workaround --tmpdir /tmp 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely created an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Issue Type: Bug Assignee: Unassigned Created: 2018/05/29 8:12 AM Environment: AIX 7.1 TL4 Priority: Normal Reporter: Tommy McNeely We recently were trying to run a "script" to install bash on AIX (which is not as simple as "yum install bash") and noticed that it was trying to run "mktemp" to make a temporary directory to upload the 'random' filename of the script to. While I appreciate not creating predictable temporary directories, we should probably use a more portable mechanism, or at least test for its existence (similar to how the PE install.bash does). Add Comment
Jira (BOLT-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely commented on BOLT-545 Re: upload/script/task don't work with --run-as on AIX (and possibly others) Alternatively, you can just remove the ":" because the group ownership of the file matching the run-as user is not likely to really matter. 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 (HI-600) Hiera is Incorrectly detecting tabs (\t) as indent characters, when they are separation characters
Title: Message Title Tommy McNeely created an issue Hiera / HI-600 Hiera is Incorrectly detecting tabs (\t) as indent characters, when they are separation characters Issue Type: Bug Assignee: Unassigned Created: 2018/04/24 2:59 PM Environment: CentOS 7.5 x86_64, Puppet Enterprise 2017.3.5 Priority: Normal Reporter: Tommy McNeely While adding saz-ssh, and the requisite hieradata, I copied some entries from /etc/ssh/sshd_config to the hiera key `ssh::server_options` and added the colons and indenting. The "AuthorizedKeysFile" apparently has a "tab" character between the key and value in the config file. Here is a very small snippet of the hiera config: hieradata/common.yaml # # ssh: https://forge.puppet.com/saz/ssh # NOTE: Remember to put 'yes' or 'no' in quotes so that it is a "string" and not a boolean (True/False)
Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Tommy McNeely updated an issue Puppet / PUP-8650 Repository error message uri is missing part of the path Note: Also affects 5.5.0 $ puppet module --debug --module_repository https://artifactory.domain.com/bogus_test/puppet/ search test Debug: Runtime environment: puppet_version=5.5.0, ruby_version=2.4.3, run_mode=user, default_encoding=UTF-8 Notice: Searching https://artifactory.domain.com/bogus_test/puppet/ ... Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Failed to load library 'pe_license' for feature 'pe_license': cannot load such file -- pe_license Debug: HTTP GET https://artifactory.domain.com/bogus_test/puppet//bogus_test/puppet/v3/modules?query=test Error: Request to Puppet Forge failed. The server being queried was https://artifactory.domain.com/v3/modules?query=test The HTTP response we received was '404 Not Found' Error: Try 'puppet help module search' for usage
Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Tommy McNeely created an issue Puppet / PUP-8650 Repository error message uri is missing part of the path Issue Type: Bug Affects Versions: PUP 5.3.5 Assignee: Unassigned Created: 2018/04/09 2:43 PM Environment: CentOS 7.4, Puppet Enterprise 2017.3.5 (puppet-agent 5.3.5) Priority: Normal Reporter: Tommy McNeely We had a problem with our artifactory server, where it would return a 404 for the Puppet repository it was providing. This caused an error message to appear, about 404 errors. I tried to install the module manually (or search for it) and also got a 404 error: [root@puppetmaster ~]# puppet module --debug search saz-sudo Debug: Runtime environment: puppet_version=5.3.5, ruby_version=2.4.3, run_mode=user, default_encoding=UTF-8 Notice: Searching https://artifactory.domain.com/artifactory/api/puppet/puppet ...
Jira (FACT-1827) AIX hardwaremodel (os -> hardware) fact is non-standard
Title: Message Title Tommy McNeely commented on FACT-1827 Re: AIX hardwaremodel (os -> hardware) fact is non-standard https://github.com/mcanevet/rspec-puppet-facts/pull/71 This should workaround the non-standard hardwaremodel, I think. The test is hardcoded to work against the facts that I submitted, but maybe someone who is better with rspec can make it more generic? 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-1827) AIX hardwaremodel (os -> hardware) fact is non-standard
Title: Message Title Tommy McNeely created an issue Facter / FACT-1827 AIX hardwaremodel (os -> hardware) fact is non-standard Issue Type: Bug Affects Versions: FACT 3.9.4 Assignee: Unassigned Created: 2018/03/02 1:58 PM Environment: AIX 7.1 TL4 (powerpc) - PE 2017.3.4 (facter 3.9.4) Priority: Normal Reporter: Tommy McNeely Was setting up rspec testing on a module after porting it to AIX and the facts are not being found. Part of the problem is that the default "hardwaremodel" filter is `x86_64`. It does have other OS cases for Solaris (i86pc) and BSD (amd64) for example. While we could add a case for AIX https://github.com/mcanevet/rspec-puppet-facts/issues/69 . The problem is, as I started looking, it looks like the "hardwaremodel" is populated with the actual product name model of the machine (such as "IBM,8284-22A"), while other OS's seem to use something like the processor architecture (x86_64). I think that hardware information belongs in a different fact, like maybe productname (based on what I am seeing on OSX) and the hardwaremodel fact should be "powerpc"
Jira (FACT-1024) Facter can't handle non-ascii ec2_userdata
Title: Message Title Tommy McNeely commented on FACT-1024 Re: Facter can't handle non-ascii ec2_userdata We just experienced this as well... We used Terraform to create the EC2 instance, and it has a gzip'd multi-part mime body. I am sure its the gzip'd (binary) data in user-data that is causing it heartburn. We just commented it out for now. Tommy Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
