-
Notifications
You must be signed in to change notification settings - Fork 83
Standalone "vagrant up" fails due to "icingacli x509 import" returning 255 #207
Comments
I have exactly same issue on latest version 2.2.0 on windows 10 using virtualbox 6.1.12 r139181 |
@Arukadox I'm not surprised because the failure is being caused by the Puppet job not dealing with the X509 certificate successfully, so the platform underlying the VM is not really a factor. |
Hi, and
|
The Standalone vagrant box does not build correctly. Using OS X Catalina / VirtualBox 6.1 / Vagrant 2.2.9.
The machine is provisioned and the Puppet catalog runs, but the important error seems to be this:
Then there are a lot of errors like this:
Finally the catalog terminates with this:
Expected Behavior
The Vagrant file (and Puppet catalog) should run to completion making a working standalone Icinga server.
Current Behavior
The Vagrant file aborts because the Puppet catalog never runs to completion. It is clear that the installations did not completely work since
httpd
is not running, and if it is started manually the following error comes from the icingaweb2 login screen:Steps to Reproduce (for bugs)
git clone https://github.com/Icinga/icinga-vagrant && cd icinga-vagrant
cd standalone
git checkout v2.2.0
vagrant up
Context
Want to give a customer a quick POC machine.
Your Environment
vagrant -v
): 2.2.9The text was updated successfully, but these errors were encountered: