Hide Forgot
description: Virt-who reports error info when it it starting in ESX mode. Version-Release number of selected component (if applicable): virt-who-0.5-3.el5 python-rhsm-0.98.8-1.el5 subscription-manager-0.98.9-1.el5 subscription-manager-gnome-0.98.9-1.el5 subscription-manager-firstboot-0.98.9-1.el5 katello-glue-candlepin-0.1.150-2.el6.noarch katello-httpd-ssl-key-pair-1.0-1.noarch katello-cli-common-0.1.30-2.el6.noarch katello-configure-0.1.42-2.el6.noarch katello-headpin-all-0.1.119-2.el6.noarch katello-cli-headpin-0.1.13-2.el6.noarch katello-certs-tools-1.0.1-2.el6.noarch katello-headpin-0.1.119-2.el6.noarch katello-trusted-ssl-cert-1.0-1.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-common-0.1.150-2.el6.noarch katello-glue-candlepin-0.1.150-2.el6.noarch candlepin-0.5.8-1.el6.noarch candlepin-tomcat6-0.5.8-1.el6.noarch thumbslug-0.0.21-1.el6.noarch How reproducible: always Steps to Reproduce: 1. prepared one rhel5.8-snapshot2.0 host, and register to SAM: #subscription-namager register --org=org1 --environment=org1-env1 --username=$username --password=$password 2.Deployed the env of ESX as following: Vcenter server IP : 10.66.5.176 Vsphere client Ip : 10.66.6.128 ESX IP: 10.66.6.66 Installed some Guests on ESX 3.Set the /etc/sysconfig/virt-who on rhel5.8-snapshot2.0 host (or on one of the guests that is installed on ESX). #vim /etc/sysconfig/virt-who VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=org1 VIRTWHO_ESX_ENV=org1-env1 VIRTWHO_ESX_SERVER=https://10.66.5.176 VIRTWHO_ESX_USERNAME=Administrator VIRTWHO_ESX_PASSWORD=123qweP 4.Start the virt-who service #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 esx mode Starting infinite loop with 3600 seconds interval and event handling [ OK ] [root@wanghui ca]# unknown url type: 10.66.5.176/sdk/vimService.wsdl Traceback (most recent call last): File "/usr/share/virt-who/virt-who.py", line 130, in _send self.checkConnections() File "/usr/share/virt-who/virt-who.py", line 110, in checkConnections self.initVirt() File "/usr/share/virt-who/virt-who.py", line 70, in initVirt self.virt = VSphere(self.logger, self.options.esx_server, self.options.esx_username, self.options.esx_password) File "/usr/share/virt-who/vsphere.py", line 94, in __init__ self.client = suds.client.Client("%s/sdk/vimService.wsdl" % url) File "/usr/lib/python2.4/site-packages/suds/client.py", line 112, in __init__ self.wsdl = reader.open(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 152, in open d = self.fn(url, self.options) File "/usr/lib/python2.4/site-packages/suds/wsdl.py", line 136, in __init__ d = reader.open(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 79, in open d = self.download(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 95, in download fp = self.options.transport.open(Request(url)) File "/usr/lib/python2.4/site-packages/suds/transport/https.py", line 60, in open return HttpTransport.open(self, request) File "/usr/lib/python2.4/site-packages/suds/transport/http.py", line 62, in open return self.u2open(u2request) File "/usr/lib/python2.4/site-packages/suds/transport/http.py", line 116, in u2open return url.open(u2request) File "/usr/lib64/python2.4/urllib2.py", line 350, in open protocol = req.get_type() File "/usr/lib64/python2.4/urllib2.py", line 233, in get_type raise ValueError, "unknown url type: %s" % self.__original ValueError: unknown url type: 10.66.5.176/sdk/vimService.wsdl Unexcepted error occurs, trying to recover unknown url type: 10.66.5.176/sdk/vimService.wsdl Traceback (most recent call last): File "/usr/share/virt-who/virt-who.py", line 130, in _send self.checkConnections() File "/usr/share/virt-who/virt-who.py", line 110, in checkConnections self.initVirt() File "/usr/share/virt-who/virt-who.py", line 70, in initVirt self.virt = VSphere(self.logger, self.options.esx_server, self.options.esx_username, self.options.esx_password) File "/usr/share/virt-who/vsphere.py", line 94, in __init__ self.client = suds.client.Client("%s/sdk/vimService.wsdl" % url) File "/usr/lib/python2.4/site-packages/suds/client.py", line 112, in __init__ self.wsdl = reader.open(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 152, in open d = self.fn(url, self.options) File "/usr/lib/python2.4/site-packages/suds/wsdl.py", line 136, in __init__ d = reader.open(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 79, in open d = self.download(url) File "/usr/lib/python2.4/site-packages/suds/reader.py", line 95, in download fp = self.options.transport.open(Request(url)) File "/usr/lib/python2.4/site-packages/suds/transport/https.py", line 60, in open return HttpTransport.open(self, request) File "/usr/lib/python2.4/site-packages/suds/transport/http.py", line 62, in open return self.u2open(u2request) File "/usr/lib/python2.4/site-packages/suds/transport/http.py", line 116, in u2open return url.open(u2request) File "/usr/lib64/python2.4/urllib2.py", line 350, in open protocol = req.get_type() File "/usr/lib64/python2.4/urllib2.py", line 233, in get_type raise ValueError, "unknown url type: %s" % self.__original ValueError: unknown url type: 10.66.5.176/sdk/vimService.wsdl Unable to recover, retry in 60 seconds. Actual results: Virt-who reports error infos when it is starting in ESX mode. Expected results: Virt-who can report guest uuid infos in ESX mode.
This bug is easy to fix, virt-who will add "https://" to the esx server address if not present. Prefix "https://" can be manually added as workaround.
Fixed in virt-who-0.5-4.el5. Build here https://brewweb.devel.redhat.com/taskinfo?taskID=3933709
I verified the issue. The result is pass. Version-Release number of selected component (if applicable): virt-who-0.5-4.el5 python-rhsm-0.98.8-1.el5 subscription-manager-0.98.9-1.el5 subscription-manager-gnome-0.98.9-1.el5 subscription-manager-firstboot-0.98.9-1.el5 katello-glue-candlepin-0.1.150-2.el6.noarch katello-httpd-ssl-key-pair-1.0-1.noarch katello-cli-common-0.1.30-2.el6.noarch katello-configure-0.1.42-2.el6.noarch katello-headpin-all-0.1.119-2.el6.noarch katello-cli-headpin-0.1.13-2.el6.noarch katello-certs-tools-1.0.1-2.el6.noarch katello-headpin-0.1.119-2.el6.noarch katello-trusted-ssl-cert-1.0-1.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-common-0.1.150-2.el6.noarch katello-glue-candlepin-0.1.150-2.el6.noarch candlepin-0.5.8-1.el6.noarch candlepin-tomcat6-0.5.8-1.el6.noarch thumbslug-0.0.21-1.el6.noarch How reproducible: always Steps to Reproduce: 1. prepared one rhel5.8-snapshot4.0 host, and register to SAM: #subscription-namager register --org=ACME_Corporation --environment=env1 --username=$username --password=$password 2.Deployed the env of ESX as following: Set the vcenter's username/password Vcenter username : Administrator Vcenter password :123qweP Vcenter server IP : 10.66.5.176 Vsphere client Ip : 10.66.6.128 ESX IP: 10.66.6.66 ESX username=$username ESX password=$password Installed some Guests on ESX 3.Set the /etc/sysconfig/virt-who on rhel5.8-snapshot4.0 host (or on one of the guests that is installed on ESX). #vim /etc/sysconfig/virt-who VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=ACME_Corporation VIRTWHO_ESX_ENV=env1 VIRTWHO_ESX_SERVER=10.66.5.176 VIRTWHO_ESX_USERNAME=Administrator VIRTWHO_ESX_PASSWORD=123qweP 4.Restart virt-who service [root@localhost ~]# 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 esx mode Starting infinite loop with 3600 seconds interval and event handling [ OK ] [root@localhost ~]# Sending updates in hosts-to-guests mapping: {44454c4c-4c00-1031-8053-b8c04f4e3258: [564daad1-a9dc-d0d9-9bfb-d2a730a888ce, 564d6e32-2f23-d7cd-09b1-e5861086c087, 564dcd6a-01ab-d413-5ea9-1275dff5ff58, 564d5f4c-b07f-22cf-a9fd-234ba11f46f9, 423bad51-b0ba-cb54-6154-2b6bcc4cae7b]} Error during update list of guests: 44454c4c-4c00-1031-8053-b8c04f4e3258: No such consumer type: hypervisor
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