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

Bug 1954299

Summary: After upgrade from 4.3 VMs nics are missing network profile
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED DUPLICATE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.6.5CC: bugs, mperina
Target Milestone: ---Keywords: Automation, AutomationBlocker, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-28 05:12:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Matyáš 2021-04-27 20:33:21 UTC 
Description of problem:
When upgrading engine from ovirt-engine-4.3.11.4-0.1.el7.noarch where I had 2 VMs running, after increasing compatibility version of cluster and DC both VMs were suddenly showing pending changes, after shutting them down both of them had missing network profiles in their nics.
For VMs that were down during the upgrade the network profile is not missing.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.6.5-0.17.el8ev.noarch

How reproducible:
always

Steps to Reproduce:
1. have 4.3 engine with running VMs
2. upgrade to 4.4
3. increase compatibility version of both cluster and DC

Actual results:
running VMs are showing changes and after shutting them down they are missing network profile

Expected results:
as the network profile is not changing (name is still the same) it should stay attached

Additional info:
Comment 2 Ales Musil 2021-04-28 05:12:18 UTC 
Closing as duplicate, the fix should be available in next engine build ovirt-engine-4.4.6-6.

*** This bug has been marked as a duplicate of bug 1953159 ***