https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • y
    Because values for 
    lookup('modulename::value')
    would be loaded from 
    hieradata/modules/modulename
    and not from 
    hieradata/modules/othermodule
    . It would force people to put values into smaller, manageable files instead of a massive 
    common.yaml
    . I personally don't think it is necessary either, but some of our admins insist on forking forge modules so they can add their own 
    data/
    directory instead of putting values in the environment storage because it can be hard to find things in a huge 
    common.yaml
  • b
    speaking of webapp, I'm working on https://github.com/betadots/hdm which would provide that
  • s
    👋 大家好！hello every one
  • s
    This message was deleted.
    y
    s
    • 3
    • 4
  • y
    *
    doesn't seem to work for me: hiera config:
    Copy code
    ---
version: 5
hierarchy:
  - name: "Vault"
    lookup_key: hiera_vault
    options:
      confine_to_keys:
        - '^vault::.*'
      strip_from_keys:
        - 'vault::'
      ssl_verify: false
      address: "<https://vault.example.com:8200>"
      token: /run/vault-puppetserver/approleToken
      default_field_parse: json
      mounts:
        puppet:
          - 'nodes/%{::trusted.certname}'
          - 'common'

  - name: "Per-node data"
    lookup_key: eyaml_lookup_key
    options:
      encrypt_method: gpg
      gpg_gnupghome: /opt/puppetlabs/server/data/puppetserver/.gnupg
    datadir: "site/hiera"
    paths:
      - "nodes/%{facts.hostname}.d/*.yaml"
      - "nodes/%{facts.hostname}.yaml"

  - name: "OS family/name/version"
    datadir: "site/hiera"
    paths:
      - "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.d/*.yaml"
      - "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.yaml"
      - "os/%{facts.operatingsystem}.d/*.yaml"
      - "os/%{facts.operatingsystem}.yaml"

  - name: "Common data"
    lookup_key: eyaml_lookup_key
    options:
      encrypt_method: gpg
      gpg_gnupghome: /opt/puppetlabs/server/data/puppetserver/.gnupg
    datadir: "site/hiera"
    paths:
      - "global.d/*.yaml"
      - "global.yaml"
    When I run 
    puppet lookup --environment production --node <http://work1.pc.example.com|work1.pc.example.com> --explain puppet::runinterval
    , it says the file doesn't exist:
    Copy code
    Environment Data Provider (hiera configuration version 5)
    Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"
    Hierarchy entry "Vault on <http://vault.example.com|vault.example.com>"
      No such key: "puppet::runinterval"
      [hiera-vault] Skipping hiera_vault backend because key 'puppet::runinterval' does not match confine_to_keys
    Hierarchy entry "Per-node data"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/nodes/work1.d/*.yaml"
        Original path: "nodes/%{facts.hostname}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/nodes/work1.yaml"
        Original path: "nodes/%{facts.hostname}.yaml"
        Path not found
    Hierarchy entry "OS family/name/version"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml"
        Original path: "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.yaml"
        Original path: "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml"
        Original path: "os/%{facts.operatingsystem}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.yaml"
        Original path: "os/%{facts.operatingsystem}.yaml"
        Path not found
    Hierarchy entry "Common data"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/global.d/*.yaml"
        Original path: "global.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/global.yaml"
        Original path: "global.yaml"
        No such key: "puppet::runinterval"
    When I look at the file system, there clearly is a file that should be loaded:
    Copy code
    # ls /etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml
/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/puppet.yaml
# cat /etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/puppet.yaml
---

puppet::runinterval: 1800
  • y
    *
    doesn't seem to work for me: hiera config (simplified):
    Copy code
    ---
version: 5
hierarchy:
  - name: "OS family/name/version"
    datadir: "site/hiera"
    paths:
      - "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.d/*.yaml"
      - "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.yaml"
      - "os/%{facts.operatingsystem}.d/*.yaml"
      - "os/%{facts.operatingsystem}.yaml"
    When I run 
    puppet lookup --environment production --node <http://work1.pc.example.com|work1.pc.example.com> --explain puppet::runinterval
    , it says the file doesn't exist:
    Copy code
    Environment Data Provider (hiera configuration version 5)
    Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"
    Hierarchy entry "Vault on <http://vault.example.com|vault.example.com>"
      No such key: "puppet::runinterval"
      [hiera-vault] Skipping hiera_vault backend because key 'puppet::runinterval' does not match confine_to_keys
    Hierarchy entry "Per-node data"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/nodes/work1.d/*.yaml"
        Original path: "nodes/%{facts.hostname}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/nodes/work1.yaml"
        Original path: "nodes/%{facts.hostname}.yaml"
        Path not found
    Hierarchy entry "OS family/name/version"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml"
        Original path: "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.yaml"
        Original path: "os/%{facts.operatingsystem}%{facts.lsbmajdistrelease}.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml"
        Original path: "os/%{facts.operatingsystem}.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/os/windows.yaml"
        Original path: "os/%{facts.operatingsystem}.yaml"
        Path not found
    Hierarchy entry "Common data"
      Path "/etc/puppetlabs/code/environments/production/site/hiera/global.d/*.yaml"
        Original path: "global.d/*.yaml"
        Path not found
      Path "/etc/puppetlabs/code/environments/production/site/hiera/global.yaml"
        Original path: "global.yaml"
        No such key: "puppet::runinterval"
    When I look at the file system, there clearly is a file that should be loaded:
    Copy code
    # ls /etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/*.yaml
/etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/puppet.yaml
# cat /etc/puppetlabs/code/environments/production/site/hiera/os/windows.d/puppet.yaml
---

puppet::runinterval: 1800
  • s
    Using Bolt to deploy big data components for Ambari's alternatives. I think it will be a big project totally by bolt without any agents. Will you want have a try?
  • y
  • s
    This message was deleted.
    n
    n
    l
    • 4
    • 43
  • n
    hi all, I have 
    runtimeout=15m
    in 
    puppet.conf
    on Windows machines, but sometimes this parameter dont work, and I get :
    Copy code
    Run of Puppet configuration client already in progress; skipping  (C:/ProgramData/PuppetLabs/puppet/cache/state/agent_catalog_run.lock exists)
    does anyone know why? I dont fine any errors in Windows Event Logs related to that. only above line, its possible to force the 
    runtimeout
    ?
  • m
    👋 I see hundreds times this message showing while I run puppet with `--debug`:
    Copy code
    Debug: Facter: Searching fact: ip6tables_version in core facts and external facts
Debug: Facter: Loading all internal facts
Debug: Facter: Loading external facts
Debug: Facter: fact "ip6tables_version" has resolved to: 1.4.21
Debug: Facter: resolving fact with user_query: ip6tables_version
Debug: Facter: Searching fact: ip6tables_version in file: ip6tables_version.rb
Debug: Facter: List of resolvable facts: [#<Facter::SearchedFact:0x000000000a8f45d0 @name="ip6tables_version", @fact_class=nil, @user_query="ip6tables_version", @type=:custom, @file=nil>]
    it's always the same, and it changes only the string: 0x000000000....
  • m
    tha custom facts does only run: "ip6tables --version", but I'm no understanding why the same command is being executed hundreds of times
  • m
    tha custom facts does only run: "ip6tables --version", but I'm no understanding why the same command is being executed hundreds of times
  • p
    question: nginx has the possibility to tell a server resource "please take care of the http->https redirect". https://github.com/voxpupuli/puppet-nginx/blob/master/manifests/resource/server.pp#L307 Does puppetlabs apache have a similar setting? I am not seeing it.
  • p
    question: nginx has the possibility to tell a server resource "please take care of the http->https redirect". https://github.com/voxpupuli/puppet-nginx/blob/master/manifests/resource/server.pp#L307 Does puppetlabs apache have a similar setting? I am not seeing it.
  • n
    Execution of Puppet configuration client did not complete within 900 seconds and was terminated.
  • v
    I don't think it does. you can just add a simple apache::vhost resource
  • s
    This message was deleted.
    👍 1
    p
    v
    • 3
    • 3
  • w
    The README has an example in it.
  • w
    apache::vhost { '<http://redirect.example.com|redirect.example.com> non-ssl':
    ...
  • n
    take your time, thank you so much... I had that issue today for first time as a service. and that was 2 days ago 😞 the proccess was hanging on Task-manager
  • g
    what is the correct way to get rid of `Error: Facter: error while resolving custom fact "virtualenv_version": undefined method 
    []' for nil:NilClass
    I already downgraded semantic_puppet from 1.0.4 to 1.0.2 but it stays. puppet agent version is 6.27.0
  • h
    it's a problem with the puppet module that is trying to look at that fact without checking if it was defined first. for us it was the puppet-python module that needs to be upgraded
  • d
  • g
    Thank you. I had to uninstall stankevich-python because it already was the newest version 😕
  • d
  • b
    oh that's really really old, puppet/python is the successor of that
  • d
  • s
    This message was deleted.
    b
    • 2
    • 1
  • t
    @binford2k ^^ ?
1...484950...428Latest