euca-run-instances fails

Bug #656012 reported by Mika Kohonen
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
David Pravec

Bug Description

I'm trying to follow the steps described in http://github.com/vishvananda/novascript , but I get this error after executing:

root@openstack:~# euca-run-instances -k test -t m1.tiny ami-tiny
RESERVATION r-f0zon4z0 admin
INSTANCE i-sl4vx1 ami-tiny 10.0.0.4 10.0.0.4 scheduling test (admin, None) 0 m1.tiny 2010-10-06 21:23:54

then I get this message executing euca-describe-instances:
root@openstack:~# euca-describe-instances
RESERVATION r-f0zon4z0 admin
INSTANCE i-sl4vx1 ami-tiny 10.0.0.4 10.0.0.4 shutdown test (admin, openstack) 0 m1.tiny 2010-10-06 21:23:54

If I check the nova-compute node then I have this trace in the logs:
2010-10-06 23:26:21+0200 [-] (root): DEBUG instance 5: starting...
DEBUG:root:Running cmd: ifconfig vlan100
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: ifconfig vlan100
DEBUG:root:Running cmd: ifconfig br100
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: ifconfig br100
DEBUG:root:Running cmd: sudo ifconfig br100 up
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo ifconfig br100 up
DEBUG:root:Running cmd: sudo iptables --delete FORWARD --in-interface br100 -j ACCEPT
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables --delete FORWARD --in-interface br100 -j ACCEPT
DEBUG:root:Running cmd: sudo iptables -I FORWARD --in-interface br100 -j ACCEPT
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables -I FORWARD --in-interface br100 -j ACCEPT
DEBUG:root:Running cmd: sudo iptables --delete FORWARD --out-interface br100 -j ACCEPT
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables --delete FORWARD --out-interface br100 -j ACCEPT
DEBUG:root:Running cmd: sudo iptables -I FORWARD --out-interface br100 -j ACCEPT
2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables -I FORWARD --out-interface br100 -j ACCEPT
DEBUG:root:instance 435059996: starting toXML method
2010-10-06 23:26:21+0200 [-] (root): DEBUG instance 435059996: starting toXML method
ERROR:root:instance 435059996: Failed to spawn
Traceback (most recent call last):
  File "/root/vishvananda-novascript-3ac378c/nova/nova/compute/manager.py", line 86, in run_instance
    yield self.driver.spawn(instance_ref)
AttributeError: 'long' object has no attribute 'startswith'
2010-10-06 23:26:21+0200 [-] (root): ERROR instance 435059996: Failed to spawn
2010-10-06 23:26:21+0200 [-] Traceback (most recent call last):
2010-10-06 23:26:21+0200 [-] File "/root/vishvananda-novascript-3ac378c/nova/nova/compute/manager.py", line 86, in run_instance
2010-10-06 23:26:21+0200 [-] yield self.driver.spawn(instance_ref)
2010-10-06 23:26:21+0200 [-] AttributeError: 'long' object has no attribute 'startswith'
2010-10-06 23:26:21+0200 [-] Unhandled error in Deferred:
2010-10-06 23:26:21+0200 [-] Unhandled Error
        Traceback (most recent call last):
          File "/root/vishvananda-novascript-3ac378c/nova/nova/exception.py", line 76, in _wrap
            return f(*args, **kw)
          File "/root/vishvananda-novascript-3ac378c/nova/nova/rpc.py", line 171, in receive
            d = defer.maybeDeferred(node_func, **node_args)
          File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 117, in maybeDeferred
            result = f(*args, **kw)
          File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 944, in unwindGenerator
            return _inlineCallbacks(None, f(*args, **kwargs), Deferred())
        --- <exception caught here> ---
          File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 821, in _inlineCallbacks
            result = result.throwExceptionIntoGenerator(g)
          File "/usr/lib/python2.6/dist-packages/twisted/python/failure.py", line 338, in throwExceptionIntoGenerator
            return g.throw(self.type, self.value, self.tb)
          File "/root/vishvananda-novascript-3ac378c/nova/nova/compute/manager.py", line 98, in run_instance
            self._update_state(context, instance_id)
          File "/root/vishvananda-novascript-3ac378c/nova/nova/compute/manager.py", line 62, in _update_state
            state = self.driver.get_info(instance_ref.name)['state']
          File "/root/vishvananda-novascript-3ac378c/nova/nova/virt/libvirt_conn.py", line 334, in get_info
            virt_dom = self._conn.lookupByName(instance_name)
          File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1441, in lookupByName
            ret = libvirtmod.virDomainLookupByName(self._o, name)
        exceptions.TypeError: virDomainLookupByName() argument 2 must be string or None, not long

My environment is a Ubuntu 10.4 Desktop 64 bits with latest updates running inside a VirtualBox 3.2.8. I have configured nova to run with slapd and mysql. Libvirt is configured for qemu.

Related branches

summary: - euca-run-instances fails running sample novascript
+ euca-run-instances fails running sample novascript in VBox with qemu
Revision history for this message
David Pravec (alekibango) wrote : Re: euca-run-instances fails running sample novascript in VBox with qemu

qemu/virtualbox is not important -- the bug is there even on real hw

Changed in nova:
status: New → Confirmed
assignee: nobody → David Pravec (alekibango-danix)
summary: - euca-run-instances fails running sample novascript in VBox with qemu
+ euca-run-instances fails running sample novascript
summary: - euca-run-instances fails running sample novascript
+ euca-run-instances fails
Changed in nova:
status: Confirmed → In Progress
Revision history for this message
Rick Clark (dendrobates) wrote :

I cannot reproduce this. What is the status, and how can it be reproduced?

Rick Clark (dendrobates)
Changed in nova:
status: In Progress → Fix Released
Revision history for this message
Mika Kohonen (mika-kohonen-1986) wrote :

It does not fail anymore in the trunk.

Revision history for this message
Kevin Fox (kevnfx) wrote : Re: [Bug 656012] Re: euca-run-instances fails
Download full text (6.1 KiB)

I saw this last week when I was pulling over the instance_id changes ... vishy had a fix in his branch that changed the return type of the name method from long to a string ... following from the logs:

2010-10-07T17:58:51 <kevnfx> vishy: regarding "startswith", I'm having the same exception. Appears that virDomainLookupByName is being passed in a long rather than a string. Wasn't instance_id recently changed?
2010-10-07T18:00:07 <vishy> kevnfx: there is a fix posted, it involves changing nova/db/sqlalchemy/models.py
2010-10-07T18:00:32 <vishy> the name method on instance should return str(self.internal_id)
2010-10-07T18:00:45 <kevnfx> vishy: cool .. thanks!

There was duplicate bug that was being fixed simultaneously, in any case, what I experienced has been fixed.

Kev

On Oct 19, 2010, at 10:50 AM, Rick Clark wrote:

> I cannot reproduce this. What is the status, and how can it be
> reproduced?
>
> --
> euca-run-instances fails
> https://bugs.launchpad.net/bugs/656012
> You received this bug notification because you are subscribed to
> OpenStack.
>
> Status in OpenStack Compute (Nova): In Progress
>
> Bug description:
> I'm trying to follow the steps described in http://github.com/vishvananda/novascript , but I get this error after executing:
>
> root@openstack:~# euca-run-instances -k test -t m1.tiny ami-tiny
> RESERVATION r-f0zon4z0 admin
> INSTANCE i-sl4vx1 ami-tiny 10.0.0.4 10.0.0.4 scheduling test (admin, None) 0 m1.tiny 2010-10-06 21:23:54
>
> then I get this message executing euca-describe-instances:
> root@openstack:~# euca-describe-instances
> RESERVATION r-f0zon4z0 admin
> INSTANCE i-sl4vx1 ami-tiny 10.0.0.4 10.0.0.4 shutdown test (admin, openstack) 0 m1.tiny 2010-10-06 21:23:54
>
> If I check the nova-compute node then I have this trace in the logs:
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG instance 5: starting...
> DEBUG:root:Running cmd: ifconfig vlan100
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: ifconfig vlan100
> DEBUG:root:Running cmd: ifconfig br100
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: ifconfig br100
> DEBUG:root:Running cmd: sudo ifconfig br100 up
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo ifconfig br100 up
> DEBUG:root:Running cmd: sudo iptables --delete FORWARD --in-interface br100 -j ACCEPT
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables --delete FORWARD --in-interface br100 -j ACCEPT
> DEBUG:root:Running cmd: sudo iptables -I FORWARD --in-interface br100 -j ACCEPT
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables -I FORWARD --in-interface br100 -j ACCEPT
> DEBUG:root:Running cmd: sudo iptables --delete FORWARD --out-interface br100 -j ACCEPT
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables --delete FORWARD --out-interface br100 -j ACCEPT
> DEBUG:root:Running cmd: sudo iptables -I FORWARD --out-interface br100 -j ACCEPT
> 2010-10-06 23:26:21+0200 [-] (root): DEBUG Running cmd: sudo iptables -I FORWARD --out-interface br100 -j ACCEPT
> DEBUG:root:in...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.