[Openstack] Heat templates and Quantum resources

2013-02-05 Thread Simon Pasquier
Hi all, I have some questions regarding the integration of Quantum in Heat: - I haven't found a way to attach an instance resource to a Quantum port that already exists. Is it possible? - When I create a Quantum port in my template and binds the instance to that port, why does Heat still create

[Openstack] [Nova] Unable to start nova-api

2013-02-05 Thread Trinath Somanchi
Hi- When I start the nova-api service, I’m getting this error: Can anyone help me troubleshoot the issue root@NewFolsomController:/etc/nova# nova-api --flagfile=/etc/nova/nova.conf 2013-02-05 12:29:29 DEBUG nova.utils [-] Inner Exception: No module named api from (pid=19874)

Re: [Openstack] [Nova] Unable to start nova-api

2013-02-05 Thread Unmesh Gurjar
Trinath, You probably have a wrong config setting. Please check the value of 'network_api_class' in your nova.conf and confirm that the module with the specified class exists. The default value of this parameter is nova.network.api.API, so you should expect class 'API' in nova/network/api.py of

Re: [Openstack] [Nova] Unable to start nova-api

2013-02-05 Thread Trinath Somanchi
Hi- Thanks a lot for the reply. it solved the issue. On Tue, Feb 5, 2013 at 3:47 PM, Unmesh Gurjar unmesh.gur...@gmail.comwrote: Trinath, You probably have a wrong config setting. Please check the value of 'network_api_class' in your nova.conf and confirm that the module with the

[Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Hello friends, I am getting problem when I try to start a VM, it keeps ate Scheduling task and doesn't start the VM. It is happining after I made a apt-get update and apt-get upgrade. I really don't know what to do, anybody can help me, please? Thank you. Guilherme.

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Ronivon Costa
Have you looked the compute.log file? You should really start from there. :D Also, if you really expect some help, you must provide some information. Search in the logs for clues, and if it can't help or you don't understand what you see, then send it along as well. Roni. No dia 5 de Fev de 2013

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Hello Roni, thank you for returning, I don't understand the logs yet, I'm working with that, but here is a piece of my nova-compute.log: 2013-02-05 10:11:07 11592 DEBUG nova.utils [-] Got semaphore compute_resources for method update_available_resource... inner

[Openstack] [OpenStack] Keystone did not start - DevStack Installation

2013-02-05 Thread Antonio Tirri
Hi all, actually i'm trying to install OpenStack through DevStack script. Unfortunately the installation is not successful because the keystone service doesn't start. This is the log of the script: 2013-02-05 13:19:05 + SCREEN_NAME=stack 2013-02-05 13:19:05 +

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Ronivon Costa
Your logs contain no useful information related to your problem. You should send the piece of log that contains the information generated when you launched the vm. ___ Mailing list: https://launchpad.net/~openstack Post to :

[Openstack] Provider network problems

2013-02-05 Thread tra26
Third time is a charm, but is there a better list for these types of questions? I am trying to get multiple public ips working, I've tried multiple vifs but got stuck so I switched to possibly using a provider network and just patching the vms to the physical network

Re: [Openstack] NFS + RDMA == stuck at Booting from hard disk

2013-02-05 Thread Mark Lehrer
Has anyone here been able to make Openstack + KVM work with Infiniband NFS-RDMA? I finally found the solution to this and wanted to pass it along. RDMA does not work with cache=none. There is an auto-detect routine deep within the python code that is supposed to switch this to writeback,

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Pranav
I believe that you have broken your configuration files. Please do make sure that your nova confi files are proper. I had similar issue where in i had to change the libvirt option to QEMU because some KVM issue and the images started spawning. ___

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
I found a solution, I guess, well, I droped the tables from quantum and create a network range again, and it worked again. Now I'm trying to figure out how to insert a floating IP to ssh and ping in my VMs. Do you have any ideas? I can login in the VM, but when I type sudo ifconfig -a it has no

Re: [Openstack] [OpenStack] Keystone did not start - DevStack Installation

2013-02-05 Thread Adam Young
On 02/05/2013 08:00 AM, Antonio Tirri wrote: Hi all, actually i'm trying to install OpenStack through DevStack script. Unfortunately the installation is not successful because the keystone service doesn't start. This is the log of the script: 2013-02-05 13:19:05 + SCREEN_NAME=stack

[Openstack] [OSSA 2013-003] Keystone denial of service through invalid token requests (CVE-2013-0247)

2013-02-05 Thread Thierry Carrez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenStack Security Advisory: 2013-003 CVE: CVE-2013-0247 Date: February 5, 2013 Title: Keystone denial of service through invalid token requests Reporter: Dan Prince (Red Hat) Products: Keystone Affects: All versions Description: Dan Prince of Red

Re: [Openstack] [OpenStack] Keystone did not start - DevStack Installation

2013-02-05 Thread Antonio Tirri
Hi Adam, thanks for your answer. First of all, the full log of my script is here www.forumaltavilla.it/joomla/Documenti/log_devstack.txt It seems that there are some problems in managing user permissions. Even if I included the stack user in /etc/sudoers adding the following line stack

[Openstack] Unable to start swift proxy service

2013-02-05 Thread Guillaume Hilt
Hello, I installed swift on Ubuntu 12.04 AMD64 following this howto: http://docs.openstack.org/developer/swift/howto_installmultinode.html However, although the storage nodes work fine, I can't start the proxy node : Feb 5 18:00:06 srv13 proxy-server UNCAUGHT EXCEPTION Traceback (most recent

Re: [Openstack] [OpenStack] Keystone did not start - DevStack Installation

2013-02-05 Thread Adam Young
You probably created /opt/stack/keystone/keystone.log as root at one point. Either delete it, or chown it to the stack user. On 02/05/2013 12:05 PM, Antonio Tirri wrote: Hi Adam, thanks for your answer. First of all, the full log of my script is here

[Openstack] Help with VMs

2013-02-05 Thread Harvey West
Not used openstack or this email forum before. Have installed openstack on unbuntu 12.4.1 LTS. Seems to work with the default  unbuntu VM image. How do I create a new image. I would to create a FreeBSS VM instance. Is this possible? Harvey___ Mailing

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Guys, I'm trying to create the network to connect my VMs, but they don't receive the IP, my network configs in the controller node is: # eth1 - link external with the internet address 10.3.77.51 # eth0 - link internal to connect the compute nodes address 192.168.3.1 And

Re: [Openstack] Unable to start swift proxy service

2013-02-05 Thread Samuel Merritt
On 2/5/13 9:04 AM, Guillaume Hilt wrote: Hello, I installed swift on Ubuntu 12.04 AMD64 following this howto: http://docs.openstack.org/developer/swift/howto_installmultinode.html However, although the storage nodes work fine, I can't start the proxy node : Feb 5 18:00:06 srv13 proxy-server

Re: [Openstack] Help with VMs

2013-02-05 Thread Lloyd Dewolf
On Tue, Feb 5, 2013 at 10:19 AM, Harvey West harvey.w...@btinternet.comwrote: Not used openstack or this email forum before. Have installed openstack on unbuntu 12.4.1 LTS. Seems to work with the default unbuntu VM image. How do I create a new image. I would to create a FreeBSS VM instance.

Re: [Openstack] Heat templates and Quantum resources

2013-02-05 Thread Steve Baker
Hi Simon There is an existing Launchpad bug for this issue: https://bugs.launchpad.net/heat/+bug/1096013 I've added your email to the comments. I'll most likely be working on this area next so I'll let you know when there is a change in the current behavior. cheers On 02/05/2013 10:40 PM,

[Openstack] How the linux bridge work in Quantum

2013-02-05 Thread Lei Zhang
Hi all, I am learning the Quantum project. But I am confused about the whole architecture. Is there any article to explain how the package flow in the network model, which will help me to debug the network issue. For example, how the ping package flow from the VMs to the external internet? --

Re: [Openstack] How the linux bridge work in Quantum

2013-02-05 Thread Lei Zhang
Directly, here is the issue I meet. I start a all-in-one openstack Folsom with Quantum network( using linux bridge plugin) - First I can not ping outside of the host. Following is the network setting. I think this should be work. But I can ping 10.10.0.1(gate way) in the host -

Re: [Openstack] How the linux bridge work in Quantum

2013-02-05 Thread Lei Zhang
I am following the steps from http://d.hatena.ne.jp/enakai00/20121118/1353226066 On Wed, Feb 6, 2013 at 2:36 PM, Lei Zhang zhang.lei@gmail.com wrote: Directly, here is the issue I meet. I start a all-in-one openstack Folsom with Quantum network( using linux bridge plugin) - First

[Openstack] [Quantum] Unable to install Quantum DHCP and L3 agents

2013-02-05 Thread Trinath Somanchi
Hi- When I install Quantum DHCP and L3 agents. I get this error root@NewFolsomController:~# apt-get install quantum-plugin-openvswitch-agent quantum-dhcp-agent quantum-l3-agent Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package

Re: [Openstack] [Quantum] Unable to install Quantum DHCP and L3 agents

2013-02-05 Thread Veera Reddy
Hi Trinath, Before installing folsom To Below Step Edit */etc/apt/sources.list.d/cloud-archive.list *: deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main Upgrade the system (and reboot if you need) : apt-get update apt-get upgrade Regards, Veera. On Wed,

Re: [Openstack] [Quantum] Unable to install Quantum DHCP and L3 agents

2013-02-05 Thread Martinx - ジェームズ
Before run apt-get update, run apt-get install ubuntu-cloud-keyring On 6 February 2013 05:06, Veera Reddy veerare...@gmail.com wrote: Hi Trinath, Before installing folsom To Below Step Edit */etc/apt/sources.list.d/cloud-archive.list *: deb

Re: [Openstack] [Quantum] Unable to install Quantum DHCP and L3 agents

2013-02-05 Thread Atul Jha
Trinath snip Hi- When I install Quantum DHCP and L3 agents. I get this error root@NewFolsomController:~# apt-get install quantum-plugin-openvswitch-agent quantum-dhcp-agent quantum-l3-agent Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_keystone_trunk #116

2013-02-05 Thread openstack-testing-bot
at 20130205

[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_quantum_trunk #264

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/264/Project:precise_grizzly_quantum_trunkDate of build:Tue, 05 Feb 2013 08:01:10 -0500Build duration:1 min 19 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_quantum_trunk #271

2013-02-05 Thread openstack-testing-bot
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/271/Project:raring_grizzly_quantum_trunkDate of build:Tue, 05 Feb 2013 08:01:10 -0500Build duration:2 min 33 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_nova_trunk #610

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/610/Project:precise_grizzly_nova_trunkDate of build:Tue, 05 Feb 2013 08:01:11 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_ceilometer_trunk #71

2013-02-05 Thread openstack-testing-bot
at 20130205

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_ceilometer_trunk #75

2013-02-05 Thread openstack-testing-bot
at 20130205

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_ceilometer_trunk #72

2013-02-05 Thread openstack-testing-bot
/pollsters.pyedittests/image/test_glance.pyedittests/network/test_floatingip.pyedittests/energy/test_kwapi.pyConsole Output[...truncated 2010 lines...]Finished at 20130205-0902Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_ceilometer_trunk #76

2013-02-05 Thread openstack-testing-bot
/swift.pyeditceilometer/energy/kwapi.pyedittests/energy/test_kwapi.pyeditceilometer/image/glance.pyConsole Output[...truncated 2578 lines...]Finished at 20130205-0903Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_ceilometer_trunk #77

2013-02-05 Thread openstack-testing-bot
Title: raring_grizzly_ceilometer_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/77/Project:raring_grizzly_ceilometer_trunkDate of build:Tue, 05 Feb 2013 09:31:12 -0500Build duration:3 min 10 secBuild cause:Started by an SCM

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_ceilometer_trunk #74

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_ceilometer_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/74/Project:precise_grizzly_ceilometer_trunkDate of build:Tue, 05 Feb 2013 12:01:10 -0500Build duration:6 min 6 secBuild cause:Started by an SCM

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_python-novaclient_trunk #54

2013-02-05 Thread openstack-testing-bot
at 20130205

[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_python-keystoneclient_trunk #64

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_python-keystoneclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/64/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Tue, 05 Feb 2013 16:01:08 -0500Build duration:1 min 12

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_glance_trunk #102

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_glance_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/102/Project:precise_grizzly_glance_trunkDate of build:Tue, 05 Feb 2013 17:01:09 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7168

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7168/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7169

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7169/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7170

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7170/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7171

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7171/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7172

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7172/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7173

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7173/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7174

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7174/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7177

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7177/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7179

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7179/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7180

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7180/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: folsom_coverage #429

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/folsom_coverage/429/ -- Started by command line by jenkins Building on master in workspace http://10.189.74.7:8080/job/folsom_coverage/ws/ No emails were triggered. [workspace] $ /bin/bash -x

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7182

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7182/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7183

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7183/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7184

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7184/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7185

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7185/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_ceilometer_trunk #75

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_ceilometer_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/75/Project:precise_grizzly_ceilometer_trunkDate of build:Tue, 05 Feb 2013 21:32:23 -0500Build duration:3 min 22 secBuild cause:Started by an SCM

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_ceilometer_trunk #79

2013-02-05 Thread openstack-testing-bot
Title: raring_grizzly_ceilometer_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/79/Project:raring_grizzly_ceilometer_trunkDate of build:Tue, 05 Feb 2013 21:31:09 -0500Build duration:5 min 40 secBuild cause:Started by an SCM

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_quantum_trunk #273

2013-02-05 Thread openstack-testing-bot
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/273/Project:raring_grizzly_quantum_trunkDate of build:Tue, 05 Feb 2013 22:05:34 -0500Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7188

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7188/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7189

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7189/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Jenkins build is back to normal : folsom_coverage #430

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/folsom_coverage/430/ -- 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 :

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7191

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7191/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7192

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7192/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7193

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7193/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #267

2013-02-05 Thread openstack-testing-bot
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/267/Project:precise_grizzly_quantum_trunkDate of build:Tue, 05 Feb 2013 23:31:10 -0500Build duration:1 min 21 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_quantum_trunk #274

2013-02-05 Thread openstack-testing-bot
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/274/Project:raring_grizzly_quantum_trunkDate of build:Tue, 05 Feb 2013 23:31:10 -0500Build duration:2 min 22 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7194

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7194/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7195

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7195/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7197

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7197/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7198

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7198/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7199

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7199/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7200

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7200/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7201

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7201/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7202

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7202/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7203

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7203/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7205

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7205/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #7206

2013-02-05 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/7206/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash