Bug 1283772

Summary:	[DOC] CFME Hyper-V version not accessible if VM is configured with a Legacy Network Adapter
Product:	Red Hat CloudForms Management Engine	Reporter:	Jeff Teehan <jteehan>
Component:	Documentation	Assignee:	Red Hat CloudForms Documentation <cloudforms-docs>
Status:	CLOSED NEXTRELEASE	QA Contact:	Red Hat CloudForms Documentation <cloudforms-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5.0	CC:	adahms, cpelland, dajohnso, drieden, hhudgeon, jhardy, jprause, obarenbo, sshveta
Target Milestone:	GA
Target Release:	5.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	scvmm:network:appliance:doc
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	If you select the legacy network adapter setting when configuring a Red Hat CloudForms virtual machine on Hyper-V, it is not possible to access the virtual machine externally such as via SSH. The network adapter setting must be selected instead. For more information, see the following TechNet article - https://technet.microsoft.com/en-us/library/ee941153.aspx	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-27 00:28:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:

Description Jeff Teehan 2015-11-19 19:42:51 UTC

Description of problem:

If the CFME VHD actual VM is created with the Legacy Network adapter, the network does not respond externally.  You can't SSH into it.

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

I only tried with 5.5.0.11, but assume it's global.  Will check 5.4.4 as well.

How reproducible:

Create the Hyper-V VM, when you configure the network selection, and you accidentally select the Legacy adapter, it works fine internally but you external access does not work.

Steps to Reproduce:
1.  Create Hyper-V VM with CFME VHD Image
2.  Configure Network for Legacy Adapter
3.  Try to SSH in externall.

Actual results:
Unable to connection.  If you open the Console, everything works fine.

Expected results:


Additional info:

I'm pretty certain we just need to document this.  This history for this is when Hyper-V first started to work with Linux images, it couldn't handle to network stuff, so they just create a very basic network.  It hasn't been an issue for any versions of Hyper-V we support.  Here is a recent Tech Note from Microsoft encouraging people to not use this selection.

https://technet.microsoft.com/en-us/library/ee941153.aspx

Comment 3 Andrew Dahms 2017-03-06 05:04:21 UTC

Moving back to the default assignee for now to be considered along with upcoming work.

Comment 4 Andrew Dahms 2018-02-27 00:28:42 UTC

Closing this bug with the addition of a known issue to the documentation.