https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • n
    yes
  • n
    tried running as admin
  • c
    same error?
  • n
    yup
  • c
    hmmm...
  • n
    any idea?
  • c
    at the moment, nope
  • c
    10K+ other folks here though... hang tight
  • c
    sorry ~ I've not seen that before
  • c
    or rather, completely do not recall it
  • y
    Any errors if you run 
    facter
    ? (or 
    facter -d
    )
  • n
    no error
  • j
    We try to avoid introducing incompatibilities between puppetserver and puppet-agent packages in any stream, but best practice is to update both of them together. For example, I wouldn't suggest installing 
    puppetserver 6.0.0
    and 
    puppet-agent 6.28.0
    on the same host.
  • s
    This message was deleted.
    n
    l
    +3
    • 6
    • 14
  • b
    Good afternoon from Hurricane Nicole country. Is there a way to reproduce this: 
    $a = '/tmp/{foo,bar}'
    file{$a: ensure => directory, } in Hiera? I've got a lot of directories I need to create under a single parent directory and I don't want to have to do: --- 
    file:
    /tmp/foo:
    ensure: directory
    /tmp/bar:
    ensure: directory
    /tmp/baz:
    ensure: directory
    but the following doesn't work: 
    file:
    /tmp/{foo,bar,baz}:
    ensure: directory
    because it yields a single file called /tmp/{foo,bar}.
  • b
    Good afternoon from Hurricane Nicole country. Is there a way to reproduce this: 
    $a = '/tmp/{foo,bar}'
    file{$a:
    ensure => directory,
    }
    in Hiera? I've got a lot of directories I need to create under a single parent directory and I don't want to have to do: --- 
    file:
    /tmp/foo:
    ensure: directory
    /tmp/bar:
    ensure: directory
    /tmp/baz:
    ensure: directory
    but the following doesn't work: 
    file:
    /tmp/{foo,bar,baz}:
    ensure: directory
    because it yields a single file called /tmp/{foo,bar}.
  • b
    Good afternoon from Hurricane Nicole country. Is there a way to reproduce this: 
    $a = '/tmp/{foo,bar}'
    file{$a:
    ensure => directory,
    }
    in Hiera? I've got a lot of directories I need to create under a single parent directory and I don't want to have to do: --- 
    file:
    /tmp/foo:
    ensure: directory
    /tmp/bar:
    ensure: directory
    /tmp/baz:
    ensure: directory
    but the following doesn't work: 
    file:
    /tmp/{foo,bar,baz}:
    ensure: directory
    because it yields a single file called /tmp/{foo,bar,baz}.
  • j
    One thing to watch out for, if your catalog contains binary data which cannot be serialized to JSON, then puppetserver/agent will downgrade to 
    pson
    which is lossy and breaks deferred resources. For example, the cached catalog may contain the following 
    resource
    parameters:
    Copy code
    "parameters":{"message":"Deferred({'name' => 'sprintf', 'arguments' => ['%s', 'I am deferred']})"}}]
  • n
    Copy code
    $dirs = [
  '/tmp/foo',
  '/tmp/bar',
]

file { $dirs:
  ensure => directory,
}

-----
The hiera data version of $dirs is just an array in YAML:

dirs:
  - /tmp/foo
  - /tmp/bar
  • b
    message has been deleted
  • n
    No harm in trying to optimize, but it’s in your Puppet code’s logic where most of that optimization will happen. And you’d have to code that logic yourself.
  • c
    I have a question about something I'm trying to understand in the documentation: https://puppet.com/docs/puppet/7/types/exec.html#exec-description Specifically these parts: ---------------------------------------------------------------------------------------------------------------- Refresh: 
    exec
    resources can respond to refresh events (via 
    notify
    , 
    subscribe
    , or the 
    ~>
    arrow). The refresh behavior of execs is non-standard, and can be affected by the 
    refresh
    and 
    refreshonly
    attributes: If the exec has already run and then receives an event, it runs its command up to two times. If an 
    onlyif
    , 
    unless
    , or 
    creates
    condition is no longer met after the first run, the second run does not occur. ---------------------------------------------------------------------------------------------------------------- If refresh events are received via 
    notify
    , 
    subscribe
    , and the 
    ~>
    arrow, then doesn't that create an ordering dependency such that the resources which provide the events will always run before the 
    exec
    which receives those events? How can an 
    exec
    receive an event after it has run?
  • n
    Yes, a refresh event also sets up ordering.
  • n
    Yes, a refresh event also sets up ordering.
  • c
    That's what I thought and that's what I've seen. Is the documentation in error?
  • c
  • c
    Maybe the behavior changed at some point? I didn't think 
    exec
    worked that way even way back then, though I wouldn't rule out me not knowing that.
  • n
    ….Yeah, now I’m not sure. I suspect the docs are wrong, because I’ve never seen that “runs at most 2 times” behavior in action.
1...231232233...428Latest