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

Bug 1414675

Summary:	core: StorageJobCallback - npe when there is no executing host
Product:	[oVirt] ovirt-engine	Reporter:	Liron Aravot <laravot>
Component:	BLL.Storage	Assignee:	Liron Aravot <laravot>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	bugs, gklein, tnisan
Target Milestone:	ovirt-4.1.0-beta	Keywords:	CodeChange
Target Release:	4.1.0.2	Flags:	rule-engine: ovirt-4.1+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-01 14:43:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liron Aravot 2017-01-19 08:38:38 UTC

Description of problem:
When there is no executing host (may happen when hosts go no responsive
during a command execution for example), the StorageJobCallback may fail
with NPE when attempting to check the host status.

How reproducible:
Always - with debugger (otherwise it's very hard to reproduce).

Steps to Reproduce:
1. Have a 4.1 DC with 2 domains and one host.
2. Create a disk
3. Attempt to move the disk
4. Before the copyData operation is executed disconnect the connection between the engine and the host

Actual results:
StorageJobCallback will fail with NPE when attempting to check the host status.

Expected results:
The StorageJobCallback should treat the job as failed as it was never submitted to a host.

Additional info:

Comment 1 Kevin Alon Goldblatt 2017-01-31 16:04:28 UTC

The following scenario was tested with devel in debug
Steps to Reproduce:
1. Have a 4.1 DC with 2 domains and one host.
2. Create a disk
3. Attempt to move the disk
4. Before the copyData operation is executed disconnect the connection between the engine and the host  ->>>> No NPE and job is failed by engine


Moving to VERIFIED!