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

puppet cert --generate returned 23 instead of one of [0]

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.8.7
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      AWS VPC
      ubuntu/images/hvm-ssd/ubuntu-trusty-14.04-amd64-server-20150325 (ami-47a23a30)
      Ubuntu 14.04.2 LTS
      puppet 3.8.7-1puppetlabs1
      puppet-common 3.8.7-1puppetlabs1

    • Template:

      Description

      We are getting the following error while trying to generate a certificate for the Puppetmaster:

      Notice: /Stage[main]/Puppet::Server::Config/Exec[puppet_server_config-generate_ca_cert]/returns: Error:
      Error: /usr/bin/puppet cert --generate ip-10-252-1-69.adrian-training.local returned 23 instead of one of [0]
      Error: /Stage[main]/Puppet::Server::Config/Exec[puppet_server_config-generate_ca_cert]/returns: change from notrun to 0 failed: /usr/bin/puppet cert --generate ip-10-252-1-69.adrian-training.local returned 23 instead of one of [0]

      We can't find any documentation on return code 23. Additionally, "puppet cert list" seems to throw the same, empty error. Changing the value while trying to generate the certificate doesn't help either.

      We were able to successfully spin up new Puppetmaster's until a few hours ago when we started to run into this issue.

      I am attaching logs from the puppet cert commands ran with the --debug flag. If any additional information is required, please let us know.

        Attachments

        1. puppet-cert-generate-debug.txt
          11 kB
          Adrian Mlodzianowski
        2. puppet-cert-list-debug.txt
          11 kB
          Adrian Mlodzianowski

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            amlodzianowski Adrian Mlodzianowski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support