[BUG] OVF file uploads not using absolute path #3555
Comments
|
Howdy 🖐 Xiol ! Thank you for your interest in this project. We value your feedback and will respond soon. If you want to contribute to this project, please make yourself familiar with the |
Xiol
added a commit
to Xiol/govmomi
that referenced
this issue
Sep 20, 2024
11 tasks
Xiol
added a commit
to Xiol/govmomi
that referenced
this issue
Oct 17, 2024
|
After further investigation this appears to have been caused by the FileArchive.Open() function not handling paths in a cross-platform manner (our code unfortunately targets Windows machines). I've opened another PR to resolve this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Similar to #3550, the actual file uploads that
Importer.Upload()attempts are done via relative paths. This results in the file not being found when the upload is attempted from a different working directory when usingimporter.Importerfrom another application.To Reproduce
Steps to reproduce the behavior:
importer.Importerwhile having your working directory different to the OVF path.Expected behavior
The upload should happen successfully regardless of the current working directory.
Affected version
v0.43.0
Screenshots/Debug Output
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: