# voxpupuli
- b
bastelfreak
07/27/2022, 8:19 PMugh 😞 - b
bastelfreak
07/27/2022, 8:19 PMsplunk-- - d
Dr Bunsen Honeydew
07/27/2022, 8:19 PMsplunk lost a life. (Karma: -1) - l
Lumiere
07/27/2022, 8:19 PMyep - t
tvaughan
07/27/2022, 8:19 PMOooh.... splunk-- - d
Dr Bunsen Honeydew
07/27/2022, 8:19 PMsplunk lost a level. (Karma: -2) - l
Lumiere
07/27/2022, 8:20 PMthey ExecStart a couple of chmod/chown in cgroupsv1 paths, which ofc don't exist in el9 - b
bastelfreak
07/27/2022, 8:20 PMthat's exactly how I imagine "enterprise" software - b
bastelfreak
07/27/2022, 8:21 PMthe error you posted, is that coming from your module that wraps ours, or do you not use the vox pupuli module at all? - l
Lumiere
07/27/2022, 8:24 PMit's coming from a random provider in voxpupuli/splunk - l
Lumiere
07/27/2022, 8:24 PMthe provider changes on every test - b
bastelfreak
07/27/2022, 8:25 PMmhm - l
Lumiere
07/27/2022, 8:25 PMbecause type/splunk_config uses inifile / ini_setting - b
bastelfreak
07/27/2022, 8:25 PMI saw that in the past - b
bastelfreak
07/27/2022, 8:26 PMsometimes generate types helped. sometimes the issue was multiple environment on puppetserver with different versions of the module - b
bastelfreak
07/27/2022, 8:26 PMbut how that's happening in the tests, good question - l
Lumiere
07/27/2022, 8:26 PMso, generally first run after a deploy does it and then puppet autogenerates types and next run succeeds - l
Lumiere
07/27/2022, 8:27 PMso puppet generate types will likely help that, but it's honestly the tests that have me very confused - b
bastelfreak
07/27/2022, 8:27 PMwhere do the tests fail? In our CI for the module or in your infra? - l
Lumiere
07/27/2022, 8:28 PMon my local system running pdk test unit - l
Lumiere
07/27/2022, 8:29 PMCopy codepdk (INFO): Using Ruby 2.5.9 pdk (INFO): Using Puppet 6.27.0 [✔] Preparing to run the unit tests. /opt/puppetlabs/pdk/private/ruby/2.5.9/bin/ruby -I/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/gems/rspec-core-3.11.0/lib:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/gems/rspec-support-3.11.0/lib /opt/puppetlabs/pdk/share/cache/ruby/2.5.0/gems/rspec-core-3.11.0/exe/rspec --pattern spec/\{aliases,classes,defines,functions,hosts,integration,plans,tasks,type_aliases,types,unit\}/\*\*/\*_spec.rb --format progress - v
VoxBot
07/27/2022, 11:05 PMbastelfreak: o/ For the record, my 'rake reference' issue last week was probably caused by me doing nasty things: by removing the puppet-strings files from my shared bundle and re-installing, the error vanished. - k
kenyon
07/28/2022, 12:47 AM@Lumiere I was just looking at https://community.splunk.com/t5/Installation/Why-is-Systemd-broken-on-new-install/td-p/482881 yesterday for some reason. I think I also had to deal with this a while ago. yeah it’s bad. splunk-- - d
Dr Bunsen Honeydew
07/28/2022, 12:47 AMsplunk took a hit! Ouch. (Karma: -3) - v
VoxBot
07/28/2022, 11:04 AMuhhhhhhhhhhhhh https://www.youtube.com/shorts/Kq28yBigDYw - v
VoxBot
07/28/2022, 11:04 AMyou can now deploy github pages via github actions - v
VoxBot
07/28/2022, 11:05 AMpreviously, github cloned the repo and stripped a bunch of git infos from the repo - v
VoxBot
07/28/2022, 11:06 AMthat means that jekyll could not determine when/who edited a file previously. that's why at https://voxpupuli.org/docs/about_vox_pupuli/ you see: - v
VoxBot
07/28/2022, 11:06 AMPublished on Jan 1, 2016. Last updated on - v
VoxBot
07/28/2022, 11:06 AMlast-updated is missing