Re: [Openstack] nova-client Error :: Please input your password for the keyring

2012-11-09 Thread heut2008
you can do  export OS_NO_CACHE=1 in your script before  using a nova Client
object. to avoid  input keyring


2012/11/9 Trinath Somanchi trinath.soman...@gmail.com

 Hi-

 I have written an resource extension in nova-api. and the test script runs
 in the compute-host. When the Keystone credentials are given in the script
 to created an nova-client 'Client' instance, for sending the request, I get
 this message

 Please input your password for the keyring

 I input the passcode that was given in the test script, it gives me the
 record string the nova-api.

 I haven't faced this issue when I run the test script in the Controller
 machine. but when I run in the host machine, I'm seeing this issue.

 Please help me resolve the issue.

 Thanking you.

 --
 Regards,
 --
 Trinath Somanchi,



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Yaguang Tang
___
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] Bug with the openVSwitch plugin Agent !

2012-11-09 Thread Skible OpenStack

I am sorry, i believe i am having a hardware problem because i have done

apt-get install -y openvswitch-switch openvswitch-datapath-dkms


on other nodes and tunneling just got back to work fine ! my mistake !

thank you for your kind help, i appreciate that !

Le 09/11/2012 03:33, Dan Wendlandt a écrit :
have you rebooted the device to make sure you're reloaded the new 
kernel module?


On Thu, Nov 8, 2012 at 1:03 PM, Skible OpenStack 
skible.openst...@gmail.com mailto:skible.openst...@gmail.com wrote:


Thank you for replying back. I had a bad day because of this problem.
I have installed openvswitch-datapath-dkms but it doesn't seem to
solve the problem.

Le 08/11/2012 21:48, Dan Wendlandt a écrit :

This is not an issue with the agent.  I believe this was handled
in another post, which pointed out that 12.10 originally shipped
with a version of OVS that did not include tunnel support, but
this has since been correctly.

See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068365

Dan

p.s. thanks to rkukura for making sure there was a friendly error
message in this case :)

On Thu, Nov 8, 2012 at 3:21 AM, Skible OpenStack
skible.openst...@gmail.com mailto:skible.openst...@gmail.com
wrote:

Hi to all !

I am using Quantum with Tunneling and this is my
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
[OVS]
tenant_network_type = gre
tunnel_id_ranges = 1:1000
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 100.10.10.51
enable_tunneling = True

When i do look in the log of the openvSwitch plugin agent, i
find this

2012-11-08 12:14:23ERROR
[quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed
to create OVS patch port. Cannot have tunneling enabled on
this agent, since this version of OVS does not support
tunnels or patch ports.

i am runing ubuntu 12.10 and my OpenVSwitch version is
1.4.3-0ubuntu2

Thank you for your help

___
Mailing list: https://launchpad.net/~openstack
https://launchpad.net/%7Eopenstack
Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
https://launchpad.net/%7Eopenstack
More help   : https://help.launchpad.net/ListHelp




-- 
~~~

Dan Wendlandt
Nicira, Inc: www.nicira.com http://www.nicira.com
twitter: danwendlandt
~~~






--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com http://www.nicira.com
twitter: danwendlandt
~~~



___
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] authentication failure for glance client in the latest devstack dev environment

2012-11-09 Thread Lu, Lianhao
Hi fellows,

Today I just updated my devstack to setup a new openstack dev environment with 
RECLONE set to yes in localrc. The stack.sh failed at the very end in 
glance image-create with the error of Invalid OpenStack Identify credential.

I then tried to run glance image-list in the command line after source 
openrc admin, it also failed with the same error. 

When the error happens, glance-api server reported the following errors on the 
screen:

2012-11-09 16:20:31 16950 ERROR keystone.middleware.auth_token [-] HTTP 
connection exception: [Errno 1] _ssl.c:504: error:140770FC:SSL 
routines:SSL23_GET_SERVER_HELLO:unknown protocol
2012-11-09 16:20:31 16950 WARNING keystone.middleware.auth_token [-] 
Authorization failed for token 
MIIL7wYJKoZIhvcNAQcCoIIL4DCCC9wCAQExCTAHBgUrDgMCGjCCCkUGCSqGSIb3DQEHAaCCCjYEggoyeyJhY2Nlc3MiOiB7InRva2VuIjogeyJpc3N1ZWRfYXQiOiAiMDg6MjA6MzEuNjM3.(..omit
 here)
A8uKBr1VlQoeF2Y-ND+DhZV+vjrM8i6FcGfeFq6Vra-1ktoQjkfh88XmG2tCcwrlGo0nVM4OrRaIs8F9Iwc4EIXHA+Aw73MzqUIRVSE8ahiFg9nNM=
2012-11-09 16:20:31 16950 INFO keystone.middleware.auth_token [-] Invalid user 
token - deferring reject downstream


And the keystone reported the following:

(eventlet.wsgi.server): 2012-11-09 16:28:21,276 DEBUG wsgi write 127.0.0.1 - - 
[09/Nov/2012 16:28:21] POST /v2.0/tokens HTTP/1.1 200 6780 0.095150

localhost - - [09/Nov/2012 16:28:21] code 400, message Bad request syntax 
(\x16\x03\x01\x00\xcd\x01\x00\x00\xc9\x03\x02P\x9c\xbe\xa5#\xc8D\xf8\xe9\xe9\x97\xc5w\x19LX\xfc\xb8\x04v\xb1w'\x04A\xa7}\xa8\x0c)
localhost - - [09/Nov/2012 16:28:21] ��P���#�DwLX�v�w'A�}� 400 -


Does anyone know what's going wrong here?

Yours,
-Lianhao
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios

2012-11-09 Thread Choe, Cheng-Dae
as you know.

I already setup my environment with below
- controller: all the things except nova-compute, quantum-l3,dhcp-agent
- network: quantum-l3-agent, quantum-dhcp-agent
- compute*2: nova-compute

and the chef installation was already opened in my github.
please refer https://github.com/whitekid/openstack-chef

because my lack of time. the documentation is missing :)
If time allow i start write the architecture and network connectivity.

2012. 11. 9., 오전 6:06, Skible OpenStack skible.openst...@gmail.com 작성:

 Thank you Dan for shedding light on this matter. However, there is something 
 concerns me and a lot of other people trying to deploy OpenStack is that most 
 Servers has 2 NICs which creates a problem because your Demo is a great one 
 but the necessary hardware is just not always met !
 
 I have been struggling to find a solution out of it, can you suggest some 
 please ?
 Le 08/11/2012 21:38, Dan Wendlandt a écrit :
 Hi,
 
 The Quantum Admin Guide indicates that you can choose to combine all 
 services onto a single node, or have separate nodes: 
 http://docs.openstack.org/trunk/openstack-network/admin/content/services.html
 
 I will update the text to indicate that that the main reason to use a 
 dedicated network gateway node is if you plan on having VMs send substantial 
 amounts of traffic through that node, and thus would not want that CPU usage 
 to conflict with other openstack services running on your controller node.
 
 dan
 
 On Thu, Nov 8, 2012 at 11:06 AM, Skible OpenStack 
 skible.openst...@gmail.com wrote:
 Can someone please enlighten us about the goods of having a separated 
 network node ?
 I honestly work in production envirnoments (over 30 nodes) and i really give 
 computing resources more credit than networking ones ! 
 
 Am i doing it the wrong way here ? 
 
 Le 08/11/2012 18:49, balaji patnala a écrit :
 Hi Openers,
  
 One doubt i have is like, as we see in the demo setup in the Quantum Admin 
 guide available in openstack.org, we have Network Node as a seperate 
 physical node connected to Controller Node and Compute Node.
  
 But i see that the openstack community who is actively using Folsom is not 
 discussing more on this kind of setup.
  
 Not sure if iam missing any key information on this like that the Network 
 Node setup may not be widely used in current deployment scenarios or it is 
 too early to use Network Node as a seperate physical host for openstack.
  
 Open comments on this will be more helpful for openstack community to 
 understand better on the features of folsom.
  
 regards,
 balaji
 
 
  
 On Thu, Nov 8, 2012 at 7:09 PM, Skible OpenStack 
 skible.openst...@gmail.com wrote:
 OpenStack Folsom install guide 
 
 You will find what you want and even more ;)
 
 Le 08/11/2012 14:30, Veera Reddy a écrit :
 Hi Skible,
 
 Can you please send me below configuration files of three setups you have 
 mentioned.
 
 ovs_quantum_plugin.ini (For controller and node)
 nova.conf (For controller and node)
 Thanks in advance
 
 
 Regards,
 Veera.
 
 On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack 
 skible.openst...@gmail.com wrote:
 Hello Stackers !
 
 I am currently trying to create pictures of my OpenStack deployment 
 architecture as a part of my OpenStack Folsom install guide and i would 
 like to ask a favorite.
 
 Could you be kind and please take a look at these Pics below and report 
 back if there is a missing or wrong thing.
 
 Thank you.
 
 
 ==Quantum  on VLAN + 3 NICs on controller node
 http://i.imgur.com/Ueh5Z.jpg
 ===
 
 ==Quantum  on VLAN + 2 NICs on controller node
 http://i.imgur.com/RK6X7.jpg
 ===
 
 ==Quantum  on GRE-tunneling + 3 NICs on controller node===
 http://i.imgur.com/1jCFC.jpg
 ===
 
 
 To make of OpenStack, the IT project of the century
 
 Best regards
 
 
 
  
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
 
 
 
 -- 
 Regards,
 VeeraReddy.B
 9959236555.
 
 
 ___
 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
 
 
 
 
 -- 
 ~~~
 Dan Wendlandt 
 Nicira, Inc: www.nicira.com
 twitter: danwendlandt
 ~~~
 
 
 ___
 Mailing list: 

Re: [Openstack] nova/quantum/ovs configuration conundrum

2012-11-09 Thread Choe, Cheng-Dae
currently.
l3_agent designed as serve all tenant's traffic or
per router per l3_agent by specify router_id in l3_agent.ini

so in current architecture. if you want deploy as production scale.
I think l3_agent must be dedicated to one router 

or the another solution is needed(nvp, midonet, cisco ...) 

2012. 11. 9., 오후 3:04, Sina Sadeghi s...@aptira.com 작성:

 I followed the instructions to add a route from 
 http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html
  but I don't immediately see how the route add helped here - but it has 
 raised an eyebrow.
 
 Tell me about it!
 
 We wanted to use Quantum mostly so we could avoid being forced to upgrade 
 from nova-network later on. Once again the difference between trunk (dev) and 
 stable (ops) kills new OpenStack features for early production adopters. 
 There is no way we can offer this to our customers. Are we expected to add a 
 new route for every subnet our customers create, across every compute node, 
 on the fly (including esoteric quantum port-list commands)?
 
 As for the idea of having one quantum-l3-agent that NATs traffic for many 
 compute nodes, I wasn't aware the concept of retro chic applied to network 
 topologies :(
 
 I shudder to think how this would operate at scale, so it looks like we will 
 be sticking to our nova-network VLAN configuration.
 
 
 --
 Sina Sadeghi
 Lead Cloud Engineer
 logo.jpg
 Aptira Pty Ltd
 1800 APTIRA
 aptira.com
 Follow @aptira
 
 On 08/11/12 22:54, Kevin Jackson wrote:
 Hi Stephen, 
 This is what I get... (note change of namespace etc as this machine is a VM 
 that was recreated).
 
 root@openstack:~# ip netns list
 qdhcp-3f0a3d53-f3a4-4da8-a5e0-1a97b6e51424
 qrouter-f26858db-3ae8-431b-86a7-edab80834586
 
 root@openstack:~# ip netns exec qrouter-f26858db-3ae8-431b-86a7-edab80834586 
 wget http://172.16.0.210:8775/
 --2012-11-08 10:52:11--  http://172.16.0.210:8775/
 Connecting to 172.16.0.210:8775... failed: No route to host.
 
 root@openstack:~# ip netns exec qrouter-f26858db-3ae8-431b-86a7-edab80834586 
 ip r  
 default via 172.16.1.254 dev qg-c396e75e-38 
 10.5.5.0/24 dev qr-031aafac-19  proto kernel  scope link  src 10.5.5.1 
 172.16.1.0/24 dev qg-c396e75e-38  proto kernel  scope link  src 172.16.1.10 
 
 So it is a problem between my router and the physical network... That 
 172.16.1.0/24 is an ext-net network created with an external router.  When 
 I spin my instances up I use the 10.5.5.0/24 int-net network.
 
 I followed the instructions to add a route from 
 http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html
  but I don't immediately see how the route add helped here - but it has 
 raised an eyebrow.
 
 The output of the port-list gave me 172.16.1.10 to use as the $ROUTER_GW_IP 
 - which is odd as that IP was set as my external floating range start IP.  
 Doing a traceroute to the 172.16.0.201 address from the router namespace 
 went via 172.16.1.10... so I've some things to play with for the time 
 being...
 
 Thanks for your help so far.  Is the Guardian looking at OpenStack for any 
 projects (I'm from TMG)?
 
 Cheers,
 Kev
 
 
 On 8 November 2012 10:49, Stephen Gran stephen.g...@guardian.co.uk wrote:
 Hi,
 
 
 On Thu, 2012-11-08 at 10:02 +, Kevin Jackson wrote:
 Thanks for that - the namspace thing is starting to make sense.
 So I see this rule in there now:
 
 Chain quantum-l3-agent-PREROUTING (1 references)
  pkts bytes target prot opt in out source   
 destination 
62  3720 DNAT   tcp  --  *  *   0.0.0.0/0
 169.254.169.254  tcp dpt:80 to:172.16.0.201:8775
 
 But I never see a connection being made when I spin up an instance.  The 
 instance reports no route to host.
 
 It's unclear at this point if the problem is that your instance can't reach 
 it's gateway (the quantum router), or if the quantum router can't reach the 
 metadata server.
 
 try:
 ip netns exec qrouter-61245d6f-1195-4ca0-ba08-f0636f7d44c6 wget 
 http://172.16.0.201:8775/
 
 To rule out the latter so you know where to concentrate your efforts.
 
 -- 
 Stephen Gran
 Senior Systems Integrator - guardian.co.uk
 Please consider the environment before printing this email.
 --
 Visit guardian.co.uk - website of the year
  
 www.guardian.co.ukwww.observer.co.uk www.guardiannews.com 
  
 On your mobile, visit m.guardian.co.uk or download the Guardian
 iPhone app www.guardian.co.uk/iphone and iPad edition 
 www.guardian.co.uk/iPad 
  
 Save up to 37% by subscribing to the Guardian and Observer - choose the 
 papers you want and get full digital access. 
 Visit guardian.co.uk/subscribe
  
 -
 This e-mail and all attachments are confidential and may also
 be privileged. If you are not the named recipient, please notify
 the 

Re: [Openstack] authentication failure for glance client in the latest devstack dev environment

2012-11-09 Thread Lu, Lianhao
My system is Ubuntu 12.04 64bit.

My nova list also failed with a HTTP 401 status error, with the following 
output on nova-api:

2012-11-09 18:30:09 ERROR keystone.common.cms [-] Verify error: Verification 
failure
139967656924832:error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature 
length:rsa_sign.c:175:
139967656924832:error:2E09A09E:CMS 
routines:CMS_SignerInfo_verify_content:verification failure:cms_sd.c:900:
139967656924832:error:2E09D06D:CMS routines:CMS_verify:content verify 
error:cms_smime.c:425:

2012-11-09 18:30:09 WARNING keystone.middleware.auth_token [-] Authorization 
failed for token ..
2012-11-09 18:30:09 INFO keystone.middleware.auth_token [-] Invalid user token 
- rejecting request
2012-11-09 18:30:09 INFO nova.osapi_compute.wsgi.server [-] 10.239.36.61 GET 
/v2/447239d7ddfd4ae89393c9ecf538d703/servers/det
ail HTTP/1.1 status: 401 len: 461 time: 0.0153220

However, the keystone command-line client works fine.

Best Regards,
Lianhao

 -Original Message-
 From: openstack-bounces+lianhao.lu=intel@lists.launchpad.net 
 [mailto:openstack-bounces+lianhao.lu=intel@lists.launchpad.net]
 On Behalf Of Lu, Lianhao
 Sent: Friday, November 09, 2012 4:31 PM
 To: openstack@lists.launchpad.net; openstack-...@lists.openstack.org
 Subject: [Openstack] authentication failure for glance client in the latest 
 devstack dev environment
 
 Hi fellows,
 
 Today I just updated my devstack to setup a new openstack dev environment 
 with RECLONE set to yes in localrc. The stack.sh failed at
 the very end in glance image-create with the error of Invalid OpenStack 
 Identify credential.
 
 I then tried to run glance image-list in the command line after source 
 openrc admin, it also failed with the same error.
 
 When the error happens, glance-api server reported the following errors on 
 the screen:
 
 2012-11-09 16:20:31 16950 ERROR keystone.middleware.auth_token [-] HTTP 
 connection exception: [Errno 1] _ssl.c:504:
 error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
 2012-11-09 16:20:31 16950 WARNING keystone.middleware.auth_token [-] 
 Authorization failed for token
 MIIL7wYJKoZIhvcNAQcCoIIL4DCCC9wCAQExCTAHBgUrDgMCGjCCCkUGCSqGSIb3DQEHAaCCCjYEggoyeyJhY2Nlc3MiOiB7InRva2VuIjogeyJp
 c3N1ZWRfYXQiOiAiMDg6MjA6MzEuNjM3.(..omit here)
 A8uKBr1VlQoeF2Y-ND+DhZV+vjrM8i6FcGfeFq6Vra-1ktoQjkfh88XmG2tCcwrlGo0nVM4OrRaIs8F9Iwc4EIXHA+Aw73MzqUIRVSE8ahiFg9nNM
 =
 2012-11-09 16:20:31 16950 INFO keystone.middleware.auth_token [-] Invalid 
 user token - deferring reject downstream
 
 
 And the keystone reported the following:
 
 (eventlet.wsgi.server): 2012-11-09 16:28:21,276 DEBUG wsgi write 127.0.0.1 - 
 - [09/Nov/2012 16:28:21] POST /v2.0/tokens HTTP/1.1 200
 6780 0.095150
 
 localhost - - [09/Nov/2012 16:28:21] code 400, message Bad request syntax
 (\x16\x03\x01\x00\xcd\x01\x00\x00\xc9\x03\x02P\x9c\xbe\xa5#\xc8D\xf8\xe9\xe9\x97\xc5w\x19LX\xfc\xb8\x04v\xb1w'\x04A\xa7}\xa8\x
 0c)
 localhost - - [09/Nov/2012 16:28:21] ��P���#�DwLX�v�w'A�}� 400 -
 
 
 Does anyone know what's going wrong here?
 
 Yours,
 -Lianhao
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] snapshots, backups of running VMs and compute node recovery

2012-11-09 Thread Jānis Ģeņģeris
Hello all,

I would like to know the available solutions that are used regarding to
backing up and/or snapshotting running
instances on compute nodes. Documentation does not mention anything related
to this. With snapshots I don't mean
the current snapshot mechanism, that imports image of the running VM into
glance. I'm using KVM, but this is
significant for any hypervisor.

Why is this important?
Consider simple scenario when hardware on compute node fails and the node
goes down immediately and is not recoverable
in reasonable time. The images of the running instances are also lost.
Shared file system is not considered here as it
may cause IO bottlenecks and adds another layer of complexity.

There have been a few discussions on the the list about this problem, but
none have really answered the question.

The documentation speaks of disaster recovery when power loss have happened
and failed compute node recovery from
shared file system. But don't cover the case without shared file system.

I can think of few solutions currently (for KVM):
a) using LVM images for VMs, and making LVM logical volume snapshots, but
then the current nova snapshot mechanism
will not work (from the docs - 'current snapshot mechanism in OpenStack
Compute works only with instances backed
with Qcow2 images');
b) snapshot machines with OpenStack snapshotting mechanism, but this
doesn't fit somehow, because it has
other goal than creating backups, will be slow and pollute the glance image
space;

