Bug 812736 - The virt-who can't report the virt.uuid when starting guest after a set of operations.
Summary: The virt-who can't report the virt.uuid when starting guest after a set of op...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-who
Version: 5.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: ---
Assignee: Radek Novacek
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 06:42 UTC by Hui Wang
Modified: 2013-01-08 07:35 UTC (History)
4 users (show)

Fixed In Version: virt-who-0.7-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 07:35:41 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0072 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2013-01-07 15:27:17 UTC

Description Hui Wang 2012-04-16 06:42:18 UTC
Description of problem:
The virt-who can't report the virt.uuid when starting guest after a set of operations.

Version-Release number of selected component (if applicable):
    katello-headpin-all-0.1.145-1.el6.noarch
    katello-cli-headpin-0.1.16-1.el6.noarch
    katello-headpin-0.1.145-1.el6.noarch
    candlepin-tomcat6-0.5.26-1.el6.noarch
    candlepin-0.5.26-1.el6.noarch
    thumbslug-0.0.21-1.el6.noarch
    virt-who-0.5-5.el5
    subscription-manager-0.98.14-1.el5

How reproducible:
100%

Steps to Reproduce:
1. Start the guest G in source host machine.                       
 	[right-click on the guest and select 'run' in virt-manager]
2. Restart libvirtd service in source host machine.              
	[cmd: service libvirtd restart]
