Skip to content
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.

vsphere-iso requires that iso_paths datastore is the same as the VM datastore #322

Open
NathanDotTo opened this issue Jul 27, 2021 · 3 comments

Comments

@NathanDotTo
Copy link

I came across this helpful fix whilst searching for a cause for my issues.

In a similar exercise with Terraform, I am creating a VM where the VM datastore and the ISOs datastore are distinct, for the sake of tidiness if nothing else.

In the Terraform case, this separation of datastores is fine.

In the Packer case, it is not, but it should be.

@rushi47 I know this is probably old but I ran into this same exact issue and what fixed it was that in your variables, you specified this

"vcenter_datastore": "ESX07-LOCAL-DS01"

But in your iso_paths, you specified a different datastore location:

 "iso_paths": [
         "[ESX01-LOCAL-DS01] /ISO/CentOS-7-x86_64-Minimal-1511.iso"

Change the iso_path and vcenter_datastore to match and you should be good.

This is the correct answer here, but this is also wrong. There is no reason to assume that the ISO files should be in the same datastore as the VM. It should be possible to have distinct datastores.

Originally posted by @NathanDotTo in #228 (comment)

@rushi47
Copy link

rushi47 commented Aug 31, 2021

@NathanDotTo Hey Nathan thanks for pointing out man 👍 , 😃 but as you said I guess I had discarded the implementation at that time because of this but I hope this helps other peeps if someone is still running with the issue.

@VladRassokhin
Copy link
Collaborator

VladRassokhin commented Sep 4, 2021

Please report the issue to the official Packer repository. Plugin moved there over a year ago.
https://github.com/hashicorp/packer-plugin-vsphere

@NathanDotTo
Copy link
Author

NathanDotTo commented Sep 5, 2021 via email

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

No branches or pull requests

3 participants