https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • b
    @vchepkov, the behavior is the same if you use 'gpg-pubkey' instead of kernel-devel. The rpm command that dnf uses to report the current version of kernel-devel might be something to look at. 
    Debug: Executing: '/bin/dnf -d 0 -e 1 -y downgrade kernel-devel-4.18.0-425.10.1.el8_7.x86_64'
    Debug: Executing: '/bin/rpm -q kernel-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
    Error: Could not update: Failed to update to version 4.18.0-425.10.1.el8_7.x86_64, got version 4.18.0-425.13.1.el8_7; 4.18.0-425.3.1.el8; 4.18.0-372.26.1.el8_6 instead
    Error: /Stage[main]/Main/Package[kernel-devel]/ensure: change from '4.18.0-372.26.1.el8_6; 4.18.0-425.13.1.el8_7; 4.18.0-425.3.1.el8' to '4.18.0-425.10.1.el8_7.x86_64' failed: Could not update: Failed to update to version 4.18.0-425.10.1.el8_7.x86_64, got version 4.18.0-425.13.1.el8_7; 4.18.0-425.3.1.el8; 4.18.0-372.26.1.el8_6 instead
    [root@nfiv-cis-02d nfiiseed]# /bin/rpm -q kernel-devel --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}'
    kernel-devel 0 4.18.0 425.13.1.el8_7 x86_64kernel-devel 0 4.18.0 425.3.1.el8 x86_64kernel-devel 0 4.18.0 372.26.1.el8_6 x86_64[root@nfiv-cis-02d nfiiseed]#
  • v
    gpg-pubkey is not really a package, but yes, any package with multiple versions will fail
  • s
    This message was deleted.
    v
    • 2
    • 1
  • r
    @vchepkov, remove the 
    ensure => $facts['kernelrelease'],
    and do three packages like :
    Copy code
    package { 'kernel-devel-<version>':
    👀 1
    clapping 1
    🤔 1
  • r
    with a simple 
    ensure => present'
  • r
    with a simple 
    ensure => present'
  • v
    brilliant, thanks
  • y
    Didn’t know it’s possible 🤔
  • v
    it's a workaround for sure 🙂
  • r
    my question would be how to use the stdlib 
    fact
    function in a string vs 
    ${facts[]}
    . If it requires converting to a var, no thanks. Something like
    Copy code
    package { "kernel-devel-${facts['kernel']['release']}"
  • r
    but with the function
  • v
    I think kernelrelease is not a legacy fact
  • v
    But it would work like this if it was
    Copy code
    package { "kernel-devel-${fact('kernel.release')}": }
  • r
    cool. Thanks
  • r
    I'm still mentally trying to make the shift
  • r
    not sure if it is worth in it strings. (Unless it is deeply nested, maybe)
  • v
    Copy code
    # puppet facts show kernelrelease --no-include_legacy_facts
{
  "kernelrelease": "4.18.0-425.13.1.el8_7.x86_64"
}
  • v
    seems normal fact
  • v
    but then it shows 
    operatingsystem
    too ¯\_(ツ)_/¯
  • v
    Copy code
    puppet facts show --no-include_legacy_facts|grep kernel
  "kernelmajversion": "4.18",
  "kernelrelease": "4.18.0-425.13.1.el8_7.x86_64",
  "kernelversion": "4.18.0",
  "kernel": "Linux",
  • r
    hrmmmm
  • s
    This message was deleted.
    m
    • 2
    • 1
  • d
    Unfortunately not. I need to keep a better eye on where those are, I forget they move around and can be close
    👍 1
  • k
    Can opensource puppetservers use puppetdbCLI w/o violating puppet licensing? https://www.puppet.com/docs/puppetdb/7/pdb_client_tools.html#step-2-install-and-configure-the-puppetdb-cli Reason I ask is, the page states at the top, "For Puppet Enterprise you have the ability to install the PuppetDB CLI...."
  • n
    The PDB client is open-source and can be used with open-source Puppetserver. See https://www.puppet.com/docs/puppetdb/7/pdb_client_tools.html
  • n
    There's a PE version that supports token auth. The non-PE version requires cert-based auth.
    🙌 1
  • a
    Seems like this should have been answered somewhere but.... the dnf package provider doesn't appear to support package groups such as "Server with GUI" I've seen use of yum::group but it doesn't "feel" right to use yum on el8/9 Any suggestions?
  • s
    This message was deleted.
    ❤️ 1
    a
    b
    • 3
    • 4
  • b
    @Andy Fry, try "dnf group list --ids" at the command line. The groups will have "short names" that you might be able to use in the package resource. You'll have to prepend a "@" to the resource name: package {'@security-tools': ensure => installed, }
  • n
    hi all, Is there a limit on the maximum number of nodes that a puppetserver can serve?
1...334335336...428Latest