3. Migrate the guest G from source host machine to target host machine. 
	[cmd: virsh migrate --live 5.8_Server_x86_64_FV xen+ssh://10.66.83.195]
4. Undefine the guest G in the source host machine.                
	[select the guest and click 'Delete' in virt-manager]
5. Destroy the guest G in the target host machine.                 
	[right-click on the guest and select 'Shut Down->Force off' in virt-manager]
6. Redefine the guest that has been destroyed in step 5 in thein source host machine.                     
	[cmd: virsh define 5.8_Server_x86_64_FV.xml]
7. Start the guest G in source host machine.                       
	[right-click on the guest and select 'run' in virt-manager]
  
Actual results:
The virt-who can NOT monitor the guest start event after above 7 and can't report the guest G virt.uuid.

Expected results:
The virt-who can monitor the guest start event after above 7 and can report the guest G virt.uuid.

Additional info:

Comment 2 RHEL Program Management 2012-04-16 06:46:56 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Hui Wang 2012-04-16 06:55:39 UTC
(In reply to comment #0)
> Description of problem:
> The virt-who can't report the virt.uuid when starting guest after a set of
> operations.
> 
> Version-Release number of selected component (if applicable):
>     katello-headpin-all-0.1.145-1.el6.noarch
>     katello-cli-headpin-0.1.16-1.el6.noarch
>     katello-headpin-0.1.145-1.el6.noarch
>     candlepin-tomcat6-0.5.26-1.el6.noarch
>     candlepin-0.5.26-1.el6.noarch
>     thumbslug-0.0.21-1.el6.noarch
>     virt-who-0.5-5.el5
>     subscription-manager-0.98.14-1.el5
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. Start the guest G in source host machine.                       
>   [right-click on the guest and select 'run' in virt-manager]
> 2. Restart libvirtd service in source host machine.              
>  [cmd: service libvirtd restart]
> 3. Migrate the guest G from source host machine to target host machine. 
>  [cmd: virsh migrate --live 5.8_Server_x86_64_FV xen+ssh://10.66.83.195]
> 4. Undefine the guest G in the source host machine.                
>  [select the guest and click 'Delete' in virt-manager]
> 5. Destroy the guest G in the target host machine.                 
>  [right-click on the guest and select 'Shut Down->Force off' in virt-manager]
> 6. Redefine the guest that has been destroyed in step 5 in thein source host
> machine.                     
>  [cmd: virsh define 5.8_Server_x86_64_FV.xml]
> 7. Start the guest G in source host machine.                       
>  [right-click on the guest and select 'run' in virt-manager]
> 
> Actual results:
> The virt-who can NOT monitor the guest start event after above 7 and can't
> report the guest G virt.uuid.
> 
> Expected results:
> The virt-who can monitor the guest start event after above 7 and can report the
> guest G virt.uuid.
> 
> Additional info:

1). The issue just happens on xen.
2). If the above step 2 is not performed, the issue will not happened.

Comment 5 Radek Novacek 2012-07-17 08:28:39 UTC
This bug has been fixed in virt-who-0.7-1.el5.

Comment 8 Hui Wang 2012-08-29 10:06:24 UTC
I verified the issue, the result is PASS. Moving to VERIFIED.

Version:
virt-who-0.7-4.el5
subscription-manager-firstboot-1.0.13-1.el5
subscription-manager-1.0.13-1.el5
subscription-manager-gui-1.0.13-1.el5
python-rhsm-1.0.5-1.el5
katello-headpin-all-0.2.13-1.el6_2.noarch
candlepin-0.6.5-1.el6_2.noarch


Step:
As comment0 on Xen.

After step 6 and 7, tail -f /var/log/rhsm/rhsm.log
.....
2012-08-29 05:57:23,767 [DEBUG]  @virt.py:72 - EVENT: Domain 5.8_Server_x86_64_FV(-1) Defined Added
2012-08-29 05:57:23,839 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Server_x86_64_PV: b762619e-3324-5a6f-7c63-63a1bf3a16b6
2012-08-29 05:57:23,847 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Client_i386_PV: 41766df1-1677-c605-9bc0-5cef2eab5782
2012-08-29 05:57:23,855 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Client_i386_PV: fc2f0e60-7b92-a284-4b12-e60dd467e0b9
2012-08-29 05:57:23,863 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Client_i386_FV: a078493b-33fc-b828-aad5-13b85a0b327d
2012-08-29 05:57:23,871 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Server_x86_64_FV: da6aa1e1-ecd8-51f2-f6c7-0e355bcecc83
2012-08-29 05:57:23,879 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Server_x86_64_PV: 8b3b82a0-a33f-e88a-c453-7b36a6d210af
2012-08-29 05:57:23,894 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Server_x86_64_FV: e59792a2-160d-2689-2725-dc712724f6c0
2012-08-29 05:57:23,898 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Client_i386_FV: 716e3954-80e4-5882-52ca-c85a1cc831a9
2012-08-29 05:57:23,900 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Client_i386_FV: 4879bd28-e3f5-2749-dbef-08c383aabdc4
2012-08-29 05:57:23,903 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Client_i386_PV: 8df4722a-5382-4d44-44f1-af07e8c02918
2012-08-29 05:57:23,907 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Server_x86_64_PV: d9cebfc7-3f28-a5f5-464b-1d71e0d986a6
2012-08-29 05:57:23,911 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Server_x86_64_FV: e5d65602-d8ac-a55e-3a61-ac09a2e28b6b
2012-08-29 05:57:23,911 [DEBUG]  @subscriptionmanager.py:81 - Sending list of uuids: ['41766df1-1677-c605-9bc0-5cef2eab5782', '4879bd28-e3f5-2749-dbef-08c383aabdc4', '716e3954-80e4-5882-52ca-c85a1cc831a9', '8b3b82a0-a33f-e88a-c453-7b36a6d210af', '8df4722a-5382-4d44-44f1-af07e8c02918', 'a078493b-33fc-b828-aad5-13b85a0b327d', 'b762619e-3324-5a6f-7c63-63a1bf3a16b6', 'd9cebfc7-3f28-a5f5-464b-1d71e0d986a6', 'da6aa1e1-ecd8-51f2-f6c7-0e355bcecc83', 'e59792a2-160d-2689-2725-dc712724f6c0', 'e5d65602-d8ac-a55e-3a61-ac09a2e28b6b', 'fc2f0e60-7b92-a284-4b12-e60dd467e0b9']
2012-08-29 05:57:24,648 [DEBUG]  @virt.py:72 - EVENT: Domain 5.8_Server_x86_64_FV(-1) Defined Added
2012-08-29 05:59:43,315 [DEBUG]  @virt.py:72 - EVENT: Domain 5.8_Server_x86_64_FV(36) Started Booted
2012-08-29 05:59:43,317 [DEBUG]  @virt.py:56 - Virtual machine found: 5.8_Server_x86_64_FV: e59792a2-160d-2689-2725-dc712724f6c0
2012-08-29 05:59:43,400 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Server_x86_64_PV: b762619e-3324-5a6f-7c63-63a1bf3a16b6
2012-08-29 05:59:43,404 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Client_i386_PV: 41766df1-1677-c605-9bc0-5cef2eab5782
2012-08-29 05:59:43,408 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Client_i386_PV: fc2f0e60-7b92-a284-4b12-e60dd467e0b9
2012-08-29 05:59:43,412 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Client_i386_FV: a078493b-33fc-b828-aad5-13b85a0b327d
2012-08-29 05:59:43,416 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Server_x86_64_FV: da6aa1e1-ecd8-51f2-f6c7-0e355bcecc83
2012-08-29 05:59:43,420 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Server_x86_64_PV: 8b3b82a0-a33f-e88a-c453-7b36a6d210af
2012-08-29 05:59:43,424 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Client_i386_FV: 716e3954-80e4-5882-52ca-c85a1cc831a9
2012-08-29 05:59:43,428 [DEBUG]  @virt.py:62 - Virtual machine found: 6.3_Client_i386_FV: 4879bd28-e3f5-2749-dbef-08c383aabdc4
2012-08-29 05:59:43,432 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Client_i386_PV: 8df4722a-5382-4d44-44f1-af07e8c02918
2012-08-29 05:59:43,436 [DEBUG]  @virt.py:62 - Virtual machine found: 5.8_Server_x86_64_PV: d9cebfc7-3f28-a5f5-464b-1d71e0d986a6
2012-08-29 05:59:43,441 [DEBUG]  @virt.py:62 - Virtual machine found: 6.2_Server_x86_64_FV: e5d65602-d8ac-a55e-3a61-ac09a2e28b6b
2012-08-29 05:59:43,441 [DEBUG]  @subscriptionmanager.py:81 - Sending list of uuids: ['41766df1-1677-c605-9bc0-5cef2eab5782', '4879bd28-e3f5-2749-dbef-08c383aabdc4', '716e3954-80e4-5882-52ca-c85a1cc831a9', '8b3b82a0-a33f-e88a-c453-7b36a6d210af', '8df4722a-5382-4d44-44f1-af07e8c02918', 'a078493b-33fc-b828-aad5-13b85a0b327d', 'b762619e-3324-5a6f-7c63-63a1bf3a16b6', 'd9cebfc7-3f28-a5f5-464b-1d71e0d986a6', 'da6aa1e1-ecd8-51f2-f6c7-0e355bcecc83', 'e59792a2-160d-2689-2725-dc712724f6c0', 'e5d65602-d8ac-a55e-3a61-ac09a2e28b6b', 'fc2f0e60-7b92-a284-4b12-e60dd467e0b9'] ^^^^^^^^^^^^Can report the add vm's uuid

Comment 10 errata-xmlrpc 2013-01-08 07:35:41 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.

http://rhn.redhat.com/errata/RHBA-2013-0072.html


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