Regards
--janis
___
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] Question about pv mode on compute and network

2012-11-09 Thread John Garbutt
Hi,

Sorry I missed this, I am still behind on my email.

In the current model every XCP node gets a VM with nova-compute running on it, 
and it must be a linux PV VM.

That node does several management tasks. For example, with raw images, it will 
stream the image into a VDI attached to that VM. In the current world, you need 
to be a PV VM for the hotplug of that volume to be allowed. So, to cut a long 
story short, yes, it needs to be a PV VM.

I noticed some storage questions. Generally you should have a single local SR 
of type EXT on each of your XCP hosts. Hopefully that is all covered in the 
Admin guide. Let me know if anything is confusing, and I will update the guide 
to help clarify things.

If you want shared storage you need to look towards using Cinder. So 
attaching volumes, doing boot-from-volume, and other such things. Right now we 
have support for things that produce iSCSI targets, and some NFS shared storage 
support is just dropping into Grizzly over the next week or so.

I hope that helps,
John

 -Original Message-
 From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net
 [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
 Behalf Of Egoitz Aurrekoetxea Aurre
 Sent: 04 November 2012 10:32
 To: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Question about pv mode on compute and network
 
  or just I nova-compute and nova-network -- 1 nova-compute and nova... I
 wanted to mean.
 
 
 El 04/11/2012, a las 11:04, Egoitz Aurrekoetxea Aurre ego...@ramattack.net
 escribió:
 
  Hi all,
 
  Why the nova-compute and nova-network services should run in pv mode??.
 What's the real reason for it?. If I have a farm of five servers of Xen Cloud
 Platform. all of them belonging to the same pool (same cloud) should I have a
 nova-compute per xcp server?? or just I nova-compute and nova-network will
 handle the whole pool smoothly??.
 
  Best regards,
 
 
  ___
  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] Generating Linux pv images uploadables to glance and bootable from Xen Cloud Platform through Nova

2012-11-09 Thread John Garbutt
Sorry for the late response.

What you really want to do is export the OVF through XenCenter, inside there 
you will find the VHD file, which is what you really want to be uploading to 
Glance (I think there are instructions there for VHD files).

Mate has a nice blog post on quicker ways to extract the VHD file, and some 
videos to help make it easier:
http://blogs.citrix.com/2012/09/06/vhd-to-openstack-using-a-xapi-host-plugin/

Thanks,
John

 -Original Message-
 From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net
 [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
 Behalf Of Egoitz Aurrekoetxea Aurre
 Sent: 28 October 2012 00:05
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Generating Linux pv images uploadables to glance and
 bootable from Xen Cloud Platform through Nova
 
 Good night,
 
 Could anyone know how to do this?. I have been able to create a image for
 FreeBSD... because it runs in hvm mode. So... I have just export to xva, then 
 take
 the vhd file convert to raw and upload to glance
 
 glance add name=FreeBSD-9.1RC1-AMD64 disk_format=raw
 container_format=bare  FREEBSD.raw
 
 Same thing is not working for Centos it hangs saying :
 
 Error 13: Invalid or unsupported executable format
 
 So like any procedures found are for KVM I would be very thankful if 
 someone
 has experience doing this...
 
 I have done some checks, read doc and so... but no way...
 
 Best regards,
 ___
 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] Nova different sr

2012-11-09 Thread John Garbutt
Cinder is the way forward to look at exposing multiple volume types.

The Cinder guys should be able to help you with how to get that working:
https://blueprints.launchpad.net/cinder/+spec/volume-type-scheduler

XCP NFS support should be in there soon too:
https://blueprints.launchpad.net/cinder/+spec/xenapi-storage-manager-nfs

Let me know if you have specific requirements for some other type of SR.
I would be very interested in how we can help you get that working.

Cheers,
John

From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On 
Behalf Of Egoitz Aurrekoetxea Aurre
Sent: 02 November 2012 20:42
To: Armando Migliaccio
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Nova different sr



Egoirz Aurrekoetxea Aurre
ego...@ramattack.netmailto:ego...@ramattack.net
Sent from my smartphone

El 02/11/2012, a las 21:12, Armando Migliaccio 
amigliac...@internap.commailto:amigliac...@internap.com escribió:
Egoirz,
On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net wrote:
Good afternoon Armando,

Thanks a lot for you're answer.

Yes basically I want to setup a virtual housing service in the way you can 
create a machine in sas or sata storage for example. If each nova-compute 
should point to just one sr (storage kind) of xcp it would be one or the other 
one (in this example... sas or sata)... Ok then. So you mean the right way of 
doing this with Openstack is to basically have different nova-computes pointing 
to different sr and sharing the other properties... Have I understand properly??

That's not exactly what I meant, especially in relation to what is _right_ in 
OpenStack; I was providing input in relation to the use of the flag you 
mentioned.

Ok so is not perhaps the right way but it's a possibility. #128515;





Actually, if you want to support storage at different levels of QoS, Cinder is 
another project worth looking at.

http://wiki.openstack.org/Cinder


I'll tale a look at it... Mainly if this gives me the possibilty...



A.



In the last two paragraph I assume you're just talking about load balancing... 
Isn't it??

Where did you get that? No I wasn't ;)


Because you were talking about where to create vm and how to manage the 
schwduler iirc #128515;



Very thankful for you're time.
Regards,

Egoirz Aurrekoetxea Aurre
ego...@ramattack.netmailto:ego...@ramattack.net
Sent from my smartphone

El 02/11/2012, a las 18:47, Armando Migliaccio 
amigliac...@internap.commailto:amigliac...@internap.com escribió:
Hi,

If I understand your request correctly, say you have two storage backends with 
different QoS and you want to use both of them in your OpenStack/XCP 
deployment, what you can do is:

1) create SR1 for XCP1 that maps to storage array at QoS1
1a) configure the compute domU for XCP1 to point to SR1, by specifying 
sr_matching_filter in your nova.conf accordingly.
2) create SR2 for XCP2 that maps to storage array at QoS2
2a) configure the compute domU for XCP2 to point to SR2, by specifying 
sr_matching_filter in your nova.conf accordingly.

You can find more details here:

http://wiki.openstack.org/XenServer/NovaFlags

Obviously this can be extended to multiple nodes; then you can use the 
CLI/scheduler filters to redirect the create request to the right host.

That is one way, but there are a few others like  or compute extra capabilities 
(Essex) or general host aggregates (Folsom+)

Hope this helps,
Armando

On Fri, Nov 2, 2012 at 9:34 AM, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net wrote:
Or unless… If I had to use forcibly the same storage…. for all vm provisioned 
in a single nova-compute…. is it anyway of saying Openstack to create a vm in a 
nova-compute or another one… depending on the storage attached to the 
nova-compute's dom0??


El 02/11/2012, a las 10:25, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net escribió:

 Good morning,

 Perhaps I have not explained properly…. I have different IBM arrays whose 
 disks are disks of different speeds… and wanted to have the possibility of 
 provisioning vm on different speed storages for example…. Could this be 
 possible??… I'm using XCP (1.5, 1.1 and 1.6 versions so I could test it in 
 all of them)… Anne the link you provided me, although has important 
 information… does not answer my question… Sorry…

 Best regards,


 El 01/11/2012, a las 15:35, Anne Gentle 
 a...@openstack.orgmailto:a...@openstack.org escribió:

 Hi Egoitz -
 This topic would probably help answer your question:

 http://docs.openstack.org/trunk/openstack-compute/install/yum/content/terminology-storage.html

 Anne

 On Wed, Oct 31, 2012 at 4:29 PM, Egoitz Aurrekoetxea Aurre
 ego...@ramattack.netmailto:ego...@ramattack.net wrote:
 Good night,

 Could anyone know if it's possible to use different nfs servers or different
 storages for launching instances in 

Re: [Openstack] instance disk space

2012-11-09 Thread John Garbutt
Sounds like a bug worth reporting.

What flavor where you selecting, and what image were you using?

There is some code in XenAPI driver that tries to resize the partition of the 
disk, and the file system on it, if I remember correctly. Can you see that in 
the logs? Maybe it fails because your image doesn't have a file system type it 
expects, or doesn't have a partition table on the disk, or vv.

John

From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On 
Behalf Of Afef MDHAFFAR
Sent: 02 November 2012 09:31
To: openstack@lists.launchpad.net
Subject: [Openstack] instance disk space

Hi all,

I am running openstack, with XCP on ubuntu 12.04.
When I tried to launch instance using the majority of existing flavors, I 
noticed that the instance never takes into account the mentioned disk space.
I also tried to create a new flavor with Ephemeral disk, but this does not 
solve the problem. I never get the required disk space. Do I have to mount some 
partitions???
Your answers are very appreciated!

Thank you,
Afef
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Nova different sr

2012-11-09 Thread John Garbutt
My bad, I noticed you have some IBM arrays. What SR type are you using to 
connect to those?
I think Cinder has some code of some IBM arrays. If that connects with iSCSI, 
it should work with XCP.

Cheers,
John

From: John Garbutt
Sent: 09 November 2012 12:08
To: 'Egoitz Aurrekoetxea Aurre'; Armando Migliaccio; Mate Lakat
Cc: openstack@lists.launchpad.net
Subject: RE: [Openstack] Nova different sr

Cinder is the way forward to look at exposing multiple volume types.

The Cinder guys should be able to help you with how to get that working:
https://blueprints.launchpad.net/cinder/+spec/volume-type-scheduler

XCP NFS support should be in there soon too:
https://blueprints.launchpad.net/cinder/+spec/xenapi-storage-manager-nfs

Let me know if you have specific requirements for some other type of SR.
I would be very interested in how we can help you get that working.

Cheers,
John

From: 
openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net
 [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On 
Behalf Of Egoitz Aurrekoetxea Aurre
Sent: 02 November 2012 20:42
To: Armando Migliaccio
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Nova different sr



Egoirz Aurrekoetxea Aurre
ego...@ramattack.netmailto:ego...@ramattack.net
Sent from my smartphone

El 02/11/2012, a las 21:12, Armando Migliaccio 
amigliac...@internap.commailto:amigliac...@internap.com escribió:
Egoirz,
On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net wrote:
Good afternoon Armando,

Thanks a lot for you're answer.

Yes basically I want to setup a virtual housing service in the way you can 
create a machine in sas or sata storage for example. If each nova-compute 
should point to just one sr (storage kind) of xcp it would be one or the other 
one (in this example... sas or sata)... Ok then. So you mean the right way of 
doing this with Openstack is to basically have different nova-computes pointing 
to different sr and sharing the other properties... Have I understand properly??

That's not exactly what I meant, especially in relation to what is _right_ in 
OpenStack; I was providing input in relation to the use of the flag you 
mentioned.

Ok so is not perhaps the right way but it's a possibility. #128515;




Actually, if you want to support storage at different levels of QoS, Cinder is 
another project worth looking at.

http://wiki.openstack.org/Cinder


I'll tale a look at it... Mainly if this gives me the possibilty...


A.



In the last two paragraph I assume you're just talking about load balancing... 
Isn't it??

Where did you get that? No I wasn't ;)


Because you were talking about where to create vm and how to manage the 
schwduler iirc #128515;


Very thankful for you're time.
Regards,

Egoirz Aurrekoetxea Aurre
ego...@ramattack.netmailto:ego...@ramattack.net
Sent from my smartphone

El 02/11/2012, a las 18:47, Armando Migliaccio 
amigliac...@internap.commailto:amigliac...@internap.com escribió:
Hi,

If I understand your request correctly, say you have two storage backends with 
different QoS and you want to use both of them in your OpenStack/XCP 
deployment, what you can do is:

1) create SR1 for XCP1 that maps to storage array at QoS1
1a) configure the compute domU for XCP1 to point to SR1, by specifying 
sr_matching_filter in your nova.conf accordingly.
2) create SR2 for XCP2 that maps to storage array at QoS2
2a) configure the compute domU for XCP2 to point to SR2, by specifying 
sr_matching_filter in your nova.conf accordingly.

You can find more details here:

http://wiki.openstack.org/XenServer/NovaFlags

Obviously this can be extended to multiple nodes; then you can use the 
CLI/scheduler filters to redirect the create request to the right host.

That is one way, but there are a few others like  or compute extra capabilities 
(Essex) or general host aggregates (Folsom+)

Hope this helps,
Armando

On Fri, Nov 2, 2012 at 9:34 AM, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net wrote:
Or unless… If I had to use forcibly the same storage…. for all vm provisioned 
in a single nova-compute…. is it anyway of saying Openstack to create a vm in a 
nova-compute or another one… depending on the storage attached to the 
nova-compute's dom0??


El 02/11/2012, a las 10:25, Egoitz Aurrekoetxea Aurre 
ego...@ramattack.netmailto:ego...@ramattack.net escribió:

 Good morning,

 Perhaps I have not explained properly…. I have different IBM arrays whose 
 disks are disks of different speeds… and wanted to have the possibility of 
 provisioning vm on different speed storages for example…. Could this be 
 possible??… I'm using XCP (1.5, 1.1 and 1.6 versions so I could test it in 
 all of them)… Anne the link you provided me, although has important 
 information… does not answer my question… Sorry…

 Best regards,


 El 

Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios

2012-11-09 Thread Veera Reddy
Hi Skible,

I followed the install guide
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

I am able to bring up guest, but unable to get ip to guest vm from network
node.

Also attached respective configuraion files .

Please help in finding the issue.



My setup :
Controller : (10.232.91.33)

nova-api
nova-cert
nova-consoleauth
nova-scheduler
quantum-server

Network Node:(10.232.90.222)

quantum-plugin-openvswitch-agent
quantum-dhcp-agent
quantum-l3-agent

Compute Node: (10.232.90.62)

quantum-plugin-openvswitch-agent
nova-compute


controller-nova.conf attached
compute_node-nova.conf attached
compute-ovs_quantum_plugin.ini attached
network_node_ovs_quantum_plugin.ini attached


Thanks in advance

Regards,
Veera.

On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack skible.openst...@gmail.com
 wrote:

  Hello Stackers !

 I am currently trying to create pictures of my OpenStack deployment
 architecture as a part of my OpenStack Folsom install 
 guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand
  i would like to ask a favorite.

 Could you be kind and please take a look at these Pics below and report
 back if there is a missing or wrong thing.

 Thank you.


 ==Quantum  on VLAN + 3 NICs on controller node
 http://i.imgur.com/Ueh5Z.jpg
 ===

 ==Quantum  on VLAN + 2 NICs on controller node
 http://i.imgur.com/RK6X7.jpg
 ===

 ==Quantum  on GRE-tunneling + 3 NICs on controller node===
 http://i.imgur.com/1jCFC.jpg
 ===


 To make of OpenStack, the IT project of the century

 Best regards





 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Regards,
VeeraReddy.B
9959236555.


comput_node-nova.conf
Description: Binary data


compute_node-ovs_quantum_plugin.ini
Description: Binary data


controller-nova.conf
Description: Binary data


network_node-ovs_quantum_plugin.ini
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] OpenStack (+ Quantum Deployment) Scenarios

2012-11-09 Thread Veera Reddy
Hi Skible,

I followed the install guide
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

I am able to bring up guest, but unable to get ip to guest vm from network
node.

Also attached respective configuraion files .

Please help in finding the issue.



My setup :
Controller : (10.232.91.33)

nova-api
nova-cert
nova-consoleauth
nova-scheduler
quantum-server

Network Node:(10.232.90.222)

quantum-plugin-openvswitch-agent
quantum-dhcp-agent
quantum-l3-agent

Compute Node: (10.232.90.62)

quantum-plugin-openvswitch-agent
nova-compute


controller-nova.conf attached
compute_node-nova.conf attached
compute-ovs_quantum_plugin.ini attached
network_node_ovs_quantum_plugin.ini attached


Thanks in advance

Regards,
Veera.

