Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1642564

Summary:	Network configuration needs to be cleaned up in the appliance
Product:	Red Hat OpenStack	Reporter:	Nenad Peric <nperic>
Component:	rhosp-v2v-appliance	Assignee:	Marek Aufart <maufart>
Status:	CLOSED ERRATA	QA Contact:	Omri Hochman <ohochman>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bthurber, ohochman
Target Milestone:	rc	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhosp-v2v-appliance-14.0-20181130.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:54:26 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 Nenad Peric 2018-10-24 16:50:16 UTC

Description of problem:

When the conversion appliance instance is deployed in OSP, it cannot receive network configuration via DHCP. 
The problem stems from the problem in ifcfg-eth0 which still has fields which are not needed and are causing the address to be rejected, namely:

HWADDR:

We should remove all the superfluous entries from that file, including UUID and IPV6 configuration as well.


How reproducible:

100%

Steps to Reproduce:
1. Deploy the appliance in OSP
2. Try to connect to it
3. Fail. 

Actual results:

The instance is not reachable since it ignores DHCP response. 

Expected results:

Accept the DHCP configuration offered by the  DHCP server. 

Additional info:

Comment 1 Marek Aufart 2018-10-28 12:52:15 UTC

Enabled networking, an Instance created from the Image gets network interface up with DHCP IP and SSHd listening on port 22.

https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/pull/13

Comment 6 errata-xmlrpc 2019-01-11 11:54:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045