build server name should not be mixed case for site.pp

[Paul Michali]

We found a problem running "puppet apply" on a site.pp file, where the build server name was in mixed case (e.g. buildServer). The install failed in pupetmaster-passenger, saying it cannot parse config file. Would also see this if a update was attempted, once the apply was done:

root@buildServer:/etc/puppet/manifests# apt-get upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up puppetmaster-passenger (2.7.11-1ubuntu2.2) ...
Could not parse configuration file: Certificate names must be lower case; see #1168
Could not parse configuration file: Certificate names must be lower case; see #1168
Could not parse configuration file: Certificate names must be lower case; see #1168
dpkg: error processing puppetmaster-passenger (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 puppetmaster-passenger
E: Sub-process /usr/bin/dpkg returned an error code (1)

Suggestion was made to add comments in site.pp warning about this issue.

[Mark T. Voelker (mvoelker)]

As the error message indicates, this is an intentional limitation of Puppet. I've added a few blurbs about this to the site.pp.example file so folks are aware of it. Pull request here:

https://github.com/CiscoSystems/folsom-manifests/pull/61

[Ian Wells (ijw-ubuntu)]

Semi-relevant: if someone has put a mixed case name in /etc/hostname, that actually *does* work (providing you use lowercase in the puppet).

[Mark T. Voelker (mvoelker)]

Grizzly pull request: https://github.com/CiscoSystems/grizzly-manifests/pull/54