On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack skible.openst...@gmail.com
 wrote:

  Hello Stackers !

 I am currently trying to create pictures of my OpenStack deployment
 architecture as a part of my OpenStack Folsom install 
 guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand
  i would like to ask a favorite.

 Could you be kind and please take a look at these Pics below and report
 back if there is a missing or wrong thing.

 Thank you.


 ==Quantum  on VLAN + 3 NICs on controller node
 http://i.imgur.com/Ueh5Z.jpg
 ===

 ==Quantum  on VLAN + 2 NICs on controller node
 http://i.imgur.com/RK6X7.jpg
 ===

 ==Quantum  on GRE-tunneling + 3 NICs on controller node===
 http://i.imgur.com/1jCFC.jpg
 ===


 To make of OpenStack, the IT project of the century

 Best regards





 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Regards,
VeeraReddy.B
9959236555.
___
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] Can't access Dashboard

2012-11-09 Thread Daniel Oliveira
Hello. Anyone?


2012/11/7 Daniel Oliveira dvalbr...@gmail.com

 My bad. This is the 
 tutorialhttp://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolinI
  talked about.


 2012/11/7 Daniel Oliveira dvalbr...@gmail.com

 Hello,

 I've been following this tutorial to install openstack on a machine
 running Ubuntu Server 12.04, and on the step regarding installation of
 Horizon, well, there must be something wrong either with the tutorial or
 with the configuration files on my machine. The point is, whenever I try to
 access the GUI via browser, I get a 404, and I have no clue as to where to
 look for the error.

 Thanks in advance.

 P.S.: I would like to say a special thanks to everybody on this
 community. You have been helping me A LOT. I've learned much from you
 people.

 --
 My best regards,

 Daniel Oliveira.




 --
 My best regards,

 Daniel Oliveira.




-- 
My best regards,

Daniel Oliveira.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Can't access Dashboard

2012-11-09 Thread Ronivon Costa
Hello,

After initial installs I had seen 404 several times, but most of the times
was not due dashboard itself.
The dashboard refuses to open when you have some critical errors such as
the nova-api not starting.
Also, when glance does not work, the Images panel on the dashboard will
throw an error. This information is here only to illustrate what might be
happening with your setup.
So, go to nova.conf and verify if everything is how it should be.

Try this also:

cd /etc/init.d;
for i in `ls openstack*`
do
  service $i restart
done

What is the output? If you did run the above commands a second time, can
you confirm that all services were still running do anyone of of them died?


Can you run keystone user-list  successfully?
Can you run glance index successfully

Are you opening the dashboard using a browser in the same box you installed
Openstack or are you using a remote browser? If so, did you open port 80 in
the firewall ? (iptables)

Cheers.


On 9 November 2012 12:19, Daniel Oliveira dvalbr...@gmail.com wrote:

 Hello. Anyone?


 2012/11/7 Daniel Oliveira dvalbr...@gmail.com

 My bad. This is the 
 tutorialhttp://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolinI
  talked about.


 2012/11/7 Daniel Oliveira dvalbr...@gmail.com

 Hello,

 I've been following this tutorial to install openstack on a machine
 running Ubuntu Server 12.04, and on the step regarding installation of
 Horizon, well, there must be something wrong either with the tutorial or
 with the configuration files on my machine. The point is, whenever I try to
 access the GUI via browser, I get a 404, and I have no clue as to where to
 look for the error.

 Thanks in advance.

 P.S.: I would like to say a special thanks to everybody on this
 community. You have been helping me A LOT. I've learned much from you
 people.

 --
 My best regards,

 Daniel Oliveira.




 --
 My best regards,

 Daniel Oliveira.




 --
 My best regards,

 Daniel Oliveira.


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
--
Ronivon C. Costa
IBM Certified for Tivoli Software
ITIL V3 Certified
Tlm: (+351) 96 676 4458
Skype: ronivon.costa
BLog ((hosted in my own personal cloud infrastructure):
http://cloud0.dyndns-web.com/blog/
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios

2012-11-09 Thread Choe, Cheng-Dae
First. Ping to your metadata_ip in network router namespace.

2012년 11월 9일 금요일에 Veera Reddy님이 작성:

 Hi Skible,

 I followed the install guide

 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

 I am able to bring up guest, but unable to get ip to guest vm from network
 node.

 Also attached respective configuraion files .

 Please help in finding the issue.



 My setup :
 Controller : (10.232.91.33)

 nova-api
 nova-cert
 nova-consoleauth
 nova-scheduler
 quantum-server

 Network Node:(10.232.90.222)

 quantum-plugin-openvswitch-agent
 quantum-dhcp-agent
 quantum-l3-agent

 Compute Node: (10.232.90.62)

 quantum-plugin-openvswitch-agent
 nova-compute


 controller-nova.conf attached
 compute_node-nova.conf attached
 compute-ovs_quantum_plugin.ini attached
 network_node_ovs_quantum_plugin.ini attached


 Thanks in advance

 Regards,
 Veera.

 On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack 
 skible.openst...@gmail.com javascript:_e({}, 'cvml',
 'skible.openst...@gmail.com'); wrote:

  Hello Stackers !

 I am currently trying to create pictures of my OpenStack deployment
 architecture as a part of my OpenStack Folsom install 
 guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand
  i would like to ask a favorite.

 Could you be kind and please take a look at these Pics below and report
 back if there is a missing or wrong thing.

 Thank you.


 ==Quantum  on VLAN + 3 NICs on controller node
 http://i.imgur.com/Ueh5Z.jpg
 ===

 ==Quantum  on VLAN + 2 NICs on controller node
 http://i.imgur.com/RK6X7.jpg
 ===

 ==Quantum  on GRE-tunneling + 3 NICs on controller node===
 http://i.imgur.com/1jCFC.jpg
 ===


 To make of OpenStack, the IT project of the century

 Best regards





 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net javascript:_e({}, 'cvml',
 'openstack@lists.launchpad.net');
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




 --
 Regards,
 VeeraReddy.B
 9959236555.



-- 
Choe, Cheng-Dae
Blog: http://www.woosum.net
___
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] [OSSA 2012-017.1] Authentication bypass for image deletion (CVE-2012-4573, CVE-2012-5482) ERRATA 1

2012-11-09 Thread Russell Bryant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OpenStack Security Advisory: 2012-017 (ERRATA 1)
CVE: CVE-2012-4573, CVE-2012-5482
Date: November 9, 2012
Title: Authentication bypass for image deletion
Impact: High
Reporter: Gabe Westmaas (Rackspace)
Products: Glance
Affects: Essex, Folsom, Grizzly

Description:
Gabe Westmaas from Rackspace reported a vulnerability in Glance
authentication of image deletion requests. Authenticated users may be
able to delete arbitrary, non-protected images from Glance servers. All
Folsom and Grizzly deployments are affected. Additionally, Essex
deployments that use the delayed_delete option are also affected.

Fixes:
Grizzly:

https://github.com/openstack/glance/commit/6ab0992e5472ae3f9bef0d2ced41030655d9d2bc

https://github.com/openstack/glance/commit/b591304b8980d8aca8fa6cda9ea1621aca000c88
2012.2 (Folsom):

https://github.com/openstack/glance/commit/90bcdc5a89e350a358cf320a03f5afe99795f6f6

https://github.com/openstack/glance/commit/fc0ee7623ec59c87ac6fc671e95a9798d6f2e2c3
2012.1 (Essex):

https://github.com/openstack/glance/commit/efd7e75b1f419a52c7103c7840e24af8e5deb29d

References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4573
http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-5482
https://bugs.launchpad.net/glance/+bug/1065187
https://bugs.launchpad.net/glance/+bug/1076506

Notes:
This fix will be included in the grizzly-1 development milestone and in
a future 2012.2 (Folsom) release.

OSSA History:
2012-11-09 - Errata 1
  - Updated to reflect that the v2 API in Folsom and Grizzly was also
affected
  - Include links to fixes for the v2 API
  - Added CVE-2012-5482 for the vulnerability against the v2 API
2012-11-07 - Original Version

- -- 
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCdDmIACgkQFg9ft4s9SAa7OgCgp5T7I/jtch2w4X+M4WXiRZIk
sswAn10Oloak4YK3pyvHUlUXVPDN9C8K
=5JZI
-END PGP SIGNATURE-

___
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] Upcoming Improvements to Security Patch Handling

2012-11-09 Thread Russell Bryant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greetings,

Over the last few days there has been some unwelcome activity around
the release of OSSA-2012-017. The Essex patch wasn't ready when the
advisory was published. After that we discovered that the patches for
Folsom and Grizzly were incomplete. This points to flaws in our
process, which we are now working to correct. The vulnerability
management team has been working with the OpenStack CI team to come up
with an improved process for handling security patches.

Before a security vulnerability is publicized, all patches and
discussion about the patch have been happening in a private bug on
launchpad. There are two problems with this. The first is that
launchpad bug comments are not nearly as efficient for code review as
gerrit. Second, the patch never hits all of the testing in jenkins
until release day.

What we're planning to have is a private instance of gerrit that will be
used for security patches. We'll have much more efficient code review
there with clearer history. We will also get the patches running
through jenkins in advance of the release. This improved process should
help us be much more confident that patches for vulnerabilities are
complete and that getting them merged on release day should not run into
unexpected problems.

Thank you,

- -- 
Russell Bryant
OpenStack Vulnerability Management Team
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCdE8UACgkQFg9ft4s9SAbg7wCfcd+4perGKL2ksWwMN/EBaofB
dsEAnicOwucy8XBrVplXsZGdJX8EzdGy
=9m8m
-END PGP SIGNATURE-

___
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] Nova API does not start

2012-11-09 Thread Leander Bessa Beernaert
Hello,

I have just installed the Folsom package of Nova API and am unable to get
it to start.

Here's the error log:

2012-11-09 14:28:40 DEBUG nova.wsgi [-] Loading app metadata from
/etc/nova/api-paste.ini from (pid=25593) load_app
/usr/lib/python2.7/dist-packages/nova/wsgi.py:371
2012-11-09 14:28:40 CRITICAL nova [-] module 'nova.api.metadata.handler'
from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has
no 'Versions' attribute
2012-11-09 14:28:40 TRACE nova Traceback (most recent call last):
2012-11-09 14:28:40 TRACE nova   File /usr/bin/nova-api, line 50, in
module
2012-11-09 14:28:40 TRACE nova server = service.WSGIService(api)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/nova/service.py, line 577, in __init__
2012-11-09 14:28:40 TRACE nova self.app = self.loader.load_app(name)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/nova/wsgi.py, line 372, in load_app
2012-11-09 14:28:40 TRACE nova return deploy.loadapp(config:%s %
self.config_path, name=name)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in
loadapp
2012-11-09 14:28:40 TRACE nova return loadobj(APP, uri, name=name, **kw)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in
loadobj
2012-11-09 14:28:40 TRACE nova return context.create()
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in
create
2012-11-09 14:28:40 TRACE nova return self.object_type.invoke(self)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in
invoke
2012-11-09 14:28:40 TRACE nova **context.local_conf)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in
fix_call
2012-11-09 14:28:40 TRACE nova val = callable(*args, **kw)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/urlmap.py, line 25, in
urlmap_factory
2012-11-09 14:28:40 TRACE nova app = loader.get_app(app_name,
global_conf=global_conf)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 350, in
get_app
2012-11-09 14:28:40 TRACE nova name=name,
global_conf=global_conf).create()
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 362, in
app_context
2012-11-09 14:28:40 TRACE nova APP, name=name, global_conf=global_conf)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 450, in
get_context
2012-11-09 14:28:40 TRACE nova global_additions=global_additions)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 559, in
_pipeline_app_context
2012-11-09 14:28:40 TRACE nova APP, pipeline[-1], global_conf)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 458, in
get_context
2012-11-09 14:28:40 TRACE nova section)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 517, in
_context_from_explicit
2012-11-09 14:28:40 TRACE nova value = import_string(found_expr)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 22, in
import_string
2012-11-09 14:28:40 TRACE nova return
pkg_resources.EntryPoint.parse(x= + s).load(False)
2012-11-09 14:28:40 TRACE nova   File
/usr/lib/python2.7/dist-packages/pkg_resources.py, line 1994, in load
2012-11-09 14:28:40 TRACE nova raise ImportError(%r has no %r
attribute % (entry,attr))
2012-11-09 14:28:40 TRACE nova ImportError: module
'nova.api.metadata.handler' from
'/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no
'Versions' attribute
2012-11-09 14:28:40 TRACE nova

A similar error has been posted on Launchpad, but it has expired [1].

Any ideas?


[1] https://answers.launchpad.net/nova/+question/211675
___
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][Glance] Error starting Glance

2012-11-09 Thread Leander Bessa Beernaert
Hello all,

I'm unable to start glance. I upgraded it from Essex to Folsom on ubuntu
12.04.  It produces the following output:

2012-11-09 14:51:27 29928 DEBUG glance.common.config [-] Loading
glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app
/usr/lib/python2.7/dist-packages/glance/common/config.py:185
ERROR: Unable to load glance-api-keystone from configuration file
/etc/glance/glance-api-paste.ini.
Got: ImportError(module 'glance.common.wsgi' from
'/usr/lib/python2.7/dist-packages/glance/common/wsgi.pyc' has no
'app_factory' attribute,)


The file /etc/glance/glance-api-paste.ini exists and is the same as the one
used before the upgrade. I'm following the details mentioned here[1] and
none of them mention this particular error.

[1] http://wiki.openstack.org/ReleaseNotes/Folsom

Regards,

Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova-client Error :: Please input your password for the keyring

2012-11-09 Thread Venkatesan, Ravikumar
You may try with option –insecure –no-cache

Regards,

Ravi

From: openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net 
[mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On 
Behalf Of Trinath Somanchi
Sent: Thursday, November 08, 2012 8:39 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] nova-client Error :: Please input your password for the 
keyring

Hi-

I have written an resource extension in nova-api. and the test script runs in 
the compute-host. When the Keystone credentials are given in the script to 
created an nova-client 'Client' instance, for sending the request, I get this 
message

Please input your password for the keyring

I input the passcode that was given in the test script, it gives me the record 
string the nova-api.

I haven't faced this issue when I run the test script in the Controller 
machine. but when I run in the host machine, I'm seeing this issue.

Please help me resolve the issue.

Thanking you.

--
Regards,
--
Trinath Somanchi,


___
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 (Nov 2-9)

2012-11-09 Thread Stefano Maffulli


   Highlights of the week


 The future of Incubation and Core
 http://markmail.org/message/hmc2cmf3wycrqhpe

Incubation is currently an OpenStack project status that grants a 
promising project more access to OpenStack shared resources, especially 
in the CI, release management and QA space. The level of maturity 
reached by OpenStack requires revising the concept of 'Core project' and 
the incubation process. Join the discussion and help the Technical 
Committee form an opinion for the Foundation's Board.



 OpenStack Keystone plans for the Grizzly release
 
http://www.rhonabwy.com/wp/2012/11/08/openstack-keystone-plans-for-the-grizzly-release/

Joe Heck published the plans for Keystone over the Grizzly release 
cycle. To read after going through the state of the project slides 
http://www.slideshare.net/ccjoe/oct-2012-state-of-project-keystone.



 OpenStack Image Service -- Grizzly Planning
 http://bcwaldon.cc/2012/11/06/openstack-image-service-grizzly.html

The primary objective of Glance is to publish a catalog of virtual 
machine images. Rather than own users' image data, Glance simply tracks 
where that data resides. Glance owns the metadata provided by users. 
Brian Waldon summarizes the plans for Glance over the Grizzly release cycle.



 FOSDEM 2013: Cloud Devroom -- Call for Participation
 http://markmail.org/message/di5u4o5bskmzrti3

The organizers of the Cloud devroom at FOSDEM 2012 invite you to submit 
a session proposal. The purpose of this devroom is to serve as a meeting 
point for cloud infrastructure projects, including a unique opportunity 
for discussion and collaboration between developers from different 
projects. This devroom will be focused on open source cloud 
infrastructure projects.



   Security Advisors

 * Authentication bypass for image deletion (CVE-2012-4573,
   CVE-2012-5482) ERRATA 1 http://markmail.org/message/hn4cxgtyoxvk2mt2


   Tips and tricks

 * By Everett Toews http://blog.phymata.com/: OpenStack devstack on
   the Rackspace open cloud
   
http://blog.phymata.com/2012/11/08/openstack-devstack-on-the-rackspace-open-cloud/
 * By Jim Jiang intern of Sina SWS: How WsgiServer Deal With Requests ?
   
http://freedomhui.com/2012/11/openstack-nova-basics-to-see-how-wsgiserver-deal-with-requests-from-the-source-code/
 * By Sébastien Han http://sebastien-han.fr/: Tip: lock an instance
   against admin permissions
   
http://sebastien-han.fr/blog/2012/11/07/tip-lock-an-instance-against-admin-permission/
 * By Sébastien Han http://sebastien-han.fr/: Tip: Add a specific
   keypair to a flavor
   
http://sebastien-han.fr/blog/2012/11/05/tip-add-a-specific-keypair-to-a-flavor/
 * OpenStack Folsom Install Guide
   
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst


   Upcoming Events

 * OpenStack China Tour: Shanghai
   http://hui.csdn.net/MeetingInfo.aspx?mid=153 Nov 10, 2012 --
   Shanghai, China
 * Hungary User Group Meeting
   http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/88548072/
   Nov 13, 2012 -- Budapest, Hungary Details
   http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/88548072/
 * Swiss OpenStack user group meeting
   http://www.meetup.com/zhgeeks/events/82917082/ Nov 15, 2012 --
   Zürich, CH Details http://www.meetup.com/zhgeeks/events/82917082/
 * Australian OpenStack User Group -- Brisbane Technical Meetup
   http://aosug.openstack.org.au/ Nov 20, 2012 -- Brisbane and other
   cities Details http://aosug.openstack.org.au/
 * OpenStack China Tour: Nanjing
   http://hui.csdn.net/MeetingInfo.aspx?mid=155 Nov 24, 2012 --
   Nanjing, China Details http://hui.csdn.net/MeetingInfo.aspx?mid=155
 * OpenStack Israel http://www.meetup.com/IGTCloud/events/87103152/
   Nov 27, 2012 -- Tel Aviv, Israel Register
   http://www.meetup.com/IGTCloud/events/87103152/
 * OpenStack in action!
   http://openstackinaction3theopenrevolution.eventbrite.com/ Nov 29,
   2012 -- Paris, France Register
   http://openstackinaction3theopenrevolution.eventbrite.com/
 * EMEA OpenStack Day http://www.openstack.org/ Dec 05, 2012 --
   London Details http://www.openstack.org/


   Other news

 * Planet OpenStack http://planet.openstack.org/ has a new skin. Add
   you OpenStack blog to the Planet
 * Hui Cheng http://freedomhui.com/ reports from China OpenStack Tour
   @ Chengdu http://freedomhui.com/2012/11/chian-openstack-tour-chengdu/
 * Julien Danjou http://julien.danjou.info/blog/ reports from
   OpenStack France meetup #2
   http://julien.danjou.info/blog/2012/openstack-france-meetup-2
 * Hendrik Volkmer http://blog.hendrikvolkmer.de/: Status of the
   SmartOS OpenStack Port
   
