You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
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:
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.
@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.
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.
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)
The text was updated successfully, but these errors were encountered: