Issue #15997 has been updated by Jo Rhett.
I don't follow your statement. Yes, it does accept the bare hostname and does contact the right system --- but the kick fails because it requires the FQDN for the cert validation to work, as per what I quoted above. ---------------------------------------- Bug #15997: puppet kick --no-fqdn fails https://projects.puppetlabs.com/issues/15997#change-69283 Author: Jo Rhett Status: Needs More Information Priority: Normal Assignee: Jo Rhett Category: Target version: Affected Puppet version: 2.7.18 Keywords: Branch: >From what I can see here, the "no-fqdn" option has no useful effect. <pre> $ sudo puppet kick --no-fqdn --host sj2-backup01 Triggering sj2-backup01 Host sj2-backup01 failed: Server hostname 'sj2-backup01' did not match server certificate; expected sj2-backup01.prod.pinger sj2-backup01 finished with exit code 2 Failed: sj2-backup01 </pre> Perhaps it was intended for some other purpose? There is no documentation for the "no-fqdn" option on the puppet kick manual page. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