http://blog.hendrikvolkmer.de/2012/11/06/status-of-the-smartos-openstack-port/
 * Matt Ray http://leastresistance.wordpress.com/: Chef for OpenStack
   Status 11/2
   
http://leastresistance.wordpress.com/2012/11/02/chef-for-openstack-status-112/
 * OpenStack Project Meeting: Summary
  

Re: [Openstack] [Openstack-announce] OpenStack Community Weekly Newsletter (Nov 2-9)

2012-11-09 Thread Stefano Maffulli

[addendum]


 Call For Presentations at Linux.Conf Australia - OpenStack
 MiniConf day http://firedaemon.wufoo.com/forms/z7x2p1/

Being held in January in Canberra, Australia, linux.conf.au is one of 
the foremost open source conferences in the world, and is considered the 
most prestigious in the southern hemisphere. Linux.conf.au's first ever 
OpenStack miniconf day is being held Jan 29, and the Call for 
Presentations is now open http://firedaemon.wufoo.com/forms/z7x2p1/.



On 11/09/2012 05:23 PM, Stefano Maffulli wrote:



Highlights of the week


  The future of Incubation and Core
  http://markmail.org/message/hmc2cmf3wycrqhpe

Incubation is currently an OpenStack project status that grants a 
promising project more access to OpenStack shared resources, 
especially in the CI, release management and QA space. The level of 
maturity reached by OpenStack requires revising the concept of 'Core 
project' and the incubation process. Join the discussion and help the 
Technical Committee form an opinion for the Foundation's Board.



  OpenStack Keystone plans for the Grizzly release
  
http://www.rhonabwy.com/wp/2012/11/08/openstack-keystone-plans-for-the-grizzly-release/

Joe Heck published the plans for Keystone over the Grizzly release 
cycle. To read after going through the state of the project slides 
http://www.slideshare.net/ccjoe/oct-2012-state-of-project-keystone.



  OpenStack Image Service -- Grizzly Planning
  http://bcwaldon.cc/2012/11/06/openstack-image-service-grizzly.html

The primary objective of Glance is to publish a catalog of virtual 
machine images. Rather than own users' image data, Glance simply 
tracks where that data resides. Glance owns the metadata provided by 
users. Brian Waldon summarizes the plans for Glance over the Grizzly 
release cycle.



  FOSDEM 2013: Cloud Devroom -- Call for Participation
  http://markmail.org/message/di5u4o5bskmzrti3

The organizers of the Cloud devroom at FOSDEM 2012 invite you to 
submit a session proposal. The purpose of this devroom is to serve as 
a meeting point for cloud infrastructure projects, including a unique 
opportunity for discussion and collaboration between developers from 
different projects. This devroom will be focused on open source cloud 
infrastructure projects.



Security Advisors

  * Authentication bypass for image deletion (CVE-2012-4573,
CVE-2012-5482) ERRATA 1 http://markmail.org/message/hn4cxgtyoxvk2mt2


Tips and tricks

  * By Everett Toews http://blog.phymata.com/: OpenStack devstack on
the Rackspace open cloud

http://blog.phymata.com/2012/11/08/openstack-devstack-on-the-rackspace-open-cloud/
  * By Jim Jiang intern of Sina SWS: How WsgiServer Deal With Requests
?

http://freedomhui.com/2012/11/openstack-nova-basics-to-see-how-wsgiserver-deal-with-requests-from-the-source-code/
  * By Sébastien Han http://sebastien-han.fr/: Tip: lock an instance
against admin permissions

http://sebastien-han.fr/blog/2012/11/07/tip-lock-an-instance-against-admin-permission/
  * By Sébastien Han http://sebastien-han.fr/: Tip: Add a specific
keypair to a flavor

http://sebastien-han.fr/blog/2012/11/05/tip-add-a-specific-keypair-to-a-flavor/
  * OpenStack Folsom Install Guide

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst


Upcoming Events

  * OpenStack China Tour: Shanghai
http://hui.csdn.net/MeetingInfo.aspx?mid=153 Nov 10, 2012 --
Shanghai, China
  * Hungary User Group Meeting
http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/88548072/
Nov 13, 2012 -- Budapest, Hungary Details
http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/88548072/
  * Swiss OpenStack user group meeting
http://www.meetup.com/zhgeeks/events/82917082/ Nov 15, 2012 --
Zürich, CH Details http://www.meetup.com/zhgeeks/events/82917082/
  * Australian OpenStack User Group -- Brisbane Technical Meetup
http://aosug.openstack.org.au/ Nov 20, 2012 -- Brisbane and
other cities Details http://aosug.openstack.org.au/
  * OpenStack China Tour: Nanjing
http://hui.csdn.net/MeetingInfo.aspx?mid=155 Nov 24, 2012 --
Nanjing, China Details http://hui.csdn.net/MeetingInfo.aspx?mid=155
  * OpenStack Israel http://www.meetup.com/IGTCloud/events/87103152/
Nov 27, 2012 -- Tel Aviv, Israel Register
http://www.meetup.com/IGTCloud/events/87103152/
  * OpenStack in action!
http://openstackinaction3theopenrevolution.eventbrite.com/ Nov
29, 2012 -- Paris, France Register
http://openstackinaction3theopenrevolution.eventbrite.com/
  * EMEA OpenStack Day http://www.openstack.org/ Dec 05, 2012 --
London Details http://www.openstack.org/


Other news

  * Planet OpenStack http://planet.openstack.org/ has a new skin.
Add you OpenStack blog to the Planet
  * Hui Cheng http://freedomhui.com/ reports from China OpenStack
Tour @ 

[Openstack] Strange network behavior

2012-11-09 Thread Joe Warren-Meeks
Hi all,

I've managed to get Openstack pretty much up and running as I wanted it. I
do have, however, a rather strange networking issue.

I created the network with
nova-manage network create --fixed_range_v4=10.0.41.0/24 --num_networks=1
--bridge=br41 --bridge_interface=eth0 --label=development
--gateway=10.0.41.1 --dns1=10.0.0.2 --vlan=41 --project_id=XXX

And i can boot instances fine. I've configured the default security group
to allow port 22, 80 and ICMP -1 in and I can ping from my work station to
the virtual instance ok:

joe@kaneda:~$ ping 10.0.41.3
PING 10.0.41.3 (10.0.41.3) 56(84) bytes of data.
64 bytes from 10.0.41.3: icmp_req=1 ttl=63 time=1.18 ms

And i can ping from the virt back too:
ubuntu@test:~$ ping 10.0.0.240
PING 10.0.0.240 (10.0.0.240) 56(84) bytes of data.
64 bytes from 10.0.0.240: icmp_req=1 ttl=64 time=0.713 ms


I can SSH out from the virt to a host in the outside world fine:
ubuntu@test:~$ ssh joe@X
joe@XX password:
-bash: fortune: command not found
joe@dixon:~ $

BUT I can't ssh from the virt to my workstation, nor from my workstation to
the Virt. Neither does http work.

What I am seeing in Tcpdump is a lot of incorrect cksums. This happens with
all Tcp connections.

17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.240.56791  10.0.41.3.22: Flags [S], cksum 0x3e21 (incorrect -
0x6de2), seq 2650163743, win 14600, options [mss 1460,sackOK,TS val
28089204 ecr 0,nop,wscale 6], length 0


17:12:38.585279 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP
(6), length 60)
10.0.41.3.22  10.0.0.240.56791: Flags [S.], cksum 0x3e21 (incorrect -
0xe5c5), seq 1530502549, ack 3098447117, win 14480, options [mss
1460,sackOK,TS val 340493 ecr 28089204,nop,wscale 3], length 0

Anyone come across this before?

 -- joe.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [OpenStack][Glance] Error starting Glance

2012-11-09 Thread Leander Bessa Beernaert
I've managed to fix the problem by replacing my old paste.ini files for
glance-api and glance-registry with the ones provided with the packages.


On Fri, Nov 9, 2012 at 2:55 PM, Leander Bessa Beernaert leande...@gmail.com
 wrote:

 Hello all,

 I'm unable to start glance. I upgraded it from Essex to Folsom on ubuntu
 12.04.  It produces the following output:

 2012-11-09 14:51:27 29928 DEBUG glance.common.config [-] Loading
 glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app
 /usr/lib/python2.7/dist-packages/glance/common/config.py:185
 ERROR: Unable to load glance-api-keystone from configuration file
 /etc/glance/glance-api-paste.ini.
 Got: ImportError(module 'glance.common.wsgi' from
 '/usr/lib/python2.7/dist-packages/glance/common/wsgi.pyc' has no
 'app_factory' attribute,)


 The file /etc/glance/glance-api-paste.ini exists and is the same as the
 one used before the upgrade. I'm following the details mentioned here[1]
 and none of them mention this particular error.

 [1] http://wiki.openstack.org/ReleaseNotes/Folsom

 Regards,

 Leander




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [OpenStack] Nova API does not start

2012-11-09 Thread Leander Bessa Beernaert
For anyone with the same problem, I've managed to fix my problem by
updating  my old api-paste.ini with the one provided with the
Folsom package.

Regards,

Leander


On Fri, Nov 9, 2012 at 2:42 PM, Leander Bessa Beernaert leande...@gmail.com
 wrote:

 Hello,

 I have just installed the Folsom package of Nova API and am unable to get
 it to start.

 Here's the error log:

 2012-11-09 14:28:40 DEBUG nova.wsgi [-] Loading app metadata from
 /etc/nova/api-paste.ini from (pid=25593) load_app
 /usr/lib/python2.7/dist-packages/nova/wsgi.py:371
 2012-11-09 14:28:40 CRITICAL nova [-] module 'nova.api.metadata.handler'
 from '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has
 no 'Versions' attribute
 2012-11-09 14:28:40 TRACE nova Traceback (most recent call last):
 2012-11-09 14:28:40 TRACE nova   File /usr/bin/nova-api, line 50, in
 module
 2012-11-09 14:28:40 TRACE nova server = service.WSGIService(api)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/nova/service.py, line 577, in __init__
 2012-11-09 14:28:40 TRACE nova self.app = self.loader.load_app(name)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 372, in load_app
 2012-11-09 14:28:40 TRACE nova return deploy.loadapp(config:%s %
 self.config_path, name=name)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in
 loadapp
 2012-11-09 14:28:40 TRACE nova return loadobj(APP, uri, name=name,
 **kw)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in
 loadobj
 2012-11-09 14:28:40 TRACE nova return context.create()
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in
 create
 2012-11-09 14:28:40 TRACE nova return self.object_type.invoke(self)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 144, in
 invoke
 2012-11-09 14:28:40 TRACE nova **context.local_conf)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 56, in
 fix_call
 2012-11-09 14:28:40 TRACE nova val = callable(*args, **kw)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/urlmap.py, line 25, in
 urlmap_factory
 2012-11-09 14:28:40 TRACE nova app = loader.get_app(app_name,
 global_conf=global_conf)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 350, in
 get_app
 2012-11-09 14:28:40 TRACE nova name=name,
 global_conf=global_conf).create()
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 362, in
 app_context
 2012-11-09 14:28:40 TRACE nova APP, name=name, global_conf=global_conf)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 450, in
 get_context
 2012-11-09 14:28:40 TRACE nova global_additions=global_additions)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 559, in
 _pipeline_app_context
 2012-11-09 14:28:40 TRACE nova APP, pipeline[-1], global_conf)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 458, in
 get_context
 2012-11-09 14:28:40 TRACE nova section)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 517, in
 _context_from_explicit
 2012-11-09 14:28:40 TRACE nova value = import_string(found_expr)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 22, in
 import_string
 2012-11-09 14:28:40 TRACE nova return
 pkg_resources.EntryPoint.parse(x= + s).load(False)
 2012-11-09 14:28:40 TRACE nova   File
 /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1994, in load
 2012-11-09 14:28:40 TRACE nova raise ImportError(%r has no %r
 attribute % (entry,attr))
 2012-11-09 14:28:40 TRACE nova ImportError: module
 'nova.api.metadata.handler' from
 '/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.pyc' has no
 'Versions' attribute
 2012-11-09 14:28:40 TRACE nova

 A similar error has been posted on Launchpad, but it has expired [1].

 Any ideas?


 [1] https://answers.launchpad.net/nova/+question/211675

___
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] [libvirt-users][LXC] Clarifications needed on usage of libvirt-lxc for openstack

2012-11-09 Thread Sujay M
Hi everyone,

I've some doubts regarding the usage/working of libvirt-lxc with openstack.
I'm doing a project titled Low density virtualization for Storage cloud

1. Can i use libvirt for lxc with Openstack swift alone (excluding nova,
glance and keystone)? If no what other openstack components should i use
for virtualization? (Is it necessary to install openstack nova to do
virtualization with libvirt-lxc?)

2. How virtualization for storage services work ? Any good articles.

3. I want to set up a cloud storage environment with low density
virtualization ie lxc. I'm using Openstack swift (Object storage) for
storage services. I want to virtualize this. Few resources on how i can do
this using libvirt-lxc?

-- 
Best Regards,

Sujay M
Final year B.Tech
Computer Engineering
NITK Surathkal

contact: +918971897571
___
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] Quantum Debug

2012-11-09 Thread Emilio García
Good day everyone,

I am doing a Folsom install following this guide:
https://github.com/EmilienM/openstack-folsom-guide

I only have set up the internal network and I can swpan instances but it
doesn't seem like I can connect to them at all, and they cannot find the
metadata host.

I have 3 interfaces in the cloudcontroller: the management one eth0, the vm
traffic one eth1 and a the external one eth2 which im not using for
anything at the moment.

The thing is after setting up Quantum in the cloudcontroller I cannot even
ping the compute node in eth1 any more (cc is 10.1.1.10 and cn is
10.1.1.20).

My set up was to create a Quantum network, then a subnet (10.1.1.0/24) and
then a router a attach the port to that subnet. I am using Quantum tunnels
too no VLAN.

Does anyone has any clue? Any recommendantions to debug Quantum? Of course
I cannot ping the instances neither.

My interfaces are:

ubuntu@folsom-cc01:~$ ifconfig -a
br-eth1   Link encap:Ethernet  HWaddr 00:50:56:a5:1a:40
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:176290 (176.2 KB)  TX bytes:0 (0.0 B)

br-ex Link encap:Ethernet  HWaddr 00:50:56:a5:1a:45
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:176290 (176.2 KB)  TX bytes:0 (0.0 B)

br-intLink encap:Ethernet  HWaddr ba:92:69:aa:06:40
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-tunLink encap:Ethernet  HWaddr 86:ed:48:ab:0e:40
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:3f
  inet addr:192.168.253.172  Bcast:192.168.253.255
 Mask:255.255.255.0
  inet6 addr: fe80::250:56ff:fea5:1a3f/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:7926 errors:0 dropped:0 overruns:0 frame:0
  TX packets:7677 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:3163435 (3.1 MB)  TX bytes:4062130 (4.0 MB)

eth1  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:40
  inet addr:10.1.1.10  Bcast:10.1.1.255  Mask:255.255.255.0
  inet6 addr: fe80::250:56ff:fea5:1a40/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2946 errors:0 dropped:4 overruns:0 frame:0
  TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:176780 (176.7 KB)  TX bytes:123444 (123.4 KB)

eth2  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:45
  inet6 addr: fe80::250:56ff:fea5:1a45/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:5873 errors:0 dropped:4 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:352390 (352.3 KB)  TX bytes:468 (468.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:323440 errors:0 dropped:0 overruns:0 frame:0
  TX packets:323440 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:70585630 (70.5 MB)  TX bytes:70585630 (70.5 MB)

And when I try to ping always get:

ubuntu@folsom-cc01:~$ ping 10.1.1.20
PING 10.1.1.20 (10.1.1.20) 56(84) bytes of data.
From 10.1.1.10 icmp_seq=1 Destination Host Unreachable
From 10.1.1.10 icmp_seq=2 Destination Host Unreachable
From 10.1.1.10 icmp_seq=3 Destination Host Unreachable
^C
--- 10.1.1.20 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5030ms
pipe 3

Any help is appreciated.

Cloudreach Limited is a limited company registered in England with registered 
number 06975407

The above terms reflect a potential business arrangement, are provided solely 
as a basis for further discussion, 
and are not intended to be and do not constitute a legally binding obligation. 
No legally binding obligations 
will be created, implied, or inferred until an agreement in final form is 
executed in writing by all parties involved.

This email may be confidential or privileged. If you received this 
communication by mistake, please don't 

Re: [Openstack] Strange network behavior

2012-11-09 Thread Rick Jones

On 11/09/2012 09:14 AM, Joe Warren-Meeks wrote:

What I am seeing in Tcpdump is a lot of incorrect cksums. This happens
with all Tcp connections.

17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF],
proto TCP (6), length 60)
 10.0.0.240.56791  10.0.41.3.22: Flags [S], cksum 0x3e21 (incorrect
- 0x6de2), seq 2650163743, win 14600, options [mss 1460,sackOK,TS val
28089204 ecr 0,nop,wscale 6], length 0


17:12:38.585279 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
TCP (6), length 60)
 10.0.41.3.22  10.0.0.240.56791: Flags [S.], cksum 0x3e21
