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

(QE-204) allow for use of local vagrant file when using --no-provision #48

Merged
merged 2 commits into from Nov 19, 2013

Conversation

@anodelman
Copy link
Contributor

@anodelman anodelman commented Oct 30, 2013

  • use already set up vagrant boxes when running with --no-provision

Workflow:

  1. initial setup of vagrant machines
    bundle exec beaker --config vagrant.cfg --preserve-hosts
  2. use those same hosts on the next run
    bundle exec beaker --config vagrant.cfg --preserve-hosts --no-provision
hack_etc_hosts @vagrant_hosts
hack_etc_hosts @vagrant_hosts
else
#we are using previsouly set up vagrant boxes, just need to set up ssh correctly
Copy link
Contributor

@justinstoller justinstoller Oct 31, 2013

Why is this an else? Don't we need to do this for newly created boxes as well?

@pcarlisle
Copy link
Contributor

@pcarlisle pcarlisle commented Nov 13, 2013

Is there a reason this is still waiting?

@anodelman
Copy link
Contributor Author

@anodelman anodelman commented Nov 13, 2013

Blocked on secondary review.

justinstoller added a commit that referenced this issue Nov 19, 2013
(QE-204) allow for use of local vagrant file when using --no-provision
@justinstoller justinstoller merged commit 1959b6f into voxpupuli:master Nov 19, 2013
1 check passed
hunner added a commit to hunner/beaker that referenced this issue Nov 20, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
hunner added a commit to hunner/beaker that referenced this issue Nov 20, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
hunner added a commit to hunner/beaker that referenced this issue Nov 21, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
hunner added a commit to hunner/beaker that referenced this issue Nov 21, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
hunner added a commit to hunner/beaker that referenced this issue Nov 21, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
hunner added a commit to hunner/beaker that referenced this issue Nov 21, 2013
The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
@anodelman anodelman deleted the fix-vagrant branch Nov 26, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants