[Openstack] Problem when running nova-manage db sync
Hi All, I'm rying to install OpenStack Essex and when I run the nova-manage db sync from this doc's part http://docs.openstack.org/essex/openstack-compute/install/apt/content/compute-db-sync.html, it returs these errors: 2012-12-10 10:56:57 DEBUG nova.utils [-] backend module 'nova.db.sqlalchemy.migration' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.pyc' from (pid=6208) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 2012-12-10 10:56:58 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:683: SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen(). Pool.__init__(self, creator, **kw) 2012-12-10 10:56:58 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:159: SADeprecationWarning: Pool.add_listener is deprecated. Use event.listen() self.add_listener(l) Can anybody help me? Thank you so much. Guilherme Russi. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Problem when running nova-manage db sync
Hi: It's simply a warning message. I guess that next releases (Folsom, Grizzly...) will not use this deprecated argument. Regards, 2012/12/10 Guilherme Russi luisguilherme...@gmail.com Hi All, I'm rying to install OpenStack Essex and when I run the nova-manage db sync from this doc's part http://docs.openstack.org/essex/openstack-compute/install/apt/content/compute-db-sync.html, it returs these errors: 2012-12-10 10:56:57 DEBUG nova.utils [-] backend module 'nova.db.sqlalchemy.migration' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.pyc' from (pid=6208) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 2012-12-10 10:56:58 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:683: SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen(). Pool.__init__(self, creator, **kw) 2012-12-10 10:56:58 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:159: SADeprecationWarning: Pool.add_listener is deprecated. Use event.listen() self.add_listener(l) Can anybody help me? Thank you so much. Guilherme Russi. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Why my vm often change into shut off status by itself?
Maybe you need to enable the following flag in nova.conf: resume_guests_state_on_host_boot=True The default is False it seems (Didn't confirm it), so if you expect the machines to be in running state when you reboot the host, you should enable that flag. Although it seems your problem seems to be when the host is not rebooted, so it may not help for your case. On Thu, Dec 6, 2012 at 5:49 PM, Wangpan hzwang...@corp.netease.com wrote: ** qemu: terminating on signal 15 from pid 1957 this means the VM is shutted off by libvirtd/libvirt api, the log of my VM is same as this, so you should check who calls the libvirt to shut down your VMs. I have no other ideas now, good luck, guy! 2012-12-06 -- Wangpan -- *发件人：*pyw *发送时间：*2012-12-06 17:34 *主题：*Re: Re: [Openstack] Why my vm often change into shut off status by itself? *收件人：*Wangpanhzwang...@corp.netease.com *抄送：*openstackopenstack@lists.launchpad.net Individual virtual machines automatically shutoff occurs frequently, this time all the virtual machines are automatic shutoff at the same time. If the nova failed to delete the virtual machine will cause the virtual machine is shut down? 2012/12/6 Wangpan hzwang...@corp.netease.com ** are that all VMs shutting down at the same time? such as '2012-12-04 06:54:27.150+: shutting down' or near this point? if this is true, I guess it may be the host's problem. 2012-12-06 -- Wangpan -- *发件人：*pyw *发送时间：*2012-12-06 17:10 *主题：*Re: [Openstack] Why my vm often change into shut off status by itself? *收件人：*Veera Reddyveerare...@gmail.com *抄送：*openstackopenstack@lists.launchpad.net Generally if you use virsh to restart the virtual machine，it seems to be able to use some time before shutoff again。 $ date Thu Dec 6 17:04:41 CST 2012 $ virsh start instance-006e Domain instance-006e started $ virsh list Id Name State -- 158 instance-006erunning /var/log/libvirt/qemu$ sudo tail -f instance-006e.log 2012-12-03 06:14:13.488+: shutting down qemu: terminating on signal 15 from pid 1957 2012-12-03 06:14:59.819+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -cpu core2duo,+lahf_lm,+aes,+popcnt,+sse4.2,+sse4.1,+cx16,-monitor,-vme -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-006e -uuid d7798df8-e225-4178-9d0b-f6691d78ce18 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-006e.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -drive file=/data0/instances/instance-006e/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:17:ca:dd,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/data0/instances/instance-006e/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:2 -k en-us -vga cirrus -incoming fd:23 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 char device redirected to /dev/pts/27 qemu: terminating on signal 15 from pid 1957 2012-12-04 06:54:27.150+: shutting down 2012-12-06 09:02:46.343+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -cpu core2duo,+lahf_lm,+aes,+popcnt,+sse4.2,+sse4.1,+cx16,-monitor,-vme -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-006e -uuid d7798df8-e225-4178-9d0b-f6691d78ce18 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-006e.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -drive file=/data0/instances/instance-006e/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:17:ca:dd,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/data0/instances/instance-006e/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:2 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 char device redirected to /dev/pts/30 We can see this two log：
[Openstack] Problem hen running VM instances
Hi again guys,
I'm sorry for all these questions, but when I learn how to install it I'll
help people with these same problems, well, I'm trying to run a VM instance
on Essex, a ubuntu image, but when I try to boot it the OS-EXT-STS:vm_state
is error.
What am I missing?
Thank you all again.
Guilherme Russi.
nova --os_tenant_name cloud image-list
+--+---+++
| ID|Name
| Status | Server |
+--+---+++
| 31d45bd5-5ba5-45b6-814e-54eef1699074 | tty-linux-ramdisk | ACTIVE |
|
| b54cd532-20c2-4b48-a735-6d7fd6b083b8 | tty-linux-kernel | ACTIVE |
|
| c16e7a7a-3c21-44db-8a38-5a49fa262ac9 | tty-linux-kernel | SAVING |
|
| d5220087-89ce-486f-a98e-3eb2c367d7ba | tty-linux | ACTIVE |
|
+--+---+++
nova --os_tenant_name cloud boot --flavor 2 --image
b54cd532-20c2-4b48-a735-6d7fd6b083b8 --security_group default imagem
+-+--+
| Property |Value |
+-+--+
| OS-DCF:diskConfig |MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
|OS-EXT-SRV-ATTR:instance_name| instance-0001
|
|OS-EXT-STS:power_state | 0
|
|OS-EXT-STS:task_state| scheduling
|
| OS-EXT-STS:vm_state |error
|
| accessIPv4 |
|
| accessIPv6 |
|
| adminPass | V4oFZcgLjrYn
|
| config_drive|
|
| created | 2012-12-10T15:56:44Z
|
|flavor | m1.small
|
|hostId |
|
| id |
f43f77e7-1e36-4e19-b752-2e4c3ba7c076 |
|image| tty-linux-kernel
|
| key_name |
|
| metadata | {}
|
| name|imagem
|
| progress | 0
|
|status |BUILD
|
| tenant_id | d52768c939ee4a1b8dc82182a29df8d2
|
| updated | 2012-12-10T15:56:44Z
|
| user_id | 830ae8bc830440c28372066bdf20d9bc
|
+-+--+
nova --os_tenant_name cloud list
+--+++--+
| ID | Name | Status | Networks |
+--+++--+
| f43f77e7-1e36-4e19-b752-2e4c3ba7c076 | imagem | ERROR | |
+--+++--+
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Problem hen running VM instances
Hi,
The simplest way to check is to have a look at /var/log/nova/nova-compute.log
Regards,
Gabriel
From: Guilherme Russi luisguilherme...@gmail.com
To: openstack@lists.launchpad.net
Sent: Monday, December 10, 2012 6:15 PM
Subject: [Openstack] Problem hen running VM instances
Hi again guys,
I'm sorry for all these questions, but when I learn how to install it I'll
help people with these same problems, well, I'm trying to run a VM instance on
Essex, a ubuntu image, but when I try to boot it the OS-EXT-STS:vm_state is
error.
What am I missing?
Thank you all again.
Guilherme Russi.
nova --os_tenant_name cloud image-list
+--+---+++
| ID | Name
| Status | Server |
+--+---+++
| 31d45bd5-5ba5-45b6-814e-54eef1699074 | tty-linux-ramdisk | ACTIVE | |
| b54cd532-20c2-4b48-a735-6d7fd6b083b8 | tty-linux-kernel | ACTIVE | |
| c16e7a7a-3c21-44db-8a38-5a49fa262ac9 | tty-linux-kernel | SAVING | |
| d5220087-89ce-486f-a98e-3eb2c367d7ba | tty-linux | ACTIVE |
|
+--+---+++
nova --os_tenant_name cloud boot --flavor 2 --image
b54cd532-20c2-4b48-a735-6d7fd6b083b8 --security_group default imagem
+-+--+
| Property | Value |
+-+--+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | instance-0001 |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | error |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | V4oFZcgLjrYn |
| config_drive | |
| created | 2012-12-10T15:56:44Z |
| flavor | m1.small |
| hostId | |
| id | f43f77e7-1e36-4e19-b752-2e4c3ba7c076 |
| image | tty-linux-kernel |
| key_name | |
| metadata | {} |
| name | imagem |
| progress | 0 |
| status | BUILD |
| tenant_id | d52768c939ee4a1b8dc82182a29df8d2 |
| updated | 2012-12-10T15:56:44Z |
| user_id | 830ae8bc830440c28372066bdf20d9bc |
+-+--+
nova --os_tenant_name cloud list
+--+++--+
| ID | Name | Status | Networks |
+--+++--+
| f43f77e7-1e36-4e19-b752-2e4c3ba7c076 | imagem | ERROR | |
+--+++--+
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Volume types
Hello. I've been playing around with OpenStack, when I noticed a section in the Dashboard where you can create/delete volume types. The problem is, I didn't understand their purpose, as when you create a new type, you only specify its name. Can anyone tell me what are volume types used for? Thanks in advance -- My best regards, Daniel Oliveira. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance no route to host problem
Ooops... I got it. Thought nova-compute has responsibilities in local iptables settings. I guess I was misled by the fact that I have default iptables rules setup at boot time in my VM which looks like rules defined in security group but it's just a coincidence. Thanks Patrick 2012/12/10 Patrick Petit patrick.michel.pe...@gmail.com Hi Lei, I could spend some more time looking at my no route to host issue today. I could be very well that the iptables on VM is the root of the problem. Here is what it looks like. *$ sudo iptables -L* *Chain INPUT (policy ACCEPT)* *target prot opt source destination * *ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED* *ACCEPT icmp -- anywhere anywhere* *ACCEPT all -- anywhere anywhere* *ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh* *REJECT all -- anywhere anywhere reject-with icmp-host-prohibited* * * *Chain FORWARD (policy ACCEPT)* *target prot opt source destination * *REJECT all -- anywhere anywhere reject-with icmp-host-prohibited* * * *Chain OUTPUT (policy ACCEPT)* *target prot opt source destination * I am not unfortunately very familiar with iptables's rules syntax Shouldn't ACCEPT all -- anywhere anywhere allow my http traffic to port 80? However, running explicitly *sudo iptables -A INPUT -p tcp -i eth0 --dport 80 -j ACCEPT* Does fix the problem. I can access my instance on port 80. But my VM is associated with the default security group in which I added a rule to enable http traffic. $ nova secgroup-list-rules default +-+---+-+---+--+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-+---+-+---+--+ | icmp| -1| -1 | 0.0.0.0/0 | | | tcp | 22| 22 | 0.0.0.0/0 | | | tcp | 80| 80 | 0.0.0.0/0 | | +-+---+-+---+--+ So the big question is why aren't my iptables rules in the VM no setup by the security group specs? I don't see any error in nova logs on the compute node. Any help would be really appreciated. Thanks Patrick 2012/12/6 Lei Zhang zhang.lei@gmail.com Could you check the iptables in the vm? Whether it drop the packets on the port 80 On Thu, Dec 6, 2012 at 12:29 AM, Patrick Petit patrick.michel.pe...@gmail.com wrote: Dear Stackers, I am running instance wordpress.WikiServer $ nova list +--+--+++ | ID | Name | Status | Networks | +--+--+++ | 6be47af7-2e29-4b4c-afeb-0a7f760f5970 | test2| ACTIVE | xlcloud=172.16.1.6 | | 5a4c552f-933c-4a06-8e6f-164176380af5 | wordpress.DatabaseServer | ACTIVE | xlcloud=172.16.1.3 | | ddb120d9-e1ad-444c-8490-37ecb15f500e | wordpress.WikiServer | ACTIVE | xlcloud=172.16.1.4, 10.197.217.131 | +--+--+++ With Security Group setup as: $ nova secgroup-list +---++ | Name | Description | +---++ | default | default | +---++ $ nova secgroup-list-rules default +-+---+-+---+--+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-+---+-+---+--+ | icmp| -1| -1 | 0.0.0.0/0 | | | tcp | 22| 22 | 0.0.0.0/0 | | | tcp | 80| 80 | 0.0.0.0/0 | | +-+---+-+---+--+ I can ping and ssh through the fix or floating IP without any problem (172.16.1.4, 10.197.217.131). But HTTP requests on port 80 doesn't go through. I get a no route host error message from wget or telnet for example. Ex. $ telnet 172.16.1.4 80 Trying 172.16.1.4... telnet: Unable to connect to remote host: No route to host. Clearly it's not a routing problem. Any idea what the problem could be or hints to debug it. Thanks Patrick
[Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Hi, I cannot start the nova-api service. [root@blade02 07-openstack-controller]# nova list ERROR: ConnectionRefused: '[Errno 111] Connection refused' I followed this guide very carefully: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/#07-openstack-controller-controller Here is api.log 2012-12-10 17:51:31 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=2536) load_app /usr/lib/python2.6/site-packages/nova/wsgi.py:371 2012-12-10 17:51:31 CRITICAL nova [-] [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova Traceback (most recent call last): 2012-12-10 17:51:31 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-12-10 17:51:31 TRACE nova server = service.WSGIService(api) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/service.py, line 584, in __init__ 2012-12-10 17:51:31 TRACE nova port=self.port) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/wsgi.py, line 72, in __init__ 2012-12-10 17:51:31 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/eventlet/convenience.py, line 38, in listen 2012-12-10 17:51:31 TRACE nova sock.bind(addr) 2012-12-10 17:51:31 TRACE nova File string, line 1, in bind 2012-12-10 17:51:31 TRACE nova error: [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova 2012-12-10 17:51:31 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-12-10 17:51:31 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-12-10 17:51:31 INFO nova.wsgi [-] Stopping WSGI server. 2012-12-10 17:51:31 INFO nova.wsgi [-] Stopping WSGI server. [root@blade02 07-openstack-controller]# cat /etc/nova/nova.conf [DEFAULT] logdir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp volumes_dir = /etc/nova/volumes dhcpbridge = /usr/bin/nova-dhcpbridge dhcpbridge_flagfile = /etc/nova/nova.conf force_dhcp_release = False injected_network_template = /usr/share/nova/interfaces.template libvirt_nonblocking = True libvirt_inject_partition = -1 network_manager = nova.network.manager.FlatDHCPManager iscsi_helper = tgtadm sql_connection = mysql://nova:x7deix7dei@controller/nova compute_driver = libvirt.LibvirtDriver firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver rpc_backend = nova.openstack.common.rpc.impl_qpid rootwrap_config = /etc/nova/rootwrap.conf verbose = True auth_strategy = keystone qpid_hostname = controller network_host = compute1 fixed_range = 10.0.0.0/24 flat_interface = eth1 flat_network_bridge = br100 public_interface = eth1 glance_host = controller vncserver_listen = 0.0.0.0 vncserver_proxyclient_address = controller novncproxy_base_url = http://37.123.104.3:6080/vnc_auto.html xvpvncproxy_base_url = http://37.123.104.3:6081/console metadata_host = 10.141.6.2 enabled_apis=ec2,osapi_compute,metadata #[keystone_authtoken] admin_tenant_name = %SERVICE_TENANT_NAME% admin_user = %SERVICE_USER% admin_password = %SERVICE_PASSWORD% auth_host = 127.0.0.1 auth_port = 35357 auth_protocol = http signing_dirname = /tmp/keystone-signing-nova There is no process using port 8774. [root@blade02 07-openstack-controller]# netstat -tunlp | grep 877 tcp0 0 0.0.0.0:87750.0.0.0:* LISTEN 2157/python Maybe it is something similar to: https://bugzilla.redhat.com/show_bug.cgi?id=877606#c3 Thanks, Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Volume types
On Mon, Dec 10, 2012 at 10:05 AM, Daniel Oliveira dvalbr...@gmail.comwrote: Hello. I've been playing around with OpenStack, when I noticed a section in the Dashboard where you can create/delete volume types. The problem is, I didn't understand their purpose, as when you create a new type, you only specify its name. Can anyone tell me what are volume types used for? Thanks in advance -- My best regards, Daniel Oliveira. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Hi Daniel, The primary idea behind volume-types is a method to deal with multiple back-ends. The volume-type corresponds to a specific back-end, or perhaps enables different characteristics of a back-end. Hopefully that helps a bit. John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Odd. This looks remarkably like it is trying to start osapi_volume even though you don't have it specified in enabled apis. Your enabled_apis setting looks correct to me. Vish On Dec 10, 2012, at 9:24 AM, Andrew Holway a.hol...@syseleven.de wrote: Hi, I cannot start the nova-api service. [root@blade02 07-openstack-controller]# nova list ERROR: ConnectionRefused: '[Errno 111] Connection refused' I followed this guide very carefully: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/#07-openstack-controller-controller Here is api.log 2012-12-10 17:51:31 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=2536) load_app /usr/lib/python2.6/site-packages/nova/wsgi.py:371 2012-12-10 17:51:31 CRITICAL nova [-] [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova Traceback (most recent call last): 2012-12-10 17:51:31 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-12-10 17:51:31 TRACE nova server = service.WSGIService(api) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/service.py, line 584, in __init__ 2012-12-10 17:51:31 TRACE nova port=self.port) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/wsgi.py, line 72, in __init__ 2012-12-10 17:51:31 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/eventlet/convenience.py, line 38, in listen 2012-12-10 17:51:31 TRACE nova sock.bind(addr) 2012-12-10 17:51:31 TRACE nova File string, line 1, in bind 2012-12-10 17:51:31 TRACE nova error: [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova 2012-12-10 17:51:31 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-12-10 17:51:31 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-12-10 17:51:31 INFO nova.wsgi [-] Stopping WSGI server. 2012-12-10 17:51:31 INFO nova.wsgi [-] Stopping WSGI server. [root@blade02 07-openstack-controller]# cat /etc/nova/nova.conf [DEFAULT] logdir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp volumes_dir = /etc/nova/volumes dhcpbridge = /usr/bin/nova-dhcpbridge dhcpbridge_flagfile = /etc/nova/nova.conf force_dhcp_release = False injected_network_template = /usr/share/nova/interfaces.template libvirt_nonblocking = True libvirt_inject_partition = -1 network_manager = nova.network.manager.FlatDHCPManager iscsi_helper = tgtadm sql_connection = mysql://nova:x7deix7dei@controller/nova compute_driver = libvirt.LibvirtDriver firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver rpc_backend = nova.openstack.common.rpc.impl_qpid rootwrap_config = /etc/nova/rootwrap.conf verbose = True auth_strategy = keystone qpid_hostname = controller network_host = compute1 fixed_range = 10.0.0.0/24 flat_interface = eth1 flat_network_bridge = br100 public_interface = eth1 glance_host = controller vncserver_listen = 0.0.0.0 vncserver_proxyclient_address = controller novncproxy_base_url = http://37.123.104.3:6080/vnc_auto.html xvpvncproxy_base_url = http://37.123.104.3:6081/console metadata_host = 10.141.6.2 enabled_apis=ec2,osapi_compute,metadata #[keystone_authtoken] admin_tenant_name = %SERVICE_TENANT_NAME% admin_user = %SERVICE_USER% admin_password = %SERVICE_PASSWORD% auth_host = 127.0.0.1 auth_port = 35357 auth_protocol = http signing_dirname = /tmp/keystone-signing-nova There is no process using port 8774. [root@blade02 07-openstack-controller]# netstat -tunlp | grep 877 tcp0 0 0.0.0.0:87750.0.0.0:* LISTEN 2157/python Maybe it is something similar to: https://bugzilla.redhat.com/show_bug.cgi?id=877606#c3 Thanks, Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Why my vm often change into shut off status by itself?
Check if you have any space in the instances dir in the filesystem. I've seen this happen when the drive gets full and libvirt gets an io error trying to write to disk so it shuts off the vms. Vish On Dec 5, 2012, at 6:59 PM, pyw pengyu...@gmail.com wrote: My virtual machine created, often in the absence of intervention into the stopped state: pyw@ven-1:~/devstack$ virsh list --all Id Name State -- - instance-0040shut off - instance-0044shut off - instance-0045shut off - instance-0046shut off - instance-0047shut off - instance-005bshut off - instance-005eshut off - instance-0065shut off - instance-006eshut off - instance-0075shut off - instance-0076shut off - instance-0077shut off - instance-007cshut off - instance-007dshut off - instance-0081shut off - instance-0082shut off - instance-0083shut off - instance-0084shut off - instance-0085shut off query the nova the database, you can see: vm_state: stopped Why is this? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack] config_drive Image UUID doesn't create disk.config
Awesome.Feel free to file a blueprint for it. I also discussed with some people the other day the idea of allowing some additions to the config drive api to allow you to specify an unattend.xml when booting an instance that would put it in the proper place on the config drive. We could create an extension for this or perhaps just accept it in user-data. Would that be enough for you?VishOn Dec 9, 2012, at 5:47 PM, Jian Hua Geng gen...@cn.ibm.com wrote:Hi Vish, I will work on this block_device_mapping enhancement if there are no other guys working on this. -- Best regard, David Geng -- graycol.gifVishvananda Ishaya ---12/06/2012 02:37:23 AM---Vishvananda Ishaya vishvana...@gmail.com Vishvananda Ishaya vishvana...@gmail.com 12/06/2012 02:37 AM ecblank.gif Toecblank.gif Jian Hua Geng/China/IBM@IBMCN, ecblank.gif ccecblank.gif openstack@lists.launchpad.net ecblank.gif Subjectecblank.gif Re: [Openstack] [openstack] config_drive Image UUID doesn't create disk.config ecblank.gifecblank.gif On Dec 4, 2012, at 3:48 AM, Jian Hua Geng gen...@cn.ibm.com wrote: Vish, Many thanks for u comments, but as you know to support windows sysprep image, we need save the unattend.xml in the CDROM or C:\ device. So, we want to extend the config drive to attach a CDROM device when launch VM. Anyway, I think attach a CDROM when launch new VM is a common requirement, right? Sounds like we need some modifications to allow for an attached cd-rom to be specified in block_device_mapping. Vish inline: pic15985.gif___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Hi, maybe this will shed some light on it..? Thanks, Andrew [root@blade02 init.d]# cat /etc/nova/api-paste.ini # Metadata # [composite:metadata] use = egg:Paste#urlmap /: meta [pipeline:meta] pipeline = ec2faultwrap logrequest metaapp [app:metaapp] paste.app_factory = nova.api.metadata.handler:MetadataRequestHandler.factory ### # EC2 # ### [composite:ec2] use = egg:Paste#urlmap /services/Cloud: ec2cloud [composite:ec2cloud] use = call:nova.api.auth:pipeline_factory noauth = ec2faultwrap logrequest ec2noauth cloudrequest validator ec2executor keystone = ec2faultwrap logrequest ec2keystoneauth cloudrequest validator ec2executor [filter:ec2faultwrap] paste.filter_factory = nova.api.ec2:FaultWrapper.factory [filter:logrequest] paste.filter_factory = nova.api.ec2:RequestLogging.factory [filter:ec2lockout] paste.filter_factory = nova.api.ec2:Lockout.factory [filter:ec2keystoneauth] paste.filter_factory = nova.api.ec2:EC2KeystoneAuth.factory [filter:ec2noauth] paste.filter_factory = nova.api.ec2:NoAuth.factory [filter:cloudrequest] controller = nova.api.ec2.cloud.CloudController paste.filter_factory = nova.api.ec2:Requestify.factory [filter:authorizer] paste.filter_factory = nova.api.ec2:Authorizer.factory [filter:validator] paste.filter_factory = nova.api.ec2:Validator.factory [app:ec2executor] paste.app_factory = nova.api.ec2:Executor.factory # # Openstack # # [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 [composite:osapi_volume] use = call:nova.api.openstack.urlmap:urlmap_factory /: osvolumeversions /v1: openstack_volume_api_v1 [composite:openstack_compute_api_v2] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_compute_app_v2 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_compute_app_v2 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_compute_app_v2 [composite:openstack_volume_api_v1] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_volume_app_v1 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_volume_app_v1 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_volume_app_v1 [filter:faultwrap] paste.filter_factory = nova.api.openstack:FaultWrapper.factory [filter:noauth] paste.filter_factory = nova.api.openstack.auth:NoAuthMiddleware.factory [filter:ratelimit] paste.filter_factory = nova.api.openstack.compute.limits:RateLimitingMiddleware.factory [filter:sizelimit] paste.filter_factory = nova.api.sizelimit:RequestBodySizeLimiter.factory [app:osapi_compute_app_v2] paste.app_factory = nova.api.openstack.compute:APIRouter.factory [pipeline:oscomputeversions] pipeline = faultwrap oscomputeversionapp [app:osapi_volume_app_v1] paste.app_factory = nova.api.openstack.volume:APIRouter.factory [app:oscomputeversionapp] paste.app_factory = nova.api.openstack.compute.versions:Versions.factory [pipeline:osvolumeversions] pipeline = faultwrap osvolumeversionapp [app:osvolumeversionapp] paste.app_factory = nova.api.openstack.volume.versions:Versions.factory ## # Shared # ## [filter:keystonecontext] paste.filter_factory = nova.api.auth:NovaKeystoneContext.factory [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory admin_tenant_name = service admin_user = nova admin_password = x7deix7dei auth_uri = http://controller:5000/ On Dec 10, 2012, at 7:10 PM, Vishvananda Ishaya wrote: Odd. This looks remarkably like it is trying to start osapi_volume even though you don't have it specified in enabled apis. Your enabled_apis setting looks correct to me. Vish On Dec 10, 2012, at 9:24 AM, Andrew Holway a.hol...@syseleven.de wrote: Hi, I cannot start the nova-api service. [root@blade02 07-openstack-controller]# nova list ERROR: ConnectionRefused: '[Errno 111] Connection refused' I followed this guide very carefully: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/#07-openstack-controller-controller Here is api.log 2012-12-10 17:51:31 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=2536) load_app /usr/lib/python2.6/site-packages/nova/wsgi.py:371 2012-12-10 17:51:31 CRITICAL nova [-] [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova Traceback (most recent call last): 2012-12-10 17:51:31 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-12-10 17:51:31 TRACE nova server = service.WSGIService(api) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/service.py, line 584, in __init__ 2012-12-10 17:51:31 TRACE nova port=self.port) 2012-12-10 17:51:31 TRACE nova File /usr/lib/python2.6/site-packages/nova/wsgi.py, line 72, in __init__ 2012-12-10
Re: [Openstack] A confuse about the FlatDHCP network
On Dec 5, 2012, at 7:19 PM, Lei Zhang zhang.lei@gmail.com wrote: thank you very much, Vishvananda. But I am still confused about the 192.168.0.0/24 and the 10.0.0.0/8 ip. What means by The addresses will be moved on to the bridge. It means the 192.168.0.0/8 will be disappear? In my opinion, the bridged NIC (eth1) should be worked under promiscuous mode and its IP should be 0.0.0.0. So the eth1 should not own any IP. No moved to the bridge means that the ip will move from eth1 to the bridge eth1 -- no ip address br100 192.168.0.2 10.0.0.2 (for example). Nova moves the eth1 ip automatically when it creates the bridge if eth1 has an ip. Vish But if the 192 address doesn't exist, how the compute-note communicate with each other? Through the eth0? I have no idea. On Thu, Dec 6, 2012 at 3:12 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Dec 5, 2012, at 1:53 AM, Lei Zhang zhang.lei@gmail.com wrote: Hi all, I am reading the http://docs.openstack.org/trunk/openstack-compute/admin/content/libvirt-flat-dhcp-networking.html, I got the following deploy architecture. But there are several that I am confused. How and why 192.168.0.0/24 ip range exist? It is necessary or not? The eth1 on the each physical machine own two ip(10.0.0.0/24 and 192.168.0.0/24)? Is that possible? In the nova-compute, the eth1 should be bridged by br100. the eth1 should not own any IP address, right? The addresses will be moved on to the bridge. The point of having an ip address is so that things like rabbit and mysql can communicate over a different set of addresses than the guest network. Usually this would be done on a separate eth device (eth2) or vlan, but I was trying to keep In a better way, should we separate the nova-network/eth0 to the internet public switch for access the internet by all VMs. and the nova-compute/eth0 should be bind to a internal switch for admin access use. Is it right? Ideally there are three eth devices / vlans a) public (for 99 adddresses in diagram) b) management (for 192 addresses in diagram) c) guest (for 10 addresses in diagram) -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack Folsom and New kind of setup
It gets the endpoint configuration from keystone. Everything has to know where the keystone server is and it can use the service catalog to talk to the other services. Vish On Dec 6, 2012, at 3:20 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi Stackers- I have got a doubt about a new kind of setup with Folsom. Need your help on the doubts i have. Lets plan that we install nova, quantum, glance, keystone, mysql-database and Horizon components of controller in individual machines. How Horizon will be able to get the set the configurations/data? Can any one help me understand this... thanks in advance -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Nope. Best i can think of is to throw some log statements into nova/service.py right before the exception gets thrown. See which api it is trying to start and what it thinks the value of enabled_apis is. Etc. Vish On Dec 10, 2012, at 10:24 AM, Andrew Holway a.hol...@syseleven.de wrote: Hi, maybe this will shed some light on it..? Thanks, Andrew [root@blade02 init.d]# cat /etc/nova/api-paste.ini # Metadata # [composite:metadata] use = egg:Paste#urlmap /: meta [pipeline:meta] pipeline = ec2faultwrap logrequest metaapp [app:metaapp] paste.app_factory = nova.api.metadata.handler:MetadataRequestHandler.factory ### # EC2 # ### [composite:ec2] use = egg:Paste#urlmap /services/Cloud: ec2cloud [composite:ec2cloud] use = call:nova.api.auth:pipeline_factory noauth = ec2faultwrap logrequest ec2noauth cloudrequest validator ec2executor keystone = ec2faultwrap logrequest ec2keystoneauth cloudrequest validator ec2executor [filter:ec2faultwrap] paste.filter_factory = nova.api.ec2:FaultWrapper.factory [filter:logrequest] paste.filter_factory = nova.api.ec2:RequestLogging.factory [filter:ec2lockout] paste.filter_factory = nova.api.ec2:Lockout.factory [filter:ec2keystoneauth] paste.filter_factory = nova.api.ec2:EC2KeystoneAuth.factory [filter:ec2noauth] paste.filter_factory = nova.api.ec2:NoAuth.factory [filter:cloudrequest] controller = nova.api.ec2.cloud.CloudController paste.filter_factory = nova.api.ec2:Requestify.factory [filter:authorizer] paste.filter_factory = nova.api.ec2:Authorizer.factory [filter:validator] paste.filter_factory = nova.api.ec2:Validator.factory [app:ec2executor] paste.app_factory = nova.api.ec2:Executor.factory # # Openstack # # [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 [composite:osapi_volume] use = call:nova.api.openstack.urlmap:urlmap_factory /: osvolumeversions /v1: openstack_volume_api_v1 [composite:openstack_compute_api_v2] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_compute_app_v2 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_compute_app_v2 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_compute_app_v2 [composite:openstack_volume_api_v1] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_volume_app_v1 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_volume_app_v1 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_volume_app_v1 [filter:faultwrap] paste.filter_factory = nova.api.openstack:FaultWrapper.factory [filter:noauth] paste.filter_factory = nova.api.openstack.auth:NoAuthMiddleware.factory [filter:ratelimit] paste.filter_factory = nova.api.openstack.compute.limits:RateLimitingMiddleware.factory [filter:sizelimit] paste.filter_factory = nova.api.sizelimit:RequestBodySizeLimiter.factory [app:osapi_compute_app_v2] paste.app_factory = nova.api.openstack.compute:APIRouter.factory [pipeline:oscomputeversions] pipeline = faultwrap oscomputeversionapp [app:osapi_volume_app_v1] paste.app_factory = nova.api.openstack.volume:APIRouter.factory [app:oscomputeversionapp] paste.app_factory = nova.api.openstack.compute.versions:Versions.factory [pipeline:osvolumeversions] pipeline = faultwrap osvolumeversionapp [app:osvolumeversionapp] paste.app_factory = nova.api.openstack.volume.versions:Versions.factory ## # Shared # ## [filter:keystonecontext] paste.filter_factory = nova.api.auth:NovaKeystoneContext.factory [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory admin_tenant_name = service admin_user = nova admin_password = x7deix7dei auth_uri = http://controller:5000/ On Dec 10, 2012, at 7:10 PM, Vishvananda Ishaya wrote: Odd. This looks remarkably like it is trying to start osapi_volume even though you don't have it specified in enabled apis. Your enabled_apis setting looks correct to me. Vish On Dec 10, 2012, at 9:24 AM, Andrew Holway a.hol...@syseleven.de wrote: Hi, I cannot start the nova-api service. [root@blade02 07-openstack-controller]# nova list ERROR: ConnectionRefused: '[Errno 111] Connection refused' I followed this guide very carefully: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/#07-openstack-controller-controller Here is api.log 2012-12-10 17:51:31 DEBUG nova.wsgi [-] Loading app metadata from /etc/nova/api-paste.ini from (pid=2536) load_app /usr/lib/python2.6/site-packages/nova/wsgi.py:371 2012-12-10 17:51:31 CRITICAL nova [-] [Errno 98] Address already in use 2012-12-10 17:51:31 TRACE nova Traceback (most recent call last):
[Openstack] Server resize API in OpenStack ESSEX
Hallo All, I am trying to use the Nova API (POST call) for changing the flavor information (to resize) from m1.tiny to m1.medium. Even though the API is successful (202 Status code), on the Horizon GUI I could see that the Status is Error and the task state is Resize Prep. I am passing the Auth Token along with the Body information in the form of json as inputs to the API. I have referred this URIhttp://docs.openstack.org/api/openstack-compute/programmer/content/resizing-servers.html for passing the body information. I am using OpenStack ESSEX and can I get to know is there any configurations that I need to do in order to get this working? Thanks Krishnaprasad ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Hi,
I have actually no idea how do do that. But the service opts look vaguely
relevant:
Does anyone have a working installation on Centos 6.3?
Thanks,
Andrew
service_opts = [
cfg.IntOpt('report_interval',
default=10,
help='seconds between nodes reporting state to datastore'),
cfg.IntOpt('periodic_interval',
default=60,
help='seconds between running periodic tasks'),
cfg.IntOpt('periodic_fuzzy_delay',
default=60,
help='range of seconds to randomly delay when starting the'
' periodic task scheduler to reduce stampeding.'
' (Disable by setting to 0)'),
cfg.StrOpt('ec2_listen',
default=0.0.0.0,
help='IP address for EC2 API to listen'),
cfg.IntOpt('ec2_listen_port',
default=8773,
help='port for ec2 api to listen'),
cfg.IntOpt('ec2_workers',
default=None,
help='Number of workers for EC2 API service'),
cfg.StrOpt('osapi_compute_listen',
default=0.0.0.0,
help='IP address for OpenStack API to listen'),
cfg.IntOpt('osapi_compute_listen_port',
default=8774,
help='list port for osapi compute'),
cfg.IntOpt('osapi_compute_workers',
default=None,
help='Number of workers for OpenStack API service'),
cfg.StrOpt('metadata_manager',
default='nova.api.manager.MetadataManager',
help='OpenStack metadata service manager'),
cfg.StrOpt('metadata_listen',
default=0.0.0.0,
help='IP address for metadata api to listen'),
cfg.IntOpt('metadata_listen_port',
default=8775,
help='port for metadata api to listen'),
cfg.IntOpt('metadata_workers',
default=None,
help='Number of workers for metadata service'),
cfg.StrOpt('osapi_volume_listen',
default=0.0.0.0,
help='IP address for OpenStack Volume API to listen'),
cfg.IntOpt('osapi_volume_listen_port',
default=8776,
help='port for os volume api to listen'),
cfg.IntOpt('osapi_volume_workers',
default=None,
help='Number of workers for OpenStack Volume API service'),
]
On Dec 10, 2012, at 7:29 PM, Vishvananda Ishaya wrote:
Nope. Best i can think of is to throw some log statements into
nova/service.py right before the exception gets thrown. See which api it is
trying to start and what it thinks the value of enabled_apis is. Etc.
Vish
On Dec 10, 2012, at 10:24 AM, Andrew Holway a.hol...@syseleven.de wrote:
Hi,
maybe this will shed some light on it..?
Thanks,
Andrew
[root@blade02 init.d]# cat /etc/nova/api-paste.ini
# Metadata #
[composite:metadata]
use = egg:Paste#urlmap
/: meta
[pipeline:meta]
pipeline = ec2faultwrap logrequest metaapp
[app:metaapp]
paste.app_factory = nova.api.metadata.handler:MetadataRequestHandler.factory
###
# EC2 #
###
[composite:ec2]
use = egg:Paste#urlmap
/services/Cloud: ec2cloud
[composite:ec2cloud]
use = call:nova.api.auth:pipeline_factory
noauth = ec2faultwrap logrequest ec2noauth cloudrequest validator ec2executor
keystone = ec2faultwrap logrequest ec2keystoneauth cloudrequest validator
ec2executor
[filter:ec2faultwrap]
paste.filter_factory = nova.api.ec2:FaultWrapper.factory
[filter:logrequest]
paste.filter_factory = nova.api.ec2:RequestLogging.factory
[filter:ec2lockout]
paste.filter_factory = nova.api.ec2:Lockout.factory
[filter:ec2keystoneauth]
paste.filter_factory = nova.api.ec2:EC2KeystoneAuth.factory
[filter:ec2noauth]
paste.filter_factory = nova.api.ec2:NoAuth.factory
[filter:cloudrequest]
controller = nova.api.ec2.cloud.CloudController
paste.filter_factory = nova.api.ec2:Requestify.factory
[filter:authorizer]
paste.filter_factory = nova.api.ec2:Authorizer.factory
[filter:validator]
paste.filter_factory = nova.api.ec2:Validator.factory
[app:ec2executor]
paste.app_factory = nova.api.ec2:Executor.factory
#
# Openstack #
#
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1: openstack_compute_api_v2
/v2: openstack_compute_api_v2
[composite:osapi_volume]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: osvolumeversions
/v1: openstack_volume_api_v1
[composite:openstack_compute_api_v2]
use = call:nova.api.auth:pipeline_factory
noauth = faultwrap sizelimit noauth ratelimit osapi_compute_app_v2
keystone = faultwrap sizelimit authtoken keystonecontext ratelimit
osapi_compute_app_v2
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext
osapi_compute_app_v2
[composite:openstack_volume_api_v1]
use = call:nova.api.auth:pipeline_factory
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
I just realized the problem. Your issue is actually the metadata api since you
have something listening on 8775. If you are running nova-api-metadata
separately then you can remove it from your list of enabled apis:
enabled_apis=ec2,osapi_compute
Alternatively just kill nova-api-metadata and allow it to run as wone of the
nova-api components.
Just for your reference, nova-api is an easy way to run all of the apis as one
service. In this case it uses the enabled_apis config option. You can also run
all of the apis separately by using the individual binaries:
nova-api-ec2
nova-api-metadata
nova-api-os-compute
nova-api-os-volume
Vish
On Dec 10, 2012, at 10:42 AM, Andrew Holway a.hol...@syseleven.de wrote:
Hi,
I have actually no idea how do do that. But the service opts look vaguely
relevant:
Does anyone have a working installation on Centos 6.3?
Thanks,
Andrew
service_opts = [
cfg.IntOpt('report_interval',
default=10,
help='seconds between nodes reporting state to datastore'),
cfg.IntOpt('periodic_interval',
default=60,
help='seconds between running periodic tasks'),
cfg.IntOpt('periodic_fuzzy_delay',
default=60,
help='range of seconds to randomly delay when starting the'
' periodic task scheduler to reduce stampeding.'
' (Disable by setting to 0)'),
cfg.StrOpt('ec2_listen',
default=0.0.0.0,
help='IP address for EC2 API to listen'),
cfg.IntOpt('ec2_listen_port',
default=8773,
help='port for ec2 api to listen'),
cfg.IntOpt('ec2_workers',
default=None,
help='Number of workers for EC2 API service'),
cfg.StrOpt('osapi_compute_listen',
default=0.0.0.0,
help='IP address for OpenStack API to listen'),
cfg.IntOpt('osapi_compute_listen_port',
default=8774,
help='list port for osapi compute'),
cfg.IntOpt('osapi_compute_workers',
default=None,
help='Number of workers for OpenStack API service'),
cfg.StrOpt('metadata_manager',
default='nova.api.manager.MetadataManager',
help='OpenStack metadata service manager'),
cfg.StrOpt('metadata_listen',
default=0.0.0.0,
help='IP address for metadata api to listen'),
cfg.IntOpt('metadata_listen_port',
default=8775,
help='port for metadata api to listen'),
cfg.IntOpt('metadata_workers',
default=None,
help='Number of workers for metadata service'),
cfg.StrOpt('osapi_volume_listen',
default=0.0.0.0,
help='IP address for OpenStack Volume API to listen'),
cfg.IntOpt('osapi_volume_listen_port',
default=8776,
help='port for os volume api to listen'),
cfg.IntOpt('osapi_volume_workers',
default=None,
help='Number of workers for OpenStack Volume API service'),
]
On Dec 10, 2012, at 7:29 PM, Vishvananda Ishaya wrote:
Nope. Best i can think of is to throw some log statements into
nova/service.py right before the exception gets thrown. See which api it is
trying to start and what it thinks the value of enabled_apis is. Etc.
Vish
On Dec 10, 2012, at 10:24 AM, Andrew Holway a.hol...@syseleven.de wrote:
Hi,
maybe this will shed some light on it..?
Thanks,
Andrew
[root@blade02 init.d]# cat /etc/nova/api-paste.ini
# Metadata #
[composite:metadata]
use = egg:Paste#urlmap
/: meta
[pipeline:meta]
pipeline = ec2faultwrap logrequest metaapp
[app:metaapp]
paste.app_factory = nova.api.metadata.handler:MetadataRequestHandler.factory
###
# EC2 #
###
[composite:ec2]
use = egg:Paste#urlmap
/services/Cloud: ec2cloud
[composite:ec2cloud]
use = call:nova.api.auth:pipeline_factory
noauth = ec2faultwrap logrequest ec2noauth cloudrequest validator
ec2executor
keystone = ec2faultwrap logrequest ec2keystoneauth cloudrequest validator
ec2executor
[filter:ec2faultwrap]
paste.filter_factory = nova.api.ec2:FaultWrapper.factory
[filter:logrequest]
paste.filter_factory = nova.api.ec2:RequestLogging.factory
[filter:ec2lockout]
paste.filter_factory = nova.api.ec2:Lockout.factory
[filter:ec2keystoneauth]
paste.filter_factory = nova.api.ec2:EC2KeystoneAuth.factory
[filter:ec2noauth]
paste.filter_factory = nova.api.ec2:NoAuth.factory
[filter:cloudrequest]
controller = nova.api.ec2.cloud.CloudController
paste.filter_factory = nova.api.ec2:Requestify.factory
[filter:authorizer]
paste.filter_factory = nova.api.ec2:Authorizer.factory
[filter:validator]
paste.filter_factory = nova.api.ec2:Validator.factory
[app:ec2executor]
paste.app_factory = nova.api.ec2:Executor.factory
#
Re: [Openstack] Server resize API in OpenStack ESSEX
2 requirements: 1) hostname for compute hosts resolve properly 2) passwordless ssh works between compute hosts. Vish On Dec 10, 2012, at 10:37 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de wrote: Hallo All, I am trying to use the Nova API (POST call) for changing the flavor information (to resize) from m1.tiny to m1.medium. Even though the API is successful (202 Status code), on the Horizon GUI I could see that the Status is Error and the task state is Resize Prep. I am passing the Auth Token along with the Body information in the form of json as inputs to the API. I have referred this URI for passing the body information. I am using OpenStack ESSEX and can I get to know is there any configurations that I need to do in order to get this working? Thanks Krishnaprasad ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Server resize API in OpenStack ESSEX
Hi Vish, Thanks for the quick reply. I have passwordless ssh between the compute hosts but could you explain me the first option. When I resize, will the instance redeploy on a different compute node? Do I need to specify this flag allow_resize_to_same_host=true in nova.conf of the compute node? Regards, Krishnaprasad From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: Montag, 10. Dezember 2012 20:03 To: Narayanan, Krishnaprasad Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Server resize API in OpenStack ESSEX 2 requirements: 1) hostname for compute hosts resolve properly 2) passwordless ssh works between compute hosts. Vish On Dec 10, 2012, at 10:37 AM, Narayanan, Krishnaprasad naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote: Hallo All, I am trying to use the Nova API (POST call) for changing the flavor information (to resize) from m1.tiny to m1.medium. Even though the API is successful (202 Status code), on the Horizon GUI I could see that the Status is Error and the task state is Resize Prep. I am passing the Auth Token along with the Body information in the form of json as inputs to the API. I have referred this URIhttp://docs.openstack.org/api/openstack-compute/programmer/content/resizing-servers.html for passing the body information. I am using OpenStack ESSEX and can I get to know is there any configurations that I need to do in order to get this working? Thanks Krishnaprasad ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] CRITICAL nova [-] [Errno 98] Address already in use
Hey,
Thanks, That seems to have done it!
Now I have some whole new errors to work on :)
2012-12-10 20:08:44 ERROR keystone.middleware.auth_token [-] HTTP connection
exception: [Errno 1] _ssl.c:490: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol
2012-12-10 20:08:44 WARNING keystone.middleware.auth_token [-] Authorization
failed for token fbb8f2fe3fcb4155b9428b862b5bb943
2012-12-10 20:08:44 INFO keystone.middleware.auth_token [-] Invalid user token
- rejecting request
2012-12-10 20:08:44 INFO nova.osapi_compute.wsgi.server [-] 127.0.0.1 - -
[10/Dec/2012 20:08:44] GET /v2/3efa0ffe282c4a0c8b0b3a2812b1b4d0/servers/detail
HTTP/1.1 401 462 0.012388
2012-12-10 20:08:44 ERROR keystone.middleware.auth_token [-] HTTP connection
exception: [Errno 1] _ssl.c:490: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol
2012-12-10 20:08:44 WARNING keystone.middleware.auth_token [-] Authorization
failed for token e6f30024fc1142638452854f03a7735c
2012-12-10 20:08:44 INFO keystone.middleware.auth_token [-] Invalid user token
- rejecting request
2012-12-10 20:08:44 INFO nova.osapi_compute.wsgi.server [-] 127.0.0.1 - -
[10/Dec/2012 20:08:44] GET /v2/3efa0ffe282c4a0c8b0b3a2812b1b4d0/servers/detail
HTTP/1.1 401 462 0.002427
Take care,
Andrew
On Dec 10, 2012, at 8:01 PM, Vishvananda Ishaya wrote:
I just realized the problem. Your issue is actually the metadata api since
you have something listening on 8775. If you are running nova-api-metadata
separately then you can remove it from your list of enabled apis:
enabled_apis=ec2,osapi_compute
Alternatively just kill nova-api-metadata and allow it to run as wone of the
nova-api components.
Just for your reference, nova-api is an easy way to run all of the apis as
one service. In this case it uses the enabled_apis config option. You can
also run all of the apis separately by using the individual binaries:
nova-api-ec2
nova-api-metadata
nova-api-os-compute
nova-api-os-volume
Vish
On Dec 10, 2012, at 10:42 AM, Andrew Holway a.hol...@syseleven.de wrote:
Hi,
I have actually no idea how do do that. But the service opts look vaguely
relevant:
Does anyone have a working installation on Centos 6.3?
Thanks,
Andrew
service_opts = [
cfg.IntOpt('report_interval',
default=10,
help='seconds between nodes reporting state to datastore'),
cfg.IntOpt('periodic_interval',
default=60,
help='seconds between running periodic tasks'),
cfg.IntOpt('periodic_fuzzy_delay',
default=60,
help='range of seconds to randomly delay when starting the'
' periodic task scheduler to reduce stampeding.'
' (Disable by setting to 0)'),
cfg.StrOpt('ec2_listen',
default=0.0.0.0,
help='IP address for EC2 API to listen'),
cfg.IntOpt('ec2_listen_port',
default=8773,
help='port for ec2 api to listen'),
cfg.IntOpt('ec2_workers',
default=None,
help='Number of workers for EC2 API service'),
cfg.StrOpt('osapi_compute_listen',
default=0.0.0.0,
help='IP address for OpenStack API to listen'),
cfg.IntOpt('osapi_compute_listen_port',
default=8774,
help='list port for osapi compute'),
cfg.IntOpt('osapi_compute_workers',
default=None,
help='Number of workers for OpenStack API service'),
cfg.StrOpt('metadata_manager',
default='nova.api.manager.MetadataManager',
help='OpenStack metadata service manager'),
cfg.StrOpt('metadata_listen',
default=0.0.0.0,
help='IP address for metadata api to listen'),
cfg.IntOpt('metadata_listen_port',
default=8775,
help='port for metadata api to listen'),
cfg.IntOpt('metadata_workers',
default=None,
help='Number of workers for metadata service'),
cfg.StrOpt('osapi_volume_listen',
default=0.0.0.0,
help='IP address for OpenStack Volume API to listen'),
cfg.IntOpt('osapi_volume_listen_port',
default=8776,
help='port for os volume api to listen'),
cfg.IntOpt('osapi_volume_workers',
default=None,
help='Number of workers for OpenStack Volume API service'),
]
On Dec 10, 2012, at 7:29 PM, Vishvananda Ishaya wrote:
Nope. Best i can think of is to throw some log statements into
nova/service.py right before the exception gets thrown. See which api it is
trying to start and what it thinks the value of enabled_apis is. Etc.
Vish
On Dec 10, 2012, at 10:24 AM, Andrew Holway a.hol...@syseleven.de wrote:
Hi,
maybe this will shed some light on it..?
Thanks,
Andrew
[root@blade02 init.d]# cat /etc/nova/api-paste.ini
# Metadata #
Re: [Openstack] Volume types
If you mean different types like block or file-oriented volume, there was a thread about that (http://markmail.org/message/ptwohhhaltcbqii2) Briefly, you had to code a volume driver matches your needs ( http://docs.openstack.org/developer/nova/api/nova.volume.driver.htmlI) Regards, JuanFra. 2012/12/10 John Griffith john.griff...@solidfire.com On Mon, Dec 10, 2012 at 10:05 AM, Daniel Oliveira dvalbr...@gmail.comwrote: Hello. I've been playing around with OpenStack, when I noticed a section in the Dashboard where you can create/delete volume types. The problem is, I didn't understand their purpose, as when you create a new type, you only specify its name. Can anyone tell me what are volume types used for? Thanks in advance -- My best regards, Daniel Oliveira. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Hi Daniel, The primary idea behind volume-types is a method to deal with multiple back-ends. The volume-type corresponds to a specific back-end, or perhaps enables different characteristics of a back-end. Hopefully that helps a bit. John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] nova list requests failing
Hi, Please excuse dumb questions. Im very new to openstack. So I have just managed to get the nova-api service running (thanks virsh) but it seems to be having a little problem with auth. [root@blade02 07-openstack-controller]# nova list ERROR: n/a (HTTP 401) [root@blade02 07-openstack-controller]# nova--os_username=nova --os_password=passw0rd--os_tenant_name=service --os_auth_url=http://controller:5000/v2.0 list ERROR: n/a (HTTP 401) Can anyone see what is going on here? Thanks, Andrew /var/log/nova/api.log 2012-12-10 20:24:49 ERROR keystone.middleware.auth_token [-] HTTP connection exception: [Errno 1] _ssl.c:490: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol 2012-12-10 20:24:49 WARNING keystone.middleware.auth_token [-] Authorization failed for token 61d0f67e79cd4f8fbe19412e4347e22c 2012-12-10 20:24:49 INFO keystone.middleware.auth_token [-] Invalid user token - rejecting request 2012-12-10 20:24:49 INFO nova.osapi_compute.wsgi.server [-] 127.0.0.1 - - [10/Dec/2012 20:24:49] GET /v2/3338bc86707e4cdb910a3c7a6fd1a649/servers/detail HTTP/1.1 401 462 0.002252 [root@blade02 07-openstack-controller]# cat /etc/nova/api-paste.ini # Metadata # [composite:metadata] use = egg:Paste#urlmap /: meta [pipeline:meta] pipeline = ec2faultwrap logrequest metaapp [app:metaapp] paste.app_factory = nova.api.metadata.handler:MetadataRequestHandler.factory ### # EC2 # ### [composite:ec2] use = egg:Paste#urlmap /services/Cloud: ec2cloud [composite:ec2cloud] use = call:nova.api.auth:pipeline_factory noauth = ec2faultwrap logrequest ec2noauth cloudrequest validator ec2executor keystone = ec2faultwrap logrequest ec2keystoneauth cloudrequest validator ec2executor [filter:ec2faultwrap] paste.filter_factory = nova.api.ec2:FaultWrapper.factory [filter:logrequest] paste.filter_factory = nova.api.ec2:RequestLogging.factory [filter:ec2lockout] paste.filter_factory = nova.api.ec2:Lockout.factory [filter:ec2keystoneauth] paste.filter_factory = nova.api.ec2:EC2KeystoneAuth.factory [filter:ec2noauth] paste.filter_factory = nova.api.ec2:NoAuth.factory [filter:cloudrequest] controller = nova.api.ec2.cloud.CloudController paste.filter_factory = nova.api.ec2:Requestify.factory [filter:authorizer] paste.filter_factory = nova.api.ec2:Authorizer.factory [filter:validator] paste.filter_factory = nova.api.ec2:Validator.factory [app:ec2executor] paste.app_factory = nova.api.ec2:Executor.factory # # Openstack # # [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 [composite:osapi_volume] use = call:nova.api.openstack.urlmap:urlmap_factory /: osvolumeversions /v1: openstack_volume_api_v1 [composite:openstack_compute_api_v2] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_compute_app_v2 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_compute_app_v2 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_compute_app_v2 [composite:openstack_volume_api_v1] use = call:nova.api.auth:pipeline_factory noauth = faultwrap sizelimit noauth ratelimit osapi_volume_app_v1 keystone = faultwrap sizelimit authtoken keystonecontext ratelimit osapi_volume_app_v1 keystone_nolimit = faultwrap sizelimit authtoken keystonecontext osapi_volume_app_v1 [filter:faultwrap] paste.filter_factory = nova.api.openstack:FaultWrapper.factory [filter:noauth] paste.filter_factory = nova.api.openstack.auth:NoAuthMiddleware.factory [filter:ratelimit] paste.filter_factory = nova.api.openstack.compute.limits:RateLimitingMiddleware.factory [filter:sizelimit] paste.filter_factory = nova.api.sizelimit:RequestBodySizeLimiter.factory [app:osapi_compute_app_v2] paste.app_factory = nova.api.openstack.compute:APIRouter.factory [pipeline:oscomputeversions] pipeline = faultwrap oscomputeversionapp [app:osapi_volume_app_v1] paste.app_factory = nova.api.openstack.volume:APIRouter.factory [app:oscomputeversionapp] paste.app_factory = nova.api.openstack.compute.versions:Versions.factory [pipeline:osvolumeversions] pipeline = faultwrap osvolumeversionapp [app:osvolumeversionapp] paste.app_factory = nova.api.openstack.volume.versions:Versions.factory ## # Shared # ## [filter:keystonecontext] paste.filter_factory = nova.api.auth:NovaKeystoneContext.factory [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory admin_tenant_name = service admin_user = nova admin_password = passw0rd auth_uri = http://controller:5000/ /etc/nova/nova.conf [DEFAULT] logdir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp volumes_dir = /etc/nova/volumes dhcpbridge = /usr/bin/nova-dhcpbridge dhcpbridge_flagfile = /etc/nova/nova.conf force_dhcp_release = False injected_network_template =
[Openstack] HA for glance api service
Hi, Any plan to support HA (High Availability) in glance api service? I noticed in Folsom it comes with a tool to facilitate the replication of glance api service (see the following link), http://docs.openstack.org/trunk/openstack-compute/admin/content/replicating-images.html But to automatically fail over or loan balance among these multiple servers, we have to use pacemaker or other third party load balance tools. Any plan to support HA clustering natively similar to Quantum multi-host in future OpenStack releases? Thanks. Dennis Qin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova list requests failing
It was this little fella in my nova.conf :) On Dec 10, 2012, at 8:35 PM, Andrew Holway wrote: #[keystone_authtoken] ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dnsmasq does not start + no xapi interface -- how to solve this problem
I don't see any errors in your network log. are nova-network and nova-compute running on the same host with the same config file? It looks like it isn't recieving a message. Are you running another nova-network that is picking up the message on another host? Vish On Dec 10, 2012, at 12:18 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: Hi all, I am facing an boring issue since Friday: nova-network is unable to start dnsmasq. Therefore the xapi0 interface is not created. Then, it is impossible to launch VMs. nova-network does not answer requests and nova-compute returns an RPC timeout. Please help me to solve this problem I am using openstack folsom release + XCP + ubuntu 12.04 log file of nova-compute and nova-network are attached to this e-mail. Thank you, Afef nova-compute.txtnova-network.log___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] 500 - Internal Server Error when using Volumes in Dashboard (Centos 6.3)
Hello, I have a Dashboard install. /dashboard/syspanel/volumes/ /dashboard/nova/volumes/ causes a 500 error. The 500 goes away when I run $nova-api-os-volume I also have a $/etc/init.d/openstack-nova-volume start Which doesn't make the 500 error go away. Can someone tell me what nova-api-os-volume is, what nova-volume is and how to get them both properly doing their thing on my Centos 6.3 install. The guide I am following has no mention of it: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/ Thanks, Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dnsmasq does not start + no xapi interface -- how to solve this problem
Check rabbitmqctl list_queues and see if there are queues that have nonzero entries. That means messages are being sent but not picked up by the nodes. If the nova-networks are hanging they are probably stuck waiting on a lock files. I believe the lock files are in /var/lock/nova by default. You could try deleting them and restarting nova-network. Vish On Dec 10, 2012, at 1:32 PM, Afef Mdhaffar mdhaf...@mathematik.uni-marburg.de wrote: 2012/12/10 Vishvananda Ishaya vishvana...@gmail.com I don't see any errors in your network log. are nova-network and nova-compute running on the same host with the same config file? Yes, nova-network and nova-compute are running on the same node -- this is the compute node It looks like it isn't recieving a message. Are you running another nova-network that is picking up the message on another host? I have another nova-network running on the cloud controller. The platform was composed of 9 nodes (1 cloud controller + 8 compute nodes) and was running till friday (when one of my colleagues has installed some updates on our gateway). each node (including the controller) runs nova-network and nova-compute. Then (after updating the gateway), only the cloud controller and one compute node are still correctly running. and the rest of the nodes returns the same error - related in my opinion to nova-network. Any ideas how to fix that? Thank you, Afef Vish On Dec 10, 2012, at 12:18 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: Hi all, I am facing an boring issue since Friday: nova-network is unable to start dnsmasq. Therefore the xapi0 interface is not created. Then, it is impossible to launch VMs. nova-network does not answer requests and nova-compute returns an RPC timeout. Please help me to solve this problem I am using openstack folsom release + XCP + ubuntu 12.04 log file of nova-compute and nova-network are attached to this e-mail. Thank you, Afef nova-compute.txtnova-network.log___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 500 - Internal Server Error when using Volumes in Dashboard (Centos 6.3)
The recommended way is to run cinder. The config that you showed before was not running osapi_volume as one of your enabled apis. Prior to folsom the way was to enable osapi_volume or run nova-api-volume. The worker that processes commands is called nova-volume (similar to nova-compute on the compute side). In cinder these are cinder-api and cinder-volume. FYI, you don't need volumes working to use nova. It is for attachable block storage devices (similar to ebs). I hope that helps. Vish On Dec 10, 2012, at 1:37 PM, Andrew Holway a.hol...@syseleven.de wrote: Hello, I have a Dashboard install. /dashboard/syspanel/volumes/ /dashboard/nova/volumes/ causes a 500 error. The 500 goes away when I run $nova-api-os-volume I also have a $/etc/init.d/openstack-nova-volume start Which doesn't make the 500 error go away. Can someone tell me what nova-api-os-volume is, what nova-volume is and how to get them both properly doing their thing on my Centos 6.3 install. The guide I am following has no mention of it: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/ Thanks, Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Server resize API in OpenStack ESSEX
As you had mentioned I went through the logs and I could see an error message with the Host Key Verification Failed with exit code 255 on Command: ssh IP address mkdir -p /var/lib/nova/instances/instance-00155. If I get it correctly, this means that the key on the compute nodes that was cached earlier has been changed. Can I get to know is this correct and how to get rid of this problem? From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: Montag, 10. Dezember 2012 20:23 To: Narayanan, Krishnaprasad Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Server resize API in OpenStack ESSEX The code scps the backing file for the instance to the new node via something along the lines of: scp /var/lib/nova/instances/instance-xxx/disk hostname:/var/lib/nova/instances/instance-xxx/disk So the hostname has to properly resolve to the ip of the target machine. You should see messages in the compute log about it trying to do this. The error message there might give you a better idea of what failed. Yes resize will go through the scheduler and usually find a new compute node. The conf option does not force it to use the same host, so it is mostly just there for testing. Vish On Dec 10, 2012, at 11:12 AM, Narayanan, Krishnaprasad naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote: Hi Vish, Thanks for the quick reply. I have passwordless ssh between the compute hosts but could you explain me the first option. When I resize, will the instance redeploy on a different compute node? Do I need to specify this flag allow_resize_to_same_host=true in nova.conf of the compute node? Regards, Krishnaprasad From: Vishvananda Ishaya [mailto:vishvana...@gmail.comhttp://gmail.com] Sent: Montag, 10. Dezember 2012 20:03 To: Narayanan, Krishnaprasad Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Server resize API in OpenStack ESSEX 2 requirements: 1) hostname for compute hosts resolve properly 2) passwordless ssh works between compute hosts. Vish On Dec 10, 2012, at 10:37 AM, Narayanan, Krishnaprasad naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote: Hallo All, I am trying to use the Nova API (POST call) for changing the flavor information (to resize) from m1.tiny to m1.medium. Even though the API is successful (202 Status code), on the Horizon GUI I could see that the Status is Error and the task state is Resize Prep. I am passing the Auth Token along with the Body information in the form of json as inputs to the API. I have referred this URIhttp://docs.openstack.org/api/openstack-compute/programmer/content/resizing-servers.html for passing the body information. I am using OpenStack ESSEX and can I get to know is there any configurations that I need to do in order to get this working? Thanks Krishnaprasad ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 500 - Internal Server Error when using Volumes in Dashboard (Centos 6.3)
Thanks for the advice. Actually Im not planning on using block volumes at all but its nice to know how everything plugs together. Could you tell me what would be the best way to attach NFS filers as shared storage? I am planning on running glusterfs on the hypervisors and then sharing that back to the hypervisors (If that makes sense). Do you have some tips for such a setup? Thanks, Andrew On Dec 10, 2012, at 10:46 PM, Vishvananda Ishaya wrote: The recommended way is to run cinder. The config that you showed before was not running osapi_volume as one of your enabled apis. Prior to folsom the way was to enable osapi_volume or run nova-api-volume. The worker that processes commands is called nova-volume (similar to nova-compute on the compute side). In cinder these are cinder-api and cinder-volume. FYI, you don't need volumes working to use nova. It is for attachable block storage devices (similar to ebs). I hope that helps. Vish On Dec 10, 2012, at 1:37 PM, Andrew Holway a.hol...@syseleven.de wrote: Hello, I have a Dashboard install. /dashboard/syspanel/volumes/ /dashboard/nova/volumes/ causes a 500 error. The 500 goes away when I run $nova-api-os-volume I also have a $/etc/init.d/openstack-nova-volume start Which doesn't make the 500 error go away. Can someone tell me what nova-api-os-volume is, what nova-volume is and how to get them both properly doing their thing on my Centos 6.3 install. The guide I am following has no mention of it: https://github.com/beloglazov/openstack-centos-kvm-glusterfs/ Thanks, Andrew ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dnsmasq does not start + no xapi interface -- how to solve this problem
2012/12/10 Vishvananda Ishaya vishvana...@gmail.com Check rabbitmqctl list_queues and see if there are queues that have nonzero entries. That means messages are being sent but not picked up by the nodes. Here is the output of the command -- there some non zero values for glance info. Is there any way to clear this queue? rabbitmqctl list_queues Listing queues ... cinder-volume 0 network.computeDomU07 0 compute.computeDomU07 0 network.computeDomU05 0 compute 0 scheduler.computeDomU05 0 consoleauth.computeDomU08 0 network.controller 0 cinder-scheduler 0 compute_fanout_470aa521abf344f398dc98bf2f99b6e1 0 scheduler.computeDomU07 0 compute.controller 0 network_fanout_209e3038f3af49849c10263ab1012e37 0 cert.computeDomU07 0 scheduler.computeDomU08 0 consoleauth.computeDomU05 0 glance_notifications.warn 0 consoleauth_fanout_9f3c92a646e74f9c88cb1317379d0a6a 0 scheduler.controller 0 network_fanout_9cf790a90c2f49c781a8046d0ea91d30 0 cinder-volume_fanout_693d1211a2a4478b828acb91099a228b 0 cert_fanout_d669d273749c432d999cdfd0a7a715a9 0 network_fanout_e4cc6507e07747d093ecc59502d62018 0 consoleauth.computeDomU07 0 cert_fanout_a9734647226c4ebda2e112ece8f6f168 0 compute.computeDomU08 0 cert.computeDomU05 0 scheduler_fanout_6c29f818954243468653858252666f2a 0 cert.controller 0 cert 0 compute.computeDomU05 0 network_fanout_b511cfb6546544aa83f7920169604fbe 0 network.computeDomU08 0 consoleauth.controller 0 scheduler 0 glance_notifications.info 132 cinder-volume.controller 0 glance_notifications.error 1 network_fanout_a4dc31150bfd4fb3bf393f24a343ff76 0 cert.computeDomU08 0 cinder-scheduler_fanout_b578bf0f687c4564920f3500ae2c9b8c 0 cinder-scheduler.controller 0 network 0 compute_fanout_c1f1cd2ab9cc4c5b87fbfd72dd25a432 0 scheduler_fanout_8aa445468b5c4aa6b2a1a4412dbc09fc 0 network_fanout_693737b6acaf4ba59c3c6cd31a70951b 0 consoleauth 0 ...done. If the nova-networks are hanging they are probably stuck waiting on a lock files. I believe the lock files are in /var/lock/nova by default. You could try deleting them and restarting nova-network. However, there is no nova directory under /var/locks Thank you, Afef Vish On Dec 10, 2012, at 1:32 PM, Afef Mdhaffar mdhaf...@mathematik.uni-marburg.de wrote: 2012/12/10 Vishvananda Ishaya vishvana...@gmail.com I don't see any errors in your network log. are nova-network and nova-compute running on the same host with the same config file? Yes, nova-network and nova-compute are running on the same node -- this is the compute node It looks like it isn't recieving a message. Are you running another nova-network that is picking up the message on another host? I have another nova-network running on the cloud controller. The platform was composed of 9 nodes (1 cloud controller + 8 compute nodes) and was running till friday (when one of my colleagues has installed some updates on our gateway). each node (including the controller) runs nova-network and nova-compute. Then (after updating the gateway), only the cloud controller and one compute node are still correctly running. and the rest of the nodes returns the same error - related in my opinion to nova-network. Any ideas how to fix that? Thank you, Afef Vish On Dec 10, 2012, at 12:18 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: Hi all, I am facing an boring issue since Friday: nova-network is unable to start dnsmasq. Therefore the xapi0 interface is not created. Then, it is impossible to launch VMs. nova-network does not answer requests and nova-compute returns an RPC timeout. Please help me to solve this problem I am using openstack folsom release + XCP + ubuntu 12.04 log file of nova-compute and nova-network are attached to this e-mail. Thank you, Afef nova-compute.txtnova-network.log___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Afef MDHAFFAR http://www.redcad.org/members/mdhaffar/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dnsmasq does not start + no xapi interface -- how to solve this problem
You could just turn off notifications in glance but that isn't causing an issue. So it seems pretty clear that your compute and network nodes are listening properly on 05, 07, 08. Is it possible that your network got configured as multi_host=False somehow? Or that you have multiple rabbits running with nodes connected to different ones? Vish On Dec 10, 2012, at 2:00 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: 2012/12/10 Vishvananda Ishaya vishvana...@gmail.com Check rabbitmqctl list_queues and see if there are queues that have nonzero entries. That means messages are being sent but not picked up by the nodes. Here is the output of the command -- there some non zero values for glance info. Is there any way to clear this queue? rabbitmqctl list_queues Listing queues ... cinder-volume 0 network.computeDomU07 0 compute.computeDomU07 0 network.computeDomU05 0 compute 0 scheduler.computeDomU05 0 consoleauth.computeDomU08 0 network.controller0 cinder-scheduler 0 compute_fanout_470aa521abf344f398dc98bf2f99b6e1 0 scheduler.computeDomU07 0 compute.controller0 network_fanout_209e3038f3af49849c10263ab1012e37 0 cert.computeDomU070 scheduler.computeDomU08 0 consoleauth.computeDomU05 0 glance_notifications.warn 0 consoleauth_fanout_9f3c92a646e74f9c88cb1317379d0a6a 0 scheduler.controller 0 network_fanout_9cf790a90c2f49c781a8046d0ea91d30 0 cinder-volume_fanout_693d1211a2a4478b828acb91099a228b 0 cert_fanout_d669d273749c432d999cdfd0a7a715a9 0 network_fanout_e4cc6507e07747d093ecc59502d62018 0 consoleauth.computeDomU07 0 cert_fanout_a9734647226c4ebda2e112ece8f6f168 0 compute.computeDomU08 0 cert.computeDomU050 scheduler_fanout_6c29f818954243468653858252666f2a 0 cert.controller 0 cert 0 compute.computeDomU05 0 network_fanout_b511cfb6546544aa83f7920169604fbe 0 network.computeDomU08 0 consoleauth.controller0 scheduler 0 glance_notifications.info 132 cinder-volume.controller 0 glance_notifications.error1 network_fanout_a4dc31150bfd4fb3bf393f24a343ff76 0 cert.computeDomU080 cinder-scheduler_fanout_b578bf0f687c4564920f3500ae2c9b8c 0 cinder-scheduler.controller 0 network 0 compute_fanout_c1f1cd2ab9cc4c5b87fbfd72dd25a432 0 scheduler_fanout_8aa445468b5c4aa6b2a1a4412dbc09fc 0 network_fanout_693737b6acaf4ba59c3c6cd31a70951b 0 consoleauth 0 ...done. If the nova-networks are hanging they are probably stuck waiting on a lock files. I believe the lock files are in /var/lock/nova by default. You could try deleting them and restarting nova-network. However, there is no nova directory under /var/locks Thank you, Afef Vish On Dec 10, 2012, at 1:32 PM, Afef Mdhaffar mdhaf...@mathematik.uni-marburg.de wrote: 2012/12/10 Vishvananda Ishaya vishvana...@gmail.com I don't see any errors in your network log. are nova-network and nova-compute running on the same host with the same config file? Yes, nova-network and nova-compute are running on the same node -- this is the compute node It looks like it isn't recieving a message. Are you running another nova-network that is picking up the message on another host? I have another nova-network running on the cloud controller. The platform was composed of 9 nodes (1 cloud controller + 8 compute nodes) and was running till friday (when one of my colleagues has installed some updates on our gateway). each node (including the controller) runs nova-network and nova-compute. Then (after updating the gateway), only the cloud controller and one compute node are still correctly running. and the rest of the nodes returns the same error - related in my opinion to nova-network. Any ideas how to fix that? Thank you, Afef Vish On Dec 10, 2012, at 12:18 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: Hi all, I am facing an boring issue since Friday: nova-network is unable to start dnsmasq. Therefore the xapi0 interface is not created. Then, it is impossible to launch VMs. nova-network does not answer requests and nova-compute returns an RPC timeout. Please help me to solve this problem I am using openstack folsom release + XCP + ubuntu 12.04 log file of nova-compute and nova-network are attached to this e-mail. Thank you, Afef nova-compute.txtnova-network.log___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp --
[Openstack] Nova metadata service
Hi guys! After looking for in the mailing list and docs, I honestly still don't understand what really is nova-api-metadata. it's a mandatory service in a multi-host deployment? it's only related to EC2? Thanks! Regards, JuanFra. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova metadata service
Its really just a binary that activates https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L100 Its a way to allow for a VM to get metadata about itself and any userdata (of which users may have provided) on boot. Said feature is not just connected to ec2, but provides a generic mechanism for getting this type of data to an instance. The ec2 folks I believe are just the 'originators' of said concept and that’s how it got named initially. From: JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.commailto:juanfra.rodriguez.card...@gmail.com Date: Monday, December 10, 2012 5:10 PM To: Openstack openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Nova metadata service Hi guys! After looking for in the mailing list and docs, I honestly still don't understand what really is nova-api-metadata. it's a mandatory service in a multi-host deployment? it's only related to EC2? Thanks! Regards, JuanFra. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] A confuse about the FlatDHCP network
Understood. Thanks guys. On Tue, Dec 11, 2012 at 2:26 AM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Dec 5, 2012, at 7:19 PM, Lei Zhang zhang.lei@gmail.com wrote: thank you very much, Vishvananda. But I am still confused about the 192.168.0.0/24 and the 10.0.0.0/8 ip. What means by The addresses will be moved on to the bridge. It means the 192.168.0.0/8 will be disappear? In my opinion, the bridged NIC (eth1) should be worked under promiscuous mode and its IP should be 0.0.0.0. So the eth1 should not own any IP. No moved to the bridge means that the ip will move from eth1 to the bridge eth1 -- no ip address br100 192.168.0.2 10.0.0.2 (for example). Nova moves the eth1 ip automatically when it creates the bridge if eth1 has an ip. Vish But if the 192 address doesn't exist, how the compute-note communicate with each other? Through the eth0? I have no idea. On Thu, Dec 6, 2012 at 3:12 AM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Dec 5, 2012, at 1:53 AM, Lei Zhang zhang.lei@gmail.com wrote: Hi all, I am reading the http://docs.openstack.org/trunk/openstack-compute/admin/content/libvirt-flat-dhcp-networking.html, I got the following deploy architecture. But there are several that I am confused. - How and why 192.168.0.0/24 ip range exist? It is necessary or not? The eth1 on the each physical machine own two ip(10.0.0.0/24 and 192.168.0.0/24)? Is that possible? In the nova-compute, the eth1 should be bridged by br100. the eth1 should not own any IP address, right? The addresses will be moved on to the bridge. The point of having an ip address is so that things like rabbit and mysql can communicate over a different set of addresses than the guest network. Usually this would be done on a separate eth device (eth2) or vlan, but I was trying to keep - In a better way, should we separate the nova-network/eth0 to the internet public switch for access the internet by all VMs. and the nova-compute/eth0 should be bind to a internal switch for admin access use. Is it right? Ideally there are three eth devices / vlans a) public (for 99 adddresses in diagram) b) management (for 192 addresses in diagram) c) guest (for 10 addresses in diagram) -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] authentication failure for glance client in the latest devstack dev environment
Try rm pem files under /var/cache/nova/ and /var/cache/glance/ , then ./stash.sh again. I just reported a bug: https://bugs.launchpad.net/devstack/+bug/1088497 2012/11/14 Gui Maluf guimal...@gmail.com I'm getting the same error! I tried to run devstack with a simple localrc but still happening the same error. stack@cloud-controller:~/devstack$ glance image-list Request returned failure status. Invalid OpenStack Identity credentials. On Fri, Nov 9, 2012 at 8:44 AM, Lu, Lianhao lianhao...@intel.com wrote: My system is Ubuntu 12.04 64bit. My nova list also failed with a HTTP 401 status error, with the following output on nova-api: 2012-11-09 18:30:09 ERROR keystone.common.cms [-] Verify error: Verification failure 139967656924832:error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature length:rsa_sign.c:175: 139967656924832:error:2E09A09E:CMS routines:CMS_SignerInfo_verify_content:verification failure:cms_sd.c:900: 139967656924832:error:2E09D06D:CMS routines:CMS_verify:content verify error:cms_smime.c:425: 2012-11-09 18:30:09 WARNING keystone.middleware.auth_token [-] Authorization failed for token .. 2012-11-09 18:30:09 INFO keystone.middleware.auth_token [-] Invalid user token - rejecting request 2012-11-09 18:30:09 INFO nova.osapi_compute.wsgi.server [-] 10.239.36.61 GET /v2/447239d7ddfd4ae89393c9ecf538d703/servers/det ail HTTP/1.1 status: 401 len: 461 time: 0.0153220 However, the keystone command-line client works fine. Best Regards, Lianhao -Original Message- From: openstack-bounces+lianhao.lu=intel@lists.launchpad.net[mailto: openstack-bounces+lianhao.lu=intel@lists.launchpad.net] On Behalf Of Lu, Lianhao Sent: Friday, November 09, 2012 4:31 PM To: openstack@lists.launchpad.net; openstack-...@lists.openstack.org Subject: [Openstack] authentication failure for glance client in the latest devstack dev environment Hi fellows, Today I just updated my devstack to setup a new openstack dev environment with RECLONE set to yes in localrc. The stack.sh failed at the very end in glance image-create with the error of Invalid OpenStack Identify credential. I then tried to run glance image-list in the command line after source openrc admin, it also failed with the same error. When the error happens, glance-api server reported the following errors on the screen: 2012-11-09 16:20:31 16950 ERROR keystone.middleware.auth_token [-] HTTP connection exception: [Errno 1] _ssl.c:504: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol 2012-11-09 16:20:31 16950 WARNING keystone.middleware.auth_token [-] Authorization failed for token MIIL7wYJKoZIhvcNAQcCoIIL4DCCC9wCAQExCTAHBgUrDgMCGjCCCkUGCSqGSIb3DQEHAaCCCjYEggoyeyJhY2Nlc3MiOiB7InRva2VuIjogeyJp c3N1ZWRfYXQiOiAiMDg6MjA6MzEuNjM3.(..omit here) A8uKBr1VlQoeF2Y-ND+DhZV+vjrM8i6FcGfeFq6Vra-1ktoQjkfh88XmG2tCcwrlGo0nVM4OrRaIs8F9Iwc4EIXHA+Aw73MzqUIRVSE8ahiFg9nNM = 2012-11-09 16:20:31 16950 INFO keystone.middleware.auth_token [-] Invalid user token - deferring reject downstream And the keystone reported the following: (eventlet.wsgi.server): 2012-11-09 16:28:21,276 DEBUG wsgi write 127.0.0.1 - - [09/Nov/2012 16:28:21] POST /v2.0/tokens HTTP/1.1 200 6780 0.095150 localhost - - [09/Nov/2012 16:28:21] code 400, message Bad request syntax (\x16\x03\x01\x00\xcd\x01\x00\x00\xc9\x03\x02P\x9c\xbe\xa5#\xc8D\xf8\xe9\xe9\x97\xc5w\x19LX\xfc\xb8\x04v\xb1w'\x04A\xa7}\xa8\x 0c) localhost - - [09/Nov/2012 16:28:21] ��P���#�DwLX�v�w'A�}� 400 - Does anyone know what's going wrong here? Yours, -Lianhao ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \t *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Best, Jian ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [swift] how to configure NWR policy
Hi all, I have a question about swift configuration for NWR policy. According to some documents of Swift, NWR is configurable. The general configuration is: N=3, W=2, R=1 or 2. Swift can provide both models of consistency: strong and eventual. But I can't find where to configure this option. Any suggestion is appreciated! Best Regards, Edward Zhang(张华) IBM China Software Development Lab inline: ecblank.gifinline: 1F033383.gif___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [swift] how to configure NWR policy
Hi, Zhang, Just add 'X-Newest: Ture' in the HTTP GET request. 2012/12/11 Hua ZZ Zhang zhu...@cn.ibm.com Hi all, I have a question about swift configuration for NWR policy. According to some documents of Swift, NWR is configurable. The general configuration is: N=3, W=2, R=1 or 2. Swift can provide both models of consistency: strong and eventual. But I can't find where to configure this option. Any suggestion is appreciated! *Best Regards, * -- *Edward Zhang(张华)* IBM China Software Development Lab ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu 1F033383.gifecblank.gif___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [swift] how to configure NWR policy
Alex, that make sense to me. thanks a lot. :-) Best Regards, Edward Zhang(张华) Alex Yang alex890714@gmail .com To Hua ZZ Zhang/China/IBM@IBMCN, 12/11/2012 11:37 cc AMopenstack@lists.launchpad.net openstack@lists.launchpad.net, Hai HJ Ji/China/IBM@IBMCN Subject Re: [Openstack] [swift] how to configure NWR policy Hi, Zhang, Just add 'X-Newest: Ture' in the HTTP GET request. 2012/12/11 Hua ZZ Zhang zhu...@cn.ibm.com Hi all, I have a question about swift configuration for NWR policy. According to some documents of Swift, NWR is configurable. The general configuration is: N=3, W=2, R=1 or 2. Swift can provide both models of consistency: strong and eventual. But I can't find where to configure this option. Any suggestion is appreciated! Best Regards, Edward Zhang(张华) IBM China Software Development Lab ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu inline: ecblank.gifinline: 70384012.gifinline: graycol.gifinline: pic17543.gif___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Quantum] Quantum OVS Plugin doubt
Hi- Thanks for the reply Gary.. But with respect to the Quantum_plugin_base_v2.py code, which is the base class for the plugins, We can see the create/update/delete network methods only in the quantum plugin. But then How about create/update/delete ports and subnet methods. These methods do exists in the ryu/nec/nicira plugins. Will ovs plugin will not consider the implementation of port and subnet? If it considers, where these are happening? Kindly help me understand the same. Thanks in advance - Trinath On Sun, Dec 9, 2012 at 5:19 PM, Gary Kotton gkot...@redhat.com wrote: Hi Trina, I am not really sure that I understand your question. The Quantum service marshals the API's to a plugin. The plugin is responsible for providing the virtual network service. In the case of the OVS plugin the ovs_quantum_plugin.py will treat the API calls. That means that it will enable the user to perform CRUD operations on the following: networks, subnets and ports. In order to do this it stores the values in a persistent database. The plugin has a layer 2 agent that performs the actual network configuration. Hope that this help. Thanks Gary On 12/07/2012 09:10 AM, Trinath Somanchi wrote: Hi Stackers- I have a doubt with respect to the Quantum OVS Plugin. [1] Do all the APIs of Quantum use the Quantum OVS plugin to get the data from the database. or they directly contact the database. Since, I have seen ovs_quantum_plugin.py code, it has create_network, update_network methods which use the db api. Is that the OVS Quantum Plugin APIs are partially used by the Quantum APIs for getting data from database? Kindly help me understand these areas of Quantum. Thanks in advance -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova metadata service
It is not a necessity, but it is very useful. Also look at config drive. -Matt On Mon, Dec 10, 2012 at 5:33 PM, Joshua Harlow harlo...@yahoo-inc.comwrote: Its really just a binary that activates https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L100 Its a way to allow for a VM to get metadata about itself and any userdata (of which users may have provided) on boot. Said feature is not just connected to ec2, but provides a generic mechanism for getting this type of data to an instance. The ec2 folks I believe are just the 'originators' of said concept and that’s how it got named initially. From: JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.com Date: Monday, December 10, 2012 5:10 PM To: Openstack openstack@lists.launchpad.net Subject: [Openstack] Nova metadata service Hi guys! After looking for in the mailing list and docs, I honestly still don't understand what really is nova-api-metadata. it's a mandatory service in a multi-host deployment? it's only related to EC2? Thanks! Regards, JuanFra. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [swift] how to configure NWR policy
Does any of our documentation say NRW are directly configurable? It's not really quite that simple. N is a property of the cluster, chosen when you build the ring. W is always a simple majority of N. R is generally 1 (eventually consisten reads), but the client can request it be bumped to N ( highly consistent reads) using X-Newest. But then there's stuff like we provide RYW consistency on default reads, which can't really be modeled by NRW notation. - Mike On Mon, Dec 10, 2012 at 9:47 PM, Hua ZZ Zhang zhu...@cn.ibm.com wrote: Alex, that make sense to me. thanks a lot. :-) *Best Regards, * -- *Edward Zhang(张华)* [image: Inactive hide details for Alex Yang ---12/11/2012 11:37:24 AM---Alex Yang alex890...@gmail.com]Alex Yang ---12/11/2012 11:37:24 AM---Alex Yang alex890...@gmail.com *Alex Yang alex890...@gmail.com* 12/11/2012 11:37 AM To Hua ZZ Zhang/China/IBM@IBMCN, cc openstack@lists.launchpad.net openstack@lists.launchpad.net, Hai HJ Ji/China/IBM@IBMCN Subject Re: [Openstack] [swift] how to configure NWR policy Hi, Zhang, Just add 'X-Newest: Ture' in the HTTP GET request. 2012/12/11 Hua ZZ Zhang *zhu...@cn.ibm.com* zhu...@cn.ibm.com Hi all, I have a question about swift configuration for NWR policy. According to some documents of Swift, NWR is configurable. The general configuration is: N=3, W=2, R=1 or 2. Swift can provide both models of consistency: strong and eventual. But I can't find where to configure this option. Any suggestion is appreciated! * Best Regards, * -- *Edward Zhang(张华)* IBM China Software Development Lab ___ Mailing list: *https://launchpad.net/~openstack*https://launchpad.net/~openstack Post to : *openstack@lists.launchpad.net*openstack@lists.launchpad.net Unsubscribe : *https://launchpad.net/~openstack*https://launchpad.net/~openstack More help : *https://help.launchpad.net/ListHelp*https://help.launchpad.net/ListHelp -- 杨雨 Email: *alex890...@gmail.com* alex890...@gmail.com GitHub: *https://github.com/AlexYangYu*https://github.com/AlexYangYu Blog:*http://alexyang.sinaapp.com*http://alexyang.sinaapp.com/ Weibo: *http://www.weibo.com/alexyangyu*http://www.weibo.com/alexyangyu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] S3 Token
On Mon, Dec 10, 2012 at 4:17 AM, Adam Young ayo...@redhat.com wrote: As a Keystone core developer, I have to say that I don't see it as a huge burden to keep it in place. We want to maintain API backward compatability, and removing it would break that. We should deprecate it and get people to sign off on a complete removal before taking it out of keystone. Thanks for the feedback guy, if that's not much of troubles to keep it in keystone we can leave it there. Cheers, Chmouel. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [swift] how to configure NWR policy
Mike, Thanks for you clarification. I'm interested in how to enable the following combinations. for case 1, can we do it without sending the HTTP head 'X-Newest'? for case 2, how to enable it? N=3, W=2, R=2 (Strong Consistence Mode) N=3, W=3, R=1 (Strict Consistence Mode) Best Regards, Edward Zhang(张华) Michael Barton mike-launchpad@w eirdlooking.com To Sent by: Hua ZZ Zhang/China/IBM@IBMCN, palr...@gmail.com cc Alex Yang alex890...@gmail.com, openstack@lists.launchpad.net 12/11/2012 02:31 openstack@lists.launchpad.net, PMHai HJ Ji/China/IBM@IBMCN Subject Re: [Openstack] [swift] how to configure NWR policy Does any of our documentation say NRW are directly configurable? It's not really quite that simple. N is a property of the cluster, chosen when you build the ring. W is always a simple majority of N. R is generally 1 (eventually consisten reads), but the client can request it be bumped to N ( highly consistent reads) using X-Newest. But then there's stuff like we provide RYW consistency on default reads, which can't really be modeled by NRW notation. - Mike On Mon, Dec 10, 2012 at 9:47 PM, Hua ZZ Zhang zhu...@cn.ibm.com wrote: Alex, that make sense to me. thanks a lot. :-) Best Regards, Edward Zhang(张华) Alex Yang ---12/11/2012 11:37:24 AM---Alex Yang alex890...@gmail.com Alex Yang alex890714@gmail. com To 12/11/2012 11:37 AM Hua ZZ Zhang/China/IBM@IBMCN, cc openstack@lists.launchpad.net openstack@lists.launchpad.net, Hai HJ Ji/China/IBM@IBMCN Subject
Re: [Openstack] Nova metadata service
Hello,
nova-api-metada service is an optional nova daemon that implements an HTTP
interface for retrieving metadata you associate to an instance at boot time
(see --user-data parameter).
Provided that you have installed and correctly configured it, try the
following sequence for better understanding.
Hope it helps,
Marco.
*At the client console, create a file and launch an instance with the
following commands:*
* *
*
*
*$ echo 'This is user data!' myFile.txt*
*$ nova boot testUserData --image=19d24df6-be35-40fe-b61d-8cf381abf1f7
--flavor=1 --user-data myFile.txt*
+-+--+
| Property| Value
|
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-011c
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | building
|
| accessIPv4 |
|
| accessIPv6 |
|
| adminPass | rXQ37SMMmu7D
|
| config_drive|
|
| created | 2012-11-14T17:11:47Z
|
| flavor | m1.tiny
|
| hostId |
|
| id |
f87e825b-e31f-4918-89ca-0fab3645cf44 |
| image | cirros-0.3.0-x86_64-uec
|
| key_name| None
|
| metadata| {}
|
| name| testUserData
|
| progress| 0
|
| security_groups | [{u'name': u'default'}]
|
| status | BUILD
|
| tenant_id | 43b38bc900c14082a14cda212c324f0a
|
| updated | 2012-11-14T17:11:47Z
|
| user_id | d3e8a1682a064f01ba80c45c28e6af6e
|
+-+--+
*To retrieve the information from the metadata service, connect to the
instance and submit the following commands:*
* *
*
*
*$ wget http://169.254.169.254/latest/user-data -O-*
Connecting to 169.254.169.254 (169.254.169.254:80)
This is user data!
-100%
||
19 --:--:-- ETA
*Note: the command for retrieving data from the metadata service may vary
both in the address of the service (here we used the default configuration
address 169.254.169.254) and in the format of the wget command (depending
on the OS of the image).*
* *
On Tue, Dec 11, 2012 at 7:29 AM, Matt Joyce matt.jo...@cloudscaling.comwrote:
It is not a necessity, but it is very useful. Also look at config drive.
-Matt
On Mon, Dec 10, 2012 at 5:33 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:
Its really just a binary that activates
https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L100
Its a way to allow for a VM to get metadata about itself and any userdata
(of which users may have provided) on boot.
Said feature is not just connected to ec2, but provides a generic
mechanism for getting this type of data to an instance.
The ec2 folks I believe are just the 'originators' of said concept and
that’s how it got named initially.
From: JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.com
Date: Monday, December 10, 2012 5:10 PM
To: Openstack openstack@lists.launchpad.net
Subject: [Openstack] Nova metadata service
Hi guys!
After looking for in the mailing list and docs, I honestly still don't
understand what really is nova-api-metadata.
it's a mandatory service in a multi-host deployment? it's only related to
EC2?
Thanks!
Regards,
JuanFra.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Understanding the Folsom-Quantum
Hi- I have the following first set of doubts regarding the Folsom Quantum [1] With regard of Quantum Plug-in, How does the RPC communication take place between the Agent and the plug-n ? In the source code, ovs_quantum_plugin.py, I find the setup_rpc method and AgentRPCAPI class what does the reverse RPC tasks. Can any one guide me on understanding this. [2] What is the significance of the file quantum/db/dhcp_rpc_base.py? Many plugins in the quantum/plugins directory use the methods in the class. [3] With core_plugin configuration being in place, can we have some other plugin too existing in Quantum? Can any one guide me on how to achieve the same, like a Fake plugin? [4] Why OVS quantum Plug-in doesn't support create/update/delete of port and subnets? Kindly help me understand these ... Thanks in advance -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_python-cinderclient_trunk #14
Title: raring_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-cinderclient_trunk/14/Project:raring_grizzly_python-cinderclient_trunkDate of build:Mon, 10 Dec 2012 11:42:13 -0500Build duration:2 min 39 secBuild cause:Started by user james-pageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 3 builds failed.33ChangesNo ChangesConsole Output[...truncated 1155 lines...]Download error on http://pypi.python.org/simple/setuptools-git/: timed out -- Some packages may not be found!Couldn't find index page for 'setuptools-git' (maybe misspelled?)Download error on http://pypi.python.org/simple/: timed out -- Some packages may not be found!No local packages or download links found for setuptools-git>=0.4Traceback (most recent call last): File "setup.py", line 58, in "console_scripts": ["cinder = cinderclient.shell:main"] File "/usr/lib/python2.7/distutils/core.py", line 112, in setup_setup_distribution = dist = klass(attrs) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 221, in __init__self.fetch_build_eggs(attrs.pop('setup_requires')) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in fetch_build_eggsparse_requirements(requires), installer=self.fetch_build_egg File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 580, in resolvedist = best[req.key] = env.best_match(req, self, installer) File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 825, in best_matchreturn self.obtain(req, installer) # try and download/install File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 837, in obtainreturn installer(requirement) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 295, in fetch_build_eggreturn cmd.easy_install(req) File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 611, in easy_installraise DistutilsError(msg)distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-git>=0.4')ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-b23c3422-4361-4084-b7d0-cb7c8e409b64', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-b23c3422-4361-4084-b7d0-cb7c8e409b64', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-cinderclient/grizzly /tmp/tmpPJ0WvE/python-cinderclientmk-build-deps -i -r -t apt-get -y /tmp/tmpPJ0WvE/python-cinderclient/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-b23c3422-4361-4084-b7d0-cb7c8e409b64', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-b23c3422-4361-4084-b7d0-cb7c8e409b64', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure--
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_python-cinderclient_trunk #15
Title: raring_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-cinderclient_trunk/15/Project:raring_grizzly_python-cinderclient_trunkDate of build:Mon, 10 Dec 2012 11:48:00 -0500Build duration:2 min 24 secBuild cause:Started by user james-pageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 4 builds failed.25ChangesNo ChangesConsole Output[...truncated 1155 lines...]Download error on http://pypi.python.org/simple/setuptools-git/: timed out -- Some packages may not be found!Couldn't find index page for 'setuptools-git' (maybe misspelled?)Download error on http://pypi.python.org/simple/: timed out -- Some packages may not be found!No local packages or download links found for setuptools-git>=0.4Traceback (most recent call last): File "setup.py", line 58, in "console_scripts": ["cinder = cinderclient.shell:main"] File "/usr/lib/python2.7/distutils/core.py", line 112, in setup_setup_distribution = dist = klass(attrs) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 221, in __init__self.fetch_build_eggs(attrs.pop('setup_requires')) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in fetch_build_eggsparse_requirements(requires), installer=self.fetch_build_egg File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 580, in resolvedist = best[req.key] = env.best_match(req, self, installer) File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 825, in best_matchreturn self.obtain(req, installer) # try and download/install File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 837, in obtainreturn installer(requirement) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 295, in fetch_build_eggreturn cmd.easy_install(req) File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 611, in easy_installraise DistutilsError(msg)distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-git>=0.4')ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-2e1b0c6c-4271-4a94-9636-d869c693c0b9', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-2e1b0c6c-4271-4a94-9636-d869c693c0b9', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-cinderclient/grizzly /tmp/tmpCZe99k/python-cinderclientmk-build-deps -i -r -t apt-get -y /tmp/tmpCZe99k/python-cinderclient/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-2e1b0c6c-4271-4a94-9636-d869c693c0b9', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-2e1b0c6c-4271-4a94-9636-d869c693c0b9', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure--
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_swift_trunk #52
Title: raring_grizzly_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_swift_trunk/52/Project:raring_grizzly_swift_trunkDate of build:Mon, 10 Dec 2012 12:31:00 -0500Build duration:5 min 14 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changescapture resetswift output in probetestsby clay.gerrardedittest/probe/common.pyAdd config of server start timeouts for probetestsby clay.gerrardeditetc/account-server.conf-sampleedittest/probe/common.pyeditetc/container-server.conf-sampleedittest/sample.confeditetc/proxy-server.conf-sampleeditetc/object-server.conf-sampleeditdoc/source/deployment_guide.rstedittest/probe/__init__.pyeditswift/common/wsgi.pyConsole Output[...truncated 2879 lines...]Fail-Stage: install-depsHost Architecture: amd64Install-Time: 0Job: swift_1.7.6+git201212101231~raring-0ubuntu1.dscMachine Architecture: amd64Package: swiftPackage-Time: 0Source-Version: 1.7.6+git201212101231~raring-0ubuntu1Space: 0Status: failedVersion: 1.7.6+git201212101231~raring-0ubuntu1Finished at 20121210-1234Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'swift_1.7.6+git201212101231~raring-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'swift_1.7.6+git201212101231~raring-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/grizzly /tmp/tmpXBsshI/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpXBsshI/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/swift/raring-grizzly --forcedch -b -D raring --newversion 1.7.6+git201212101231~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201212101231~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A swift_1.7.6+git201212101231~raring-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'swift_1.7.6+git201212101231~raring-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'swift_1.7.6+git201212101231~raring-0ubuntu1.dsc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_nova_trunk #261
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/261/Project:raring_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 14:02:15 -0500Build duration:4 min 31 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesAdd generic customization hooks via decorator.by brian.elliottaddnova/hooks.pyeditnova/compute/manager.pyeditnova/compute/api.pyadddoc/source/devref/hooks.rstedittools/pip-requiresaddnova/tests/test_hooks.pyeditdoc/source/devref/index.rstFix fname concurrency tests.by clark.boylaneditnova/tests/test_libvirt.pyUnpin lxml requirementsby chuck.shorteditnova/tests/test_libvirt_config.pyedittools/pip-requireslibvirt: enable apic setting for Xen or KVM guest.by yufang521247editnova/virt/libvirt/driver.pyeditnova/tests/test_libvirt.pyeditnova/tests/test_libvirt_config.pyeditnova/virt/libvirt/config.pyConsole Output[...truncated 5904 lines...]patching file nova/tests/test_api.pyHunk #1 succeeded at 433 (offset -3 lines).Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch avoid_setuptools_git_dependency.patchpatching file tools/pip-requiresApplying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-0eec92f1-4d97-4733-9c38-964259075ee0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-0eec92f1-4d97-4733-9c38-964259075ee0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpir_7PZ/novamk-build-deps -i -r -t apt-get -y /tmp/tmpir_7PZ/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201212101403~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-0eec92f1-4d97-4733-9c38-964259075ee0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-0eec92f1-4d97-4733-9c38-964259075ee0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #260
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/260/Project:precise_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 14:31:02 -0500Build duration:2 min 44 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse fixtures library for nova test fixtures.by mordrededitnova/tests/compute/test_rpcapi.pyeditnova/tests/integrated/integrated_helpers.pyeditnova/tests/test_test.pyeditbin/nova-dhcpbridgeeditnova/tests/network/test_manager.pyeditnova/tests/xenapi/stubs.pyeditnova/tests/test_imagecache.pyeditnova/test.pydeletenova/tests/fake_flags.pyaddnova/tests/conf_fixture.pyConsole Output[...truncated 4700 lines...]patching file nova/tests/test_api.pyHunk #1 succeeded at 433 (offset -3 lines).Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch avoid_setuptools_git_dependency.patchpatching file tools/pip-requiresApplying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-6fbeff70-a718-4bf4-a9f1-964311c8bd1f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-6fbeff70-a718-4bf4-a9f1-964311c8bd1f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmp4qozfI/novamk-build-deps -i -r -t apt-get -y /tmp/tmp4qozfI/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201212101432~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-6fbeff70-a718-4bf4-a9f1-964311c8bd1f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-6fbeff70-a718-4bf4-a9f1-964311c8bd1f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #262
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/262/Project:raring_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 14:31:03 -0500Build duration:3 min 43 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse fixtures library for nova test fixtures.by mordreddeletenova/tests/fake_flags.pyeditnova/tests/integrated/integrated_helpers.pyeditnova/tests/xenapi/stubs.pyeditnova/tests/compute/test_rpcapi.pyeditnova/tests/network/test_manager.pyaddnova/tests/conf_fixture.pyeditbin/nova-dhcpbridgeeditnova/tests/test_test.pyeditnova/tests/test_imagecache.pyeditnova/test.pyConsole Output[...truncated 5904 lines...]patching file nova/tests/test_api.pyHunk #1 succeeded at 433 (offset -3 lines).Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch avoid_setuptools_git_dependency.patchpatching file tools/pip-requiresApplying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-02d04dfa-fb18-4707-97be-5856645535a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-02d04dfa-fb18-4707-97be-5856645535a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpSWqqrx/novamk-build-deps -i -r -t apt-get -y /tmp/tmpSWqqrx/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201212101431~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-02d04dfa-fb18-4707-97be-5856645535a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-02d04dfa-fb18-4707-97be-5856645535a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #261
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/261/Project:precise_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 15:31:03 -0500Build duration:2 min 38 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesUse conductor for bw_usage operationsby danmseditnova/conductor/rpcapi.pyeditnova/conductor/manager.pyeditnova/compute/manager.pyeditnova/conductor/api.pyConsole Output[...truncated 4700 lines...]patching file nova/tests/test_api.pyHunk #1 succeeded at 433 (offset -3 lines).Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch avoid_setuptools_git_dependency.patchpatching file tools/pip-requiresApplying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5fdc8f52-a63e-4561-b760-a9fd8d061b79', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5fdc8f52-a63e-4561-b760-a9fd8d061b79', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpH5NScl/novamk-build-deps -i -r -t apt-get -y /tmp/tmpH5NScl/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201212101531~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5fdc8f52-a63e-4561-b760-a9fd8d061b79', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5fdc8f52-a63e-4561-b760-a9fd8d061b79', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #263
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/263/Project:raring_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 15:32:09 -0500Build duration:4 min 13 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesUse conductor for bw_usage operationsby danmseditnova/compute/manager.pyeditnova/conductor/api.pyeditnova/conductor/manager.pyeditnova/conductor/rpcapi.pyConsole Output[...truncated 5904 lines...]patching file nova/tests/test_api.pyHunk #1 succeeded at 433 (offset -3 lines).Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch avoid_setuptools_git_dependency.patchpatching file tools/pip-requiresApplying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-f9a21c89-c461-4f85-b9f0-f221dcc49b10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-f9a21c89-c461-4f85-b9f0-f221dcc49b10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpHtLxBV/novamk-build-deps -i -r -t apt-get -y /tmp/tmpHtLxBV/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201212101533~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-f9a21c89-c461-4f85-b9f0-f221dcc49b10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-f9a21c89-c461-4f85-b9f0-f221dcc49b10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #262
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/262/Project:precise_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 17:01:02 -0500Build duration:3 min 2 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesSet default DNS driver to No-op.by dprinceeditnova/config.pyaddnova/network/noop_dns_driver.pyConsole Output[...truncated 4727 lines...]Applying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-7d1f1d6f-b6d2-4b16-bf66-6585f8dd9bd8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-7d1f1d6f-b6d2-4b16-bf66-6585f8dd9bd8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpQTuRRz/novamk-build-deps -i -r -t apt-get -y /tmp/tmpQTuRRz/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 6c92e3c7885c1eb7da3032862a30a10348b2d810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201212101702~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [af28110] Set default DNS driver to No-op.dch -a [8e9bdd7] Use conductor for bw_usage operationsdch -a [d0e930b] libvirt: enable apic setting for Xen or KVM guest.dch -a [6b50880] Raise NotImplementedError in dns_driver.DNSDriver.dch -a [63f5839] Unpin lxml requirementsdch -a [797e9dc] Added sample tests to FlavorManage API.dch -a [70965c3] Use fixtures library for nova test fixtures.dch -a [87ced20] Fix fname concurrency tests.dch -a [e937a53] Add generic customization hooks via decorator.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-7d1f1d6f-b6d2-4b16-bf66-6585f8dd9bd8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-7d1f1d6f-b6d2-4b16-bf66-6585f8dd9bd8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #264
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/264/Project:raring_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 17:03:52 -0500Build duration:3 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesSet default DNS driver to No-op.by dprinceaddnova/network/noop_dns_driver.pyeditnova/config.pyConsole Output[...truncated 5931 lines...]Applying patch fix-libvirt-tests.patchpatching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-e96dce56-4d8d-4cfe-9159-92105edb4cfa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-e96dce56-4d8d-4cfe-9159-92105edb4cfa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpQaAAl1/novamk-build-deps -i -r -t apt-get -y /tmp/tmpQaAAl1/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 6c92e3c7885c1eb7da3032862a30a10348b2d810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201212101704~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [af28110] Set default DNS driver to No-op.dch -a [8e9bdd7] Use conductor for bw_usage operationsdch -a [d0e930b] libvirt: enable apic setting for Xen or KVM guest.dch -a [6b50880] Raise NotImplementedError in dns_driver.DNSDriver.dch -a [63f5839] Unpin lxml requirementsdch -a [797e9dc] Added sample tests to FlavorManage API.dch -a [70965c3] Use fixtures library for nova test fixtures.dch -a [87ced20] Fix fname concurrency tests.dch -a [e937a53] Add generic customization hooks via decorator.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-e96dce56-4d8d-4cfe-9159-92105edb4cfa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-e96dce56-4d8d-4cfe-9159-92105edb4cfa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #263
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/263/Project:precise_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 19:31:03 -0500Build duration:2 min 30 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix bw_usage_update issue with conductorby danmseditnova/tests/conductor/test_conductor.pyeditnova/conductor/manager.pyeditnova/conductor/api.pyConsole Output[...truncated 4730 lines...]patching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f8cbb1e6-7578-48c7-8557-80e7ca52b04a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f8cbb1e6-7578-48c7-8557-80e7ca52b04a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmp_RI4xe/novamk-build-deps -i -r -t apt-get -y /tmp/tmp_RI4xe/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 6c92e3c7885c1eb7da3032862a30a10348b2d810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201212101931~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [07848e7] Fix bw_usage_update issue with conductordch -a [af28110] Set default DNS driver to No-op.dch -a [8e9bdd7] Use conductor for bw_usage operationsdch -a [d0e930b] libvirt: enable apic setting for Xen or KVM guest.dch -a [6b50880] Raise NotImplementedError in dns_driver.DNSDriver.dch -a [63f5839] Unpin lxml requirementsdch -a [797e9dc] Added sample tests to FlavorManage API.dch -a [70965c3] Use fixtures library for nova test fixtures.dch -a [87ced20] Fix fname concurrency tests.dch -a [e937a53] Add generic customization hooks via decorator.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f8cbb1e6-7578-48c7-8557-80e7ca52b04a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f8cbb1e6-7578-48c7-8557-80e7ca52b04a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #265
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/265/Project:raring_grizzly_nova_trunkDate of build:Mon, 10 Dec 2012 19:31:03 -0500Build duration:3 min 30 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix bw_usage_update issue with conductorby danmseditnova/conductor/manager.pyeditnova/conductor/api.pyeditnova/tests/conductor/test_conductor.pyConsole Output[...truncated 5947 lines...]patching file nova/tests/test_libvirt_config.pyHunk #1 FAILED at 366.Hunk #2 FAILED at 387.Hunk #3 FAILED at 535.3 out of 3 hunks FAILED -- rejects in file nova/tests/test_libvirt_config.pyPatch fix-libvirt-tests.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-296ba4c7-131d-420a-860d-019526aebf96', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-296ba4c7-131d-420a-860d-019526aebf96', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpb_iDUV/novamk-build-deps -i -r -t apt-get -y /tmp/tmpb_iDUV/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 6c92e3c7885c1eb7da3032862a30a10348b2d810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201212101931~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [07848e7] Fix bw_usage_update issue with conductordch -a [af28110] Set default DNS driver to No-op.dch -a [8e9bdd7] Use conductor for bw_usage operationsdch -a [d0e930b] libvirt: enable apic setting for Xen or KVM guest.dch -a [6b50880] Raise NotImplementedError in dns_driver.DNSDriver.dch -a [63f5839] Unpin lxml requirementsdch -a [797e9dc] Added sample tests to FlavorManage API.dch -a [70965c3] Use fixtures library for nova test fixtures.dch -a [87ced20] Fix fname concurrency tests.dch -a [e937a53] Add generic customization hooks via decorator.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-296ba4c7-131d-420a-860d-019526aebf96', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-296ba4c7-131d-420a-860d-019526aebf96', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
