Bug 1057358 - If an inactive SD is off network, new hosts will not activate
Summary: If an inactive SD is off network, new hosts will not activate
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 3.4.0
Assignee: Liron Aravot
QA Contact: Raz Tamir
Whiteboard: storage
Depends On:
Blocks: rhev3.4beta 1142926
TreeView+ depends on / blocked
Reported: 2014-01-23 22:01 UTC by Jake Hunsaker
Modified: 2019-04-28 09:24 UTC (History)
12 users (show)

Fixed In Version: 3.3
Doc Type: Bug Fix
Doc Text:
Previously, a host added to a cluster with an inactive storage domain failed to initiate, because it was attempting, unsuccessfully, to connect to that storage domain. Now, host activation completes successfully even if there are inactive storage domains in the cluster.
Clone Of:
Last Closed: 2014-06-09 15:09:34 UTC
oVirt Team: Storage
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0506 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.4.0 update 2014-06-09 18:55:38 UTC

Description Jake Hunsaker 2014-01-23 22:01:13 UTC
Description of problem:

If a SD in a cluster is marked inactive, and a new hypervisor tries to activate, the hypervisor will fall into an "unassigned" state and then timeout to non-operational. From the attached case, we could see that the host initiated an attempt to connect to the SD, but would never have a FINISH log entry nor fail out as it would if the IP for the SD was up but the LUN was missing. 

Version-Release number of selected component (if applicable):


How reproducible:

Was 100% for us

Steps to Reproduce:
1. Bring down a SD and mark inactive
2. Take the IP for said SD offline
3. Try to activate a hypervisor

Actual results:

Hypervisor will go into an "Unassigned" state and then take ~10 minutes to fall into non-operational.

Expected results:

Since the hypervisor will come Up if the IP is reachable but the LUN is missing, so to should the hypervisor come Up if the IP is unreachable for an INactive SD

Additional info:

Comment 1 Sean Cohen 2014-01-28 06:51:19 UTC
Tal please check if it should be still the case for 3.3

Comment 2 Liron Aravot 2014-01-28 12:42:01 UTC
this should be currently resolved. failing to connect to one of the sds shouldn't fail host activation.

Comment 4 Raz Tamir 2014-02-02 13:19:03 UTC
Got the Expected results

Comment 5 errata-xmlrpc 2014-06-09 15:09:34 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.


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