Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recent commit breaks vagrant up #231

Closed
edmcman opened this issue Mar 6, 2017 · 3 comments · Fixed by #234
Closed

Recent commit breaks vagrant up #231

edmcman opened this issue Mar 6, 2017 · 3 comments · Fixed by #234
Assignees

Comments

@edmcman
Copy link

edmcman commented Mar 6, 2017

64d1e68 has completely broken my setup.

==> imagemagick-afl4: Setting custom memory: 8000
==> imagemagick-afl4: Setting custom cpu count: 4
==> imagemagick-afl4: Calling vSphere CloneVM with the following settings:
==> imagemagick-afl4:  -- Source VM: vullab-line/vm/packer-templates/ubufuzz-cli-amd64-vmware-sas
==> imagemagick-afl4:  -- Target VM: vullab-line/vm/vagrant-machines/count-compare-fuzzers-new_imagemagick-afl4_1488831955587_28485
==> imagemagick-afl4: New virtual machine successfully cloned
==> imagemagick-afl4: Waiting for the machine to report its IP address...
    imagemagick-afl4: Timeout: 240 seconds
undefined method `ipAddress' for nil:NilClass
@edmcman
Copy link
Author

edmcman commented Mar 6, 2017

log.txt

Jkovarik added a commit that referenced this issue Mar 7, 2017
@Jkovarik Jkovarik self-assigned this Mar 7, 2017
Jkovarik added a commit that referenced this issue Mar 7, 2017
@edmcman
Copy link
Author

edmcman commented Mar 7, 2017

I'll test later today. Thanks!

@edmcman
Copy link
Author

edmcman commented Mar 7, 2017

Works for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants