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

Bug 1362193

Summary: [engine-backend] NPE for a failed GetCapabilitiesVDSCommand
Product: [oVirt] vdsm-jsonrpc-java Reporter: Elad <ebenahar>
Component: CoreAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: high    
Version: 1.2CC: bugs, lsvaty, mgoldboi, mperina, pkliczew, pkubica
Target Milestone: ovirt-4.0.5Flags: rule-engine: ovirt-4.0.z+
mgoldboi: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+
Target Release: 1.2.6   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 07:37:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log, server.log, vdsm.log none

Description Elad 2016-08-01 13:34:28 UTC
Created attachment 1186434 [details]
engine.log, server.log, vdsm.log

Description of problem:
While a host in a non responsive state, GetCapabilitiesVDSCommand fails with a NullPointerException.

Version-Release number of selected component (if applicable):
rhevm-4.0.2.3-0.1.el7ev.noarch


How reproducible:
100%

Steps to Reproduce:
1. Block connectivity between host and engine or reboot the host 


Actual results:

Host moves to non-responsive and GetCapabilitiesVDSCommand fails with a NullPointerException:

2016-08-01 16:30:01,116 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler7) [5ce6392] Failed to refresh VDS , vds = 'green-vdsd' : '78df4cbc-f574-489c-8ec2-7b3c9831194e', error = 'null', continuing.
2016-08-01 16:30:01,116 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler7) [5ce6392] Exception: java.lang.NullPointerException


Expected results:
No NPE

Additional info:
engine.log, server.log, vdsm.log

Comment 1 Martin Perina 2016-08-01 15:20:23 UTC
NPE looks ugly, but it does not affect activation of the host when connection issues are over, so targeting to 4.0.4

Comment 2 Lukas Svaty 2016-10-24 14:06:55 UTC
verified in vdsm-jsonrpc-java-1.2.6-1.el7ev.noarch

Comment 3 Piotr Kliczewski 2016-10-27 11:56:50 UTC
*** Bug 1386710 has been marked as a duplicate of this bug. ***