Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686208 - When migration completed "oc get vmi" shows obsolete IP address
Summary: When migration completed "oc get vmi" shows obsolete IP address
Status: NEW
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 2.0
Assignee: Vladik Romanovsky
QA Contact: Denys Shchedrivyi
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-06 22:48 UTC by Denys Shchedrivyi
Modified: 2019-04-16 12:13 UTC (History)
4 users (show)

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

Attachments (Terms of Use)

Description Denys Shchedrivyi 2019-03-06 22:48:28 UTC
Description of problem:
 After successful migration new POD has new IP address, but "oc get vmi" and "oc describe vmi" show old one:

# oc get pod -o wide
NAME                                    READY     STATUS      RESTARTS   AGE       IP            NODE                                        NOMINATED NODE   <none>
virt-launcher-vm-cirros-pvc-cdi-kr6nh   0/1       Completed   0          44m     <none>
virt-launcher-vm-cirros-pvc-cdi-rl6ww   1/1       Running     0          37m     <none>

# oc get vmi
NAME                AGE       PHASE     IP            NODENAME
vm-cirros-pvc-cdi   52m       Running

# oc describe vmi | grep Ip
    Ip Address:

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

How reproducible:

Steps to Reproduce:
1. create MV
2. run migration
3. check IP Address

Actual results:
 "oc get vmi" shows obsolete IP address

Expected results:
 IP address should be updated

Additional info:

Comment 1 Fabian Deutsch 2019-03-26 19:48:22 UTC
It's only definetly a bug, if the IP of a NIC with the default network wasn't changed.

IOW Only the IP of a NIC attached to the POD network must return the new IP (of the target pod) after migration.

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