Jira (FACT-3201) Facter should report macOS "extra" version from Rapid Security Response updates
Title: Message Title Aria Li updated an issue Facter / FACT-3201 Facter should report macOS "extra" version from Rapid Security Response updates Change By: Aria Li Team: Phoenix 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.485206.1683227494000.11738.1683663060029%40Atlassian.JIRA.
Jira (FACT-3180) Facter mixes up OracleLinux and Redhat
Title: Message Title Josh Cooper updated an issue Facter / FACT-3180 Facter mixes up OracleLinux and Redhat Change By: Josh Cooper Fix Version/s: FACT 4.4.1 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.479622.1674731331000.11710.1683658200108%40Atlassian.JIRA.
Jira (FACT-3180) Facter mixes up OracleLinux and Redhat
Title: Message Title Josh Cooper commented on FACT-3180 Re: Facter mixes up OracleLinux and Redhat This was fixed in https://github.com/puppetlabs/facter/pull/2572#issuecomment-1539143483. Note the new behavior sets os.distro.id to Ol not RedHatEnterpriseServer 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.479622.1674731331000.11709.1683658200047%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Chris Payne commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows This doesn't seem to work properly. I have enable => delayed and I see this running puppet agent -t: Notice: /Stage[main]/Profile::Myservice/Service[svc test]/enable: enable changed 'true' to 'delayed' (corrective) But the actual service goes to "Automatic," not "Automatic (Delayed)." The registry key that should be modified is Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svc test\DelayedAutostart But puppet doesn't seem to do anything here. 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.135151.1464896598000.11695.1683657480023%40Atlassian.JIRA.
Jira (FACT-3199) facts with regular expression matching characters in the name of the fact cause facter 4 to crash
Title: Message Title Josh Cooper updated an issue Facter / FACT-3199 facts with regular _expression_ matching characters in the name of the fact cause facter 4 to crash Change By: Josh Cooper Priority: Normal Major 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.485170.1683128012000.11726.1683661800035%40Atlassian.JIRA.
Jira (FACT-3201) Facter should report macOS "extra" version from Rapid Security Response updates
Title: Message Title Aria Li commented on FACT-3201 Re: Facter should report macOS "extra" version from Rapid Security Response updates Hi Clay Caviness thank you for the PR! We don't currently support macOS 13 but this would be a helpful feature, we'll review your PR later when we add support for macOS 13. 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.485206.1683227494000.11740.1683663120080%40Atlassian.JIRA.
Jira (FACT-3201) Facter should report macOS "extra" version from Rapid Security Response updates
Title: Message Title Aria Li updated an issue Facter / FACT-3201 Facter should report macOS "extra" version from Rapid Security Response updates Change By: Aria Li Epic Link: PA-4773 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.485206.1683227494000.11739.1683663120034%40Atlassian.JIRA.
Jira (FACT-3199) facts with regular expression matching characters in the name of the fact cause facter 4 to crash
Title: Message Title Aria Li updated an issue Facter / FACT-3199 facts with regular _expression_ matching characters in the name of the fact cause facter 4 to crash Change By: Aria Li Epic Link: PA-5411 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.485170.1683128012000.11748.1683663480033%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Charmaine Pritchett updated an issue PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Charmaine Pritchett Labels: jira_escalated 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.484959.1682619597000.11441.1683631200104%40Atlassian.JIRA.
Jira (PDB-5633) Investigate why (some?) command discards aren't including the stack
Title: Message Title Charmaine Pritchett updated an issue PuppetDB / PDB-5633 Investigate why (some?) command discards aren't including the stack Change By: Charmaine Pritchett Zendesk Ticket Count: 1 Zendesk Ticket IDs: 51495 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.484959.1682619597000.11440.1683631200039%40Atlassian.JIRA.
Jira (FACT-3180) Facter mixes up OracleLinux and Redhat
Title: Message Title Bernhard Suttner commented on FACT-3180 Re: Facter mixes up OracleLinux and Redhat I don't know if facter 3 did this different. AFAIK, the "id" should not point to Redhat, if the server is actually a Oracle. 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.479622.1674731331000.11435.1683627660027%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title
Diana Scannicchio commented on FACT-3186
Re: facter 4.2.13: bug "facter partitions"
Hi Josh Cooper , as mentioned there is no disk on the node which is netbooted, the OS is in memory: [root@sbc-tbed-717 ~]# df -hl Filesystem Size Used Avail Use% Mounted on none 512M 136M 377M 27% / devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 112M 1.8G 6% /run tmpfs 100K 4.0K 96K 4% /dev/shm tmpfs 100K 0 100K 0% /mnt tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /tmpfs 64M 0 64M 0% /var/atlas AFS 2.0T 0 2.0T 0% /afs tmpfs 374M 0 374M 0% /run/user/42056 tmpfs 374M 0 374M 0% /run/user/0 Puppet apply is run puppet apply $PUPOPT --config=/mnt/bwm/prod/puppet/puppet.conf --onetime --no-daemonize $@ /mnt/bwm/prod/puppet//manifests/ --modulepath=/mnt/bwm/atds_puppet_modules_macro The area is mounted like that tbed-storage-bwm:/exports/bwm on /mnt/bwm type nfs4 (ro,noatime,vers=4.1,rsize=32768,wsize=32768,namlen=255,soft,proto=tcp,timeo=100,retrans=2,sec=sys,clientaddr=10.193.24.19,local_lock=none,addr=10.193.2.105) I pasted below the output of the script you suggested. Note "nil" in the first line cause by the issue described. Thank you very much abd cheers, Diana [root@sbc-tbed-717 ~]# /opt/puppetlabs/puppet/bin/ruby test.rb nil [{:device=>"10.193.2.107:/clients/cc7/79_20221130/x86_64", :filesystem=>"nfs4", :path=>"/readonly", :options=> ["rw", "relatime", "vers=4.1", "rsize=1048576", "wsize=1048576", "namlen=255", "hard", "proto=tcp", "timeo=600", "retrans=2", "sec=sys", "clientaddr=10.193.24.19", "local_lock=none", "addr=10.193.2.107"], :size_bytes=>105554903040, :available_bytes=>40687894528, :used_bytes=>59481522176, :capacity=>"59.38%", :size=>"98.31 GiB", :available=>"37.89 GiB", :used=>"55.40 GiB"}, {:device=>"rpc_pipefs", :filesystem=>"rpc_pipefs", :path=>"/readonly/var/lib/nfs/rpc_pipefs", :options=>["rw", "relatime"], :size_bytes=>0, :available_bytes=>0, :used_bytes=>0, :capacity=>"100%", :size=>"0 bytes", :available=>"0 bytes", :used=>"0 bytes"}, {:device=>"none", :filesystem=>"tmpfs", :path=>"/", :options=>["rw", "relatime", "size=524288k", "nr_inodes=0", "mode=755"], :size_bytes=>536870912, :available_bytes=>394506240, :used_bytes=>142364672, :capacity=>"26.52%", :size=>"512.00 MiB", :available=>"376.23 MiB", :used=>"135.77 MiB"}, {:device=>"10.193.2.107:/clients/cc7/79_20221130/x86_64/usr/bin", :filesystem=>"nfs4", :path=>"/bin", :options=> ["rw", "relatime", "vers=4.1", "rsize=1048576", "wsize=1048576", "namlen=255", "hard", "proto=tcp", "timeo=600", "retrans=2", "sec=sys", "clientaddr=10.193.24.19", "local_lock=none", "addr=10.193.2.107"], :size_bytes=>105554903040, :available_bytes=>40687894528, :used_bytes=>59481522176, :capacity=>"59.38%", :size=>"98.31 GiB", :available=>"37.89 GiB", :used=>"55.40 GiB"}, {:device=>"10.193.2.107:/clients/cc7/79_20221130/x86_64/boot", :filesystem=>"nfs4", :path=>"/boot", :options=> ["rw", "relatime", "vers=4.1", "rsize=1048576", "wsize=1048576", "namlen=255", "hard", "proto=tcp", "timeo=600", "retrans=2", "sec=sys", "clientaddr=10.193.24.19", "local_lock=none", "addr=10.193.2.107"], :size_bytes=>105554903040, :available_bytes=>40687894528, :used_bytes=>59481522176, :capacity=>"59.38%", :size=>"98.31 GiB", :available=>"37.89 GiB", :used=>"55.40 GiB"},
Jira (PUP-11830) Declare Stop Ship Line (code complete) milestone (Puppet Platform 8.0.0)
Title: Message Title Mae Caballes commented on PUP-11830 Re: Declare Stop Ship Line (code complete) milestone (Puppet Platform 8.0.0) From: Mae Caballes Date: Monday, April 24, 2023 at 5:51 PM To: Team-Skeletor , Team-Dumpling , team-phoenix , Team Nimbus , Puppet Team Release Engineering , Ingrida Cazers , Parker Leach Cc: Jason Dennis , Nirupama Mantha , Aaron Robinson , David Piekny , Lisa Ross , Jaleen Walker , Micah Wilson Subject: Re: Release Milestones Target Dates || Puppet 8- GO for April 25th release Hello All, Puppet 8 reached Feature Complete last week; today, we have an official GO to kick off release activites tomorrow – April 25th. Thank you, Mae 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.484354.168132560.11465.1683641820125%40Atlassian.JIRA.
Jira (PUP-11833) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 8.0.0)
Title: Message Title Mae Caballes commented on PUP-11833 Re: Declare Ready to Ship (go/no-go) milestone (Puppet Platform 8.0.0) From: Mae Caballes Date: Monday, April 24, 2023 at 5:51 PM To: Team-Skeletor , Team-Dumpling , team-phoenix , Team Nimbus , Puppet Team Release Engineering , Ingrida Cazers , Parker Leach Cc: Jason Dennis , Nirupama Mantha , Aaron Robinson , David Piekny , Lisa Ross , Jaleen Walker , Micah Wilson Subject: Re: Release Milestones Target Dates || Puppet 8- GO for April 25th release Hello All, Puppet 8 reached Feature Complete last week; today, we have an official GO to kick off release activites tomorrow – April 25th. Thank you, Mae 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.484358.1681325603000.11469.1683641880177%40Atlassian.JIRA.
Jira (PUP-10589) Provide the ability to generate a CSR without submitting to the CA
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10589 Provide the ability to generate a CSR without submitting to the CA Change By: Josh Cooper Team: Coremunity Phoenix 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.366691.1595280947000.11622.1683652140033%40Atlassian.JIRA.
Jira (PUP-10589) Provide the ability to generate a CSR without submitting to the CA
Title: Message Title Nick GW commented on PUP-10589 Re: Provide the ability to generate a CSR without submitting to the CA Please implement this, it'd be super handy for working with external CAs 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.366691.1595280947000.11623.1683652140096%40Atlassian.JIRA.
Jira (PUP-10589) Provide the ability to generate a CSR without submitting to the CA
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10589
Provide the ability to generate a CSR without submitting to the CA
Change By:
Josh Cooper
The https://github.com/puppetlabs/puppet-agent-bootstrap application was created to allow the agent to generate a CSR in a way that doesn't requires network access to the CA (since the CA requires the SSL client to provide a client certificate, which the agent doesn't have yet).The application uses {{Puppet::SSL::Host.localhost}} to accomplish this and it works in 5.5.x. However, the version in puppet#master does not due to:{noformat}git bisect goodde34cc03d570a7f06b117c1f1387c40cb6353377 is the first bad commitcommit de34cc03d570a7f06b117c1f1387c40cb6353377Author: Maggie Dreyer Date: Mon Aug 27 17:09:13 2018 -0700(PUP-8912) Remove CertificateAuthority, fixup HostThis commit removes the CertificateAuthority class and begins cleaningup the consequences:* Remove CA logic from SSL::Host* Remove certificate_status indirection* Remove CA logic from ssl_file* Get Host unit tests passing{noformat}In particular, the `Host#ca_location=` method was removed which the bootstrap application used to set to `:none`, to prevent the Host from accessing the CA.We should add a {{puppet ssl generate_csr}} action to generate the private key and CSR, but not submit the CSR. Once that's done, puppet-agent-bootstrap could be deprecated and archived. *UPDATE*It would be fairly trivial to implement this. The {{puppet ssl}} application needs a new action to generate the CSR. It needs to implement this section of code to [load or generate the private key and generate the CSR|https://github.com/puppetlabs/puppet/blob/ad7d75b08dfff5e308fde199407d84308d74e538/lib/puppet/application/ssl.rb#L164-L176]. And then call {{puts csr.to_text}} to write the contents to stdout. Also needs a test in spec/unit/application/ssl_spec.rb
Add Comment
