Although this shouldn't matter, it is consistent/repeatable. While deployments using the CentOS succeed, they fail with the Fedora ISO on Hyper-V with (while pass with Fedora+KVM [on the same host from a VM even])
-- Starting OpenShift cluster ..................................................................................................Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --use-existing-config --routing-suffix 10.0.75.128.nip.io --host-pv-dir /var/lib/minishift/openshift.local.pv --host-config-dir /var/lib/minishift/openshift.local.config --host-data-dir /var/lib/minishift/hostdata --host-volumes-dir /var/lib/minishift/openshift.local.volumes --public-hostname 10.0.75.128
err : exit status 1
output : Using nsenter mounter for OpenShift volumes
Using public hostname IP 10.0.75.128 as the host IP
Using 10.0.75.128 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
-- Starting OpenShift container ...
Creating initial OpenShift configuration
StartingFAIL
Error: failed to start the web console server: timed out waiting for the condition
Although this shouldn't matter, it is consistent/repeatable. While deployments using the CentOS succeed, they fail with the Fedora ISO on Hyper-V with (while pass with Fedora+KVM [on the same host from a VM even])