Bug 1772340 - VM Node isn't changed after migrating it to other node
Summary: VM Node isn't changed after migrating it to other node
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.3.0
Assignee: Ido Rosenzwig
QA Contact: Nelly Credi
Depends On:
TreeView+ depends on / blocked
Reported: 2019-11-14 08:03 UTC by Guohua Ouyang
Modified: 2020-01-23 11:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-01-23 11:12:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 3434 0 'None' 'open' 'Bug 1772340: Return the latest pod created for a VM' 2019-11-17 10:12:44 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:13:03 UTC

Description Guohua Ouyang 2019-11-14 08:03:43 UTC
Description of problem:
Migrate a VM to another node, go to vm overview page, the node is still the old one. If check the vmi nodeName from cli, it can see the nodeName is changed accordingly.

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

How reproducible:

Steps to Reproduce:
1. have a running vm
2. migrate the vm
3. look at the node in vm overview 

Actual results:
the node is not changed at all

Expected results:
the node change to the node which the vm is migrated to.

Additional info:

Comment 1 Tomas Jelinek 2019-11-14 12:37:44 UTC
lets aim for 4.3 but not really a blocker in my opinion.

Comment 3 Guohua Ouyang 2019-12-10 02:18:03 UTC
Verified on 4.3.0-0.nightly-2019-12-04-054458.

Comment 5 errata-xmlrpc 2020-01-23 11:12:45 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.


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