Bug 1953159 - VM with next run configuration can't get IP after it's restarted becasue the VM's vNIC profile is set to <Empty>
Summary: VM with next run configuration can't get IP after it's restarted becasue the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.4.6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.6
: ---
Assignee: eraviv
QA Contact: Michael Burman
URL:
Whiteboard:
: 1954299 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-24 08:41 UTC by Qin Yuan
Modified: 2021-05-05 05:36 UTC (History)
9 users (show)

Fixed In Version: ovirt-engine-4.4.6.6
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-05 05:36:18 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.4+
mperina: blocker?


Attachments (Terms of Use)
logs_of_engine_host_guest (105.29 KB, application/x-xz)
2021-04-25 07:20 UTC, Qin Yuan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 114506 0 master MERGED core: load vnics from db with full state 2021-04-27 14:02:29 UTC
oVirt gerrit 114512 0 master MERGED core: set vnics to synced with stored procedure 2021-04-28 06:33:20 UTC

Description Qin Yuan 2021-04-24 08:41:59 UTC
Description of problem:
VM with next run configuration can't get IP after it's restarted.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.6.5-0.17.el8ev.noarch
vdsm-4.40.60.5-1.el8ev.x86_64
libvirt-7.0.0-13.module+el8.4.0+10604+5608c2b4.x86_64
Host: kernel-4.18.0-304.el8.x86_64 (rhel8.4)
Guest: kernel-4.18.0-240.el8.x86_64 (rhel8.3)

How reproducible:
100%

Steps to Reproduce:
1. Create and run a VM in RHV 4.4.6-6 ENV(compatibility version 4.6, template latest-rhel-guest-image-8.3-infra)
2. Edit a VM parameter which won't be applied immediately, such as enabling Smartcard, adding vCPUs and selecting apply later.
3. Stop VM, and run it again, wait to check VM IP.

Actual results:
1. VM can't get IP after restarted.

Expected results:
1. VM with next run configuration should get IP after it's restarted.

Additional info:

Comment 1 Michal Skrivanek 2021-04-25 05:32:27 UTC
please attach logs fro m engine, host, and guest

Comment 2 Qin Yuan 2021-04-25 07:20:45 UTC
Created attachment 1775159 [details]
logs_of_engine_host_guest

Comment 3 Qin Yuan 2021-04-25 07:28:31 UTC
I noticed when the VM with next run configuration is stopped, its nic's profile changes to empty. Tried to select a vNic profile for the VM nic again, it can get IP then.

Comment 4 Arik 2021-04-26 11:12:05 UTC
As it's a regression + automation, I suspect it might be related to your recent changes for out of sync NICs - would it make sense?

Comment 9 Ales Musil 2021-04-28 05:12:18 UTC
*** Bug 1954299 has been marked as a duplicate of this bug. ***

Comment 10 Michael Burman 2021-05-02 14:52:14 UTC
Verified on - rhvm-4.4.6.6-0.10.el8ev.noarch

Comment 11 Sandro Bonazzola 2021-05-05 05:36:18 UTC
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE.

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


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