I have a bit of a unique situation as I work on a secured system so I am unable to directly export my code. Essentially this is what is happening...
$ovfConfig = Get-OvfConfiguration -ovf /path/to/ova/vm.ova
($ovfConfig).NetworkMapping | Get-Member -MemberType CodeProperty | Select name
name
pg_123
pg_456
pg_789
VM_Network
When in the OVA itself I verified (just to make sure I wasn't crazy) that the values are pg-123 pg-456, pg-789, VM Network. I have also updated to the latest version of PowerCLI as of today. I am running on PowerShell for Linux but I am unsure if that would make a difference as I have encountered no issues so far. I need to be able to pull this information so that I can look for the VMHosts with the correct networks and then deploy to them. I know its goofy but this (as far as I know) is my best option considering the constant changing of networks and different site configurations. Any support would be greatly appreciated. I know its a burden not being able to directly export the code so sorry in advance.
Do you see the same when querying the properties with the ovftool?
ovftool --hideEula /path/to/ova/vm.ova
If no, then you should open an SR and report a bug in the Get-OvfConfiguration cmdlet.
Btw, I don't see that behaviour
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Hey LucD
Running the ovftool command shows the correct network names. Are you running in a windows environment? If so I think I'll try and spin up a windows VM to see if I get the same error before sending in an SR.
Yes, I tested from a Windows box
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
