Hi, I am working on a team that uses Vagrant VMs as part of our test pipelines. However, recently, we have had all VMs go into 'aborted' state during our builds without warning. The VMs never go into 'aborted' state at the same time. This issue happens inconsistently; sometimes the test pipeline succeeds just fine, and other times it doesn't, with no change in our code that provisions the Vagrant VMs. I tried running the build with INFO Level logging set up, but this did not give me any useful information re: why the VMs were going into aborted state. I tried looking at VirtualBox logs, which also gave no new information. I tried looking at /var/log/messages and dmesg too, to no avail. Has anyone else ever suffered this issue? Does anyone know where I should look next / what methods I can use to debug this issue?
We use Vagrant with VirtualBox running on OEL. Vagrant version: Vagrant 1.7.4 VirtualBox version: 5.0.10r104061 -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/066459cc-b981-4032-b06d-db1d6574d24f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