(incorrect - 0xe5c5), seq 1530502549, ack 3098447117, win 14480,
options [mss 1460,sackOK,TS val 340493 ecr 28089204,nop,wscale 3], length 0

Anyone come across this before?


When a Network Interface card (NIC) offers ChecKsum Offload (CKO) in the 
outbound/transmit direction, the computation of the Layer 4 (eg TCP, 
UDP) checksum is deferred to the NIC.  You can see if a given 
interface/NIC has checksum offload, or other offloads, enabled via 
ethtool -k interface


When the packet passes the promiscuous tap on the way down the stack to 
a NIC offering CKO, the packet will be in essence unchecksummed and so 
tcpdump will report that as an incorrect checksum.  It is therefore 
possibly a false positive.  I say possibly because I just did a quick 
netperf test on my Ubuntu 11.04 workstation to see what the SYN's looked 
like there, and I didn't see an incorrect checksum warning out of 
tcpdump though I know the egress interface is offering outbound CKO, 
making me think that TCP may not bother with CKO for small segments like 
SYNchronize segments. One way to check if the incorrect checksum report 
is valid would be to run tcpdump on 10.0.41.3 as well.  And/or disable 
CKO if you see it is enabled in ethtool.


I would not have expected to see invalid checksums reported by tcpdump 
for an inbound packet though.  Might be good to cross-check with the 
netstat statistics.


There is what appears to be an inconsistency between those two TCP 
segments.  The sequence number of the SYNchronize (that 'S' in flags) 
segment from 10.0.0.240.56791 to 10.0.41.3.22 is 2650163743.  The SYN 
from 10.0.41.3.22 to 10.0.0.240.56791 though has the ACK flag set ('.') 
but the ACKnowledgement number is 3098447117 rather than what I would 
have expected - 2650163744.


FWIW, that there was a SYN-ACK sent in response to the SYN in the first 
place suggests that 10.0.41.3 received what it thought was a properly 
checksummed SYN segment.  All the more reason I suspect to take traces 
at both ends and compare the packets byte by byte.


rick jones



___
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] snapshots, backups of running VMs and compute node recovery

2012-11-09 Thread Vishvananda Ishaya
The libvirt driver has actually gotten quite good at rebuilding all of the data 
for instances. This only thing it can't do right now is redownload base images 
from glance. With current state if you simply back up the instances directory 
(usually /var/lib/nova/instances) then you can recover by bringing back the 
whole directory and doing a nova reboot uuid for each instance.

You could just stick the whole thing on an lvm and snaphot it regularly for dr. 
The _base directory can be regenerated with images from glance so you could 
also write a script to regenerate it and not have to worry about backing it up. 
The code to add to nova to make it automatically re-download the image from 
glance if it isn't there shouldn't be too bad either, which would mean you 
could safely ignore the _base directory for backups. Additionally using qcow 
images in glance and the config option `force_raw_images=False` will keep this 
directory much smaller.

Vish


On Nov 9, 2012, at 2:51 AM, Jānis Ģeņģeris janis.genge...@gmail.com wrote:

 Hello all,
 
 I would like to know the available solutions that are used regarding to 
 backing up and/or snapshotting running 
 instances on compute nodes. Documentation does not mention anything related 
 to this. With snapshots I don't mean 
 the current snapshot mechanism, that imports image of the running VM into 
 glance. I'm using KVM, but this is 
 significant for any hypervisor.
 
 Why is this important?
 Consider simple scenario when hardware on compute node fails and the node 
 goes down immediately and is not recoverable 
 in reasonable time. The images of the running instances are also lost. Shared 
 file system is not considered here as it 
 may cause IO bottlenecks and adds another layer of complexity.
 
 There have been a few discussions on the the list about this problem, but 
 none have really answered the question.
 
 The documentation speaks of disaster recovery when power loss have happened 
 and failed compute node recovery from 
 shared file system. But don't cover the case without shared file system.
 
 I can think of few solutions currently (for KVM):
 a) using LVM images for VMs, and making LVM logical volume snapshots, but 
 then the current nova snapshot mechanism
 will not work (from the docs - 'current snapshot mechanism in OpenStack 
 Compute works only with instances backed 
 with Qcow2 images');
 b) snapshot machines with OpenStack snapshotting mechanism, but this doesn't 
 fit somehow, because it has
 other goal than creating backups, will be slow and pollute the glance image 
 space;
 
 Regards
 --janis
 ___
 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] how to decide orders of multiple nic

2012-11-09 Thread Yi Sun
I have two nic cards, I want eth0 to always be connected to network1
and eth1 to always be connected to network2.
In the essex, I can do this by arrange the order of --nic options in
the nova boot command. But in the folsom,it does not seem to work
anymore, the following commands connect eth0 to the same network
nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
--flavor 2 --nic net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 --nic
net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 user-host-2
nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
--flavor 2  --nic net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 --nic
net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 user-host-2

Could someone tell me how to solve this problem?
Thanks
Yi
-- 
Android-x86
http://www.android-x86.org

___
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] Strange network behavior

2012-11-09 Thread Vishvananda Ishaya
What is the ip address of your workstation? You may be running into something 
similar to this issue:

http://lists.openstack.org/pipermail/openstack-dev/2012-September/001212.html

I suspect either:

a) Traffic not getting snatted when it should. This is usually due to 
overlapping ranges between your internal network and fixed_range

this would be fixed by limiting fixed_range in your config file to just the 
instances range: (fixed_range=10.0.41.0/24 ?)

or

b) Traffic getting snatted when it shouldn't. This is usually because your 
workstation ip is on an ip that is internally routable but not routable from 
the external network of the compute host, so it can't get back to the snatted ip

this is fixed by stopping snatting to the workstation by setting dmz_cidr to a 
value that includes your workstation network: (dmz_cidr=10.0.0.0/24 ?)

Vish

On Nov 9, 2012, at 9:14 AM, Joe Warren-Meeks joe.warren.me...@gmail.com wrote:

 Hi all,
 
 I've managed to get Openstack pretty much up and running as I wanted it. I do 
 have, however, a rather strange networking issue.
 
 I created the network with
 nova-manage network create --fixed_range_v4=10.0.41.0/24 --num_networks=1 
 --bridge=br41 --bridge_interface=eth0 --label=development --gateway=10.0.41.1 
 --dns1=10.0.0.2 --vlan=41 --project_id=XXX
 
 And i can boot instances fine. I've configured the default security group to 
 allow port 22, 80 and ICMP -1 in and I can ping from my work station to the 
 virtual instance ok:
 
 joe@kaneda:~$ ping 10.0.41.3
 PING 10.0.41.3 (10.0.41.3) 56(84) bytes of data.
 64 bytes from 10.0.41.3: icmp_req=1 ttl=63 time=1.18 ms
 
 And i can ping from the virt back too:
 ubuntu@test:~$ ping 10.0.0.240
 PING 10.0.0.240 (10.0.0.240) 56(84) bytes of data.
 64 bytes from 10.0.0.240: icmp_req=1 ttl=64 time=0.713 ms
 
 
 I can SSH out from the virt to a host in the outside world fine:
 ubuntu@test:~$ ssh joe@X
 joe@XX password: 
 -bash: fortune: command not found
 joe@dixon:~ $ 
 
 BUT I can't ssh from the virt to my workstation, nor from my workstation to 
 the Virt. Neither does http work.
 
 What I am seeing in Tcpdump is a lot of incorrect cksums. This happens with 
 all Tcp connections. 
 
 17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF], proto 
 TCP (6), length 60)
 10.0.0.240.56791  10.0.41.3.22: Flags [S], cksum 0x3e21 (incorrect - 
 0x6de2), seq 2650163743, win 14600, options [mss 1460,sackOK,TS val 28089204 
 ecr 0,nop,wscale 6], length 0
 
 
 17:12:38.585279 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP 
 (6), length 60)
 10.0.41.3.22  10.0.0.240.56791: Flags [S.], cksum 0x3e21 (incorrect - 
 0xe5c5), seq 1530502549, ack 3098447117, win 14480, options [mss 
 1460,sackOK,TS val 340493 ecr 28089204,nop,wscale 3], length 0
 
 Anyone come across this before?
 
  -- joe.
 
 ___
 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 decide orders of multiple nic

2012-11-09 Thread Vishvananda Ishaya
The api doesn't support any way to order these, so they are being returned in 
db order. In essex we retrieved each network individually, but now they are 
retrieved together. I believe the following will fix your issue:

diff --git a/nova/network/manager.py b/nova/network/manager.py
index d032fe1..4866803 100644
--- a/nova/network/manager.py
+++ b/nova/network/manager.py
@@ -1797,8 +1797,10 @@ class NetworkManager(manager.SchedulerDependentManager):
project_only=allow_none)
 
 def _get_networks_by_uuids(self, context, network_uuids):
-return self.db.network_get_all_by_uuids(context, network_uuids,
-project_only=allow_none)
+networks = self.db.network_get_all_by_uuids(context, network_uuids,
+project_only=allow_none)
+networks.sort(key=lambda x: network_uuids.index(x['uuid']))
+return networks
 
 @wrap_check_policy
 def get_vifs_by_instance(self, context, instance_id):
@@ -2114,8 +2116,10 @@ class VlanManager(RPCAllocateFixedIP, FloatingIP, 
NetworkManager):
 # NOTE(vish): Don't allow access to networks with project_id=None as
 # these are networksa that haven't been allocated to a
 # project yet.
-return self.db.network_get_all_by_uuids(context, network_uuids,
-project_only=True)
+networks = self.db.network_get_all_by_uuids(context, network_uuids,
+project_only=True)
+networks.sort(key=lambda x: network_uuids.index(x['uuid']))
+return networks
 
 def _get_networks_for_instance(self, context, instance_id, project_id,
requested_networks=None):

If you could verify that it helps and report a bug, I would be happy to propose 
it into essex and backport it.

Vish

On Nov 9, 2012, at 11:57 AM, Yi Sun beyo...@gmail.com wrote:

 I have two nic cards, I want eth0 to always be connected to network1
 and eth1 to always be connected to network2.
 In the essex, I can do this by arrange the order of --nic options in
 the nova boot command. But in the folsom,it does not seem to work
 anymore, the following commands connect eth0 to the same network
 nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
 --flavor 2 --nic net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 --nic
 net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 user-host-2
 nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
 --flavor 2  --nic net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 --nic
 net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 user-host-2
 
 Could someone tell me how to solve this problem?
 Thanks
 Yi
 -- 
 Android-x86
 http://www.android-x86.org
 
 ___
 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] Quantum Debug

2012-11-09 Thread Emilio García
Hi again,

I won't have access again to the system till Monday so I will test it then,
but a colleague of mine just told me (he is just trying the same set up
with similar issues):

when virtual machine is booting on the compute node, on the controller node
i can see the following:

22:18:39.500044 IP 10.10.10.2  10.10.10.1: GREv0, key=0x1, length 354: IP
0.0.0.0.bootpc  255.255.255.255.bootps: BOOTP/DHCP, Request from
fa:16:3e:d6:1b:12 (oui Unknown), length 300
22:18:39.500074 IP 10.10.10.1  10.10.10.2: ICMP 10.10.10.1 protocol 47
port 25944 unreachable, length 382
22:18:39.596341 IP 10.10.10.2  10.10.10.1: GREv0, key=0x1, length 90: IP6
::  ff02::1:ffd6:1b12: ICMP6, neighbor solicitation, who has
fe80::f816:3eff:fed6:1b12, length 24
22:18:39.596372 IP 10.10.10.1  10.10.10.2: ICMP 10.10.10.1 protocol 47
port 25944 unreachable, length 118
22:18:39.936583 IP 10.10.10.2  10.10.10.1: GREv0, key=0x1, length 102: IP6
::  ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s),
length 28

10.10.10.1 - controller node
10.10.10.2 - compute node

looks like controller accepts requirest, but doesn't know what to do with it

Kind regards.

On 9 November 2012 20:16, Ivan Kolodyazhny e...@e0ne.info wrote:

 Hello, Emilio.

 It looks like you use Quantum and Opwn vSwitch plugin wich used network
 namespaces. Try to pind instance from the router namespace:
 # ip netns
 # ip netnx exec qrouter-1fceeb5c-2792-4b73-b523-d7d55586a1eb ping 10.1.1.20

 Regards,
 Ivan Kolodyazhny,
 Web Developer,
 http://blog.e0ne.info/,
 http://notacash.com/,
 http://kharkivpy.org.ua/



 On Fri, Nov 9, 2012 at 8:51 PM, Emilio García 
 emilio.gar...@cloudreach.co.uk wrote:

 Good day everyone,

 I am doing a Folsom install following this guide:
 https://github.com/EmilienM/openstack-folsom-guide

 I only have set up the internal network and I can swpan instances but it
 doesn't seem like I can connect to them at all, and they cannot find the
 metadata host.

 I have 3 interfaces in the cloudcontroller: the management one eth0, the
 vm traffic one eth1 and a the external one eth2 which im not using for
 anything at the moment.

 The thing is after setting up Quantum in the cloudcontroller I cannot
 even ping the compute node in eth1 any more (cc is 10.1.1.10 and cn is
 10.1.1.20).

 My set up was to create a Quantum network, then a subnet (10.1.1.0/24)
 and then a router a attach the port to that subnet. I am using Quantum
 tunnels too no VLAN.

 Does anyone has any clue? Any recommendantions to debug Quantum? Of
 course I cannot ping the instances neither.

 My interfaces are:

 ubuntu@folsom-cc01:~$ ifconfig -a
 br-eth1   Link encap:Ethernet  HWaddr 00:50:56:a5:1a:40
   BROADCAST MULTICAST  MTU:1500  Metric:1
   RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:176290 (176.2 KB)  TX bytes:0 (0.0 B)

 br-ex Link encap:Ethernet  HWaddr 00:50:56:a5:1a:45
   BROADCAST MULTICAST  MTU:1500  Metric:1
   RX packets:2938 errors:0 dropped:8 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:176290 (176.2 KB)  TX bytes:0 (0.0 B)

 br-intLink encap:Ethernet  HWaddr ba:92:69:aa:06:40
   BROADCAST MULTICAST  MTU:1500  Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 br-tunLink encap:Ethernet  HWaddr 86:ed:48:ab:0e:40
   BROADCAST MULTICAST  MTU:1500  Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 eth0  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:3f
   inet addr:192.168.253.172  Bcast:192.168.253.255
  Mask:255.255.255.0
   inet6 addr: fe80::250:56ff:fea5:1a3f/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:7926 errors:0 dropped:0 overruns:0 frame:0
   TX packets:7677 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:3163435 (3.1 MB)  TX bytes:4062130 (4.0 MB)

 eth1  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:40
   inet addr:10.1.1.10  Bcast:10.1.1.255  Mask:255.255.255.0
   inet6 addr: fe80::250:56ff:fea5:1a40/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:2946 errors:0 dropped:4 overruns:0 frame:0
   TX packets:2934 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:176780 (176.7 KB)  TX bytes:123444 (123.4 KB)

 eth2  Link encap:Ethernet  HWaddr 00:50:56:a5:1a:45
  

[Openstack] [Doc] Folsom release branch

2012-11-09 Thread Anne Gentle
Hi all -
We plan to have a Folsom branch release of the documentation in the
next few days. The CI Team is doing the work to cut a stable/folsom
branch for openstack-manuals.

To make it, I followed the steps in
http://wiki.openstack.org/Documentation/Release.

So from now on, the master branch is for Grizzly, and the
stable/folsom branch is for Folsom. Typically we back port docs to
stable/folsom for a long while. Instructions for how to do so are
found at 
http://wiki.openstack.org/Documentation/HowTo#How_to_a_cherry-pick_a_change_to_a_stable_branch.
I'll update the page to reflect the stable/folsom rather than
stable/essex examples after the branch is ready.

Thanks all for getting to this point!
Anne

___
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 decide orders of multiple nic

2012-11-09 Thread Yi Sun
Thanks, will these changes ever be added back to the later releases?
Yi

On Fri, Nov 9, 2012 at 1:02 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
 The api doesn't support any way to order these, so they are being returned in 
 db order. In essex we retrieved each network individually, but now they are 
 retrieved together. I believe the following will fix your issue:

 diff --git a/nova/network/manager.py b/nova/network/manager.py
 index d032fe1..4866803 100644
 --- a/nova/network/manager.py
 +++ b/nova/network/manager.py
 @@ -1797,8 +1797,10 @@ class 
 NetworkManager(manager.SchedulerDependentManager):
 project_only=allow_none)

  def _get_networks_by_uuids(self, context, network_uuids):
 -return self.db.network_get_all_by_uuids(context, network_uuids,
 -project_only=allow_none)
 +networks = self.db.network_get_all_by_uuids(context, network_uuids,
 +
 project_only=allow_none)
 +networks.sort(key=lambda x: network_uuids.index(x['uuid']))
 +return networks

  @wrap_check_policy
  def get_vifs_by_instance(self, context, instance_id):
 @@ -2114,8 +2116,10 @@ class VlanManager(RPCAllocateFixedIP, FloatingIP, 
 NetworkManager):
  # NOTE(vish): Don't allow access to networks with project_id=None as
  # these are networksa that haven't been allocated to a
  # project yet.
 -return self.db.network_get_all_by_uuids(context, network_uuids,
 -project_only=True)
 +networks = self.db.network_get_all_by_uuids(context, network_uuids,
 +project_only=True)
 +networks.sort(key=lambda x: network_uuids.index(x['uuid']))
 +return networks

  def _get_networks_for_instance(self, context, instance_id, project_id,
 requested_networks=None):

 If you could verify that it helps and report a bug, I would be happy to 
 propose it into essex and backport it.

 Vish

 On Nov 9, 2012, at 11:57 AM, Yi Sun beyo...@gmail.com wrote:

 I have two nic cards, I want eth0 to always be connected to network1
 and eth1 to always be connected to network2.
 In the essex, I can do this by arrange the order of --nic options in
 the nova boot command. But in the folsom,it does not seem to work
 anymore, the following commands connect eth0 to the same network
 nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
 --flavor 2 --nic net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 --nic
 net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 user-host-2
 nova --no-cache boot --image db64c7ed-3496-499e-a097-73362cb5f447
 --flavor 2  --nic net-id=12e964db-14e3-4e85-98c8-45987c89e1d1 --nic
 net-id=ff899ad7-a0c2-4e46-a0a4-bf086eda9164 user-host-2

 Could someone tell me how to solve this problem?
 Thanks
 Yi
 --
 Android-x86
 http://www.android-x86.org

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Android-x86
http://www.android-x86.org

