[Openstack] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Hi everyone, The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. This was an extremely busy milestone, with 100 blueprints implemented and more than 450 bugfixes overall. You can find the full list of new features and fixed bugs, as well as tarball downloads, at: https://launchpad.net/keystone/grizzly/grizzly-3 https://launchpad.net/glance/grizzly/grizzly-3 https://launchpad.net/nova/grizzly/grizzly-3 https://launchpad.net/horizon/grizzly/grizzly-3 https://launchpad.net/quantum/grizzly/grizzly-3 https://launchpad.net/cinder/grizzly/grizzly-3 Those projects are now temporarily feature-frozen (apart from already-granted exceptions) as we switch to testing and bugfixing mode in preparation for our first release candidates. Please test, try the new features, report bugs and help fix them ! Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] Grizzly-3 development milestone available (Ceilometer, Heat)
Thierry Carrez wrote: The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. And with perfect sync now, our two grizzly-incubated projects, Ceilometer and Heat, also have their grizzly-3 milestone available: https://launchpad.net/ceilometer/grizzly/grizzly-3 https://launchpad.net/heat/grizzly/grizzly-3 Happy testing and bugfixing! -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] VM does not get IP address
Hi,
I am following this manual
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/cbc6c95e749dea86fb4c77fcbf485e55c37a297d/OpenStack_Folsom_Install_Guide_WebVersion.rst
to install OpenStack Folsom
I have created one tenant net called net1. When I launch an
instance, there is this error:
nitializing random number generator... done.
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 1/30: up 10.09. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 2/30: up 11.10. request failed
wget: can't connect to remote host (169.254.169.254): Network is unreachable
Here are outputs:
root@folsom-controller:/etc/init.d# quantum net-list
+--+--+--+
| id | name | subnets
|
+--+--+--+
| 3c2eed52-969b-44a2-bd33-790999c5da5c | net1 |
a82109bf-5777-4730-b44a-5dceebc835cb |
+--+--+--+
root@folsom-controller:/etc/init.d#quantum port-list
+--+--+---+-+
| id | name | mac_address |
fixed_ips
|
+--+--+---+-+
| 0a410916-ce92-4d41-9085-1358f6493269 | | fa:16:3e:4e:d9:40 |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.2} |
| eea126e8-8661-4d55-b3e0-655d758a9203 | | fa:16:3e:ff:7e:ab |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.1} |
+--+--+---+-+
Please could you help me solve this problem?
What configuration files do you need?
Thank you!!!
--
Lukáš Vízner
___
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-volume] Problem of attaching a volume to a vm
Greetings all,
I have a problem of attaching volume to vm,
After attaching a volume to a vm, there are no error display on horizon(but
no success either),
and I found the following error in the /var/log/nova/compute.log,
2013-02-21 09:06:52 1588 TRACE nova.compute.manager [instance:
95763834-a8c4-4d53-bc46-2937379855a4] libvirtError: internal error unable
to execute QEMU command '__com.redhat_drive_add': Device
'drive-virtio-disk1' could not be initialized
2013-02-21 09:06:52 1588 TRACE nova.openstack.common.rpc.amqp rv =
meth(*args,**kwargs)
2013-02-21 09:06:52 1588 TRACE nova.openstack.common.rpc.amqp File
/usr/lib64/python2.6/site-packages/libvirt.py, line 419, in
attachDeviceFlags
2013-02-21 09:06:52 1588 TRACE nova.openstack.common.rpc.amqp if ret ==
-1: raise libvirtError ('virDomainAttachDeviceFlags() failed', dom=self)
2013-02-21 09:06:52 1588 TRACE nova.openstack.common.rpc.amqp libvirtError:
internal error unable to execute QEMU command '__com.redhat_drive_add':
Device 'drive-virtio-disk1' could not be initialized
==
It looks like something problem happened by libvirtd?
Did anyone have a similar problem like this before?
Please give me a hint,
Thanks,
Jeff
___
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] LXC on Folsom
Thank you Visgvananda. Chuan-Heng : Can you please tell us how did you upload the image into glance: ( The detailed commands would help) and have you done anything else beside installing nova-compute-lxc ?? Thanks Bilel On 02/22/2013 04:04 AM, Chuan-Heng Hsiao wrote: Hi Vishvananda, Thank you very much! I just tried and it launched! Though I can't access through VNC right now (code: 1006) I believe it's the problem related to VNC setting and not related to lxc. Sincerely, Hsiao The following is the startup console: init: Unable to create device: /dev/kmsg cloud-init start-local running: Fri, 22 Feb 2013 02:26:40 +. up 52122.82 seconds no instance data found in start-local ci-info: lo: 1 127.0.0.1 255.0.0.0 . ci-info: eth0 : 1 . . fa:16:3e:74:2f:f5 route_info failed cloud-init start running: Fri, 22 Feb 2013 02:31:43 +. up 52425.78 seconds 2013-02-22 02:31:43,997 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:44,999 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:46,000 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:47,002 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:48,003 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [4/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:49,004 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:51,111 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [7/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:53,114 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:55,116 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [11/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:57,118 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:31:59,120 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [15/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:02,124 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [18/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:05,127 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [21/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:08,130 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [24/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:11,133 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [27/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:14,137 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [30/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:18,138 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [34/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:22,142 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [38/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:26,147 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [42/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:30,151 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [46/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:34,155 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:39,161 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [55/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:44,166 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [60/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:49,171 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [65/120s]: url error [[Errno 101] Network is unreachable] 2013-02-22 02:32:54,172 - util.py[WARNING]:
Re: [Openstack] LXC on Folsom
On 02/22/2013 04:04 AM, Chuan-Heng Hsiao wrote: Hi Vishvananda, Thank you very much! I just tried and it launched! Though I can't access through VNC right now (code: 1006) I believe it's the problem related to VNC setting and not related to lxc. Hi, I don't think LXC does VNC (it does not emulate a VGA device). You can use ssh -XC to run graphical applications from your VM and there are some alternatives: http://ubuntuforums.org/showthread.php?p=3816948 http://www.ibm.com/developerworks/library/l-lxc-containers/ Ciao Bernhard M. ___ 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] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Hi! What is the status of Openstack Grizzly-3 Ubuntu packages? Can we already set it up using apt-get / aptitude? With packaged Heat, Ceilometer and etc? Which version is recommended to test Grizzly-3, Precise (via testing UCA), Raring? Is Grizzly planed to be the default Openstack for Raring? Thanks for the AWESOME work on Openstack! Regards, Thiago On 22 February 2013 05:47, Thierry Carrez thie...@openstack.org wrote: Hi everyone, The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. This was an extremely busy milestone, with 100 blueprints implemented and more than 450 bugfixes overall. You can find the full list of new features and fixed bugs, as well as tarball downloads, at: https://launchpad.net/keystone/grizzly/grizzly-3 https://launchpad.net/glance/grizzly/grizzly-3 https://launchpad.net/nova/grizzly/grizzly-3 https://launchpad.net/horizon/grizzly/grizzly-3 https://launchpad.net/quantum/grizzly/grizzly-3 https://launchpad.net/cinder/grizzly/grizzly-3 Those projects are now temporarily feature-frozen (apart from already-granted exceptions) as we switch to testing and bugfixing mode in preparation for our first release candidates. Please test, try the new features, report bugs and help fix them ! Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Martinx - ジェームズ wrote: What is the status of Openstack Grizzly-3 Ubuntu packages? Can we already set it up using apt-get / aptitude? With packaged Heat, Ceilometer and etc? Which version is recommended to test Grizzly-3, Precise (via testing UCA), Raring? Is Grizzly planed to be the default Openstack for Raring? I suspect it will take a few days for grizzly-3 to appear in Ubuntu, as the tarballs were cut a few hours ago. As far as I know, Grizzly is indeed the planned default OpenStack for Raring. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] VM doesnt get IP
Hello Aaron, Here are the outputs. Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com The output to the following would be a good start: quantum net-list quantum port-list ovs-dpctl show (on all nodes) Also make sure the quantum-dhcp-agent is running on your network node. Aaron On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Sorry about that, I'm using Folsom release with quantum, I'm installing the controller node and the network node in the same physical machine, I'm following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html Which config files do you need? Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com Hi, You'll have to provide more information than this for anyone to help you: i.e are you using quantum or nova-network, if your using quantum which plugin, config files etc. Aaron On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello guys, I'm getting problem in my VMs' creation, they don't get IP, the log piece shows: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed Do you have any idea how I can solve it? Thank you so much. Guilherme. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp outputs Description: Binary data ___ 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] LXC on Folsom
Hi Bernhard, Thank you very much for the information. I'll use ssh for the lxc instances. Sincerely, Hsiao On Fri, Feb 22, 2013 at 6:15 PM, Bernhard M. Wiedemann bwiedem...@suse.dewrote: On 02/22/2013 04:04 AM, Chuan-Heng Hsiao wrote: Hi Vishvananda, Thank you very much! I just tried and it launched! Though I can't access through VNC right now (code: 1006) I believe it's the problem related to VNC setting and not related to lxc. Hi, I don't think LXC does VNC (it does not emulate a VGA device). You can use ssh -XC to run graphical applications from your VM and there are some alternatives: http://ubuntuforums.org/showthread.php?p=3816948 http://www.ibm.com/developerworks/library/l-lxc-containers/ Ciao Bernhard M. ___ 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] How to use the novaclient python API
Thanks Vishvanda, that did help. I'm having an issue with endpoints, but I think when I installed openstack I might not have add all the needed endpoints: File /usr/lib/python2.7/dist-packages/novaclient/service_catalog.py, line 67, in url_for raise novaclient.exceptions.EndpointNotFound() novaclient.exceptions.EndpointNotFound JR On 2/21/2013 5:42 PM, Vishvananda Ishaya wrote: Looks like those docs are pretty outdated. I have a github repository where I have been putting together some examples of doing common commands with a) cli b) python-*client c) curl It is incomplete but this should help get you started: # helper method to create the client https://github.com/vishvananda/openstack-examples/blob/master/helper.py # keypair methods https://github.com/vishvananda/openstack-examples/blob/master/keypair.py Vish On Feb 21, 2013, at 2:20 PM, JR botem...@gmail.com wrote: Greetings all, http://docs.openstack.org/developer/python-novaclient/api.html says that: from novaclient import OpenStack nova = OpenStack(USERNAME, PASSWORD, AUTH_URL) Should work. But: (virtual-python2.7)ftc-ms01:test# pip search python-novaclient |head -3 python-novaclient - Client library for OpenStack Nova API. INSTALLED: .98.daee5438f2232c0467d93029bd636fc2114e4c09 LATEST:2.11.1 (virtual-python2.7)ftc-ms01:test# cat a.py from novaclient import OpenStack (virtual-python2.7)ftc-ms01:test# which python /src/virtual-python2.7/bin/python (virtual-python2.7)ftc-ms01:test# python a.py Traceback (most recent call last): File a.py, line 1, in module from novaclient import OpenStack ImportError: cannot import name OpenStack I've heard that the python api isn't well documented but, looking at the code there seems to be lots of functionality. Could someone give me a hint on how to use it? Thanks JR ___ 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] Within VM Guest : Can't ping to DNS ip's. DNS lookup work. iptables?
From reading http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html I think its related to iptables NAT chain rules required. Am I on the right lines? Openstack Host: /etc/nova/nova.conf # network specific settings --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth1 --flat_network_bridge=br100 --fixed_range=10.0.2.32/27 --floating_range=10.0.1.224/27 --network_size=32 --flat_network_dhcp_start=10.0.2.33 --flat_injected=False --force_dhcp_release --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose Openstack Host: ifconfig settings br100 10.0.2.33/27 eth0 192.168.1.38/24 Gateway 192.168.1.200 (office network) virbr0 192.168.1.122 vnet0 VM Guest: ifconfig settings vtnet0 10.0.2.34 Openstack VM Guest instance IPs: 10.0.2.34 10.0.1.229 (floating ip pool) So from this I think my floating ip = 10.0.1.229 fix ip = 10.0.2.34 So I need to enter this ... Does this look right? iptables -A nova-network-OUTPUT -d floating ip/27 -j DNAT --to-destination fix ip iptables -A nova-network-PREROUTING -d floating ip/27 -j DNAT --to-destination fix ip iptables -A nova-network-floating-snat -s fix ip/27 -j SNAT --to-source floating ip___ 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] LXC on Folsom
Thank you Chuan-Heng Hsiao for your reply. I already have an OpenStack Folsom running with LXC. I was just wondering how did you upload Vishvananda's image to glance. He is talking about the root file system and i am not sure what does that mean. When i untar the package vish said, i have .img, floppy, loader, vmlinuz files and don't really now what to do. Kind regards, Bilel On 02/22/2013 03:46 PM, Chuan-Heng Hsiao wrote: 2. glance image-create --location http://uec-images.ubuntu.com/releases/12.04/release/ubuntu-12.04-server-cloudimg-amd64-disk1.img --is-public true --disk-format raw --container-format bare --name Ubuntu 3. glance image-update [img-uuid] --property hypervisor_type=lxc ___ 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] Grizzly-3 development milestone available (Ceilometer, Heat)
On Fri, Feb 22, 2013 at 10:15 AM, Thierry Carrez thie...@openstack.org wrote: Thierry Carrez wrote: The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. And with perfect sync now, our two grizzly-incubated projects, Ceilometer and Heat, also have their grizzly-3 milestone available: https://launchpad.net/ceilometer/grizzly/grizzly-3 https://launchpad.net/heat/grizzly/grizzly-3 Happy testing and bugfixing! -- Thierry Carrez (ttx) Release Manager, OpenStack You can read more about the Grizzly-3 milestone for Ceilometer at: https://launchpad.net/ceilometer/+announcement/11199 Cheers, -- Nicolas Barcet nico...@barcet.com a.k.a. nijaba, nick ___ 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] VM doesnt get IP
So guys, any idea about what am i missing? Thanks. 2013/2/22 Guilherme Russi luisguilherme...@gmail.com Hello Aaron, Here are the outputs. Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com The output to the following would be a good start: quantum net-list quantum port-list ovs-dpctl show (on all nodes) Also make sure the quantum-dhcp-agent is running on your network node. Aaron On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Sorry about that, I'm using Folsom release with quantum, I'm installing the controller node and the network node in the same physical machine, I'm following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html Which config files do you need? Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com Hi, You'll have to provide more information than this for anyone to help you: i.e are you using quantum or nova-network, if your using quantum which plugin, config files etc. Aaron On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello guys, I'm getting problem in my VMs' creation, they don't get IP, the log piece shows: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed Do you have any idea how I can solve it? Thank you so much. Guilherme. ___ 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] VM doesnt get IP
Hi Guilherme, (next time please paste these in the email rather than attaching, thx). From the text in the attachment (show below). It seems like you are not running the quantum-openvswitch-agent on your network node as there is no GRE tunnel from that to your compute node. Once you have quantum-openvswitch-agent running on all your machines you should be able to run ovs-dpctl looking under br-tun and see a tunnel between each host. Aaron CONTROLLER + NETWORK NODE: system@br-tun: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) system@br-int: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-int (internal) port 1: tap817d2f70-a0 (internal) port 2: qr-ea64e9aa-31 (internal) port 3: patch-tun (patch: peer=patch-int) system@br-ex: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-ex (internal) port 2: qg-95fe3fa1-d1 (internal) COMPUTE NODES COMPUTE NODE 01: ovs-dpctl show system@br-int: lookups: hit:380 missed:7590 lost:0 flows: 0 port 0: br-int (internal) port 2: patch-tun (patch: peer=patch-int) port 3: qvo981ae82e-d4 port 6: qvoc9df3a96-5f port 7: qvoc153ac28-ae port 8: qvo722a5d05-e4 system@br-tun: lookups: hit:381 missed:7589 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1) On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi luisguilherme...@gmail.com wrote: So guys, any idea about what am i missing? Thanks. 2013/2/22 Guilherme Russi luisguilherme...@gmail.com Hello Aaron, Here are the outputs. Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com The output to the following would be a good start: quantum net-list quantum port-list ovs-dpctl show (on all nodes) Also make sure the quantum-dhcp-agent is running on your network node. Aaron On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Sorry about that, I'm using Folsom release with quantum, I'm installing the controller node and the network node in the same physical machine, I'm following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html Which config files do you need? Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com Hi, You'll have to provide more information than this for anyone to help you: i.e are you using quantum or nova-network, if your using quantum which plugin, config files etc. Aaron On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello guys, I'm getting problem in my VMs' creation, they don't get IP, the log piece shows: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed Do you have any idea how I can solve it? Thank you so much. Guilherme. ___ 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] VM doesnt get IP
Hello Aaron, Sorry about attaching the infos, about the quantum agent, is it the quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at the controller and the compute nodes: service quantum-plugin-openvswitch-agent start start: Job is already running: quantum-plugin-openvswitch-agent Is there another thing i should do? I'm running my controller node and the network node at the same machine with 2 NICs, maybe can be a problem how i am making my network config? Thanks again. Guilherme. 2013/2/22 Aaron Rosen aro...@nicira.com Hi Guilherme, (next time please paste these in the email rather than attaching, thx). From the text in the attachment (show below). It seems like you are not running the quantum-openvswitch-agent on your network node as there is no GRE tunnel from that to your compute node. Once you have quantum-openvswitch-agent running on all your machines you should be able to run ovs-dpctl looking under br-tun and see a tunnel between each host. Aaron CONTROLLER + NETWORK NODE: system@br-tun: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) system@br-int: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-int (internal) port 1: tap817d2f70-a0 (internal) port 2: qr-ea64e9aa-31 (internal) port 3: patch-tun (patch: peer=patch-int) system@br-ex: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-ex (internal) port 2: qg-95fe3fa1-d1 (internal) COMPUTE NODES COMPUTE NODE 01: ovs-dpctl show system@br-int: lookups: hit:380 missed:7590 lost:0 flows: 0 port 0: br-int (internal) port 2: patch-tun (patch: peer=patch-int) port 3: qvo981ae82e-d4 port 6: qvoc9df3a96-5f port 7: qvoc153ac28-ae port 8: qvo722a5d05-e4 system@br-tun: lookups: hit:381 missed:7589 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1) On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi luisguilherme...@gmail.com wrote: So guys, any idea about what am i missing? Thanks. 2013/2/22 Guilherme Russi luisguilherme...@gmail.com Hello Aaron, Here are the outputs. Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com The output to the following would be a good start: quantum net-list quantum port-list ovs-dpctl show (on all nodes) Also make sure the quantum-dhcp-agent is running on your network node. Aaron On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Sorry about that, I'm using Folsom release with quantum, I'm installing the controller node and the network node in the same physical machine, I'm following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html Which config files do you need? Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com Hi, You'll have to provide more information than this for anyone to help you: i.e are you using quantum or nova-network, if your using quantum which plugin, config files etc. Aaron On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello guys, I'm getting problem in my VMs' creation, they don't get IP, the log piece shows: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed Do you have any idea how I can solve it? Thank you so much. Guilherme. ___ 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] [Keystone][Swift] Problems with admin_user, admin_password, admin_tenant_name
Back to my first question, should I create admin_user, admin_password,
admin_tenant_name by keystone command myself?
On Fri, Feb 22, 2013 at 9:02 AM, Kun Huang academicgar...@gmail.com wrote:
Dolph, thanks your advice, but in my environment, both below two case
1. setting admin_token,admin_user, admin_password, admin_tenant_name in
proxy.conf and setting admin_token in keystone.conf
2. setting admin_user, admin_password, admin_tenant_name in proxy.conf and
setting admin_token in keystone.conf
only admin_token in keystone.conf is valuable. (default ADMIN)
Should I create admin_user, admin_password, admin_tenant_name by keystone
command myself?
On Fri, Feb 22, 2013 at 1:45 AM, Dolph Mathews dolph.math...@gmail.comwrote:
Setting the admin_token config is overriding the admin_user,
admin_password, and admin_tenant_name values by specifying a static token.
I'd recommend removing it and using the auth credentials you've already
provided.
-Dolph
On Thu, Feb 21, 2013 at 3:10 AM, Kun Huang academicgar...@gmail.comwrote:
Following another question:
In document:
http://docs.openstack.org/developer/keystone/middleware_architecture.html
,
[filter:tokenauth]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
auth_uri = http://127.0.0.1:5000/
admin_token = Super999Sekret888Password777
admin_user = admin
admin_password = SuperSekretPassword
admin_tenant_name = service
;Uncomment next line and check ip:port to use memcached to cache tokens
;memcache_servers = 127.0.0.1:11211
That admin token is not admin_token = ADMIN in keystone, right?
On Thu, Feb 21, 2013 at 4:06 PM, Kun Huang academicgar...@gmail.comwrote:
I'm building environment with Swift + Keystone.
I have set admin_user, admin_password, admin_tenant_name, but it
doesn't work.
I followed the document:
http://docs.openstack.org/developer/swift/overview_auth.html and chmouel's
blog:
http://blog.chmouel.com/2011/11/24/swift-and-keystone-middleware-part1/
My swift and keystone run well:
[image: Inline image 1]
But failed in curl:
[image: Inline image 2]
I guess the value of admin_user/admin_password/admin_tenant_name
doesn't save in db.
Which step do I missed? or some problems in my proxy config?
Here is my current config.
[DEFAULT]
bind_port =
user = swift
[pipeline:main]
pipeline = catch_errors healthcheck cache authtoken keystoneauth
proxy-server
[app:proxy-server]
use = egg:swift#proxy
account_autocreate = true
[filter:keystoneauth]
use = egg:swift#keystoneauth
operator_roles = admin, swiftoperator
[filter:authtoken]
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
paste.filter_factory =
keystoneclient.middleware.auth_token:filter_factory
auth_host = keystonehost
auth_port = 35357
auth_protocol = http
auth_uri = http://keystonehost:5000/
admin_tenant_name = service
admin_user = swift
admin_password = password
[filter:cache]
use = egg:swift#memcache
set log_name = cache
[filter:catch_errors]
use = egg:swift#catch_errors
[filter:healthcheck]
use = egg:swift#healthcheck
___
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] VM does not get IP address
The other thread currently active at the moment is titled [Openstack]
VM doesnt get IP.
Aaron Rosen, Quantum core developer, is assisting a member of the
community who's apparently having exactly the same problem as you are.
Please note that 169.254.169.254 is the metadata address. In order for
metadata access to work, with the Folsom Quantum release, you also
need to create a Quantum router and connect your network to it (and,
of course, ensure the l3-agent is running with the appropriate IP and
port configured for the metadata server).
Salvatore
On 22 February 2013 19:08, Anil Vishnoi vishnoia...@gmail.com wrote:
Hi Lukas,
There few threads on openstack mailing list where people discussed this
issue. You can search with wget: can't connect to remote host
(169.254.169.254): Network is unreachable and you will see most of those
threads. These threads will give you some insight on how to debug this issue
to find the root cause. If you get stuck and have queries please feel free
to drop a mail to the list.
Anil
On Fri, Feb 22, 2013 at 2:57 PM, Lukáš Vízner lukasviz...@gmail.com wrote:
Hi,
I am following this manual
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/cbc6c95e749dea86fb4c77fcbf485e55c37a297d/OpenStack_Folsom_Install_Guide_WebVersion.rst
to install OpenStack Folsom
I have created one tenant net called net1. When I launch an
instance, there is this error:
nitializing random number generator... done.
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cloud-setup: checking
http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
cloud-setup: failed 1/30: up 10.09. request failed
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
cloud-setup: failed 2/30: up 11.10. request failed
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
Here are outputs:
root@folsom-controller:/etc/init.d# quantum net-list
+--+--+--+
| id | name | subnets
|
+--+--+--+
| 3c2eed52-969b-44a2-bd33-790999c5da5c | net1 |
a82109bf-5777-4730-b44a-5dceebc835cb |
+--+--+--+
root@folsom-controller:/etc/init.d#quantum port-list
+--+--+---+-+
| id | name | mac_address |
fixed_ips
|
+--+--+---+-+
| 0a410916-ce92-4d41-9085-1358f6493269 | | fa:16:3e:4e:d9:40 |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.2} |
| eea126e8-8661-4d55-b3e0-655d758a9203 | | fa:16:3e:ff:7e:ab |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.1} |
+--+--+---+-+
Please could you help me solve this problem?
What configuration files do you need?
Thank you!!!
--
Lukáš Vízner
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Thanks
Anil
___
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] VM does not get IP address
Hello Lukas,
We can share our problems at the same thread, i saw a post of yours there
and, apparently, we have the same problem with the VM's IP.
Regards.
Guilherme.
2013/2/22 Salvatore Orlando sorla...@nicira.com
The other thread currently active at the moment is titled [Openstack]
VM doesnt get IP.
Aaron Rosen, Quantum core developer, is assisting a member of the
community who's apparently having exactly the same problem as you are.
Please note that 169.254.169.254 is the metadata address. In order for
metadata access to work, with the Folsom Quantum release, you also
need to create a Quantum router and connect your network to it (and,
of course, ensure the l3-agent is running with the appropriate IP and
port configured for the metadata server).
Salvatore
On 22 February 2013 19:08, Anil Vishnoi vishnoia...@gmail.com wrote:
Hi Lukas,
There few threads on openstack mailing list where people discussed this
issue. You can search with wget: can't connect to remote host
(169.254.169.254): Network is unreachable and you will see most of those
threads. These threads will give you some insight on how to debug this
issue
to find the root cause. If you get stuck and have queries please feel
free
to drop a mail to the list.
Anil
On Fri, Feb 22, 2013 at 2:57 PM, Lukáš Vízner lukasviz...@gmail.com
wrote:
Hi,
I am following this manual
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/cbc6c95e749dea86fb4c77fcbf485e55c37a297d/OpenStack_Folsom_Install_Guide_WebVersion.rst
to install OpenStack Folsom
I have created one tenant net called net1. When I launch an
instance, there is this error:
nitializing random number generator... done.
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cloud-setup: checking
http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
cloud-setup: failed 1/30: up 10.09. request failed
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
cloud-setup: failed 2/30: up 11.10. request failed
wget: can't connect to remote host (169.254.169.254): Network is
unreachable
Here are outputs:
root@folsom-controller:/etc/init.d# quantum net-list
+--+--+--+
| id | name | subnets
|
+--+--+--+
| 3c2eed52-969b-44a2-bd33-790999c5da5c | net1 |
a82109bf-5777-4730-b44a-5dceebc835cb |
+--+--+--+
root@folsom-controller:/etc/init.d#quantum port-list
+--+--+---+-+
| id | name | mac_address |
fixed_ips
|
+--+--+---+-+
| 0a410916-ce92-4d41-9085-1358f6493269 | | fa:16:3e:4e:d9:40 |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.2} |
| eea126e8-8661-4d55-b3e0-655d758a9203 | | fa:16:3e:ff:7e:ab |
{subnet_id: a82109bf-5777-4730-b44a-5dceebc835cb, ip_address:
10.5.5.1} |
+--+--+---+-+
Please could you help me solve this problem?
What configuration files do you need?
Thank you!!!
--
Lukáš Vízner
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Thanks
Anil
___
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
Re: [Openstack] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Now that we are at feature freeze, is there a description of incompatible configuration or api changes that happened since Folsom? That is, a description of how deploying grizzly differs from deploying folsom. -David On 2/22/2013 7:21 AM, Thierry Carrez wrote: Martinx - ジェームズ wrote: What is the status of Openstack Grizzly-3 Ubuntu packages? Can we already set it up using apt-get / aptitude? With packaged Heat, Ceilometer and etc? Which version is recommended to test Grizzly-3, Precise (via testing UCA), Raring? Is Grizzly planed to be the default Openstack for Raring? I suspect it will take a few days for grizzly-3 to appear in Ubuntu, as the tarballs were cut a few hours ago. As far as I know, Grizzly is indeed the planned default OpenStack for Raring. ___ 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] VM doesnt get IP
Running with two nics for this should be fine for tunneling as ip routing would handle which nic the packets should go out. From what you pasted I see that one HV has a gre tunnel setup to 10.10.10.1 -- Who is that host? Can you attach your /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini on your nodes. I suspect the issue is a configuration issue in the [OVS] section. You'll need something along the lines of this in that section: [OVS] local_ip = ip address of HV enable_tunneling = True tunnel_id_ranges = 1:1000 tenant_network_type = gre On Fri, Feb 22, 2013 at 9:54 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello Aaron, Sorry about attaching the infos, about the quantum agent, is it the quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at the controller and the compute nodes: service quantum-plugin-openvswitch-agent start start: Job is already running: quantum-plugin-openvswitch-agent Is there another thing i should do? I'm running my controller node and the network node at the same machine with 2 NICs, maybe can be a problem how i am making my network config? Thanks again. Guilherme. 2013/2/22 Aaron Rosen aro...@nicira.com Hi Guilherme, (next time please paste these in the email rather than attaching, thx). From the text in the attachment (show below). It seems like you are not running the quantum-openvswitch-agent on your network node as there is no GRE tunnel from that to your compute node. Once you have quantum-openvswitch-agent running on all your machines you should be able to run ovs-dpctl looking under br-tun and see a tunnel between each host. Aaron CONTROLLER + NETWORK NODE: system@br-tun: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) system@br-int: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-int (internal) port 1: tap817d2f70-a0 (internal) port 2: qr-ea64e9aa-31 (internal) port 3: patch-tun (patch: peer=patch-int) system@br-ex: lookups: hit:0 missed:0 lost:0 flows: 0 port 0: br-ex (internal) port 2: qg-95fe3fa1-d1 (internal) COMPUTE NODES COMPUTE NODE 01: ovs-dpctl show system@br-int: lookups: hit:380 missed:7590 lost:0 flows: 0 port 0: br-int (internal) port 2: patch-tun (patch: peer=patch-int) port 3: qvo981ae82e-d4 port 6: qvoc9df3a96-5f port 7: qvoc153ac28-ae port 8: qvo722a5d05-e4 system@br-tun: lookups: hit:381 missed:7589 lost:0 flows: 0 port 0: br-tun (internal) port 1: patch-int (patch: peer=patch-tun) port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1) On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi luisguilherme...@gmail.com wrote: So guys, any idea about what am i missing? Thanks. 2013/2/22 Guilherme Russi luisguilherme...@gmail.com Hello Aaron, Here are the outputs. Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com The output to the following would be a good start: quantum net-list quantum port-list ovs-dpctl show (on all nodes) Also make sure the quantum-dhcp-agent is running on your network node. Aaron On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Sorry about that, I'm using Folsom release with quantum, I'm installing the controller node and the network node in the same physical machine, I'm following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html Which config files do you need? Thanks. Guilherme. 2013/2/21 Aaron Rosen aro...@nicira.com Hi, You'll have to provide more information than this for anyone to help you: i.e are you using quantum or nova-network, if your using quantum which plugin, config files etc. Aaron On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Hello guys, I'm getting problem in my VMs' creation, they don't get IP, the log piece shows: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40-network failed Do you have any idea how I can solve it? Thank you so much. Guilherme. ___ 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] VM doesnt get IP
Here is my controller + network node: cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini [DATABASE] # This line MUST be changed to actually run the plugin. # Example: # sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum # Replace 127.0.0.1 above with the IP address of the database used by the # main quantum server. (Leave it as is if the database runs on this host.) sql_connection = mysql://quantum:password@localhost:3306/quantum # Database reconnection retry times - in event connectivity is lost # set to -1 implies an infinite retry count # sql_max_retries = 10 # Database reconnection interval in seconds - in event connectivity is lost reconnect_interval = 2 [OVS] # (StrOpt) Type of network to allocate for tenant networks. The # default value 'local' is useful only for single-box testing and # provides no connectivity between hosts. You MUST either change this # to 'vlan' and configure network_vlan_ranges below or change this to # 'gre' and configure tunnel_id_ranges below in order for tenant # networks to provide connectivity between hosts. Set to 'none' to # disable creation of tenant networks. # # Default: tenant_network_type = local # Example: tenant_network_type = gre tenant_network_type = gre # (ListOpt) Comma-separated list of # physical_network[:vlan_min:vlan_max] tuples enumerating ranges # of VLAN IDs on named physical networks that are available for # allocation. All physical networks listed are available for flat and # VLAN provider network creation. Specified ranges of VLAN IDs are # available for tenant network allocation if tenant_network_type is # 'vlan'. If empty, only gre and local networks may be created. # # Default: network_vlan_ranges = # Example: network_vlan_ranges = physnet1:1000:2999 # (BoolOpt) Set to True in the server and the agents to enable support # for GRE networks. Requires kernel support for OVS patch ports and # GRE tunneling. # # Default: enable_tunneling = False enable_tunneling = True # (ListOpt) Comma-separated list of tun_min:tun_max tuples # enumerating ranges of GRE tunnel IDs that are available for tenant # network allocation if tenant_network_type is 'gre'. # # Default: tunnel_id_ranges = # Example: tunnel_id_ranges = 1:1000 tunnel_id_ranges = 1:1000 # Do not change this parameter unless you have a good reason to. # This is the name of the OVS integration bridge. There is one per hypervisor. # The integration bridge acts as a virtual patch bay. All VM VIFs are # attached to this bridge and then patched according to their network # connectivity. # # Default: integration_bridge = br-int integration_bridge = br-int # Only used for the agent if tunnel_id_ranges (above) is not empty for # the server. In most cases, the default value should be fine. # # Default: tunnel_bridge = br-tun tunnel_bridge = br-tun # Uncomment this line for the agent if tunnel_id_ranges (above) is not # empty for the server. Set local-ip to be the local IP address of # this hypervisor. # # Default: local_ip = local_ip = 10.10.10.1 And here is my compute node: cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini [DATABASE] # This line MUST be changed to actually run the plugin. # Example: # sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum # Replace 127.0.0.1 above with the IP address of the database used by the # main quantum server. (Leave it as is if the database runs on this host.) sql_connection = mysql://quantum:password@192.168.3.1:3306/quantum # Database reconnection retry times - in event connectivity is lost # set to -1 implies an infinite retry count # sql_max_retries = 10 # Database reconnection interval in seconds - in event connectivity is lost reconnect_interval = 2 [OVS] # (StrOpt) Type of network to allocate for tenant networks. The # default value 'local' is useful only for single-box testing and # provides no connectivity between hosts. You MUST either change this # to 'vlan' and configure network_vlan_ranges below or change this to # 'gre' and configure tunnel_id_ranges below in order for tenant # networks to provide connectivity between hosts. Set to 'none' to # disable creation of tenant networks. # # Default: tenant_network_type = local # Example: tenant_network_type = gre tenant_network_type = gre # (ListOpt) Comma-separated list of # physical_network[:vlan_min:vlan_max] tuples enumerating ranges # of VLAN IDs on named physical networks that are available for # allocation. All physical networks listed are available for flat and # VLAN provider network creation. Specified ranges of VLAN IDs are # available for tenant network allocation if tenant_network_type is # 'vlan'. If empty, only gre and local networks may be created. # # Default: network_vlan_ranges = # Example: network_vlan_ranges = physnet1:1000:2999 # (BoolOpt) Set to True in the server and the agents to enable support # for GRE networks. Requires kernel support for OVS patch ports and # GRE tunneling. # # Default: enable_tunneling = False enable_tunneling
Re: [Openstack] VM doesnt get IP
From the network+controller node can you ping to 192.168.3.3 (just to confirm there is ip connectivity between those). Your configs look fine to me. The issue you are having is that your network+controller node doesn't have a tunnel to your HV node. I'd suggest restarting the quantum-plugin-openvswitch-agent service on both nodes and see if that does the trick in order to get the agent to add the tunnel for you. Perhaps you edited this file and didn't restart the agent? Aaron On Fri, Feb 22, 2013 at 10:55 AM, Guilherme Russi luisguilherme...@gmail.com wrote: Here is my controller + network node: cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini [DATABASE] # This line MUST be changed to actually run the plugin. # Example: # sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum # Replace 127.0.0.1 above with the IP address of the database used by the # main quantum server. (Leave it as is if the database runs on this host.) sql_connection = mysql://quantum:password@localhost:3306/quantum # Database reconnection retry times - in event connectivity is lost # set to -1 implies an infinite retry count # sql_max_retries = 10 # Database reconnection interval in seconds - in event connectivity is lost reconnect_interval = 2 [OVS] # (StrOpt) Type of network to allocate for tenant networks. The # default value 'local' is useful only for single-box testing and # provides no connectivity between hosts. You MUST either change this # to 'vlan' and configure network_vlan_ranges below or change this to # 'gre' and configure tunnel_id_ranges below in order for tenant # networks to provide connectivity between hosts. Set to 'none' to # disable creation of tenant networks. # # Default: tenant_network_type = local # Example: tenant_network_type = gre tenant_network_type = gre # (ListOpt) Comma-separated list of # physical_network[:vlan_min:vlan_max] tuples enumerating ranges # of VLAN IDs on named physical networks that are available for # allocation. All physical networks listed are available for flat and # VLAN provider network creation. Specified ranges of VLAN IDs are # available for tenant network allocation if tenant_network_type is # 'vlan'. If empty, only gre and local networks may be created. # # Default: network_vlan_ranges = # Example: network_vlan_ranges = physnet1:1000:2999 # (BoolOpt) Set to True in the server and the agents to enable support # for GRE networks. Requires kernel support for OVS patch ports and # GRE tunneling. # # Default: enable_tunneling = False enable_tunneling = True # (ListOpt) Comma-separated list of tun_min:tun_max tuples # enumerating ranges of GRE tunnel IDs that are available for tenant # network allocation if tenant_network_type is 'gre'. # # Default: tunnel_id_ranges = # Example: tunnel_id_ranges = 1:1000 tunnel_id_ranges = 1:1000 # Do not change this parameter unless you have a good reason to. # This is the name of the OVS integration bridge. There is one per hypervisor. # The integration bridge acts as a virtual patch bay. All VM VIFs are # attached to this bridge and then patched according to their network # connectivity. # # Default: integration_bridge = br-int integration_bridge = br-int # Only used for the agent if tunnel_id_ranges (above) is not empty for # the server. In most cases, the default value should be fine. # # Default: tunnel_bridge = br-tun tunnel_bridge = br-tun # Uncomment this line for the agent if tunnel_id_ranges (above) is not # empty for the server. Set local-ip to be the local IP address of # this hypervisor. # # Default: local_ip = local_ip = 10.10.10.1 And here is my compute node: cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini [DATABASE] # This line MUST be changed to actually run the plugin. # Example: # sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum # Replace 127.0.0.1 above with the IP address of the database used by the # main quantum server. (Leave it as is if the database runs on this host.) sql_connection = mysql://quantum:password@192.168.3.1:3306/quantum # Database reconnection retry times - in event connectivity is lost # set to -1 implies an infinite retry count # sql_max_retries = 10 # Database reconnection interval in seconds - in event connectivity is lost reconnect_interval = 2 [OVS] # (StrOpt) Type of network to allocate for tenant networks. The # default value 'local' is useful only for single-box testing and # provides no connectivity between hosts. You MUST either change this # to 'vlan' and configure network_vlan_ranges below or change this to # 'gre' and configure tunnel_id_ranges below in order for tenant # networks to provide connectivity between hosts. Set to 'none' to # disable creation of tenant networks. # # Default: tenant_network_type = local # Example: tenant_network_type = gre tenant_network_type = gre # (ListOpt) Comma-separated list of #
Re: [Openstack] [Keystone]Question: Assignment of default role
Yes, this is new. We are removing the direct associtation between users and projects (Project members) and replacing it with a Role (_member_) The _ is there to ensure it does not conflict with existing roles. The two different ways of associating users to projects was causing problems. With RBAC, we can now enforce policy about project membership that we could not do before. On 02/21/2013 09:39 PM, Leo Toyoda wrote: Hi, everyone I'm using the master branch devstack. I hava a question about assignment of default role (Keystone). When I create a user to specify the tenant, '_member_' is assigned to the roles. $ keystone user-create --name test --tenant-id e61..7f6 --pass test --email t...@example.com +--+---+ | Property | Value| +--+---+ | email | te...@example.com | | enabled | True| |id| af1..8d2 | | name | test| | tenantId | e61..7f6 | +--+---+ $ keystone user-role-list --user test --tenant e61..7f6 +--+--+--+---+ |id| name | user_id | tenant_id | +--+--+--+---+ | 9fe..bab | _member_ | af1..8d2 | e61..7f6 | +--+--+--+---+ Then, assign the Member role to the user. Hitting assigned two roles of 'Member' and '_member_'. $ keystone user-role-add --user af1..8d2 --role 57d..d1f --tenant e61..7f6 $ keystone user-role-list --user af1..8d2 --tenant e61..7f6 +--+--+--+---+ |id| name | user_id | tenant_id | +--+--+--+---+ | 57d..d1f | Member | af1..8d2 | e61..7f6 | | 9fe..bab | _member_ | af1..8d2 | e61..7f6 | +--+--+--+---+ When I create a user without specifying a tenant, I assign 'Member' role. In this case, Only one role is assigned. $ keystone user-create --name test2 --pass test --email te...@example.com +--+---+ | Property | Value| +--+---+ | email | te...@example.com | | enabled | True | |id|c22..a6d | | name | test2| | tenantId | | +--+---+ $ keystone user-role-add --user c22..a6d --role 57d..d1f --tenant e61..7f6 $ keystone user-role-list --user c22..a6d --tenant e61..7f6 +--+--+--+---+ |id| name | user_id | tenant_id | +--+--+--+---+ | 57d..d1f | Member | c22..a6d | e61..7f6 | +--+--+--+---+ Is it expected behavior that two rolls are assigned? Thanks Leo Toyoda ___ 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] OpenStack Community Weekly Newsletter (Feb 15 – 22)
Highlights of the week Important CLA changes coming this weekend http://markmail.org/message/azrdwianmnt2j5oc Starting on February 24, 2013 all contributors MUST review and agree to the new OpenStack Individual Contributor License Agreement and provide updated contact information at https://review.openstack.org/#/settings/agreements. On that day the Gerrit interface will be changing to present the new CLA text referring to the OpenStack Foundation, and will prompt you to agree to it there. Any previous agreement with OpenStack LLC will be marked expired at that time. The text of the new agreement is available for your convenience https://review.openstack.org/static/cla.html (changes “LLC” to “Foundation”, restores a sentence from ASF https://review.openstack.org/#/c/22396/2/modules/openstack_project/files/gerrit/cla.html and corrects a few typographical errors). You must also sign up for an OpenStack Foundation Individual Membership with the same E-mail address as used for your Gerrit contact information: http://openstack.org/register/. OpenStack outpaces Amazon, at least by hype http://www.mirantis.com/blog/openstack-outpaces-amazon-at-least-by-hype/ A study conducted by TrendKite shows that at this point OpenStack has more media mentions than Amazon EC2, Eucalyptus, CloudStack and OpenNebula combined. If that is not enough, another chart from the same study appears to show that “OpenStack” media mentions are on par with that of “Cloud Computing.” CloudEnvy: Development in the cloud! http://jake.ai/cloudenvy-development-in-the-cloud Jake Dahn is working on a project called CloudEnvy which has potential to change the development patterns of web developers everywhere: it allows you to configure and distribute reproducible development environments in the cloud. Bring on the Crazy: Zero to Book in Five Days http://www.openstack.org/blog/2013/02/bring-on-the-crazy-zero-to-book-in-five-days/ Anne Gentle is leading a “crazy” project: a large, highly focused documentation sprint to write that operator’s guide — for operators by operators. Anne promised to pluck operators out of their day jobs, put them in a room, fuel them with coffee, BBQ, and TexMex, and get to writing. Sounds awesome to me: I’m voting for their panel On Writing the OpenStack Operations Manual in 5 Days http://www.openstack.org/summit/portland-2013/vote-for-speakers/presentation/444 at the upcoming OpenStack Summit. The OpenStack Gate http://dague.net/2013/02/21/the-openstack-gate/ The OpenStack project has a really impressive continuous integration system, which is one of its core strengths as a project. Every proposed change to our gerrit review https://review.openstack.org/#/ system is subjected to a battery of tests on each commit, which has grown dramatically with time, and after formal review by core contributors, we run them all again before the merge. How can this gate merge hundreds of changes per day? Learn about Zuul, the OpenStack gatekeeper. Security Advisories * OSSA 2013-005] Keystone EC2-style authentication accepts disabled user/tenants (CVE-2013-0282) http://lists.openstack.org/pipermail/openstack-announce/2013-February/79.html * OSSA 2013-004] Information leak and Denial of Service using XML entities (CVE-2013-1664, CVE-2013-1665) http://lists.openstack.org/pipermail/openstack-announce/2013-February/78.html Tips and Tricks * By Victoria Martínez de la Cruz http://vmartinezdelacruz.com/: How to work with blueprints without losing your mind http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/ * By Anita Kuno http://anteaya.info/: OpenStack Release Cycle – n00b’s Eyeview http://anteaya.info/blog/2013/02/20/openstack-release-cycle-n00bs-eyeview/ * By Daniel P. Berrangé https://www.berrange.com/: A reminder why you should never mount guest disk images on the host OS https://www.berrange.com/posts/2013/02/20/a-reminder-why-you-should-never-mount-guest-disk-images-on-the-host-os/ * By Everett Toews http://blog.phymata.com/: Swift Only with OpenStack DevStack on the Rackspace Cloud http://blog.phymata.com/2013/02/18/swift-only-with-openstack-devstack-on-the-rackspace-cloud/ * By Laura Alves http://ladquin.dreamwidth.org/: Doc for code and Doc as code – Part I http://ladquin.dreamwidth.org/1207.html * By Russell Bryant http://russellbryantnet.wordpress.com/: Deployment Considerations for nova-conductor Service in OpenStack Grizzly http://russellbryantnet.wordpress.com/2013/02/19/deployment-considerations-for-nova-conductor-service-in-openstack-grizzly/ * By Sébastien Han http://sebastien-han.fr/:override DHCP information sent by DNSMASQ to a VM http://sebastien-han.fr/blog/2013/02/18/openstack-override-dhcp-information-send-by-dnsmasq-to-the-vm/ Upcoming Events * SCALE 11x
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #51
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/51/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 02:45:26 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13169 lines...]INFO:root:Setting up connection to test-09.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #52
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/52/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 08:45:46 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13169 lines...]INFO:root:Setting up connection to test-07.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_cinder_trunk #184
Title: raring_grizzly_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/184/Project:raring_grizzly_cinder_trunkDate of build:Fri, 22 Feb 2013 14:19:24 -0500Build duration:5 min 11 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 7130 lines...]Finished at 20130222-1424Build needed 00:02:30, 37848k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpnoM_sW/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpnoM_sW/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 716b67f4790774858ccc9d4b696ac12f7e793b0b..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [b138481] Fixed cinder-backup start errors seen with devstackdch -a [762f2e1] Cinder devref doc cleanupsdch -a [c3c31fc] Fix various exception pathsdch -a [6670314] Implement metadata options for snapshotsdch -a [8169eb6] Skip timestamp check if 'capabilities' is nonedch -a [f7bcf95] Fix stale volume list for NetApp 7-mode ISCSI driverdch -a [f50c8cb] Implement a basic backup-volume-to-swift servicedch -a [217e194] Moved cinder_emc_config.xml.sample to emc folderdch -a [d2742e1] Uses tempdir module to create/delete xml filedch -a [74d1add] Add HUAWEI volume driver in Cinderdch -a [f2ce698] XenAPINFS: Create volume from image (generic)dch -a [ea2c405] Bump the oslo-config version to address issues.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A cinder_2013.1.a5.g64ee4ac+git201302221419~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', 'cinder_2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error 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', 'cinder_2013.1.a5.g64ee4ac+git201302221419~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build 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_deploy #53
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/53/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 14:15:54 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13135 lines...]INFO:root:Setting up connection to test-04.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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 Fixed: precise_grizzly_glance_trunk #135
Title: precise_grizzly_glance_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/135/Project:precise_grizzly_glance_trunkDate of build:Fri, 22 Feb 2013 15:01:13 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesDocument db_auto_create in default config filesby paul-david.bourkeeditetc/glance-api.confeditetc/glance-registry.confeditdoc/source/configuring.rstRemove compat cfg wrapperby markmceditglance/db/sqlalchemy/api.pydeleteglance/openstack/common/cfg.pyConsole Output[...truncated 7462 lines...] Uploading glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1.debian.tar.gz: done. Uploading glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_amd64.changes']Skipping inclusion of 'glance-registry' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Skipping inclusion of 'glance-api' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Skipping inclusion of 'glance-common' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Skipping inclusion of 'python-glance-doc' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Skipping inclusion of 'glance' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Skipping inclusion of 'python-glance' '2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1' in 'precise-grizzly|main|amd64', as it has already '2013.1.a127.gce8dadf+git201302211401~precise-0ubuntu1'.Deleting files just added to the pool but not used.(to avoid use --keepunusednewfiles next time)deleting and forgetting pool/main/g/glance/glance-api_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/precise-grizzly']Pushed up to revision 238.1 tag updated.INFO:root:Storing current commit for next build: dbecc93705dd0ecb05e5189f34d89ee19000aafcINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpMWujP7/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpMWujP7/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log a12e81d5b40a725168b1012b22a72f3fa873fe97..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [dbecc93] Remove compat cfg wrapperdch -a [fe0c2d2] Document db_auto_create in default config filesdch -a [b0b380f] Add migration 20 - drop images.locationdch -a [fd9d069] Add migration 19 - move image location datadch -a [780a1c7] Update oslo-config version.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly glance_2013.1.a11.g253fb52+git201302221501~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list:
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #54
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/54/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 17:17:54 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13148 lines...]INFO:root:Setting up connection to test-09.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #55
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/55/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 18:15:56 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13304 lines...]INFO:root:Setting up connection to test-08.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #56
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/56/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 19:02:36 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13135 lines...]INFO:root:Setting up connection to test-10.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_glance_trunk #136
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/136/Project:precise_grizzly_glance_trunkDate of build:Fri, 22 Feb 2013 20:01:11 -0500Build duration:9 min 43 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse more-specific value for X-Object-Manifest header.by sameditglance/store/swift.pyConsole Output[...truncated 5952 lines...]Distribution: precise-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 40Job: glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 498Source-Version: 2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1Space: 23604Status: attemptedVersion: 2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1Finished at 20130222-2010Build needed 00:08:18, 23604k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpGMq22U/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpGMq22U/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a13.g19aecaf+git20130001~precise-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', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error 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', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build 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_glance_trunk #151
Title: raring_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/151/Project:raring_grizzly_glance_trunkDate of build:Fri, 22 Feb 2013 20:01:11 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse more-specific value for X-Object-Manifest header.by sameditglance/store/swift.pyConsole Output[...truncated 7128 lines...]Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 36Job: glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 700Source-Version: 2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1Space: 23596Status: attemptedVersion: 2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1Finished at 20130222-2015Build needed 00:11:40, 23596k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpm7oGxv/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpm7oGxv/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1.a13.g19aecaf+git20130001~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', 'glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error 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', 'glance_2013.1.a13.g19aecaf+git20130001~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build 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_glance_trunk #137
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/137/Project:precise_grizzly_glance_trunkDate of build:Fri, 22 Feb 2013 21:31:15 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesFix migration 015 downgrade with sqlite.by treinisheditglance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.pyRemove unnecessary logging from migration 019by treinisheditglance/db/sqlalchemy/migrate_repo/versions/019_migrate_image_locations.pyConsole Output[...truncated 5952 lines...]Distribution: precise-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 35Job: glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 516Source-Version: 2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1Space: 23600Status: attemptedVersion: 2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1Finished at 20130222-2141Build needed 00:08:36, 23600k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmp3J9T0D/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp3J9T0D/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a17.g1c83f8a+git20130131~precise-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', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error 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', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build 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_glance_trunk #152
Title: raring_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/152/Project:raring_grizzly_glance_trunkDate of build:Fri, 22 Feb 2013 21:31:09 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFix migration 015 downgrade with sqlite.by treinisheditglance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.pyRemove unnecessary logging from migration 019by treinisheditglance/db/sqlalchemy/migrate_repo/versions/019_migrate_image_locations.pyConsole Output[...truncated 7083 lines...]Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 35Job: glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 747Source-Version: 2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1Space: 23600Status: attemptedVersion: 2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1Finished at 20130222-2146Build needed 00:12:27, 23600k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpnQ5sa5/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpnQ5sa5/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1.a17.g1c83f8a+git20130131~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', 'glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error 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', 'glance_2013.1.a17.g1c83f8a+git20130131~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build 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_deploy #57
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/57/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 21:18:13 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13344 lines...]INFO:root:Setting up connection to test-04.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #58
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/58/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 22:45:14 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13342 lines...]INFO:root:Setting up connection to test-09.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #59
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/59/Project:raring_grizzly_deployDate of build:Fri, 22 Feb 2013 23:31:55 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13098 lines...]INFO:root:Setting up connection to test-09.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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
