nova-compute-xen fails to contact XCP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After I finished the packaging of XCP in Debian SID (you can try it, it's available right now), I'm now trying to have it to run with Openstack (current version in Experimental: 2012.1~
http://
and when checking if Openstack can connect to XCP, here's what I get:
root@GPLHost:os>_ ~# nova-manage shell python
Python 2.7.2+ (default, Dec 17 2011, 16:58:10)
[GCC 4.6.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveCon
>>> import XenAPI
>>> import nova.virt.
>>> nova.virt.
>>> x = nova.virt.
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/usr/lib/
self.
File "/usr/lib/
return tuple(int(part) for part in product_
File "/usr/lib/
return tuple(int(part) for part in product_
ValueError: invalid literal for int() with base 10: ''
I know the authentication part already worked, since I get a different reply if I type a wrong root password.
Please let me know and CC me if possible (my email: <email address hidden>).
Cheers,
Thomas
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → Invalid |
Your XCP installation is not returning it's version in xx.xx.xx format that get_production_ version wants.
While this is a problem with your version of XCP, it's also a problem with XenAPISession: get_product_ version as it should be trapping the
return tuple(int(part) for part in product_ version. split(' .'))
with if it doesn't split properly.
I would propose that if the product_ version. split(' .') doesn't work correctly, we should return a standard value or error. Looking at the codebase, it appears that the path of least interruption would be to set it to something like 0.0.0 , but I'm not familiar enough with XenAPI to make this call.
Comments or Suggestions ?