allow(Facter:Util:Resolution).to receive(:which).with('lldpctl').and_return('/usr/sbin/lldpctl')

gussing you have lldpctl in your path

ha

lol

thanks

np

I got a bunch of ruby errors.... I suspect my super new ruby is to blame.

I run on Ruby 3.1 with Fedora 36, mostly works

you get some deprecation warnings, but functionally it works for me

hmmm, I must be doing something wrongly then....

so what are the errors you see?

I'm getting a giant stack trace on

bundle exec rake changelog

I'll see about just spinning up a container with an older ruby

Does https://github.com/voxpupuli/puppet-logrotate/pull/200 look right?

Does https://github.com/voxpupuli/puppet-logrotate/pull/200 look right?

Hi I’m having a problem with a

systemd

call which fails with

Exec[systemd-solr.service-systemctl-daemon-reload] failed: 'systemctl daemon-reload' is not qualified and no path was specified.

Just wondering if this is a os specific thing - and if anyone has come across it before? I’ve tried with

systemd::daemon_reload { 'solr':
    enable => false
  }

but to no avail. I don’t really understand what

systemd

is actually doing in this case.

# site/profile/manifests/solr.pp

[4:22 PM] # Profile to install Apache Solr
class profile::solr {
  class { '::systemd': }

  systemd::daemon_reload { 'solr':
    enable => false
  }

  class { '::solr':
    version => '8.5.1',
  }
}

Any pointers greatly appreciated!

Hi I’m having a problem with a

systemd

call which fails with

Exec[systemd-solr.service-systemctl-daemon-reload] failed: 'systemctl daemon-reload' is not qualified and no path was specified.

Just wondering if this is a os specific thing - and if anyone has come across it before? I’ve tried with

systemd::daemon_reload { 'solr':
    enable => false
  }

but to no avail. I don’t really understand what

systemd

is actually doing in this case.

# site/profile/manifests/solr.pp

[4:22 PM] # Profile to install Apache Solr
class profile::solr {
  class { '::systemd': }

  systemd::daemon_reload { 'solr':
    enable => false
  }

  class { '::solr':
    version => '8.5.1',
  }
}

Any pointers greatly appreciated!

what do you see when you do

puppet facts show path

also I suggest to fix the solr module if it requires a daemon reload

the test is

frozen_string_literal: true

require 'puppet_helper'

describe 'profile::solr' do
  include PuppetHelper

  context 'when there is a Linux kernel' do
    let(:facts) { {
      'path' => '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
      'kernel' => 'Linux',
      'osfamily' => 'RedHat',
      'os' => { 'family' => 'RedHat', 'name' => 'RedHat', 'release' => { 'full' => '7.7' } },
    } }
    it { should contain_class('solr') }
  end
end

but the catalogue fails nevertheless

I highly recommend switching to rspec-puppet-facts

does only the test fail or also the actual puppet run?

actually that test passes - so it is a dependency fail

I’ll see what happens with

rspec-puppet-facts

and get back if I’m still having issues - thanks for your pointer

and get back if I’m still having issues - thanks for your pointer

@bastelfreak Hi! Did you ever have a crack at fixing https://github.com/kuleuven/puppet-lint-manifest_whitespace-check/issues/10 ?