https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • o
    how people usually manage sysctl entries. i used this module before: https://forge.puppet.com/modules/herculesteam/augeasproviders_sysctl/dependencies but that is still depending on the herculesteam/augeasproviders_core module (replaced by puppet/augeasproviders_core). can probably use file resource oir make my own small define. wonder how other people do this ?
  • b
    the sysctl module got migrated to vox pupuli, you can still use it: https://github.com/voxpupuli/puppet-augeasproviders_sysctl
  • o
  • s
    This message was deleted.
    b
    r
    +2
    • 5
    • 10
  • s
    This message was deleted.
    k
    s
    o
    • 4
    • 4
  • s
    This seems to be nonsensical, as I am clearly running puppet 5
  • s
    I am testing writing a manifest to upgrade a Puppet 5 agent to Puppet 7, using the puppet_agent module, but it keeps failing here due to this: https://github.com/puppetlabs/puppetlabs-puppet_agent/commit/dca67e0db8788b8415a306a08e6fd74aaba4e2e5
  • s
    This message was deleted.
    r
    s
    • 3
    • 4
  • u
    hey there
  • u
    Need some help here. Shouldn’t this work? 
    $pkey_base64  = getvar("pvars::${pkey_pvars}")
    $pkey_content = base64('decode', $pkey_base64)
    I’m trying to create a file with content => $pkey_content, but Puppet (6.28) just creates an empty file (and doesn’t complain of a single thing, both on agent and server). Any pointers?
  • u
    message has been deleted
  • g
    How common is adding 
    notify => Exec['apt_update']
    to every package resource vs setting 
    apt::update::frequency: always
    ?
  • r
    You can use a collector if you really need to
  • b
    you want that notify usually on apt repos, not on packages
  • v
    AWS changed it's mind and renamed AL2022 to AL2023. el9 build of puppet agent seems to be working there
  • v
    Copy code
    # puppet facts os
{
  "os": {
    "architecture": "x86_64",
    "distro": {
      "codename": "Amazon Linux",
      "description": "Amazon Linux release 2023 (Amazon Linux)",
      "id": "Amazon",
      "release": {
        "full": "2023",
        "major": "2023"
      }
    },
    "family": "RedHat",
    "hardware": "x86_64",
    "name": "Amazon",
    "release": {
      "full": "2023",
      "major": "2023"
    },
    "selinux": {
      "config_mode": "permissive",
      "config_policy": "targeted",
      "current_mode": "permissive",
      "enabled": true,
      "enforced": false,
      "policy_version": "33"
    }
  }
}
  • o
    actually have no idea how to do that. facts are created prior evaluating the manifests. and i can use no conditions that are defined on the manifest. maybe i need to create a fact prior to this module somehow and put it in some custom facts directory, to have a preexisting fact to determine creating the kmod facts, however i don't think that fact is then already available during the same puppet catalog compilation. so actually not sure ( and a bit baffled by it, that i can not disable it)
  • o
    blocking kmods.* seemed to be fine also tried networking.interfaces.veth* and networking.interfaces.veth.* but that unfortunately doesn't work..
  • s
    This message was deleted.
    v
    y
    m
    • 4
    • 38
  • m
    so, I tell the 
    define
    to create a config, for 3 nomad agents, for the network 192.168.1.0/24 Puppet will detects the free hosts, remove 3 (the number of the agents) and split by 3 and it will create 3 json files with 3 different IPAM configurations
  • m
    the reason being, Calico uses 
    etcd
    to share these information, but I could easily split the ranges with puppet
  • m
    Calico stores this information onto 
    etcd
    , and makes it available to all the PODs
  • m
    but if I need to split by the number of Agents (to create ranges), I need to know what number I have to divide. In the example above, is: 254 - broadcast IP - ip assigned to VXLAN ....
  • m
    but if I need to split by the number of Agents (to create ranges), I need to know what number I have to divide. In the example above, is: 254 - broadcast IP - ip assigned to VXLAN , divided by agents and rounded
  • s
    This message was deleted.
    l
    • 2
    • 1
  • l
    Hello, I am testing puppet 7 agent on our amd64 Windows 10 image, and after a manual install of 7.23.0 and setting up our server and cert, I get the error:
    Copy code
    Error: Could not retrieve local facts: cannot load such file -- facter/util/wmi
Error: Failed to apply catalog: Could not retrieve local facts: cannot load such file -- facter/util/wmi
    As I'm just testing I ran this as 
    puppet agent -t
    as system from cmd.exe. Some version info:
    Copy code
    puppet -V
7.23.0
    Copy code
    facter -v
4.3.0
  • l
    Hello, I am testing puppet 7 agent on our amd64 Windows 10 image, and after a manual install of 7.23.0 and setting up our server and cert, I get the error:
    Copy code
    Error: Could not retrieve local facts: cannot load such file -- facter/util/wmi
Error: Failed to apply catalog: Could not retrieve local facts: cannot load such file -- facter/util/wmi
    As I'm just testing I ran this as 
    puppet agent -t
    as system from cmd.exe. Some version info:
    Copy code
    puppet -V
7.23.0
    Copy code
    facter -v
4.3.0
    Here is the output from `puppet agent -t --trace`: https://termbin.com/2ipoi
  • s
    This message was deleted.
    b
    v
    r
    • 4
    • 6
  • r
    is it more preferable to use 
    $facts['something']
    than 
    fact('something')
    ? or whats is the difference, preferred way?
  • r
    the difference comes with 
    $facts["something"]["something"]
    vs 
    facts("something.something")
1...318319320...428Latest