minishift: User data deployment seems to be broken / Hyper-V static ip address assignment / authentication does not work

General information

• Minishift version: minishift v1.14.0+1ec5877 & minishift-centos-iso 1.7.0
• OS: Windows
• Hypervisor: Hyper-V

Static IPv4 address assignment seems to have been broken when minishift-centos-iso v1.7.0 is used.

Steps to reproduce

1. Upgrade minishift-centos7.iso from 1.6.1 to 1.7.0
2. minishift configuration as follows

- check-network-http-host: http://nexus.corp.com:8081
- check-network-ping-host: nexus.corp.com
- disk-size            : 50G
- image-caching        : true
- insecure-registry    : [nexus.corp.com:5000]
- iso-url              : http://nexus.corp.com:8081/repository/binary/minishift-centos7-1.7.0.iso
- memory               : 8G
- network-gateway      : 192.168.123.1
- network-ipaddress    : 192.168.123.123
- network-nameserver   : 123123.123.123
- public-hostname      : master.local.dev.corp.com
- registry-mirror      : [https://nexus.corp.com:5000]
- routing-suffix       : apps.local.dev.corp.com
- show-libmachine-logs : true
- skip-check-openshift-release: true

Expected

IPv4 ip address is assigned to the VM, as specified in the minishift configuration option “network-ipaddress”

(minishift) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minishift ).networkadapters[0]).ipaddresses[0]
(minishift) DBG | [stdout =====>] : 192.168.123.123

Actual

Introducing minishift-centos-iso ver 1.7.0, breaks the expected behavior.

(minishift) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM minishift ).networkadapters[0]).ipaddresses[0]
(minishift) DBG | [stdout =====>] : fe80::215:5dff:fe12:d662

Logs

minishift start --show-libmachine-logs -v5