Bug 1373090 – [downstream clone - 3.6.9] [Upgrade] Cluster compatibility upgrade 3.6-> 4.0 failed on a specific system

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1373090 - [downstream clone - 3.6.9] [Upgrade] Cluster compatibility upgrade 3.6-> 4.0 failed on a specific system

Summary:	[downstream clone - 3.6.9] [Upgrade] Cluster compatibility upgrade 3.6-> 4.0 ...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	ovirt-3.6.9
Target Release:	---
Assigned To:	Andrej Krejcir
QA Contact:	Israel Pinto
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression, ZStream

Depends On:	1367025
Blocks:
	Show dependency tree / graph

Reported:	2016-09-05 02:57 EDT by rhev-integ
Modified:	2016-09-21 14:06 EDT (History)
CC List:	16 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Previously, a virtual machine with a null CPU profile id stored in the database caused a NPE when editing the virtual machine. Now, a virtual machine with a null CPU profile id stored in the database is correctly handled and the virtual machine can be edited.
Story Points:	---
Clone Of:	1367025
Environment:
Last Closed:	2016-09-21 14:06:52 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	63296	ovirt-engine-3.6	MERGED	core: Allow null cpu_profile_id in the DB	2016-09-05 12:26 EDT
oVirt gerrit	63382	ovirt-engine-3.6.9	MERGED	core: Allow null cpu_profile_id in the DB	2016-09-06 05:20 EDT
Red Hat Product Errata	RHSA-2016:1929	normal	SHIPPED_LIVE	Moderate: Red Hat Virtualization Manager (RHV) bug fix 3.6.9	2016-09-21 17:57:10 EDT

Groups: None (edit)

Comment 1 Roy Golan 2016-09-05 03:02:35 EDT

Israel I need you to confirm if this VM didn't went through a cluster change. If it didn't it means we have some other place that caused the cpu profile to be null.

Comment 2 Israel Pinto 2016-09-05 03:20:11 EDT

The VM is create from template, it did not change cluster.
In the beginning of the test we update cpu socket and core, and then start the VM.

Comment 4 Israel Pinto 2016-09-13 02:03:16 EDT

Verify with: 3.6.9.1-0.1.1.el6
Host: 
OS Version: RHEL - 7.2 - 13.0.el7ev
Kernel Version: 3.10.0 - 327.30.1.el7.x86_64
KVM Version: 2.3.0 - 31.el7_2.21
LIBVIRT Version: libvirt-1.2.17-13.el7_2.5
VDSM Version: vdsm-4.17.35-1.el7ev

Steps: 
1. Create VM
2. Hot plug CPU to VM
3. Run Automation tests.

Results:
All Pass

Automation run:
https://rhev-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/3.6-GE-Tier1-x86_64/305/testReport/automation.ART.art.tests.rhevmtests.virt.hot_plug.hot_plug_cpu.hot_plug_cpu_test/

Comment 6 errata-xmlrpc 2016-09-21 14:06:52 EDT

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.

https://rhn.redhat.com/errata/RHSA-2016-1929.html

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