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

puppet config set certname accepts upper-case names

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.5.0, PUP 3.5.1
    • Fix Version/s: PUP 7.0.0, PUP 6.20.0
    • Component/s: None
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Previously, the "puppet config set" command could set a value that was invalid, which would cause puppet to fail the next time it ran or the service was restarted. Now the command validates the settings' value prior to committing the change to puppet.conf.
      Show
      Previously, the "puppet config set" command could set a value that was invalid, which would cause puppet to fail the next time it ran or the service was restarted. Now the command validates the settings' value prior to committing the change to puppet.conf.

      Description

      On CentOS 6 with Puppet 3.5.0, the certname subcommand accepts upper case letters for the certname. If you then try to change the name to lower-case, puppet complains and refuses to do so:

      [sharon.fonge@puppetmaster ~]$ sudo puppet cert list
      [sharon.fonge@puppetmaster ~]$ puppet cert sign puppetclient.local.org
      Error: Could not find certificate request for puppetclient.local.org
      [sharon.fonge@puppetmaster ~]$ sudo rm -rf /etc/puppet/ssl /var/lib/puppet/ssl
      [sharon.fonge@puppetmaster ~]$ sudo rm -rf /etc/puppet/ssl /usr/lib/puppet/ssl
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              josh Josh Cooper
              Reporter:
              kurt.wall Kurt Wall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support