___
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 decide orders of multiple nic

2012-11-09 Thread Vishvananda Ishaya
Pardon me, the bottom line should have said, propose it into trunk and backport 
it (into folsom/stable). So the answer to your question is yes.

Vish

On Nov 9, 2012, at 3:22 PM, Yi Sun beyo...@gmail.com wrote:

 Thanks, will these changes ever be added back to the later releases?
 Yi


___
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] [Tempest] unable to run subset of tests via nosetests

2012-11-09 Thread Stef T
Hey Everyone,
So, I was trying to run only a single test from Tempest, and I
naively tried the usual nosetest syntax of;

nosetests -v
tempest.tests.compute.servers.test_server_actions:ServerActionsTestBase.test_resize_server_confirm

No dice, so, I then tried the slightly more bulky but still
relatively quick;

nosetests -v tempest.tests.compute.servers.test_server_actions

And I got 8 errors. I got this down to 4 by moving the __init__.py
from tempest/tests/compute into tempest/tests/compure/servers but, this
can't be right. Can it ? Is Tempest not designed to run a single
functional test or a subset ? I find this hard to believe, and I pray I
am doing something 'duh'. Python 2.7.2, tempest -TRUNK.
   
Regards
S.
___
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] [Tempest] unable to run subset of tests via nosetests

2012-11-09 Thread Venkatesan, Ravikumar
To run a single test from Tempest:

~/openstack_projects/tempest$ nosetests -sv 
tempest/tests/compute/flavors/test_flavors.py
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker ... ok
The list of flavors should be filtered by disk space ... ok
The list of flavors should be filtered by RAM ... ok
Only the expected number of flavors should be returned ... ok
The list of flavors should start from the provided marker ... ok
Detailed list of all flavors should contain the expected flavor ... ok
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker ... ok
The list of flavors should be filtered by disk space ... ok
The list of flavors should be filtered by RAM ... ok
Only the expected number of flavors should be returned ... ok
The list of flavors should start from the provided marker ... ok
Detailed list of all flavors should contain the expected flavor ... ok

--
Ran 26 tests in 7.230s

OK

Regards,

Ravi

From: openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net 
[mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On 
Behalf Of Stef T
Sent: Friday, November 09, 2012 4:06 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [Tempest] unable to run subset of tests via nosetests

Hey Everyone,
So, I was trying to run only a single test from Tempest, and I naively 
tried the usual nosetest syntax of;

nosetests -v 
tempest.tests.compute.servers.test_server_actions:ServerActionsTestBase.test_resize_server_confirm

No dice, so, I then tried the slightly more bulky but still relatively 
quick;

nosetests -v tempest.tests.compute.servers.test_server_actions

And I got 8 errors. I got this down to 4 by moving the __init__.py from 
tempest/tests/compute into tempest/tests/compure/servers but, this can't be 
right. Can it ? Is Tempest not designed to run a single functional test or a 
subset ? I find this hard to believe, and I pray I am doing something 'duh'. 
Python 2.7.2, tempest -TRUNK.

Regards
S.
___
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] [Tempest] unable to run subset of tests via nosetests

2012-11-09 Thread Venkatesan, Ravikumar
Test_server_actions.py

~/openstack_projects/tempest$ nosetests -sv 
tempest/tests/compute/servers/test_server_actions.py
The server's password should be set to the provided password ... SKIP: Change 
password not available.
Negative Test: The server reboot on non existent server should return ... ok
The server should be power cycled ... ok
The server should be signaled to reboot gracefully ... SKIP: Until bug 1014647 
is dealt with.
Negative test: The server rebuild for a non existing server should not ... ok
The server should be rebuilt using the provided image and data ... ok
The server's RAM and disk space should be modified to that of ... SKIP: Resize 
not available.
The server's RAM and disk space should return to its original ... SKIP: Resize 
not available.
The server's password should be set to the provided password ... SKIP: Change 
password not available.
Negative Test: The server reboot on non existent server should return ... ok
The server should be power cycled ... ok
The server should be signaled to reboot gracefully ... SKIP: Until bug 1014647 
is dealt with.
Negative test: The server rebuild for a non existing server should not ... ok
The server should be rebuilt using the provided image and data ... ok
The server's RAM and disk space should be modified to that of ... SKIP: Resize 
not available.
The server's RAM and disk space should return to its original ... SKIP: Resize 
not available.

--
Ran 16 tests in 127.553s

OK (SKIP=8)

Regards,

Ravi

From: openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net 
[mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On 
Behalf Of Venkatesan, Ravikumar
Sent: Friday, November 09, 2012 4:13 PM
To: Stef T; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Tempest] unable to run subset of tests via nosetests

To run a single test from Tempest:

~/openstack_projects/tempest$ nosetests -sv 
tempest/tests/compute/flavors/test_flavors.py
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker ... ok
The list of flavors should be filtered by disk space ... ok
The list of flavors should be filtered by RAM ... ok
Only the expected number of flavors should be returned ... ok
The list of flavors should start from the provided marker ... ok
Detailed list of all flavors should contain the expected flavor ... ok
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker ... ok
The list of flavors should be filtered by disk space ... ok
The list of flavors should be filtered by RAM ... ok
Only the expected number of flavors should be returned ... ok
The list of flavors should start from the provided marker ... ok
Detailed list of all flavors should contain the expected flavor ... ok

--
Ran 26 tests in 7.230s

OK

Regards,

Ravi

