-
Notifications
You must be signed in to change notification settings - Fork 83
Startup of the distributed environment fails #153
Comments
+1 Received same for Distributed Vagrant version: Vagrant 2.0.2 |
I don't have time atm to refactor this box. Probably I'll delete it, the setup wizards in 2.9 are super easy to build such an environment with just two blank VMs. |
This creates an empty client certificate.
https://github.com/Icinga/puppet-icinga2/blob/master/manifests/pki/ca.pp#L157
|
I've created the Puppet hieradata profiles based on a patch in git master which lately has been reverted. Therefore the used CA does not provide a valid RSA key. See Icinga/icinga2#5555. This isn't visible in the other boxes since they're just generating the certificates at runtime. |
Fixed it with creating new static certificates. |
Expected Behavior
Both nodes in the distributed environment start.
Current Behavior
Provisioning fails with the following error messsage
I saw in the puppet provisioning log, that some steps are skipped because of a failed dependency:
I sshed into the box and looked why Icinga 2 fails to start, it seems that Icinga 2 can't find/read the certificate because the file is almost empty.
A full provisioning log:
vagrant-icinga2-distributed-full-log.txt
Steps to Reproduce (for bugs)
Context
Ran into this issue while testing.
Your Environment
vagrant -v
): Vagrant 2.1.1The text was updated successfully, but these errors were encountered: