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
The fix introduced in #193 erroneously assumed that the ipAddress values returned for each adapter was in a consistent order (ipV4address, ipv6address).
We've demonstrated this is not the case for our internal machines (running vsphere 6) :
This results in vagrant attempting to SSH to the ipV6 address entry. Given the ipAddress array isn't reliably ordered, we should examine all the returned values and filter to discern the expected ip address.
The text was updated successfully, but these errors were encountered:
The fix introduced in #193 erroneously assumed that the ipAddress values returned for each adapter was in a consistent order (ipV4address, ipv6address).
We've demonstrated this is not the case for our internal machines (running vsphere 6) :
pry(#<VagrantPlugins::VSphere::Action::GetSshInfo>)> vm.guest.net[0].ipAddress => ["XXXX::XXXX:XXXX:XXXX:XXXX", "XXX.XXX.XXX.XXX"]
This results in vagrant attempting to SSH to the ipV6 address entry. Given the ipAddress array isn't reliably ordered, we should examine all the returned values and filter to discern the expected ip address.
The text was updated successfully, but these errors were encountered: