Don't use full path to manifest with Puppet, exposes bug in VMware

This commit is contained in:
Mitchell Hashimoto 2013-03-15 15:00:28 -07:00
parent 9464796c6d
commit 529cb21154
2 changed files with 3 additions and 1 deletions

View File

@ -12,6 +12,8 @@ BUG FIXES:
- When there is no route to host for SSH, re-establish a new connection.
- `vagrant package` once again works, no more nil error. [GH-1423]
- Human friendly error when "metadata.json" is missing in a box.
- Don't use the full path to the manifest file with the Puppet provisioner
because it exposes a bug with Puppet path lookup on VMware.
## 1.1.0 (March 14, 2013)

View File

@ -19,7 +19,7 @@ module VagrantPlugins
root_path = @machine.env.root_path
@expanded_manifests_path = @config.expanded_manifests_path(root_path)
@expanded_module_paths = @config.expanded_module_paths(root_path)
@manifest_file = File.join(manifests_guest_path, @config.manifest_file)
@manifest_file = @config.manifest_file
# Setup the module paths
@module_paths = []