Bug 754330 - Can not retrieve running guests UUID in RHEVH node.
Summary: Can not retrieve running guests UUID in RHEVH node.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-who
Version: 5.8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 5.8
Assignee: Radek Novacek
QA Contact:
URL:
Whiteboard:
Depends On: 765728
Blocks: 703617 715031 758797 759462
TreeView+ depends on / blocked
 
Reported: 2011-11-16 07:24 UTC by cshao
Modified: 2016-12-01 00:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 759462 (view as bug list)
Environment:
Last Closed: 2012-02-21 06:06:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhsm.log (16.13 KB, text/plain)
2011-11-16 07:24 UTC, cshao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0225 0 normal SHIPPED_LIVE new package: virt-who 2012-02-20 15:07:56 UTC

Description cshao 2011-11-16 07:24:55 UTC
Created attachment 533920 [details]
rhsm.log

Description of problem:
Can not retrieve running guests UUID in RHEVH node.

Version-Release number of selected component (if applicable):
rhev-hypervisor5-5.8-20111108.0.el5
vdsm22-4.5-67.el5_7
virt-who-0.3-3.el5
libvirt-0.8.2-24.el5
rhevm-3.0.0_0001-57.el6.x86_64 & SM 110

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H, and register to RHEV-M.
2. Create some guests, run the guests.
3. Configure the virt-who.
    # vi /etc/sysconfig/virt-who
    VIRTWHO_BACKGROUND=1 (enable debugging)
    VIRTWHO_DEBUG=1 (run in background)     
4. Restart the virt-who service.
    # service virt-who restart
5. Get consumer uuid
    # subscription-manager identity
  
Actual results:
Can not retrieve running guests UUID in RHEVH node.


#/etc/init.d/virt-who restart
Stopping virt-who:                                         [  OK  ]
Starting virt-who:                                         [  OK  ]
[root@hp-slot2-eth0 rhsm]# Unable to obtain status from server, UEPConnection is likely not usable:
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/__init__.py", line 731, in emit
  File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 272, in getMessage
AttributeError: RemoteServerException instance has no attribute 'args'
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/handlers.py", line 71, in emit
  File "/usr/lib64/python2.4/logging/handlers.py", line 149, in shouldRollover
  File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 272, in getMessage
AttributeError: RemoteServerException instance has no attribute 'args'
Sending update to updateConsumer: []
Entering infinite loop

# subscription-manager identity
Current identity is: 38a7b46c-6578-4b1e-9cc3-a331b40c667e
name: hp-slot2-eth0.qe.lab.eng.nay.redhat.com
org name: 6445999
org id: 8a99f981335b908601336a13524b51fe
# 


Expected results:
Can retrieve running guests UUID in RHEVH node.

Additional info:

Comment 1 Radek Novacek 2011-11-16 07:37:55 UTC
Have you created the guests using libvirt or vdsm? For vdsm you have to set VIRTWHO_VDSM=1 in /etc/sysconfig/virt-who.

Comment 3 Keqin Hong 2011-11-16 08:13:45 UTC
Radek,
Looks like vdsm code has not been in virt-who-0.3-3.el5.

Comment 4 Radek Novacek 2011-11-16 14:47:09 UTC
Keqin, you are correct, sorry, I forgot that. Thanks.

Should I do another build for RHEL-5 or is the workflow for RHEVH different?

Comment 8 Radek Novacek 2011-12-02 08:15:42 UTC
Brew build done:

https://brewweb.devel.redhat.com/taskinfo?taskID=3865459

Comment 10 Hui Wang 2011-12-19 06:50:30 UTC
verified as following:
1. Install RHEV-H, and register to RHEV-M and candlepin.
2. Create some guests, run the guests.
3. Configure the virt-who.
    # vi /etc/sysconfig/virt-who
    VIRTWHO_BACKGROUND=1 (enable debugging)
    VIRTWHO_DEBUG=1 (run in background)
    VIRTWHO_VDSM=1     

4. Restart the virt-who service.
    # service virt-who restart

[root@wanghui02 ~]# service virt-who restart
Stopping virt-who:                                         [  OK  ]
Starting virt-who: Listening for events is not available in VDSM or ESX mode
Virt-who is running in vdsm mode
Starting infinite loop with 3600 seconds interval and event handling
                                                           [  OK  ]
[root@wanghui02 ~]# Unable to obtain status from server, UEPConnection is likely not usable:
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/__init__.py", line 731, in emit
  File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 272, in getMessage
AttributeError: RemoteServerException instance has no attribute 'args'
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/handlers.py", line 71, in emit
  File "/usr/lib64/python2.4/logging/handlers.py", line 149, in shouldRollover
  File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
  File "/usr/lib64/python2.4/logging/__init__.py", line 272, in getMessage
AttributeError: RemoteServerException instance has no attribute 'args'
Sending update to updateConsumer: ['7f0c8f4a-67a2-4f09-b983-87069ed5ce82', '8684588c-2db4-4bf7-ad82-da0afd4b25bd']

Comment 13 errata-xmlrpc 2012-02-21 06:06:42 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/RHEA-2012-0225.html


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