Bug 1284245 - [z-stream clone - 3.5.6] Host installation fails or host activation fails with NPE if numaNodeDistance is null
Summary: [z-stream clone - 3.5.6] Host installation fails or host activation fails wit...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-3.5.7
: 3.5.7
Assignee: Martin Sivák
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On: 1252055
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-22 11:15 UTC by rhev-integ
Modified: 2022-05-16 06:38 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1252055
Environment:
Last Closed: 2016-01-12 20:40:35 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46027 0 None None None 2022-05-16 06:38:26 UTC
Red Hat Knowledge Base (Solution) 1569743 0 None None None Never
Red Hat Product Errata RHBA-2016:0029 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.5.7 update 2016-01-13 01:39:40 UTC
oVirt gerrit 45652 0 master MERGED Fix NPE when processing NUMA info that lacks distances Never
oVirt gerrit 48074 0 ovirt-engine-3.6 MERGED Fix NPE when processing NUMA info that lacks distances Never
oVirt gerrit 50087 0 ovirt-engine-3.5 MERGED Improve the handling of empty NUMA distances Never

Comment 1 Artyom 2015-12-17 15:10:36 UTC 
Verified on rhevm-3.5.7-0.1.el6ev.noarch
1) Change caps['numaNodeDistance'] = {}
2) restart vdsmd
3) Install host to engine
Engine succeed to deploy host without any errors and numa distance equal to 0 under engine.
Comment 4 errata-xmlrpc 2016-01-12 20:40:35 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-0029.html
Comment 5 Artyom 2016-03-31 11:54:45 UTC 
It is some corner case, that happened because hardware error, so I prefer do not add it to QE coverage.
Note You need to log in before you can comment on or make changes to this bug.