Bug 1666838 - [v2v][ops] IP address is missing on interface of the migrated instance
Summary: [v2v][ops] IP address is missing on interface of the migrated instance
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.z
Assignee: Brett Thurber
QA Contact: Yadnyawalk Tale
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1626503
Blocks: 1723478
TreeView+ depends on / blocked
 
Reported: 2019-01-16 17:30 UTC by Ido Ovadia
Modified: 2019-07-31 09:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-31 09:45:52 UTC
Category: ---
Cloudforms Team: V2V
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
console screensot (212.63 KB, image/png)
2019-01-16 17:30 UTC, Ido Ovadia
no flags Details

Description Ido Ovadia 2019-01-16 17:30:27 UTC
Created attachment 1521089 [details]
console screensot

Description of problem:
=======================
After migration of instance, IP address is missing on its interface

Version-Release number of selected component:
=============================================
5.10.0.31

How reproducible:
=================
2/2

Steps to Reproduce:
===================
1. On Openstack - Create a network and subnut 10.8.58.0/23 with IP range Start 10.8.58.4 - End 10.8.59.240
2. Configure the OSP and VMware provider for migration
3. Create Infra mapping and Migration plan.
   - VM IP 10.8.59.132
   - VM MAC 00:50:56:b1:21:60 
   
            
5. After migration finished successfully verify instance IP and MAC (on OSP CLI)
   - instance IP 10.8.59.132
   - instance MAC 00:50:56:b1:21:60

6. On instance console run IP a

Actual results:
===============
interface ens3 appear with correct map but w/o IP address.
And failed on ifup

Expected results:
=================
interface should create with IP address an UP

Additional info:
===============
Screenshot enclosed

Comment 2 Fabien Dupont 2019-03-07 13:50:29 UTC
Ido, have you reproduced this issue since 2019-01-16 ? If no, can you close this BZ, please ?

Comment 3 Ido Ovadia 2019-07-31 09:22:49 UTC
(In reply to Fabien Dupont from comment #2)
> Ido, have you reproduced this issue since 2019-01-16 ? If no, can you close
> this BZ, please ?

I did not try, but may @Yadnyawalk Tale reproduced

Comment 4 Fabien Dupont 2019-07-31 09:25:15 UTC
@ytale, did you reproduce this since January ?

Comment 5 Yadnyawalk Tale 2019-07-31 09:44:17 UTC
(In reply to Fabien Dupont from comment #4)
> @ytale, did you reproduce this since January ?
Yes Fabien, we did saw this issue at that but I saw it is fixed yesterday only.

(In reply to Ido Ovadia from comment #3)
> I did not try, but may @Yadnyawalk Tale reproduced
We have tested this usecase when we were verifying https://bugzilla.redhat.com/show_bug.cgi?id=1678376#c2.
It is no more reproducible and we are getting same interfaces on target OSP workloads which we have on vcenter workloads.


@Ido/@Fabien we can close this issue since this is WORKSFORME. Thanks for revisiting feature.


Note You need to log in before you can comment on or make changes to this bug.