Bug 1531166

Summary:	CDK 3.2 - Static IP assignment on Wyper-V still doesn't work
Product:	Container Development Kit (CDK)	Reporter:	Bruno Andrade <bandrade>
Component:	vms	Assignee:	Lalatendu Mohanty <lmohanty>
Status:	NEW ---	QA Contact:	Ondřej Pták <optak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jgreguske, kanderso, timoran
Target Milestone:	---
Target Release:	2.3
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno Andrade 2018-01-04 17:28:31 UTC

Description of problem:

Unable to start CDK minishift  with static IP address on Windows 10 Hyper-V  environment .
https://access.redhat.com/documentation/en-us/red_hat_container_development_kit/3.2/html/getting_started_guide/using_cdk#hyperv-static-ip

It seems the functionality for static ip assignment on Hyper-V is partly implemented in the ISO files
https://github.com/minishift/minishift-b2d-iso/issues/59
https://github.com/minishift/minishift-centos-iso/issues/137
When using the Community minishift 1.9.0 together with minishift-centos7.iso containing static IP fix , the static IP adress assignment works fine.  A similar fix needs probably be applied to the RHEL  iso image distributed with CDK.


Version-Release number of selected component (if applicable):

3.2


How reproducible:


The static IP address assignment not working
Expected results:
The static IP address assignment works fine

Additional info: