Bug 1305586 - [z-stream clone - 3.5.8] Issue with vdsm-hook-vmfex-dev-4.16.33-1 - "InvalidatedWeakRef"
Summary: [z-stream clone - 3.5.8] Issue with vdsm-hook-vmfex-dev-4.16.33-1 - "Invalida...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.7
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ovirt-3.5.8
: 3.5.8
Assignee: Dan Kenigsberg
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1305338
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 16:08 UTC by rhev-integ
Modified: 2016-02-29 14:50 UTC (History)
7 users (show)

Fixed In Version: vt20.2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1305338
Environment:
Last Closed: 2016-02-29 14:50:24 UTC
oVirt Team: Network
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0317 0 normal SHIPPED_LIVE vdsm 3.5.8 - bug fix and enhancement update 2016-02-29 19:48:53 UTC
oVirt gerrit 53160 0 master MERGED vmfex hook: hold a ref for a virDomain object 2016-02-08 16:08:29 UTC
oVirt gerrit 53200 0 ovirt-3.6 MERGED vmfex hook: hold a ref for a virDomain object 2016-02-08 16:08:29 UTC
oVirt gerrit 53202 0 ovirt-3.6.3 MERGED vmfex hook: hold a ref for a virDomain object 2016-02-08 16:08:29 UTC
oVirt gerrit 53203 0 ovirt-3.5 MERGED vmfex hook: hold a ref for a virDomain object 2016-02-08 16:08:29 UTC

Comment 4 Michael Burman 2016-02-11 09:14:33 UTC
Verified on - rhevm-3.5.8-0.1.el6ev.noarch with 
vdsm-4.16.34-2.el6ev.x86_64
vdsm-hook-vmfex-dev-4.16.34-2.el6ev.noarch

Comment 6 errata-xmlrpc 2016-02-29 14:50:24 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.

https://rhn.redhat.com/errata/RHBA-2016-0317.html


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