Bug 963546

Summary:	Hypervisor is unassigned after upgrade
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pavel Zhukov <pzhukov>
Component:	ovirt-engine	Assignee:	Roy Golan <rgolan>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.1.2	CC:	acathrow, alonbl, bazulay, dougsland, hateya, iheim, jkt, lpeer, nobody, pep, perobins, pzhukov, Rhev-m-bugs, sputhenp, tcameron, thomas, ukar, ybronhei, yeylon, yzaslavs
Target Milestone:	---
Target Release:	3.2.3
Hardware:	All
OS:	All
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-12 15:25:18 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:
Bug Depends On:
Bug Blocks:	902971

Description Pavel Zhukov 2013-05-16 06:37:20 UTC

Description of problem:
After hypervisor upgrading and changing name of ISCSI initiator (because of the bug) hypervisor goes to Unassigned state for a long time. Now way to change status.

Version-Release number of selected component (if applicable):
rhevm-3.1.0-50.el6ev.noarch 
Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130415.0.el6_4)

How reproducible:
Unkonow (WIP)

Steps to Reproduce:
1. Updagrade hypervisor (RHEV UI)
2. Change ISCSI initiator name to something wrong
3. Boot hypervisor => NonOperational
4. Change ISCSI initiator name
5. Host goes to unassigned state and never to NonOperational or UP
  
Expected results:
Non-Operational or UP state, possibility to put host to Maintenance

Additional info:
After last reboot looks like host has un-syncronized networks.It was about 2 weeks between steps 3 and 4

Comment 7 Yaniv Bronhaim 2013-05-19 12:20:01 UTC

Pavel, Host in unassigned mode always move to non-operational or connecting when the host is reachable, this state is a temporary state before moving the host to up, if it can't move to up it should return to non-operational. 
Just to clarify the description, your host was non-operational, then you changed back the initiator name, automatically after period of time the status was changed to unassigned and got stuck there?

Comment 8 Pavel Zhukov 2013-05-19 19:42:08 UTC

Yaniv, 
Yes, You're right. Host went to unassigned state and got stuck there for a long time (20hrs at least).

Comment 14 Barak 2013-06-06 12:47:37 UTC

Douglas
- can you please try it with the exact versions described above ?
- In addition go over the logs and see if you can find any reference to a reason for that to happen.

Comment 15 Douglas Schilling Landgraf 2013-06-06 12:55:09 UTC

(In reply to Barak from comment #14)
> Douglas
> - can you please try it with the exact versions described above ?
> - In addition go over the logs and see if you can find any reference to a
> reason for that to happen.

Sure.

Comment 22 Simon Grinberg 2013-06-17 11:45:46 UTC

*** Bug 966957 has been marked as a duplicate of this bug. ***

Comment 31 Pavel Zhukov 2013-07-23 10:58:38 UTC

Reproduced at home. 

Host is in Maintenance state -> Try to activate it (with missed network or ISO domain) -> Non-Operational (as expected) -> Fix the reason of Non-Operational state -> Activate -> Host (sometimes!) gets stuck in unassigned state. Restart ovirt-engine helps.