Bug 1531166 - CDK 3.2 - Static IP assignment on Wyper-V still doesn't work
Summary: CDK 3.2 - Static IP assignment on Wyper-V still doesn't work
Keywords:
Status: NEW
Alias: None
Product: Container Development Kit (CDK)
Classification: Red Hat
Component: vms
Version: unspecified
Hardware: Unspecified
OS: Windows
unspecified
unspecified
Target Milestone: ---
: 2.3
Assignee: Lalatendu Mohanty
QA Contact: Ondřej Pták
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-04 17:28 UTC by Bruno Andrade
Modified: 2023-07-21 23:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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:
Note You need to log in before you can comment on or make changes to this bug.