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

Bug 917548

Summary:

engine: Can't do reinitialize to storage pool when all hosts are non-operational and all storage domains are inactive

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

Elad <ebenahar>

Component:

ovirt-engine

Assignee:

Liron Aravot <laravot>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Elad <ebenahar>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

3.2.0

CC:

abaron, acathrow, amureini, bazulay, dyasny, hateya, iheim, lnatapov, lpeer, mlipchuk, Rhev-m-bugs, scohen, yeylon, ykaul

Target Milestone:

---

Keywords:

Regression

Target Release:

3.2.0

Hardware:

x86_64

OS:

Unspecified

Whiteboard:

storage

Fixed In Version:

sf16

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

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:

Bug Depends On:

Bug Blocks:

888259, 948448

Attachments:

Description	Flags
logs	none

Description Elad 2013-03-04 10:45:16 UTC

Description of problem:

1. we cannot create a new domain when hosts are non-operational without creating a new pool. 

2. we cannot reinitialize because engine will block reinitialize if the host is in non-operational state (we need a host in up state to be able to reinitialize) 

Version-Release number of selected component (if applicable):
vdsm-4.10.2-10.0.el6ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Have 1 host and one master domain (also reproduced with 2 hosts)
2. Block connectivity between host and master domain. the host becomes 'non-operational'. 
3. Try to create an unattached domain 
4. Try to reinitialize with an unattached domain

Actual results:
The actions won't work because the host is in 'non-operational' state. 

Expected results:
since the flow of host state changed and now all hosts will be non-operational we should be able to reinitialize master domain when host in non-operational. 

Additional info: logs

Comment 1 Elad 2013-03-04 10:46:38 UTC

Created attachment 704853 [details]
logs

Comment 6 Ayal Baron 2013-03-22 21:02:08 UTC

After discussing with Barak, it was agreed that hosts should go back to UP if domain is moved to inactive and host was in non-op due to connection problems with the domain.

Comment 7 Barak 2013-03-24 13:24:43 UTC

 (In reply to comment #6)
> After discussing with Barak, it was agreed that hosts should go back to UP
> if domain is moved to inactive and host was in non-op due to connection
> problems with the domain.

This is in the long run,
However in a single host scenario you should be able to perform reinitialize (it's a regression otherwise), per the  changes done related to Bug 882671,
So this scenario should be solved for 3.2 in a single host as well.

On multiple hosts it should be o.k. on any UP host, it is not clear to me from the bug description why both hosts are in none-operational.

Moving back to storage.

Comment 8 Allon Mureinik 2013-05-02 09:12:12 UTC

Change-Id I6418b9d2826146e1e4ceff4341c6d7cd3a0024af (referenced in the external tracker) should solve this issue too.

Comment 9 Elad 2013-05-13 09:34:44 UTC

Now we can create a new unattached domain when host is non-operational. Also, we are able to reinitialize pool from the unattached domain.

Checked on RHEVM-3.2-SF16:
rhevm-3.2.0-10.25.beta3.el6ev.noarch
vdsm-4.10.2-18.0.el6ev.x86_64
libvirt-0.10.2-18.el6_4.4.x86_64

Comment 10 Itamar Heim 2013-06-11 09:09:01 UTC

3.2 has been released

Comment 11 Itamar Heim 2013-06-11 09:09:02 UTC

3.2 has been released

Comment 12 Itamar Heim 2013-06-11 09:09:02 UTC

3.2 has been released

Comment 13 Itamar Heim 2013-06-11 09:37:20 UTC

3.2 has been released