Hi Filipe,
OpenvSwitch module is properly loaded in the kernel.
I was able to create bridges. I now have problems in
creating private networks using Quantum CLI.
( This has been posted in another thread to the list )
Thank you,
On Thu, May 9, 2013 at 3:35 AM, Filipe Manco filipe.ma...@gmail.com
Hi Ashutosh,
In reply to your query on Quantum CLI errors on Grizzly
I have similar error when running quantum net-create private as per step
13.1 Create a private network according to
https://fedoraproject.org/wiki/Packstack_to_Quantum
My System information:
RHEL 6.4
Installation done
Hi Kamarul,
Thanks for the response. It helped me resolve the issue.
On Thu, May 9, 2013 at 11:52 AM, Kamarul profkama...@gmail.com wrote:
Hi Ashutosh,
In reply to your query on Quantum CLI errors on Grizzly
I have similar error when running quantum net-create private as per step
13.1
Hi folks,
Am all set to launch an instance after getting good
response from this mailing list for most of my queries.
I am now facing issues in creating volumes from the
dashboard. Here is volume log file for reference :
2013-05-09 15:24:49ERROR [cinder.service] Unhandled exception
Traceback
Does pvscan show any disks assigned to the cinder-volumes volume group on any
of your cinder nodes? That's the default volume group used for new volume
creation.
From: Openstack
[mailto:openstack-bounces+eric_e_smith=dell@lists.launchpad.net] On Behalf
Of Ashutosh Narayan
Sent: Thursday,
Hi Eric,
Output of *pvscan *throws - No matching physical volumes found
Where else can I see ?
On Thu, May 9, 2013 at 3:40 PM, eric_e_sm...@dell.com wrote:
Does pvscan show any disks assigned to the “cinder-volumes” volume group
on any of your cinder nodes? That’s the default volume group
If you have a disk or partition that you can use to create that volume group
then it might very well start working.
From: Ashutosh Narayan [mailto:aashutoshnara...@gmail.com]
Sent: Thursday, May 09, 2013 5:20 AM
To: Smith, Eric E
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack]
Hi all,
I've managed to install OpenStack (Version 2012.1.1-18) on top of a
XenServer installation. Instances are created fine, but it takes really
long for Openstack to realize that the instance is up and running. In the
nova-compute.log I see the following messages:
2013-05-09 05:19:47
Hi,
We are working on essex version of Openstack.
We are using Vlan Manager as the network manager. The instances booted get the
compute node IP as the gateway.
We have tried giving specific gateway IP(using --gateway option) during vlan
creation, but it was not successful. The instances
Hi Eric,
Yes, I was able to create volumes after adding a new disk to the instance.
I then created a physical volume followed by volume group and all went fine
after that.
Thank you,
On Thu, May 9, 2013 at 3:55 PM, eric_e_sm...@dell.com wrote:
If you have a disk or partition that you can use
Hi Gonzalo,
The agent referred to here is the Rackspace-supplied agents that can be
installed in images, so are present when they are booted and you do not suffer
this timeout. I believe these are currently available from
https://github.com/rackerlabs/openstack-guest-agents-unix and
Hi Folks,
All set but am not able to boot the instance from dashboard.
*Environment details:*
I have installed CentOS 6.3 as a VM on Xen Server 6.0.2 and
it's on this CentOS VM I have installed Grizzly.
Is there any issue with the driver that am using in nova.conf
which is effecting this
Hi Ashutosh,
The problem appears to be - as you suggested - that you're using the libvirt
driver when you're running on XenServer.
Have a look at
http://docs.openstack.org/trunk/openstack-compute/admin/content/introduction-to-xen.html
and set the compute_driver and supporting values as
Hi Bob,
thanks a lot for your answer, but neither of the solutions worked for
me.
The Rackspace-supplied agent latest version simply refuses to install
on Ubuntu 13.03 and Debian 7.0. I will ask the rackerlabs people about it
with a detailed description of my errors, but it doesn't seem
Hi Gonzalo,
My apologies - I made a mistake when copy/pasting the key. I hope that adding
the key didn't make any difference?
The key should be using underscores, not hyphens: xenapi_disable_agent=True
I raised https://bugs.launchpad.net/nova/+bug/1178223 as a bug to fix the
default value.
Hi Bob,
Still nothing :(
I've changed the nova.conf file to reflect the new key:
xenapi_disable_agent=True
but still doesn't work. I keep getting the timeout error messages in
the nova-compute.log and the dashboard keeps showing the 'Spawning' message
much longer than it should.
Hi Gonzalo,
That's very strange. We've checked the code and have confirmed it should be
responding to this config value as described. We've also got several test
scenarios that do not have the agent installed that are not suffering from this
- although there may be another configuration
Hi Bob,
well, it seems to me that the openstack version shipped with Debian 7.0
wheezy (2012.1.1) does not include that config key.
I've made the change myself in the vmops.py file to ignore all the
logic regarding the agent. I've created a patch in case somebody with the
same debian
A - understood. I now see the changes - sorry I had assumed that the
config key I was talking about was present in the version of the code you are
running.
You could also achieve a similar result to reduce the timeout waiting for the
agent by setting agent_version_timeout to a value lower
Thanks, Anne and Gabriel. So I believe, if we develop something based on
Identity v2.0 API then it will also support Identity v3.0, please
correct me if I am wrong.
Thanks,
Devendra Gupta
On 09-May-13 5:27 AM, Gabriel Hurley wrote:
In Grizzly I can send Keystone requests to either
On Wed, May 8, 2013 at 6:57 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote:
In Grizzly I can send Keystone requests to either *http://keyston**
e_host:5000/v2.0/* or to *http://keystone_host:5000/v3/* and both work
just fine (provided I send the right request). Both APIs are enabled, and
Hi guys,
We need to schedule our trips and get our budgets ready for the next
summit, and we wanted to know if its going to happen finally on Hong Kong,
dates, city and location if its already defined, we really dont want to
miss it !
Thanks in advance
Lean
Mercadolibre cloudbuilders
Hi,
Snip
Hi guys,
We need to schedule our trips and get our budgets ready for the next summit,
and we wanted to know if its going to happen finally on Hong Kong, dates, city
and location if its already defined, we really dont want to miss it !
Thanks in advance
Lean
Mercadolibre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenStack Security Advisory: 2013-010
CVE: CVE-2013-2030
Date: May 9, 2013
Title: Nova uses insecure keystone middleware tmpdir by default
Reporter: Grant Murphy (Red Hat), Anton Lundin
Products: Nova
Affects: Folsom, Grizzly
Description:
Grant
That's not entirely the case - the API structure has changed rather
significantly (mostly made more consistent and unified), so API calls to V2 may
or may not match entirely with API calls to V3. We did go to the trouble of
writing a very thorough spec, and then checking and updating it as we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenStack Security Advisory: 2013-011
CVE: CVE-2013-2059
Date: May 9, 2013
Title: Keystone tokens not immediately invalidated when user is deleted
Reporter: Sam Stoelinga
Products: Keystone
Affects: All versions
Description:
Sam Stoelinga reported
Hi guys,
I'm having an issue deploying a vm to a hyper-v host, i wont boot
note: the disk_image itself was built by that very hyperv host
I'm currently using openstack (devstack) build grizzly
within a Ubuntu 12.04 LTS.
And my HyperV has got the Hyper-V Nova-Compute Driver
please, check it
Hi Chuan,
Did you manage to resolve the following issue?
init: Unable to create device: /dev/kmsg
I'm having a similar problem while running LXC on Folsom.
https://lists.launchpad.net/openstack/msg23438.html
Thanks and Regards,
Shashank Sahni
___
I am seeing this email after a long time. Quite recently I tried installing
Grizzly on Ubuntu 13.04 on x86 64 machine. It installed fine except that i
am facing some network configuration issues after the VMs start running.
On Fri, Apr 26, 2013 at 12:05 AM, skible.openst...@gmail.com
By the way,
I forgot to mention that the disk_image was originally created by HyperV 2008 R2
in a VHDX format.
And when I uploaded it with *glance image-create*, i set it up for the
format as vhd
and the container as bare.
I also noticed that after the nova boot deployed the disk image to
the
AS the official translation of the citiy names are Yichang and Yili, we
are facing a risk to pick up a Chinese city name that most Chinese won't
recognize.
If we really have to choose a city, IMO, Yichang (ichang) would be a
better choice, as the Yili(ili) is more than 2300 miles away from
Hi Shashank,
If you mean running VNC in LXC,
it seems that currently there is some issue between VNC and LXC.
What I did is login to LXC through ssh.
Sincerely,
Hsiao
On Fri, May 10, 2013 at 12:44 AM, Shashank Sahni shredde...@gmail.comwrote:
Hi Chuan,
Did you manage to resolve the
Hi Shashank,
If you mean you have problem on network settings,
please go through the following link:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst
(especially network node and compute node.)
Sincerely,
Hsiao
On
Good point. A long time ago we used to call Beijing as Peking, but
the journalists now will always pick up the pinyin version: Beijing. Since
we are after I, we are pretty much down to either Ichang or Ili. Should
either one be chosen, I think that we should document the pinyin version as
well.
Hello,
I just got Folsom installed and everything works fine.
I now want the /etc/hosts file in the VM (am using ubuntu as an example)
to have a mapping of hostname to floating IP address.
Is there a way to automate that using user-data/metadata and cloud-init?
Of course it works manually but I
'Impossible' might be a good name... seeing as how impossible it is
becoming to find a word beginning with I in the region.
On Thu, May 9, 2013 at 12:04 PM, John Wong gokoproj...@gmail.com wrote:
Good point. A long time ago we used to call Beijing as Peking, but
the journalists now will
+1 for island -- this makes the most sense.
On Mon, May 6, 2013 at 1:00 AM, Sylvain Bauza sylvain.ba...@digimind.comwrote:
I would give my vote to Island, which is pretty universal and at the same
time referring to what HK is : an island.
Le 02/05/2013 16:01, Thierry Carrez a écrit :
Hi all,
I was too late to respond here i would love to see next release name as
India. I am saying because India is in APAC still i have need to find out
rule book for release.
Just my 1$ suggestion. :)
Cheers!!
Atul
From: Openstack
Did you explicitly create the vm as a VHD. If not it was created as VHDX.
VHDX isn't currently supported, it's on our roadmap for Havana.
p
Peter J. Pouliot, CISSP
Senior SDET, OpenStack
Microsoft
New England Research Development Center
One Memorial Drive,Cambridge, MA 02142
+1
Rajesh
From: Openstack [openstack-bounces+rvellank=rackspace@lists.launchpad.net]
on behalf of Atul Jha [atul@csscorp.com]
Sent: Thursday, May 09, 2013 2:31 PM
To: Matt Joyce; John Wong
Cc: Thierry Carrez; openstack@lists.launchpad.net
Subject: Re:
Hi Peter,
Yeah, that's exactly it, I had originally created the vm as a VHDX.
I've just used the Hyper-V Edit Disk feature to convert it from
VHDX to VHD, re-uploaded it (glance image-create) and then everything
went smoothly. Just a while ago I managed to deploy it from my
devstack to the
Sorry Bruno, just catching this here.
VHDx is your problem.
Create it as vhd or download one from here:
http://www.cloudbase.it/ws2012/
Peter J. Pouliot, CISSP
Senior SDET, OpenStack
Microsoft
New England Research Development Center
One Memorial Drive,Cambridge, MA 02142
The Horizon UI novaclient method requests nova endpoints from the service
catalog without specifying an endpoint_type parameter. Would it be more
correct for those requests to default to the 'internalURL' instead? There are
use cases where the publicURL is not exposed or defined, but if you
Thanks
But it's fine, already. So no worries. I managed to use the Hyper-V Edit Image
to convert them to the standard VHD.
Even so, thank you again
Bruno de Oliveira
Developer, System Analyst
+55 11 9-6193-3987
skype: brunnop.oliveira
brunnop.olive...@gmail.com
On Thu, May 9, 2013 at 5:12 PM,
Hi-
I am trying to get a better understanding of how Swift recovers from
failure. I've read the documentation, but the process is still somewhat
unclear.
I have a simple 5-node Swift cluster deployed with a replica count of 3 (3
zones and 2 handoff zones for a total of 5).I load the
Replication will be logged and you can look for a Object replication complete
log message.
For a more detailed look at how swift handles failures, you can watch this
video:
http://mirror.linux.org.au/linux.conf.au/2013/mp4/Playing_with_OpenStack_Swift.mp4
(I need to post my blog post that has
Hi guys,
I've got a quick question regarding HyperV and Xen
virtualization modes and their compatibility.
Can you help me out on this? Here's the deal:
Knowing that when xen boots up a Windows box, it goes
as HVM (Hardware Virtualization) but needs some PV
(Paravirtualization) drivers...
And
I forgot to mention that I found this doc mentioning how to migrate
http://jeff-brady.blogspot.com.br/2011/12/linux-on-hyper-v-migrate-redhat-vm-from.html
*But* I'm more concerned for the aspect of driver-wise.
Technically a xen-to-hyperV image will boot, would it be
auto-suficient?
I mean,
So, no one here have Windows 7 on Grizzly?
Tks!
Thiago
On 1 May 2013 21:10, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:
Hi!
With Folsom, I used to create a Windows 7 image, with KVM+libvirt and
then, upload it to Glance with the following command:
glance image-create --name Windows
Hello Rajesh,
There's a number of guides out there which should walk you
through getting your own OpenStack cluster set up and customized for your
environment, however here's a few links to some more automated deployment
tools.
http://www.rackspace.com/cloud/private/openstack_software/
If that config option is not being respected for the Nova API calls that's a
bug. Please file a ticket on Launchpad so we can track fixing it.
Thanks!
- Gabriel
From: Openstack
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Behalf Of Wyllys Ingersoll
Will do, thanks.
On May 9, 2013, at 7:26 PM, Gabriel Hurley
gabriel.hur...@nebula.commailto:gabriel.hur...@nebula.com wrote:
If that config option is not being respected for the Nova API calls that’s a
bug. Please file a ticket on Launchpad so we can track fixing it.
Thanks!
-
I agree to narrow down the names to Ili or Ichang. A word in pinyin starting
with I is a mission impossible:)
My 2 cents are we can google map “Peking” and “Ili” which go to China. But I
google map “Ichang”, it can’t locate to “Yichang” in China.
On Wikipedia, Ichang goes to the Yichang entry,
If the next release summit is going to be held in Japan, it should be easier
to give a name:)
--
Shane Wang
From: Openstack
[mailto:openstack-bounces+shane.wang=intel@lists.launchpad.net] On Behalf
Of Rajesh Vellanki
Sent: Friday, May 10, 2013 3:50 AM
To: Atul Jha; Matt Joyce; John Wong
Hello folks,
now that the traffic on https://ask.openstack.org has increased, I think
it's time we start collecting guidelines for the moderators so we keep
having a very informative tool, with consistently good questions and
answers.
I think it helps for example to pay attention to the
Alternatively... we name it after a kung fu movie.
Invincible Fist for instance was a Shaw Brothers film. Hong Kong is famous
for it's Kung Fu films =P
On Thu, May 9, 2013 at 8:57 PM, Wang, Shane shane.w...@intel.com wrote:
If the next release summit is going to be held in “Japan”, it
Title: saucy_havana_python-ceilometerclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_python-ceilometerclient_trunk/6/Project:saucy_havana_python-ceilometerclient_trunkDate of build:Thu, 09 May 2013 11:56:39 -0400Build duration:2 min 5 secBuild
Title: saucy_havana_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_keystone_trunk/7/Project:saucy_havana_keystone_trunkDate of build:Thu, 09 May 2013 12:02:03 -0400Build duration:1 min 48 secBuild cause:Started by an SCM changeStarted by an
Title: precise_folsom_keystone_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_stable/103/Project:precise_folsom_keystone_stableDate of build:Thu, 09 May 2013 12:03:52 -0400Build duration:2 min 0 secBuild cause:Started by an SCM
at 20130509-1205Build needed 00:01:35, 36196k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/44/Project:precise_havana_cinder_trunkDate of build:Thu, 09 May 2013 12:05:54 -0400Build duration:1 min 33 secBuild cause:Started by an SCM changeStarted by an
Title: quantal_folsom_keystone_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_stable/114/Project:quantal_folsom_keystone_stableDate of build:Thu, 09 May 2013 12:05:03 -0400Build duration:2 min 27 secBuild cause:Started by an SCM
Title: saucy_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_cinder_trunk/12/Project:saucy_havana_cinder_trunkDate of build:Thu, 09 May 2013 12:07:28 -0400Build duration:1 min 34 secBuild cause:Started by an SCM changeStarted by an SCM
Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/29/Project:saucy_havana_quantum_trunkDate of build:Thu, 09 May 2013 12:08:11 -0400Build duration:1 min 32 secBuild cause:Started by an SCM changeStarted by an
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/44/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 12:08:14 -0400Build duration:2 min 13 secBuild cause:Started by an SCM changeStarted by an SCM
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/99/Project:precise_havana_quantum_trunkDate of build:Thu, 09 May 2013 12:07:31 -0400Build duration:3 min 23 secBuild cause:Started by an SCM changeStarted by
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/127/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 12:30:28 -0400Build duration:3 min 4 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/30/Project:saucy_havana_quantum_trunkDate of build:Thu, 09 May 2013 13:00:24 -0400Build duration:1 min 43 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/128/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 13:00:26 -0400Build duration:3 min 14 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/100/Project:precise_havana_quantum_trunkDate of build:Thu, 09 May 2013 13:00:25 -0400Build duration:3 min 20 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/45/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 13:03:41 -0400Build duration:2 min 15 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_horizon_trunk/13/Project:saucy_havana_horizon_trunkDate of build:Thu, 09 May 2013 13:30:24 -0400Build duration:1 min 19 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_horizon_trunk/33/Project:precise_havana_horizon_trunkDate of build:Thu, 09 May 2013 13:30:24 -0400Build duration:2 min 40 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_keystone_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_stable/104/Project:precise_folsom_keystone_stableDate of build:Thu, 09 May 2013 14:00:25 -0400Build duration:1 min 30 secBuild cause:Started by an SCM
Title: quantal_folsom_keystone_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_stable/115/Project:quantal_folsom_keystone_stableDate of build:Thu, 09 May 2013 14:00:24 -0400Build duration:2 min 27 secBuild cause:Started by an SCM
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/129/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 14:42:09 -0400Build duration:2 min 44 secBuild cause:Started by user Chuck ShortBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/46/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 14:43:28 -0400Build duration:1 min 37 secBuild cause:Started by user Chuck ShortBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/47/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 14:51:54 -0400Build duration:1 min 41 secBuild cause:Started by user Chuck ShortBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/48/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 14:54:27 -0400Build duration:1 min 42 secBuild cause:Started by user Chuck ShortBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/49/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 14:57:15 -0400Build duration:3 min 29 secBuild cause:Started by user Chuck ShortBuilt
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/101/Project:precise_havana_quantum_trunkDate of build:Thu, 09 May 2013 15:30:23 -0400Build duration:3 min 21 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/50/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 15:30:26 -0400Build duration:3 min 45 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/130/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 15:31:28 -0400Build duration:3 min 21 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/31/Project:saucy_havana_quantum_trunkDate of build:Thu, 09 May 2013 15:30:23 -0400Build duration:9 min 27 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/102/Project:precise_havana_quantum_trunkDate of build:Thu, 09 May 2013 16:00:22 -0400Build duration:3 min 7 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/52/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 16:30:28 -0400Build duration:3 min 27 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/133/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 18:30:25 -0400Build duration:3 min 12 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/53/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 18:32:12 -0400Build duration:3 min 13 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_glance_trunk/43/Project:precise_havana_glance_trunkDate of build:Thu, 09 May 2013 18:30:23 -0400Build duration:8 min 8 secBuild cause:Started by an SCM changeBuilt
at 20130509-1838Build
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/134/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 19:00:23 -0400Build duration:2 min 50 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_nova_trunk/54/Project:saucy_havana_nova_trunkDate of build:Thu, 09 May 2013 19:01:20 -0400Build duration:3 min 44 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/45/Project:precise_havana_cinder_trunkDate of build:Thu, 09 May 2013 19:30:23 -0400Build duration:1 min 35 secBuild cause:Started by an SCM changeBuilt
Title: saucy_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_cinder_trunk/13/Project:saucy_havana_cinder_trunkDate of build:Thu, 09 May 2013 19:30:23 -0400Build duration:2 min 5 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_glance_trunk/44/Project:precise_havana_glance_trunkDate of build:Thu, 09 May 2013 21:00:23 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt
at 20130509
Title: test_tempest_smoke
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/99/Project:test_tempest_smokeDate of build:Thu, 09 May 2013 21:57:00 -0400Build duration:40 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/135/Project:precise_havana_nova_trunkDate of build:Thu, 09 May 2013 22:00:26 -0400Build duration:4 min 3 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_ceilometer_trunk/40/Project:precise_havana_ceilometer_trunkDate of build:Thu, 09 May 2013 22:30:24 -0400Build duration:1 min 38 secBuild cause:Started by an SCM
Title: saucy_havana_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_ceilometer_trunk/26/Project:saucy_havana_ceilometer_trunkDate of build:Thu, 09 May 2013 22:30:24 -0400Build duration:2 min 8 secBuild cause:Started by an SCM changeBuilt
1 - 100 of 103 matches
Mail list logo
