Jira (FACT-3093) Facter fails to resolve custom/environment facts in some circumstances
Title: Message Title Adam Tkac created an issue Facter / FACT-3093 Facter fails to resolve custom/environment facts in some circumstances Issue Type: Bug Affects Versions: FACT 4.2.5 Assignee: Unassigned Components: Facter 4 Created: 2021/11/10 2:08 AM Environment: CentOS 8 Stream facter 4.2.5 Priority: Normal Reporter: Adam Tkac Hello facter upstream, when upgrading facter from 4.0.51 to the latest (4.2.5), I found that under certain circumstances, facter fails to resolve custom/environment facts. Reproducer: $ cat facter/1.rb Facter.add(:ec2data_type) do setcode do "cl_ftp"
Jira (FACT-3092) Retrieve of two facts consecutively via API fails with facter 4.2.5
Title: Message Title Adam Tkac created an issue Facter / FACT-3092 Retrieve of two facts consecutively via API fails with facter 4.2.5 Issue Type: Bug Affects Versions: FACT 4.2.5 Assignee: Unassigned Created: 2021/11/09 7:24 AM Environment: Linux, CentOS 8.4 ruby -v ruby 2.5.9p229 (2021-04-05 revision 67939) [x86_64-linux] facter 4.2.5 Priority: Normal Reporter: Adam Tkac Hello facter upstream, During upgrade of facter from version 4.0.51 to 4.2.5, we spotted issue that on our AWS EC2 instances facter API fails to retrieve some facts when we call Facter.value multiple times in a row. Reproducer: $ facter -v 4.2.5
Jira (FACT-3057) Facter ruby API/binding fails to resolve facts from environment variables
Title: Message Title Adam Tkac created an issue Facter / FACT-3057 Facter ruby API/binding fails to resolve facts from environment variables Issue Type: Bug Affects Versions: FACT 4.2.2 Assignee: Unassigned Created: 2021/07/23 1:12 AM Priority: Normal Reporter: Adam Tkac Hello, during regular upgrade of our puppet ecosystem, we upgraded facter from 4.0.51 version to 4.2.2 version and hit issue, that ruby API/bindings fails to resolve facts from environment variables. Reproducer: # cat fact.rb require 'facter' puts(Facter.value(:myfact))
Jira (FACT-2846) Facter 4 fails to parse linux tun* interfaces on our openvpn server
Title: Message Title Adam Tkac commented on FACT-2846 Re: Facter 4 fails to parse linux tun* interfaces on our openvpn server Thank you for the fix! We will test it when we spot new facter release on github/rubygems if you don't mind 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.375629.1603354499000.85753.1606219980134%40Atlassian.JIRA.
Jira (FACT-2846) Facter 4 fails to parse linux tun* interfaces on our openvpn server
Title: Message Title Adam Tkac created an issue Facter / FACT-2846 Facter 4 fails to parse linux tun* interfaces on our openvpn server Issue Type: Bug Affects Versions: FACT 4.0.43 Assignee: Unassigned Components: Facter 4 Created: 2020/10/22 1:14 AM Environment: Linux, up2date CentOS 7.8 Working: # facter --version 3.14.10 Non-working (missing interfaces in networking fact): # facter --version 4.0.43 Priority: Normal Reporter:
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Adam Tkac commented on PUP-2169 Re: Not possible to manage SELinux file contexts via puppet in a sane way I created new ticket PUP-10548 to track issue mentioned by Ewoud Kohl van Wijngaarden and Nathan Ward (selinux policy RPM updated via puppet and subsequent wrong file contexts) 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.31124.1396878028000.94447.1593020340122%40Atlassian.JIRA.
Jira (PUP-10548) Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy
Title: Message Title
Adam Tkac created an issue
Puppet / PUP-10548
Wrong SELinux contexts on files if puppet installs new rpm with SELinux policy
Issue Type:
Bug
Affects Versions:
PUP 6.15.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2020/06/24 10:36 AM
Priority:
Normal
Reporter:
Adam Tkac
Puppet Version: 6.15.0 Puppet Server Version: not applicable, we don't use it in our environment (we use "git pull && puppet apply -e " on every node) OS Name/Version: CentOS 7.8 In our company, we have custom SELinux policy shipped in rpm. When we deploy new instance, our puppet recipes installs SELinux policy rpm and then create various file resources. However those resources are created with wrong SELinux labels because puppet doesn't refresh selinux contexts on file resources after new package is installed. To get proper file contexts, we must run puppet twice (first run install SELinux policy and the second run fixes file contexts) In our environment, we use something like this:
package { 'gdc-selinux':
ensure => latest;