From: 
openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.netmailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net
 [mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On 
Behalf Of Stef T
Sent: Friday, November 09, 2012 4:06 PM
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: [Openstack] [Tempest] unable to run subset of tests via nosetests

Hey Everyone,
So, I was trying to run only a single test from Tempest, and I naively 
tried the usual nosetest syntax of;

nosetests -v 
tempest.tests.compute.servers.test_server_actions:ServerActionsTestBase.test_resize_server_confirm

No dice, so, I then tried the slightly more bulky but still relatively 
quick;

nosetests -v tempest.tests.compute.servers.test_server_actions

And I got 8 errors. I got this down to 4 by moving the __init__.py from 
tempest/tests/compute into tempest/tests/compure/servers but, this can't be 
right. Can it ? Is Tempest not designed to run a single functional test or a 
subset ? I find this hard to believe, and I pray I am doing something 'duh'. 
Python 2.7.2, tempest -TRUNK.

Regards
S.
___

Re: [Openstack] [Tempest] unable to run subset of tests via nosetests

2012-11-09 Thread Stef T

Hey Ravi,
Cool, and how do you run (say) only test_reboot_server_hard from
ServerActionsTestBase ?

Whenever I try, I get;

stack@DevStack:~/tempest$ nosetests -sv
tempest.tests.compute.servers.test_server_actions.py:ServerActionsTestBase.test_reboot_server_hard
The server should be power cycled ... ERROR

==
ERROR: The server should be power cycled
--
Traceback (most recent call last):
  File /usr/lib/pymodules/python2.7/nose/case.py, line 371, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File /usr/lib/pymodules/python2.7/nose/util.py, line 478, in try_run
return func()
  File
/opt/stack/tempest/tempest/tests/compute/servers/test_server_actions.py,
line 39, in setUp
resp, server = self.client.create_server(self.name,
AttributeError: 'ServerActionsTestBase' object has no attribute 'client'
  begin captured logging  
tempest.config: INFO: Using tempest config file
/opt/stack/tempest/etc/tempest.conf
tempest.tests.compute: DEBUG: Entering tempest.tests.compute.setup_package
-  end captured logging  -


On 11/09/2012 07:16 PM, Venkatesan, Ravikumar wrote:

 Test_server_actions.py

  

 ~/openstack_projects/tempest$ nosetests -sv
 tempest/tests/compute/servers/test_server_actions.py

 The server's password should be set to the provided password ... SKIP:
 Change password not available.

 Negative Test: The server reboot on non existent server should return
 ... ok

 The server should be power cycled ... ok

 The server should be signaled to reboot gracefully ... SKIP: Until bug
 1014647 is dealt with.

 Negative test: The server rebuild for a non existing server should not
 ... ok

 The server should be rebuilt using the provided image and data ... ok

 The server's RAM and disk space should be modified to that of ...
 SKIP: Resize not available.

 The server's RAM and disk space should return to its original ...
 SKIP: Resize not available.

 The server's password should be set to the provided password ... SKIP:
 Change password not available.

 Negative Test: The server reboot on non existent server should return
 ... ok

 The server should be power cycled ... ok

 The server should be signaled to reboot gracefully ... SKIP: Until bug
 1014647 is dealt with.

 Negative test: The server rebuild for a non existing server should not
 ... ok

 The server should be rebuilt using the provided image and data ... ok

 The server's RAM and disk space should be modified to that of ...
 SKIP: Resize not available.

 The server's RAM and disk space should return to its original ...
 SKIP: Resize not available.

  

 --

 Ran 16 tests in 127.553s

  

 OK (SKIP=8)

  

 Regards,

  

 Ravi

  

 *From:*openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net
 [mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net]
 *On Behalf Of *Venkatesan, Ravikumar
 *Sent:* Friday, November 09, 2012 4:13 PM
 *To:* Stef T; openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] [Tempest] unable to run subset of tests via
 nosetests

  

 To run a single test from Tempest:

  

 ~/openstack_projects/tempest$ nosetests -sv
 tempest/tests/compute/flavors/test_flavors.py

 The expected flavor details should be returned ... ok

 Ensure 404 returned for non-existant flavor ID ... ok

 flavor details are not returned for non existant flavors ... ok

 List of all flavors should contain the expected flavor ... ok

 The detailed list of flavors should be filtered by disk space ... ok

 The detailed list of flavors should be filtered by RAM ... ok

 Only the expected number of flavors (detailed) should be returned ... ok

 The list of flavors should start from the provided marker ... ok

 The list of flavors should be filtered by disk space ... ok

 The list of flavors should be filtered by RAM ... ok

 Only the expected number of flavors should be returned ... ok

 The list of flavors should start from the provided marker ... ok

 Detailed list of all flavors should contain the expected flavor ... ok

 The expected flavor details should be returned ... ok

 Ensure 404 returned for non-existant flavor ID ... ok

 flavor details are not returned for non existant flavors ... ok

 List of all flavors should contain the expected flavor ... ok

 The detailed list of flavors should be filtered by disk space ... ok

 The detailed list of flavors should be filtered by RAM ... ok

 Only the expected number of flavors (detailed) should be returned ... ok

 The list of flavors should start from the provided marker ... ok

 The list of flavors should be filtered by disk space ... ok

 The list of flavors should be filtered by RAM ... ok

 Only the expected number of flavors should be returned ... ok

 The list of flavors 

Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios

2012-11-09 Thread Veera Reddy
Hi,

In my setup metadata_ip is controller ip.
I am able to ping to controller from network node.

Regards,
Veera.

On Fri, Nov 9, 2012 at 7:02 PM, Choe, Cheng-Dae white...@gmail.com wrote:


 First. Ping to your metadata_ip in network router namespace.

 2012년 11월 9일 금요일에 Veera Reddy님이 작성:

 Hi Skible,

 I followed the install guide

 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

 I am able to bring up guest, but unable to get ip to guest vm from
 network node.

 Also attached respective configuraion files .

 Please help in finding the issue.



 My setup :
 Controller : (10.232.91.33)

 nova-api
 nova-cert
 nova-consoleauth
 nova-scheduler
 quantum-server

 Network Node:(10.232.90.222)

 quantum-plugin-openvswitch-agent
 quantum-dhcp-agent
 quantum-l3-agent

 Compute Node: (10.232.90.62)

 quantum-plugin-openvswitch-agent
 nova-compute


 controller-nova.conf attached
 compute_node-nova.conf attached
 compute-ovs_quantum_plugin.ini attached
 network_node_ovs_quantum_plugin.ini attached


 Thanks in advance

 Regards,
 Veera.

 On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack 
 skible.openst...@gmail.com wrote:

  Hello Stackers !

 I am currently trying to create pictures of my OpenStack deployment
 architecture as a part of my OpenStack Folsom install 
 guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand
  i would like to ask a favorite.

 Could you be kind and please take a look at these Pics below and report
 back if there is a missing or wrong thing.

 Thank you.


 ==Quantum  on VLAN + 3 NICs on controller node
 http://i.imgur.com/Ueh5Z.jpg
 ===

 ==Quantum  on VLAN + 2 NICs on controller node
 http://i.imgur.com/RK6X7.jpg
 ===

 ==Quantum  on GRE-tunneling + 3 NICs on controller node===
 http://i.imgur.com/1jCFC.jpg
 ===


 To make of OpenStack, the IT project of the century

 Best regards





 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




 --
 Regards,
 VeeraReddy.B
 9959236555.



 --
 Choe, Cheng-Dae
 Blog: http://www.woosum.net




-- 
Regards,
VeeraReddy.B
9959236555.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_swift_trunk #15

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/15/Project:precise_grizzly_swift_trunkDate of build:Fri, 09 Nov 2012 08:01:21 -0500Build duration:4 min 23 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesuse Host: for location rewritesby mikeeditswift/common/swob.pyedittest/unit/common/test_swob.pycharset for default responsesby mikeedittest/unit/common/test_swob.pyeditswift/common/swob.pyConsole Output[...truncated 2831 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 106Source-Version: 1.7.6+git201211090801~precise-0ubuntu1Space: 17652Status: attemptedVersion: 1.7.6+git201211090801~precise-0ubuntu1Finished at 20121109-0805Build needed 00:01:46, 17652k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211090801~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211090801~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-grizzly-proposed /tmp/tmp_GwiS4/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmp_GwiS4/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-grizzly --forcedch -b -D precise --newversion 1.7.6+git201211090801~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [65554ea] charset for default responsesdch -a [188f834] use Host: for location rewritesdch -a [5e4ca30] Fixed swift-bench when using -b and a conf filedch -a [f46a4d8] Fixed bugs with internal client and object expirerdch -a [d61dfb3] Use computed size on object PUT, not fstat.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211090801~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A swift_1.7.6+git201211090801~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', 'swift_1.7.6+git201211090801~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', 'swift_1.7.6+git201211090801~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: precise_grizzly_quantum_trunk #24

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/24/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 08:04:19 -0500Build duration:2 min 43 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesEnsure that the anyjson version is correct.by gkottonedittools/pip-requiresFix openssl zombiesby gkottoneditbin/quantum-serverClean up executable modulesby zhongyue.naheditquantum/agent/dhcp_agent.pyeditquantum/plugins/cisco/client/cli.pyeditquantum/plugins/cisco/run_tests.pyeditquantum/plugins/cisco/services/service_insertion.pyeditquantum/agent/l3_agent.pyeditquantum/debug/shell.pyClean up quantum.api.v2.validatorsby zhongyue.naheditquantum/api/v2/attributes.pyConsole Output[...truncated 2525 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ad4cfea2-0c68-425b-a76f-2faa3198e74e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ad4cfea2-0c68-425b-a76f-2faa3198e74e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmp33C0dB/quantummk-build-deps -i -r -t apt-get -y /tmp/tmp33C0dB/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211090804~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [c89d71f] Clean up quantum.api.v2.validatorsdch -a [f9cadb9] Clean up executable modulesdch -a [db0846d] Fix openssl zombiesdch -a [a5e6ebd] Remove nova code from Quantum Cisco Plugindch -a [3d07b33] Use isinstance for _validate_booleandebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ad4cfea2-0c68-425b-a76f-2faa3198e74e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ad4cfea2-0c68-425b-a76f-2faa3198e74e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_keystone_trunk #15

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/15/Project:precise_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 08:01:21 -0500Build duration:6 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImprove feedback on test failureby dolph.mathewsedittests/test_sql_upgrade.pyFix default port for identity.internalURLby apevecedittools/sample_data.shConsole Output[...truncated 14607 lines...]Machine Architecture: amd64Package: keystonePackage-Time: 175Source-Version: 2013.1+git201211090801~precise-0ubuntu1Space: 11136Status: attemptedVersion: 2013.1+git201211090801~precise-0ubuntu1Finished at 20121109-0807Build needed 00:02:55, 11136k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211090801~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211090801~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-grizzly-proposed /tmp/tmpMSEfZq/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpMSEfZq/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211090801~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172dch -a [0478276] SQL upgrade test.dch -a [2eea455] Include 'extra' attributes twice (bug 1076120)debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211090801~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201211090801~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', 'keystone_2013.1+git201211090801~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', 'keystone_2013.1+git201211090801~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 Fixed: precise_grizzly_python-keystoneclient_trunk #7

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/7/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Fri, 09 Nov 2012 08:07:02 -0500Build duration:3 min 34 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40Changesremoving repeat attempt at authorization in clientby heckjaddkeystoneclient/access.pyeditkeystoneclient/v2_0/client.pyedittests/test_http.pyeditkeystoneclient/v2_0/tenants.pyaddtests/test_access.pyeditkeystoneclient/v2_0/tokens.pyeditkeystoneclient/shell.pyedittests/v2_0/test_auth.pyeditREADME.rsteditkeystoneclient/client.pyConsole Output[...truncated 2016 lines...]INFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_source.changes']gpg: Signature made Fri Nov  9 08:08:40 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Fri Nov  9 08:08:40 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpMNpo40/python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpMNpo40/python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1.dsc: done.  Uploading python-keystoneclient_0.1.3.64+git201211090807~precise.orig.tar.gz: done.  Uploading python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1.debian.tar.gz: done.  Uploading python-keystoneclient_0.1.3.64+git201211090807~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', 'python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-keystoneclient/python-keystoneclient_0.1.3.61+git201211061534~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly']Pushed up to revision 35.INFO:root:Storing current commit for next build: f1cc3cfc42db902589785320547204388aa170a3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly-proposed /tmp/tmpMNpo40/python-keystoneclientmk-build-deps -i -r -t apt-get -y /tmp/tmpMNpo40/python-keystoneclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0fddc40e88f7697d8a4c25dcd97c645f768786ed..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly --forcedch -b -D precise --newversion 1:0.1.3.64+git201211090807~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [f1cc3cf] removing repeat attempt at authorization in clientdch -a [b75c2d6] Update --os-* error messagesdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-keystoneclient_0.1.3.64+git201211090807~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-keystoneclient/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: 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 #7

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/7/Project:precise_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 08:10:37 -0500Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUnit test remaining glance-replicator methods.by mikaleditglance/tests/unit/test_glance_replicator.pyeditbin/glance-replicatorConsole Output[...truncated 2233 lines...]Hunk #9 succeeded at 361 (offset 3 lines).Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-283f181e-b550-4313-92eb-492f7eeeb6ca', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-283f181e-b550-4313-92eb-492f7eeeb6ca', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmpQdPpbi/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpQdPpbi/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211090810~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [b591304] Ensure authorization before deleting from storedch -a [231de61] Port uuidutils to Glancedch -a [6ab0992] Delete from store after registry delete.dch -a [4c80ec1] Unit test remaining glance-replicator methods.dch -a [9dae32d] Use openstack common timeutils in simple db apidebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-283f181e-b550-4313-92eb-492f7eeeb6ca', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-283f181e-b550-4313-92eb-492f7eeeb6ca', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_horizon_trunk #9

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_horizon_trunk/9/Project:precise_grizzly_horizon_trunkDate of build:Fri, 09 Nov 2012 08:11:54 -0500Build duration:3 min 4 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesChanged Delete volume success message textby t.trifonoveditopenstack_dashboard/dashboards/project/images_and_snapshots/volume_snapshots/tests.pyeditopenstack_dashboard/test/test_data/nova_data.pyeditopenstack_dashboard/dashboards/project/volumes/tests.pyeditopenstack_dashboard/dashboards/project/volumes/tables.pyeditopenstack_dashboard/dashboards/project/images_and_snapshots/volume_snapshots/tables.pyWhen editing an image, correctly set the is_public checkbox.by jpichoneditopenstack_dashboard/dashboards/project/images_and_snapshots/images/tests.pyeditopenstack_dashboard/dashboards/project/images_and_snapshots/images/views.pyConsole Output[...truncated 2703 lines...]Perhaps you used the wrong -p or --strip option?The text leading up to this was:--|Index: horizon-2012.2/horizon/tests/testsettings.py|===|--- horizon-2012.2.orig/horizon/tests/testsettings.py	2012-08-23 18:52:34.647973328 -0700|+++ horizon-2012.2/horizon/tests/testsettings.py	2012-08-23 18:54:36.615968847 -0700--No file to patch.  Skipping patch.1 out of 1 hunk ignoredPatch fix-ubuntu-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5609f191-cb12-4cb7-918a-7884134fef0a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5609f191-cb12-4cb7-918a-7884134fef0a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/precise-grizzly-proposed /tmp/tmpoiEPmr/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpoiEPmr/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/horizon/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211090811~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [89904e6] Remove superfluous slash from admin usage.csv templatedch -a [e202400] When editing an image, correctly set the 'is_public' checkbox.dch -a [e837b10] Changed "Delete volume" success message textdch -a [82c19ae] Flavor Extra Specs support.dch -a [92510f1] Wrap a project list call with exception handler.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5609f191-cb12-4cb7-918a-7884134fef0a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5609f191-cb12-4cb7-918a-7884134fef0a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


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

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/14/Project:raring_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 08:17:12 -0500Build duration:7 min 16 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImprove feedback on test failureby dolph.mathewsedittests/test_sql_upgrade.pyFix default port for identity.internalURLby apevecedittools/sample_data.shConsole Output[...truncated 44406 lines...]Status: attemptedVersion: 2013.1+git201211090817~raring-0ubuntu1Finished at 20121109-0824Build needed 00:03:30, 11280k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211090817~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211090817~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/raring-grizzly-proposed /tmp/tmppo3URF/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmppo3URF/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log df148a09fc1c7d44f2134a2dc6566ef1dbe772df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211090817~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172dch -a [0478276] SQL upgrade test.dch -a [2eea455] Include 'extra' attributes twice (bug 1076120)dch -a [fddacf7] bug 1069945: generate certs for the tests in one placedch -a [ef65550] monkeypatch cms Popendch -a [5761a2c] HACKING compliance: consistent use of 'except'dch -a [3733170] Fixed typo in log messagedch -a [399cb4c] Identity API v3 Config, Routers, Controllersdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211090817~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201211090817~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', 'keystone_2013.1+git201211090817~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', 'keystone_2013.1+git201211090817~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 Failure: raring_grizzly_glance_trunk #8

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/8/Project:raring_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 08:14:58 -0500Build duration:11 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUnit test remaining glance-replicator methods.by mikaleditglance/tests/unit/test_glance_replicator.pyeditbin/glance-replicatorConsole Output[...truncated 10353 lines...]INFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201211090815~raring-0ubuntu1_source.changes']gpg: Signature made Fri Nov  9 08:18:22 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Fri Nov  9 08:18:22 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmp3JiW2O/glance_2013.1+git201211090815~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp3JiW2O/glance_2013.1+git201211090815~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2013.1+git201211090815~raring-0ubuntu1.dsc: 550 ~openstack-ubuntu-testing/grizzly-trunk-testing/ubuntu/glance_2013.1+git201211090815~raring-0ubuntu1.dsc: No such file or directory.Note: This error might indicate a problem with your passive_ftp setting.  Please consult dput.cf(5) for details on this configuration option.ERROR:root:Error occurred during package creation/build: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201211090815~raring-0ubuntu1_source.changes']' returned non-zero exit status 1ERROR:root:Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201211090815~raring-0ubuntu1_source.changes']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/raring-grizzly-proposed /tmp/tmp3JiW2O/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp3JiW2O/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+git201211090815~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+git201211090815~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1+git201211090815~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1+git201211090815~raring-0ubuntu1_source.changesTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201211090815~raring-0ubuntu1_source.changes']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201211090815~raring-0ubuntu1_source.changes']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #55

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/55/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 08:17:57 -0500Build duration:19 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesmake diagnostics workable for libvirt with Xenby berendteditnova/virt/libvirt/driver.pyConsole Output[...truncated 31025 lines...]Good signature on /tmp/tmpPjafQ2/nova_2013.1+git201211090818~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpPjafQ2/nova_2013.1+git201211090818~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading nova_2013.1+git201211090818~precise-0ubuntu1.dsc: 550 ~openstack-ubuntu-testing/grizzly-trunk-testing/ubuntu/nova_2013.1+git201211090818~precise-0ubuntu1.dsc: No such file or directory.Note: This error might indicate a problem with your passive_ftp setting.  Please consult dput.cf(5) for details on this configuration option.ERROR:root:Error occurred during package creation/build: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090818~precise-0ubuntu1_source.changes']' returned non-zero exit status 1ERROR:root:Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090818~precise-0ubuntu1_source.changes']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpPjafQ2/novamk-build-deps -i -r -t apt-get -y /tmp/tmpPjafQ2/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 46d7a40413373d0c150b48004884ce33227b4d7e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211090818~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [0406d1f] make diagnostics workable for libvirt with Xendch -a [81767e7] Send instance_type to resize_instance.dch -a [0d51778] Remove instance_type db lookup in prep_resize.dch -a [1a3ac5a] Send all aggregate data to remove_aggregate_host.dch -a [8935c3b] Limit formatting routes when adding resourcesdch -a [cfa8444] Fix verification in test_api_samples.pydch -a [7af5bdd] Make HostManager.get_all_host_states() return an iteratordebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211090818~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211090818~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211090818~precise-0ubuntu1_source.changesTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090818~precise-0ubuntu1_source.changes']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090818~precise-0ubuntu1_source.changes']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #57

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/57/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 08:24:29 -0500Build duration:29 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesmake diagnostics workable for libvirt with Xenby berendteditnova/virt/libvirt/driver.pyConsole Output[...truncated 32309 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpFSLMrA/nova_2013.1+git201211090825~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpFSLMrA/nova_2013.1+git201211090825~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):Directory to upload to does not exist.ERROR:root:Error occurred during package creation/build: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090825~raring-0ubuntu1_source.changes']' returned non-zero exit status 1ERROR:root:Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090825~raring-0ubuntu1_source.changes']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpFSLMrA/novamk-build-deps -i -r -t apt-get -y /tmp/tmpFSLMrA/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 46d7a40413373d0c150b48004884ce33227b4d7e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211090825~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [0406d1f] make diagnostics workable for libvirt with Xendch -a [81767e7] Send instance_type to resize_instance.dch -a [0d51778] Remove instance_type db lookup in prep_resize.dch -a [1a3ac5a] Send all aggregate data to remove_aggregate_host.dch -a [8935c3b] Limit formatting routes when adding resourcesdch -a [cfa8444] Fix verification in test_api_samples.pydch -a [7af5bdd] Make HostManager.get_all_host_states() return an iteratordebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211090825~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211090825~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211090825~raring-0ubuntu1_source.changesTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090825~raring-0ubuntu1_source.changes']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'nova_2013.1+git201211090825~raring-0ubuntu1_source.changes']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #56

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/56/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 10:31:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAnother case of dictionary accessby rbryanteditnova/tests/test_image_utils.pyeditnova/virt/libvirt/utils.pyMake utils.mkfs() set label when fs=swapby notsueditnova/utils.pyeditnova/tests/test_utils.pyConsole Output[...truncated 31053 lines...]INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmp8e3pTH/novamk-build-deps -i -r -t apt-get -y /tmp/tmp8e3pTH/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 46d7a40413373d0c150b48004884ce33227b4d7e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091032~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [3001c79] Make utils.mkfs() set label when fs=swapdch -a [528add2] Another case of dictionary accessdch -a [0406d1f] make diagnostics workable for libvirt with Xendch -a [81767e7] Send instance_type to resize_instance.dch -a [0d51778] Remove instance_type db lookup in prep_resize.dch -a [1a3ac5a] Send all aggregate data to remove_aggregate_host.dch -a [8935c3b] Limit formatting routes when adding resourcesdch -a [cfa8444] Fix verification in test_api_samples.pydch -a [7af5bdd] Make HostManager.get_all_host_states() return an iteratordebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091032~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211091032~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091032~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211091032~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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_quantum_trunk #25

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/25/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 12:01:21 -0500Build duration:1 min 57 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesExplicitly include versioninfo in tarball.by dprinceeditMANIFEST.inConsole Output[...truncated 2526 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f057acb0-0a8e-45e3-9373-606fb2da4af6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f057acb0-0a8e-45e3-9373-606fb2da4af6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpwQzBvs/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpwQzBvs/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [014e0b4] Explicitly include versioninfo in tarball.dch -a [c89d71f] Clean up quantum.api.v2.validatorsdch -a [f9cadb9] Clean up executable modulesdch -a [db0846d] Fix openssl zombiesdch -a [a5e6ebd] Remove nova code from Quantum Cisco Plugindebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f057acb0-0a8e-45e3-9373-606fb2da4af6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f057acb0-0a8e-45e3-9373-606fb2da4af6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #57

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/57/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:01:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesclean up dnsdomain_unregisterby devananda.vdveditnova/db/sqlalchemy/api.pyadd missing opts to test_db_api.pyby devananda.vdveditnova/tests/test_db_api.pyConsole Output[...truncated 31067 lines...]deleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091032~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091032~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpx8qjcX/novamk-build-deps -i -r -t apt-get -y /tmp/tmpx8qjcX/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 3001c7918f503a04e85bfb429321d13129ddd180..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091202~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [9807d38] add missing opts to test_db_api.pydch -a [94b7abf] clean up dnsdomain_unregisterdch -a [528add2] Another case of dictionary accessdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091202~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211091202~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091202~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211091202~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #59

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/59/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:01:25 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesclean up dnsdomain_unregisterby devananda.vdveditnova/db/sqlalchemy/api.pyadd missing opts to test_db_api.pyby devananda.vdveditnova/tests/test_db_api.pyConsole Output[...truncated 32381 lines...]deleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091032~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091032~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpE3Pjt2/novamk-build-deps -i -r -t apt-get -y /tmp/tmpE3Pjt2/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 3001c7918f503a04e85bfb429321d13129ddd180..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091202~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [9807d38] add missing opts to test_db_api.pydch -a [94b7abf] clean up dnsdomain_unregisterdch -a [528add2] Another case of dictionary accessdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091202~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211091202~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091202~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211091202~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #58

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/58/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:31:29 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove nova-volume DBby jogoeditnova/tests/test_quota.pyeditdoc/api_samples/os-used-limits/usedlimits-get-resp.jsoneditnova/tests/integrated/api_samples/os-used-limits/usedlimits-get-resp.xml.tpleditnova/tests/test_nova_manage.pyeditnova/tests/api/openstack/compute/test_limits.pyeditnova/tests/api/openstack/compute/contrib/test_volumes.pyeditnova/quota.pyeditnova/db/sqlalchemy/models.pyeditnova/tests/test_libvirt.pyeditnova/tests/integrated/api_samples/limit-get-resp.json.tpleditnova/db/api.pyeditnova/tests/api/ec2/test_cloud.pyeditnova/tests/test_db_api.pyeditnova/tests/integrated/api_samples/limit-get-resp.xml.tpleditnova/tests/api/openstack/compute/contrib/test_quota_classes.pyeditnova/api/openstack/compute/views/limits.pyeditnova/tests/test_xenapi.pyeditdoc/api_samples/os-used-limits/usedlimits-get-resp.xmleditnova/db/sqlalchemy/api.pyeditdoc/api_samples/limit-get-resp.jsoneditbin/nova-manageeditdoc/api_samples/limit-get-resp.xmleditnova/tests/api/openstack/compute/contrib/test_quotas.pyeditnova/tests/integrated/api_samples/os-used-limits/usedlimits-get-resp.json.tplConsole Output[...truncated 31042 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211091202~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091202~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091202~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091202~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091202~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpwJ7mXv/novamk-build-deps -i -r -t apt-get -y /tmp/tmpwJ7mXv/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091232~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091232~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211091232~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091232~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211091232~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #60

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/60/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:31:24 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove nova-volume DBby jogoeditnova/tests/integrated/api_samples/os-used-limits/usedlimits-get-resp.json.tpleditnova/tests/test_quota.pyeditnova/tests/test_xenapi.pyeditdoc/api_samples/limit-get-resp.jsoneditnova/tests/api/openstack/compute/contrib/test_quota_classes.pyeditnova/tests/integrated/api_samples/os-used-limits/usedlimits-get-resp.xml.tpleditnova/tests/test_nova_manage.pyeditdoc/api_samples/limit-get-resp.xmleditdoc/api_samples/os-used-limits/usedlimits-get-resp.jsoneditnova/tests/test_db_api.pyeditnova/tests/test_libvirt.pyeditnova/db/sqlalchemy/models.pyeditnova/db/sqlalchemy/api.pyeditnova/quota.pyeditbin/nova-manageeditnova/tests/api/openstack/compute/test_limits.pyeditnova/tests/api/openstack/compute/contrib/test_volumes.pyeditnova/api/openstack/compute/views/limits.pyeditnova/db/api.pyeditnova/tests/api/ec2/test_cloud.pyeditnova/tests/integrated/api_samples/limit-get-resp.json.tpleditnova/tests/api/openstack/compute/contrib/test_quotas.pyeditnova/tests/integrated/api_samples/limit-get-resp.xml.tpleditdoc/api_samples/os-used-limits/usedlimits-get-resp.xmlConsole Output[...truncated 32370 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211091202~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091202~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091202~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091202~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091202~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmprj5ICD/novamk-build-deps -i -r -t apt-get -y /tmp/tmprj5ICD/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091232~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091232~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211091232~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091232~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211091232~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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_keystone_trunk #16

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/16/Project:precise_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 13:01:22 -0500Build duration:5 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix transient test failures (bug 1077065, bug 1045962)by dolph.mathewseditkeystone/service.pyeditkeystone/test.pyedittests/test_service.pyedittests/test_keystoneclient.pyConsole Output[...truncated 14607 lines...]Machine Architecture: amd64Package: keystonePackage-Time: 180Source-Version: 2013.1+git201211091301~precise-0ubuntu1Space: 11140Status: attemptedVersion: 2013.1+git201211091301~precise-0ubuntu1Finished at 20121109-1307Build needed 00:03:00, 11140k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211091301~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211091301~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-grizzly-proposed /tmp/tmpmijJ92/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpmijJ92/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091301~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [a10bd7a] Fix transient test failures (bug 1077065, bug 1045962)dch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172dch -a [0478276] SQL upgrade test.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211091301~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201211091301~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', 'keystone_2013.1+git201211091301~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', 'keystone_2013.1+git201211091301~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_keystone_trunk #15

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/15/Project:raring_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 13:01:23 -0500Build duration:7 min 57 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix transient test failures (bug 1077065, bug 1045962)by dolph.mathewsedittests/test_service.pyeditkeystone/service.pyedittests/test_keystoneclient.pyeditkeystone/test.pyConsole Output[...truncated 44409 lines...]Version: 2013.1+git201211091301~raring-0ubuntu1Finished at 20121109-1309Build needed 00:03:56, 11288k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211091301~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211091301~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/raring-grizzly-proposed /tmp/tmpZj38ZE/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpZj38ZE/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log df148a09fc1c7d44f2134a2dc6566ef1dbe772df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091301~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [a10bd7a] Fix transient test failures (bug 1077065, bug 1045962)dch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172dch -a [0478276] SQL upgrade test.dch -a [2eea455] Include 'extra' attributes twice (bug 1076120)dch -a [fddacf7] bug 1069945: generate certs for the tests in one placedch -a [ef65550] monkeypatch cms Popendch -a [5761a2c] HACKING compliance: consistent use of 'except'dch -a [3733170] Fixed typo in log messagedch -a [399cb4c] Identity API v3 Config, Routers, Controllersdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211091301~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201211091301~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', 'keystone_2013.1+git201211091301~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', 'keystone_2013.1+git201211091301~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_nova_trunk #59

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/59/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 13:01:24 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove generic topic support from filter schedulerby cbehrenseditnova/tests/scheduler/fakes.pyeditnova/scheduler/filter_scheduler.pyeditnova/tests/scheduler/test_host_manager.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/scheduler/host_manager.pyeditnova/scheduler/filters/core_filter.pyeditnova/scheduler/filters/compute_filter.pyeditnova/tests/scheduler/test_host_filters.pyeditnova/tests/scheduler/test_least_cost.pyConsole Output[...truncated 31042 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211091232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091232~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpaVxWqz/novamk-build-deps -i -r -t apt-get -y /tmp/tmpaVxWqz/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091302~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091302~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211091302~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091302~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211091302~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #61

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/61/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 13:01:27 -0500Build duration:17 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove generic topic support from filter schedulerby cbehrenseditnova/tests/scheduler/test_least_cost.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/scheduler/filters/compute_filter.pyeditnova/tests/scheduler/fakes.pyeditnova/tests/scheduler/test_host_manager.pyeditnova/scheduler/host_manager.pyeditnova/scheduler/filter_scheduler.pyeditnova/tests/scheduler/test_host_filters.pyeditnova/scheduler/filters/core_filter.pyConsole Output[...truncated 32356 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211091232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091232~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: 9807d380d3c50cb5a8bf79a4b5c2732ed29496a1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmptMhmqa/novamk-build-deps -i -r -t apt-get -y /tmp/tmptMhmqa/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091302~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091302~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211091302~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091302~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211091302~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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 #8

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/8/Project:precise_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 14:01:22 -0500Build duration:1 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesPep8 fixes to bin/glance* scripts.by dprinceeditbin/glance-replicatoreditbin/glance-cache-manageConsole Output[...truncated 2233 lines...]Hunk #9 succeeded at 361 (offset 3 lines).Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1429ecbc-a6e1-4c42-b873-fa69eec05ad7', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1429ecbc-a6e1-4c42-b873-fa69eec05ad7', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmpEDiXGP/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpEDiXGP/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091401~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [859fd1c] Pep8 fixes to bin/glance* scripts.dch -a [b591304] Ensure authorization before deleting from storedch -a [231de61] Port uuidutils to Glancedch -a [6ab0992] Delete from store after registry delete.dch -a [4c80ec1] Unit test remaining glance-replicator methods.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1429ecbc-a6e1-4c42-b873-fa69eec05ad7', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1429ecbc-a6e1-4c42-b873-fa69eec05ad7', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_glance_trunk #9

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/9/Project:raring_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 14:01:22 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesPep8 fixes to bin/glance* scripts.by dprinceeditbin/glance-cache-manageeditbin/glance-replicatorConsole Output[...truncated 10363 lines...]Checking signature on .changesGood signature on /tmp/tmpSx2fao/glance_2013.1+git201211091401~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpSx2fao/glance_2013.1+git201211091401~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2013.1+git201211091401~raring-0ubuntu1.dsc: done.  Uploading glance_2013.1+git201211091401~raring.orig.tar.gz: done.  Uploading glance_2013.1+git201211091401~raring-0ubuntu1.debian.tar.gz: done.  Uploading glance_2013.1+git201211091401~raring-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', 'raring-grizzly', 'glance_2013.1+git201211091401~raring-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-client_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1+git201211081601~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1+git201211081601~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/raring-grizzly']Pushed up to revision 219.INFO:root:Storing current commit for next build: 859fd1c40906f66ccaedf791717c6c49ca97cff1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/raring-grizzly-proposed /tmp/tmpSx2fao/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpSx2fao/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log b591304b8980d8aca8fa6cda9ea1621aca000c88..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091401~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [859fd1c] Pep8 fixes to bin/glance* scripts.dch -a [4c80ec1] Unit test remaining glance-replicator methods.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201211091401~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1+git201211091401~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1+git201211091401~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly glance_2013.1+git201211091401~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/raring-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
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_quantum_trunk #27

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/27/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 14:31:22 -0500Build duration:2 min 20 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImport lockutils and fileutils from openstack-commonby nachiaddquantum/openstack/common/lockutils.pyeditopenstack-common.confaddquantum/openstack/common/fileutils.pyAdds test scripts for _validate_valuesby zhongyue.naheditquantum/tests/unit/test_attributes.pyeditquantum/api/v2/attributes.pyConsole Output[...truncated 2528 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b880b58a-1604-421c-b85a-638ae91268e1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b880b58a-1604-421c-b85a-638ae91268e1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmphr6TSu/quantummk-build-deps -i -r -t apt-get -y /tmp/tmphr6TSu/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091431~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [014e0b4] Explicitly include versioninfo in tarball.dch -a [8781765] Adds test scripts for _validate_valuesdch -a [c89d71f] Clean up quantum.api.v2.validatorsdch -a [13a3486] Add indication when quantum server started.dch -a [ab6de7f] Import lockutils and fileutils from openstack-commondebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b880b58a-1604-421c-b85a-638ae91268e1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b880b58a-1604-421c-b85a-638ae91268e1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_swift_trunk #16

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/16/Project:precise_grizzly_swift_trunkDate of build:Fri, 09 Nov 2012 14:31:22 -0500Build duration:4 min 6 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesgive swob default content-typeby mikeedittest/functionalnosetests/test_container.pyeditswift/proxy/controllers/base.pyeditswift/common/swob.pyedittest/functionalnosetests/test_object.pyConsole Output[...truncated 2833 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 105Source-Version: 1.7.6+git201211091431~precise-0ubuntu1Space: 17652Status: attemptedVersion: 1.7.6+git201211091431~precise-0ubuntu1Finished at 20121109-1435Build needed 00:01:45, 17652k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211091431~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211091431~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-grizzly-proposed /tmp/tmpj1OSXS/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpj1OSXS/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-grizzly --forcedch -b -D precise --newversion 1.7.6+git201211091431~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [34ca0f0] give swob default content-typedch -a [65554ea] charset for default responsesdch -a [188f834] use Host: for location rewritesdch -a [5e4ca30] Fixed swift-bench when using -b and a conf filedch -a [f46a4d8] Fixed bugs with internal client and object expirerdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211091431~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A swift_1.7.6+git201211091431~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', 'swift_1.7.6+git201211091431~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', 'swift_1.7.6+git201211091431~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: precise_grizzly_swift_trunk #17

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/17/Project:precise_grizzly_swift_trunkDate of build:Fri, 09 Nov 2012 15:31:22 -0500Build duration:3 min 32 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMake DELETE requests to expired objects return 404.by samedittest/unit/obj/test_server.pyeditswift/obj/server.pyConsole Output[...truncated 2833 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 109Source-Version: 1.7.6+git201211091531~precise-0ubuntu1Space: 17660Status: attemptedVersion: 1.7.6+git201211091531~precise-0ubuntu1Finished at 20121109-1534Build needed 00:01:49, 17660k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211091531~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211091531~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-grizzly-proposed /tmp/tmpSNazHt/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpSNazHt/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-grizzly --forcedch -b -D precise --newversion 1.7.6+git201211091531~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [34ca0f0] give swob default content-typedch -a [237a440] Make DELETE requests to expired objects return 404.dch -a [65554ea] charset for default responsesdch -a [188f834] use Host: for location rewritesdch -a [5e4ca30] Fixed swift-bench when using -b and a conf filedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211091531~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A swift_1.7.6+git201211091531~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', 'swift_1.7.6+git201211091531~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', 'swift_1.7.6+git201211091531~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: precise_grizzly_nova_trunk #62

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/62/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 16:01:28 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesValidate is-public parameter to flavor creationby russelleditnova/compute/instance_types.pySimplify topic handling in network rpcapi.by rbryanteditnova/network/rpcapi.pyRemove unused functions.by driptoneditnova/db/api.pyeditnova/db/sqlalchemy/api.pyConsole Output[...truncated 31090 lines...]DEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 5d197cb45d6824c889a398e0f84baf8bbaf2a02cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpKF5coS/novamk-build-deps -i -r -t apt-get -y /tmp/tmpKF5coS/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log c6dd816cb6f09cb0148730875f02018b4949e9b6..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211091602~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [5d197cb] Remove unused functions.dch -a [f0437ed] Make tox.ini run pep8/hacking checks on bin.dch -a [a3318d8] Fix import ordering in /bin scripts.dch -a [7fc8389] Remove generic topic support from filter schedulerdch -a [f9a8481] Simplify topic handling in network rpcapi.dch -a [36f47b8] Validate is-public parameter to flavor creationdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091602~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211091602~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091602~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211091602~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #64

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/64/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 16:01:28 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesValidate is-public parameter to flavor creationby russelleditnova/compute/instance_types.pySimplify topic handling in network rpcapi.by rbryanteditnova/network/rpcapi.pyRemove unused functions.by driptoneditnova/db/sqlalchemy/api.pyeditnova/db/api.pyConsole Output[...truncated 32389 lines...]DEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: 5d197cb45d6824c889a398e0f84baf8bbaf2a02cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpHtBHKt/novamk-build-deps -i -r -t apt-get -y /tmp/tmpHtBHKt/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log c6dd816cb6f09cb0148730875f02018b4949e9b6..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091602~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [5d197cb] Remove unused functions.dch -a [f0437ed] Make tox.ini run pep8/hacking checks on bin.dch -a [a3318d8] Fix import ordering in /bin scripts.dch -a [7fc8389] Remove generic topic support from filter schedulerdch -a [f9a8481] Simplify topic handling in network rpcapi.dch -a [36f47b8] Validate is-public parameter to flavor creationdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091602~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211091602~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091602~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211091602~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #65

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/65/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 18:01:24 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemoved two unused imports.by mordrededitnova/test.pyConsole Output[...truncated 32388 lines...]deleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091602~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: 910a5487352dc0d36a4520f5b2787ec2290d965fINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpJPLGMv/novamk-build-deps -i -r -t apt-get -y /tmp/tmpJPLGMv/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 5d197cb45d6824c889a398e0f84baf8bbaf2a02c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211091802~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [910a548] Removed two unused imports.dch -a [c6dd816] Fixes a bug in nova.utils, due to Windows compatibility issues.dch -a [f9a8481] Simplify topic handling in network rpcapi.dch -a [36f47b8] Validate is-public parameter to flavor creationdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211091802~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211091802~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211091802~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211091802~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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_keystone_trunk #17

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/17/Project:precise_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 22:01:22 -0500Build duration:4 min 1 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUse the right subprocess based on os monkeypatchby ayoungeditbin/keystone-alleditkeystone/common/cms.pyeditkeystone/middleware/auth_token.pyConsole Output[...truncated 14607 lines...]Machine Architecture: amd64Package: keystonePackage-Time: 111Source-Version: 2013.1+git201211092201~precise-0ubuntu1Space: 11140Status: attemptedVersion: 2013.1+git201211092201~precise-0ubuntu1Finished at 20121109-2205Build needed 00:01:51, 11140k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211092201~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211092201~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-grizzly-proposed /tmp/tmpRVHlFC/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpRVHlFC/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211092201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [164326b] Use the right subprocess based on os monkeypatchdch -a [a10bd7a] Fix transient test failures (bug 1077065, bug 1045962)dch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211092201~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201211092201~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', 'keystone_2013.1+git201211092201~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', 'keystone_2013.1+git201211092201~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: precise_folsom_python-keystoneclient_trunk #68

2012-11-09 Thread openstack-testing-bot
Title: precise_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_python-keystoneclient_trunk/68/Project:precise_folsom_python-keystoneclient_trunkDate of build:Fri, 09 Nov 2012 22:31:21 -0500Build duration:3 min 18 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesMake initial structural changes to keystoneclient in preparationby henryneditrun_tests.shaddkeystoneclient/openstack/common/cfg.pyeditopenstack-common.confeditkeystoneclient/openstack/common/setup.pyaddkeystoneclient/openstack/common/iniparser.pyaddkeystoneclient/common/__init__.pyaddkeystoneclient/openstack/common/timeutils.pyaddkeystoneclient/openstack/common/jsonutils.pyaddkeystoneclient/middleware/__init__.pyConsole Output[...truncated 2043 lines...]  Uploading python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise.orig.tar.gz: done.  Uploading python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1.debian.tar.gz: done.  Uploading python-keystoneclient_0.1.3.66.gf617b09+git201211092231~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-folsom', 'python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_amd64.changes']File "pool/main/p/python-keystoneclient/python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_all.deb" is already registered with different checksums!md5 expected: 82960a64d7fceecd6f34a719e5d0ce81, got: d9dc2516da62ed30e98b18a7b6b1ffd1sha1 expected: 960588be5e392c55226ebe7535f1d728062de2ad, got: 34eda4b55b4ba005072aa23d8d1b4f2a0c175536sha256 expected: d257fdbb7320ff2a0bf9f9e241fedfb9c9388ea8f48448ca51af3e6af0cd3709, got: 85245305601fe2197f93e63994d9c016e0c2c52fb6aaee4caa942f5b0e53862dsize expected: 59622, got: 59798There have been errors!ERROR:root:Error occurred during package creation/build: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254ERROR:root:Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-keystoneclient/precise-folsom-proposed /tmp/tmpqJ9Kpu/python-keystoneclientmk-build-deps -i -r -t apt-get -y /tmp/tmpqJ9Kpu/python-keystoneclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f1cc3cfc42db902589785320547204388aa170a3..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-keystoneclient/precise-folsom --forcedch -b -D precise --newversion 1:0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [76b7d92] Make initial structural changes to keystoneclient in preparation to moving auth_token here from keystone.  No functional change should occur from this commit (even though it did refresh a newer copy of openstack.common.setup.py, none of the newer updates are in functions called from this client)debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_amd64.changesTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'python-keystoneclient_0.1.3.66.gf617b09+git201211092231~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254Error 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 '['reprepro', 

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_keystone_trunk #18

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/18/Project:precise_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 22:31:21 -0500Build duration:5 min 20 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRewrite initial migrationby dolph.mathewseditkeystone/common/sql/migrate_repo/versions/001_add_initial_tables.pyConsole Output[...truncated 14607 lines...]Machine Architecture: amd64Package: keystonePackage-Time: 133Source-Version: 2013.1+git201211092231~precise-0ubuntu1Space: 11140Status: attemptedVersion: 2013.1+git201211092231~precise-0ubuntu1Finished at 20121109-2236Build needed 00:02:13, 11140k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211092231~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211092231~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-grizzly-proposed /tmp/tmpxw34em/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpxw34em/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211092231~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [164326b] Use the right subprocess based on os monkeypatchdch -a [a10bd7a] Fix transient test failures (bug 1077065, bug 1045962)dch -a [84e69a4] Rewrite initial migrationdch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211092231~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201211092231~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', 'keystone_2013.1+git201211092231~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', 'keystone_2013.1+git201211092231~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_keystone_trunk #17

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/17/Project:raring_grizzly_keystone_trunkDate of build:Fri, 09 Nov 2012 22:34:35 -0500Build duration:6 min 29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRewrite initial migrationby dolph.mathewseditkeystone/common/sql/migrate_repo/versions/001_add_initial_tables.pyConsole Output[...truncated 44420 lines...]Finished at 20121109-2241Build needed 00:02:55, 11288k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211092234~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201211092234~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/raring-grizzly-proposed /tmp/tmpJyffWk/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpJyffWk/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log df148a09fc1c7d44f2134a2dc6566ef1dbe772df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211092234~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [164326b] Use the right subprocess based on os monkeypatchdch -a [a10bd7a] Fix transient test failures (bug 1077065, bug 1045962)dch -a [84e69a4] Rewrite initial migrationdch -a [b446a77] Fix default port for identity.internalURLdch -a [28c52ac] Improve feedback on test failuredch -a [7cc02c8] fixes bug 1074172dch -a [0478276] SQL upgrade test.dch -a [2eea455] Include 'extra' attributes twice (bug 1076120)dch -a [fddacf7] bug 1069945: generate certs for the tests in one placedch -a [ef65550] monkeypatch cms Popendch -a [5761a2c] HACKING compliance: consistent use of 'except'dch -a [3733170] Fixed typo in log messagedch -a [399cb4c] Identity API v3 Config, Routers, Controllersdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211092234~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201211092234~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', 'keystone_2013.1+git201211092234~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', 'keystone_2013.1+git201211092234~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_nova_trunk #64

2012-11-09 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/64/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 23:01:23 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesGet rid of pylint E0203 in filter_scheduler.pyby notsueditnova/scheduler/filter_scheduler.pyConsole Output[...truncated 31081 lines...]deleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091802~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091802~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091802~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091802~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpnx83YQ/novamk-build-deps -i -r -t apt-get -y /tmp/tmpnx83YQ/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 910a5487352dc0d36a4520f5b2787ec2290d965f..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211092302~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d993d94] Get rid of pylint E0203 in filter_scheduler.pydebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211092302~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211092302~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211092302~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211092302~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #66

2012-11-09 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/66/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 23:01:25 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesGet rid of pylint E0203 in filter_scheduler.pyby notsueditnova/scheduler/filter_scheduler.pyConsole Output[...truncated 32385 lines...]deleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211091802~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211091802~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211091802~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211091802~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpOREn45/novamk-build-deps -i -r -t apt-get -y /tmp/tmpOREn45/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 910a5487352dc0d36a4520f5b2787ec2290d965f..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211092302~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [d993d94] Get rid of pylint E0203 in filter_scheduler.pydebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211092302~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211092302~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211092302~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211092302~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c  : Check for SCM changes before starting the build, and if   there's no change, exit without doing a build -p  : Specify the build parameters in the key=value format. -s  : Wait until the completion/abortion of the command --username VAL  : User name to authenticate yourself to Jenkins --password VAL  : Password for authentication. Note that passing a   password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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