Bug 983032 - Moving hosts to maintenance and updating libvirt causes host to get stuck on "unassigned" status
Moving hosts to maintenance and updating libvirt causes host to get stuck on ...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
3.3.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.3.0
Assigned To: Yaniv Bronhaim
infra
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-10 06:40 EDT by Ohad Basan
Modified: 2016-02-10 14:02 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-06 08:49:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
activate host after upgrading libvirt version (1.73 MB, text/x-log)
2013-08-06 06:57 EDT, Yaniv Bronhaim
no flags Details
activate host after upgrading libvirt version (195.85 KB, text/x-log)
2013-08-06 06:58 EDT, Yaniv Bronhaim
no flags Details

  None (edit)
Description Ohad Basan 2013-07-10 06:40:27 EDT
Description of problem:
when trying to yum update libvirt when the hosts are in maintenance.
after trying to activate them they get stuck in "unassigned" status
I can't remove, reinstall them or perform any other operation to free them



Steps to Reproduce:
1.install a host on rhev is5.
2.move host to maintenance.
3.run yum update libvirt on the host
4. activate host from the ui

Actual results:
host gets stuck on unassigned

Expected results:

host should become active
Comment 1 Ohad Basan 2013-07-10 06:44:29 EDT
imho, if it's impossible to update a libvirt's host.
at least the "reinstall host" option should be provided.
Comment 4 Ohad Basan 2013-07-10 06:58:54 EDT
restarting vdsm service on the host fixed the problem and the hosts are activate again
Comment 5 Barak 2013-07-10 17:13:31 EDT
From which  version to which version was libvirt updated?
Usually when manually yum updating a service (libvirt in this case) one must restart the version manually otherwise changes might not take place , was this performed in this case?
Comment 6 Ohad Basan 2013-07-11 04:42:37 EDT
I updated it from version  libvirt-0.10.2-18.el6_4.9.x86_64
from libvirt-0.10.2-18.el6_4.8.x86_64

I did not restart the libvirtd after updating.
maybe this was the problem
Comment 7 Barak 2013-07-25 08:28:51 EDT
Yaniv,

Please check whether:
- move host to maintenance
- yum update libvirt
- restart libvirt

It it works fine than this bug needs to move to CLOSE NOPTABUG
Comment 8 Yaniv Bronhaim 2013-08-06 06:57:14 EDT
Created attachment 783268 [details]
activate host after upgrading libvirt version
Comment 9 Yaniv Bronhaim 2013-08-06 06:58:48 EDT
Created attachment 783269 [details]
activate host after upgrading libvirt version
Comment 10 Yaniv Bronhaim 2013-08-06 06:59:32 EDT
Did deploy with libvirt-0.10.2-18.el6_4.8.x86_64, put on maintenance, upgrade to libvirt-0.10.2-18.el6_4.9.x86_64 and activate. All worked as expected.
                                                                                
Attaching yum.log and engine.log                                                
The reason for unassigned stuck status wasn't the upgrade
Comment 11 Yaniv Bronhaim 2013-08-06 07:13:51 EDT
is it duplicated of Bug 991729 ?
Comment 12 Barak 2013-08-06 08:49:39 EDT
per comment #10 moving to CLOSED NOTABUG

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