https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • a
    Yeah... but my head hurts now šŸ˜«
  • n
    you want the exit to be 0 if the host is already in your inventory
  • n
    unless would be what I would recommend here
  • a
    Unless always runs, onlyif never runs
  • n
    this would need extra testing but I think this might work
    Copy code
    exec { 'add_to_inventory':
  command => 'curl blah',
  unless  => 'curl (host url from awx) 2>/dev/null | grep -c $hostname || exit 0'
}
  • a
    That's bash exit code, not stdout value right
  • n
    this would need extra testing but I think this might work
    Copy code
    exec { 'add_to_inventory':
  command => 'curl blah',
  unless  => 'curl (host url from awx) 2>/dev/null | grep -c $hostname || exit 0'
}
  • n
    yes correct.. its the return code of the unless
  • n
    yes correct.. its the return code of the unless
  • n
    it may be useful to have a dedicated script in your 
    unless
    to handle the logic better
  • a
    I think I may have to do that. Was hoping to avoid it but the logic may be too complex
  • a
    This failed I'm afraid. Unless didn't run and onlyif runs every time now lol.
  • y
    curl return codes are.. a bit special.. there is an option that simplifies things but I donā€™t remember it :) I hit into return code issue while ago and found some unexpected behaviour which is explained in man page though
  • n
    but was that machine in your inventory already @Andy Fry?
  • n
    exec shouldn't run if it was in the inventory
  • s
    This message was deleted.
    a
    • 2
    • 1
  • y
    Ah, good catch!
  • s
    This message was deleted.
    y
    g
    • 3
    • 4
  • s
    This message was deleted.
    y
    • 2
    • 1
  • y
    you should be able to do it once on a Linux server šŸ™‚
  • g
    hi team any solution for above error
  • g
    message has been deleted
  • g
    Error: Could not request certificate: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [certificate is not yet valid for /CN=Puppet CA generated on us.********.com Exiting; failed to retrieve certificate and waitforcert is disabled
  • m
    ā€œcertificate is not yet valid forā€
  • m
    this implies that the certs start date is in the future relative to to the time on the CA server
  • m
    so either the cert was generated intentionally in the future, on a machine whos clock is wrong, or the CA servers clock is wrong
  • g
    is there any solution to resolve
  • b
    checking if NTP is configured is a good first step
    šŸ’Æ 1
  • g
    is there any chance to change the clock in ssl crtificates
  • g
    how to check the NTP issue
1...276277278...428Latest