https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • m
    I was trying to create a release for 
    ipset
    module (though I don't know yet, if I belong to proper group in Voxpupuli, but I'll discover it soon). I was using the instructions on Voxpupuli and I ran the command: 
    bundle exec rake release
    I got this error: 
    remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
    1. I can create a PR for Voxpupuli website and amend the command (what was the repo name for the website? 🙂 ) 2. do you know the correct command on top of your head?
  • m
    message has been deleted
  • b
    first you nee fto use the changelog task to update changelog.md and propose that in a PR
  • b
    or was that already done?
  • m
    @bastelfreak entirely wrong procedure.... 🙂 sorry
  • v
  • s
    This message was deleted.
    y
    y
    • 3
    • 3
  • v
    FYI, 
    puppet/rhsm 5.1.0
    added a resource dependency cycles
  • d
  • v
    Copy code
    File[/etc/yum.repos.d/redhat.repo] => Class[Rhsm] => Class[Yum] => File[/etc/yum.repos.d] => File[/etc/yum.repos.d/redhat.repo
  • b
    mhm, why didn't we see that in our tests
  • b
    is that coming from the yum module?
  • a
  • a
  • a
    @vchepkov But are you the one defining the relationship between 
    Class[Rhsm]
    and 
    Class[Yum]
    in your profiles?
  • a
  • a
    (Not much point in declaring it otherwise)
  • v
    Yes, yum requires rhsm in my profile. system should be subscribed before configuration adjusted
  • v
    imho, yum should leave file alone, not rhsm
  • v
    also, that yum code is questionable. It assumes that yumrepo creates a file resource. that's not the case
    Copy code
    # grep -E "yumrepo|yum.repos.d" /opt/puppetlabs/puppet/cache/state/resources.txt 
file[/etc/yum.repos.d]
yumrepo[epel]
yumrepo[vvc]
yumrepo[vvc-source]
yumrepo[choria_release]
yumrepo[choria_nightly]
yumrepo[puppet-tools]
file[/etc/yum.repos.d/pe_repo.repo]
file[/etc/yum.repos.d/pc_repo.repo]
yumrepo[puppet_enterprise]
  • v
    so it would fight with yumrepo each time
  • v
    I address it differently, with a purge resource
    Copy code
    if $purge_enable {
      # disable unauthorized repositories
      purge { 'yumrepo':
        manage_property => 'enabled',
        state           => '0',
        unless          => ['baseurl', '=~', $satellite::client::server],
      }
    }
  • l
    @bastelfreak any thoughts on what would cause
    Copy code
    Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/splunk_config: Could not autoload puppet/provider/splunk_metadata/ini_setting: no such file to load -- puppet/util/ini_file
    on first run (or on puppet apply and how to fix it in tests)
  • b
    did you run puppet generate types?
  • l
    no, I can add that to the deployment code which might fix the on-puppet-run, but it doesnt' solve for unit testing
  • b
    give it a try. depending on the PE/r10k version this might already be executed
  • b
    which tests fail? the unit tests for our splunk module?
  • l
    specifically a tests for my splunk profile
  • l
    I was having to work around a cgroupsv2 issue in the systemd unit file splunk generates
  • l
    for el9
1...113114115...648Latest