Bug 1228992 - The task "Handling non responsive host" doesn't end
Summary: The task "Handling non responsive host" doesn't end
Keywords:
Status: CLOSED DUPLICATE of bug 1218548
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Eli Mesika
QA Contact: Shira Maximov
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-07 12:15 UTC by Shira Maximov
Modified: 2016-02-10 19:32 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-21 11:12:37 UTC
oVirt Team: Infra
Embargoed:

Attachments (Terms of Use)
logs and snapshot (1.91 MB, application/x-gzip)
2015-06-07 12:15 UTC, Shira Maximov 		no flags Details
View All

Description Shira Maximov 2015-06-07 12:15:29 UTC 
Created attachment 1035864 [details]
logs and snapshot

Description of problem:
The task "Handling non responsive host" doesn't end 

Version-Release number of selected component (if applicable):
vdsm-4.17.0-822.git9b11a18.el7.noarch
oVirt Engine Version: 3.6.0-0.0.master.20150519172219.git9a2e2b3.el6

How reproducible:
100%

Steps to Reproduce:
1. remove vdsm from host -> see that host become non responsive  
2. reinstall host -> host become up 
3. look at the task and see that the task "Handling non responsive host" doesn't end. 

Actual results:
"Handling non responsive host" task doesn't end. 

Expected results:
the task should be end when the host is in up state

Additional info:
Comment 1 Eli Mesika 2015-06-16 13:58:40 UTC 
(In reply to Shira Maximov from comment #0)
> Created attachment 1035864 [details]
> Steps to Reproduce:
> 1. remove vdsm from host -> see that host become non responsive  

Uninstall or stop the service  ???
Comment 2 Shira Maximov 2015-06-18 08:48:17 UTC 
Uninstall
Comment 3 Eli Mesika 2015-06-21 11:12:37 UTC 

*** This bug has been marked as a duplicate of bug 1218548 ***
Note You need to log in before you can comment on or make changes to this bug.