Bug 1795397

Summary:	Unable to create Code Ready Containers (v1.4) on Windows 10 1903 Enterprise
Product:	OpenShift Container Platform	Reporter:	Rick Wagner <rwagner>
Component:	crc	Assignee:	Praveen Kumar <prkumar>
Status:	CLOSED DEFERRED	QA Contact:	Tomáš Sedmík <tsedmik>
Severity:	unspecified	Docs Contact:	Kevin Owen <kowen>
Priority:	unspecified
Version:	unspecified	CC:	cfergeau, gbraad, kowen, rodney.ricks, tsedmik, veillard
Target Milestone:	---	Flags:	rodney.ricks: needinfo?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 00:57:51 UTC	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 Rick Wagner 2020-01-27 21:26:01 UTC

Description of problem:
Users are unable to install and run CodeReady Containers 1.4 on Win 10 Enterprise (v 1903)


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


How reproducible:
Try to install and run CRC.


Steps to Reproduce:
1.  Try to install
2.  Try to run
3.  Expect error

Actual results:
PS C:\Program Files (x86)\CRC> .\crc.exe start --log-level info
INFO Checking if oc binary is cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
ERRO Failed checking if user is part of hyperv admins group
FATA Failed checking if user is part of hyperv admins group
PS C:\Program Files (x86)\CRC> .\crc.exe start --log-level debug
DEBU No new version available. The latest version is 1.4.0
INFO Checking if oc binary is cached
DEBU oc binary already cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
DEBU exit status 1
ERRO Failed checking if user is part of hyperv admins group
DEBU Failed checking if user is part of hyperv admins group
FATA Failed checking if user is part of hyperv admins group



Expected results:
(Successful installation)

Additional info:
Per the documentation [1]:

"On Microsoft Windows, CodeReady Containers requires the Windows 10 (Pro or Home) FallCreators Update (version 1709). CodeReady Containers does not work on earlier versions oreditions of Microsoft Windows."

We think it's likely other business users will be using Windows 10 Enterprise (opposed to 'Home' or even 'Pro').  Please make an allowance to allow it to be functional.

Thank you

[1] https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/1.0/pdf/getting_started_guide/Red_Hat_CodeReady_Containers-1.0-Getting_Started_Guide-en-US.pdf

Comment 1 Gerard Braad (Red Hat) 2020-01-28 02:29:23 UTC

It is possible to run on Enterprise, but this involves manual creation of a Virtual Switch. This is why we haven't taken this functionality out of testing, as there are no tests to confirm the created network is properly set up.

You would have to create a Virtual Switch named 'crc', that is either external, bridged or even internal (not recommended). But you have to make sure you have a working DHCP server that hands out addresses and allowed to attach a DNS server.

Comment 2 Gerard Braad (Red Hat) 2020-01-28 02:32:10 UTC

For the user check, you might run into issues with Active Directory. If the user can manually add the current user to the Hyper-V Administrators group, you could try tknoverride this check with:

PS> crc config set skip-check-user-in-hyperv-group true

Comment 3 rodney.ricks 2020-06-24 18:03:57 UTC

I agree with Rick Wagner.

I am also trying to get CodeReady Containers working for use at a business, using Windows 10 Enterprise.

I am using CRC Version 1.9, have Hyper-V configured, am able to get a CRC VM running, and have used Hyper-V Manager to create an internal Virtual Switch named 'crc', but I am only able to get an fe80 link-local IPv6 addresses assigned to the CRC VM, so the host can't connect to it.

Should I open a separate Bugzilla ticket for this?

Rick,

1. Did you run crc setup before running crc start?
2. You need Windows Admin privileges to do the Hyper-V configuration.
3. If you get an error saying "the user has not been granted the requested logon type at this computer", start services.msc as Administrator and restart the "Windows Management Instrumentation" service.

Comment 4 Rick Wagner 2020-06-26 16:14:35 UTC

Ack those notes, Rodney.  Thank you for those.

I think we probably can let the above comment stay with this BZ, unless further analysis reveals it to be a separate matter.  (The owners of this BZ can make that determination.)

Comment 5 Shiftzilla 2023-03-09 00:57:51 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-8765