PE 3.2 Issue when Upgrading from PE 3.1.3

[Louis]

I have new Vagrant Box with a recent installation of PE 3.1.3 and it fails the upgrade with the following error.

Complete!
Loaded plugins: fastestmirror, security
Cleaning repos: 
Cleaning up Everything
Cleaning up list of fastest mirrors
## Preserving existing puppet.conf for now...
## Preserving existing auth.conf
## Setting up puppet master...
Error: Could not intialize global default settings: Error converting value for param 'modulepath': Could not find value for $confdir
## Checking the agent certificate name detection...
!! ERROR: The agent certificate name was incorrect; please check that your system can correctly resolve its own FQDN
   in DNS.

 

[jcbollinger]

Is it right?  That is, what's the certname on the agent's certificate, and is the agent able to resolve it?

That does seem to be either a poor error message or a misguided test, however, as generally speaking, it is only a convention that agents' certificates use (one of) the machine's FQDN(s) as certname.  I guess PE might elevate that from convention to requirement, though.


John

[Craig Dunn]

You appear to be hitting this...

https://tickets.puppetlabs.com/browse/ENTERPRISE-92

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/aedfcadf-fd6f-4fb7-ab55-e4deb0089e4a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Enviatics | Automation and configuration management

http://www.enviatics.com | @Enviatics

Puppet Training http://www.enviatics.com/training/

[Craig Dunn]

Next time I'll read the names of ticket contributors :)  doh.