Fixed linked clone failure when master VM is missing
If the master VM is removed, but the master_id file exists, Vagrant would still attempt to clone using the master_id rather then importing re-importing first. Fixes #6742
This commit is contained in:
parent
1f88a97373
commit
e0ecda961c
|
@ -51,6 +51,8 @@ module VagrantPlugins
|
|||
"Master VM for '#{env[:machine].box.name}' already exists " +
|
||||
" (id=#{env[:clone_id]}) - skipping import step.")
|
||||
return
|
||||
else
|
||||
env.delete(:clone_id)
|
||||
end
|
||||
|
||||
env[:ui].info(I18n.t("vagrant.actions.vm.clone.setup_master"))
|
||||
|
|
Loading…
Reference in New Issue