Red Hat Bugzilla – Bug 963546
Hypervisor is unassigned after upgrade
Last modified: 2016-02-10 14:17:18 EST
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):
Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130415.0.el6_4)
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
Non-Operational or UP state, possibility to put host to Maintenance
After last reboot looks like host has un-syncronized networks.It was about 2 weeks between steps 3 and 4
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?
Yes, You're right. Host went to unassigned state and got stuck there for a long time (20hrs at least).
- 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.
(In reply to Barak from comment #14)
> - 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.
*** Bug 966957 has been marked as a duplicate of this bug. ***
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.