Closed wonkas-factory closed 4 years ago
Hello @wonkas-factory, have tried a docker version? It is available at @Skejven' AET repo (https://github.com/Skejven/aet-docker).
Thanks this was a lot easier!
The docker swarm doesn't save db state of test results after docker swarm leave --force? How do we save the results...
Docker swarm leave does not affect volumes therefore the results should not be lost. I suggest you open new issue on aet-docker repo and provide some details about your configuration and steps to reproduce.
Describe the bug When building with vagrant up:
==> default: * ruby_block[karaf-config-guard] action run ==> default: ==> default: waiting for response code 401 from http://localhost:8181/system/console/bundles ==> default: incorrect response code. will try again in 5 seconds... ==> default: incorrect response code. will try again in 5 seconds...
Aborting since waiting for response code 401 from http://localhost:8181/system/console/bundles took more than 600 seconds
All the other services seem to be running fine Tomcat,ActiveMQ, MongoDB, Selenium Grid
AET 3.3.0
,Vagrant 2.2.9
,Virtualbox 6.1.8r137981
, 'chefdk 4.7.73'To Reproduce From basic setup:
v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
Expected behavior No errors with vagrant up
Screenshots
Additional context chef-stacktrace.out
Vagrant output provision.log