Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4938

Puppet agent dies on SIGUSR1 if certificate isn't yet signed

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.3.2, PUP 4.2.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      When running as a service, Puppet agent will do a configuration run every half hour. A manual run can be triggered by sending it a SIGUSR1 signal. Usually this works great.
      However, on first use, when Puppet agent doesn't have a signed client certificate yet, it doesn't work. If it receives a SIGUSR1 then, it dies. This is unfortunate. Instead, it should just do the regular thing: in this case, check if the client certificate is signed yet, and continue from there. So exactly the same thing that it would be doing 30 minutes later anyway.

      In December 2014 this bug was reported by someone else against Ubuntu, but never fixed:
      https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910
      I am seeing this issue in Fedora.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                erikl Erik L.
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support