Bug 1413968
Summary: | [z-stream clone - 3.6.11] After hotplugging CPU results in frequent KeyError. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine | Assignee: | Milan Zamazal <mzamazal> |
Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.9 | CC: | achareka, eedri, eheftman, lsurette, mavital, mgoldboi, michal.skrivanek, mzamazal, rbalakri, Rhev-m-bugs, srevivo, tjelinek, troels, ykaul, ylavi |
Target Milestone: | ovirt-3.6.11 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, there were frequent KeyError tracebacks in the vdsm.log after CPU hotplug. Now, these errors are no longer produced by VDSM after CPU hotplug.
|
Story Points: | --- |
Clone Of: | 1408790 | Environment: | |
Last Closed: | 2017-05-09 17:04:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1408790 | ||
Bug Blocks: |
Description
rhev-integ
2017-01-17 13:13:26 UTC
Yes, this is fixed in 4.1. Is that enough or an earlier release is requested? (Originally by michal.skrivanek) Patch backported to 4.0, backport to 3.6 posted. (Originally by Milan Zamazal) Verify with: Red Hat Enterprise Virtualization Manager Version: 3.6.11-0.1.el6 Steps: 1. Create VM with 1 CPU and Run it 2. Hotplug CPU to 2 and check vdsm log Results: CPU is updated, No Error in vdms log 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://access.redhat.com/errata/RHEA-2017:1210 |