Re: [Openstack] nova-network: how to remove

2013-04-26 Thread Unmesh Gurjar
Arindam,

You can do it using 'nova-manage service disable --host hostname
--service service' command. Similarly, you can enable the network service
in controller node.


-Unmesh.


On Thu, Apr 25, 2013 at 9:16 PM, Arindam Choudhury arin...@live.com wrote:

 Hi,

 I mistakenly installed nova-network in a compute node and its became the
 default one. Though I can start the nova-network in the controller, it does
 not start the dnsmasq. How to disable the nova-network from the compute
 node and enable the one in the controller?

 ___
 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] Ceilometer Install

2013-04-26 Thread Riki Arslan
The command line I am using is: sudo /usr/local/bin/ceilometer-api.

However, the ceilometer.ini file is missing. The version of Ceilometer I am
using is ceilometer-2013.1~g2.tar.gz. And, I only have the following
configuration files:

/etc/ceilometer/ceilometer.conf
/etc/ceilometer/policy.json
/etc/ceilometer/sources.json

Thanks.


On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:




 On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I have
 installed the driver Mongo using sudo pip install pymongo.


 Ceilometer does use a database. You have to install the right driver. If
 you want Mongo, then it sounds like you've done the right thing. It's
 possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235, in
 run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 That is coming from oslo.config. Can you post the ceilometer.ini file and
 command line you are using to start the service?

 Doug



 Thank for the help.


 On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance
 endpoint 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed
 the v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError:
 No module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the
 sqlalchemy storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is
 as follows:
 AttributeError: 'OptGroup' object has no attribute
 '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error 
 disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution python-keystoneclient 0.2.3
 conflicts with requirement python-keystoneclient=0.1.2,0.2

 The funny thing is, although pip-requires states
 python-keystoneclient=0.2,0.3, the error message complains that it 
 is
 not python-keystoneclient=0.1.2,0.2.


 Something else you have installed already wants an older version of
 the keystone client, so 

[Openstack] Swift container's rwx permissions

2013-04-26 Thread Shashank Sahni
Hi everyone,

I've been experimenting with using Swift(1.8) as Hadoop's DFS backend.

https://github.com/DmitryMezhensky/Hadoop-and-Swift-integration

After a few glitches, I'm able to create/access/delete objects/containers
using hadoop's cli fs tool. But whenever I'm trying to run the job it fails
with the following error.

ERROR security.UserGroupInformation: PriviledgedActionException as:dharmesh
cause:java.io.IOException: The ownership/permissions on the staging
directory
swift://hadooptest.rackspace/tmp/app/mapred/staging/dharmesh/.staging is
not as expected. It is owned by and permissions are rwxrwxrwx. The
directory must be owned by the submitter dharmesh or by dharmesh and
permissions must be rwx--

Note that, the local system username is dharmesh and the openstack
account and associated tenant is dharmesh too.

I tried setting the permissions by creating tmp container using swift
post -r 'dharmesh:dharmesh', but unfortunately ended up with the same
result. Is there an other way to set rwx ACLs in swift?

--
Shashank Sahni
___
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 Training

2013-04-26 Thread Heling Yao
Hi Chris,

Rackspace has a free CloudU training and certification program (
http://www.rackspace.com/knowledge_center/cloudu/), which should provide
you with a solid grounding in the area of cloud computing.

And to learn openstack, in addition to what John said, there are many
aspects of OpenStack, such as OpenStack operations, business opportunities
etc. Getting involved in the community is a good start.

Speaking of using laptop, I just installed RDO from Redhat (
openstack.redhat.com) in a xen vm, and it worked like a charm :-)


Cheers,

Heling


On Fri, Apr 26, 2013 at 4:15 AM, Chris Bartels ch...@christopherbartels.com
 wrote:

 Hi,

 ** **

 My experience with virtualization has been limited to the ProxmoxVE
 platform, and with it I’m quite adept after working with it for a few
 years, however I’m looking forward to migrating to OpenStack  would like
 to find a way to learn as much about it as I can, in as efficient a manner
 as possible.

 ** **

 I’m currently in the process of selling my laptop on eBay so that I can
 buy a cheap used server with which to tinker with the new OpenStack Grizzly
 release so I can start to learn first-hand about working with the software,
 so I have that to look forward to, but I’m also on the lookout for more
 opportunities to soak up information.

 ** **

 Today I found the ‘OpenStack Foundation’ YouTube channel, and have been
 watching videos all morning. I’m happy with this to a degree. One in
 particular entitled “Solving The OpenStack Talent Gap” turned me on to a
 resource called ‘Cloud Academy’, which seemed promising at first, but after
 getting registered with them- as far as I can tell they don’t have training
 content up  available yet, as their project is in its infancy apparently.
 

 ** **

 So I come to you all here on the list for suggestions as to whether there
 exists reputable formal online training that I can sign up for somewhere-
 free is better however I don’t mind spending a thousand dollars for
 top-notch training if it provides an industry recognized certification at
 the end such as the CompTIA A+ (which I’m signed up for this fall, btw-
 because it’s the closest I can get to what I’m after at the local community
 college).

 ** **

 What do people here know that I don’t know about OpenStack learning 
 training? Do any programs stand out as being great that you know of?

 ** **

 Please advise.

 ** **

 ** **

 Kindest Regards,

 -Chris

 ___
 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] No Network and Router sections in Grizzly's Admin tab

2013-04-26 Thread Ashutosh Narayan
Hi folks,

I have just installed Grizzly release on CentOS 6.3 after following the
documentations
given on this link - http://openstack.redhat.com/Quickstart
After logging in with admin user, I do not see Networks and Routers
section under
Admin tab. I have installed Grizzly using packstack --allinone command.
Did this miss out Network configuration ?

(keystone_admin)]# nova network-list
++-+-+
| ID | Label   | Cidr|
++-+-+
| 1  | novanetwork | 192.168.32.0/22 |
++-+-+

Please suggest where I went wrong.


Thank you,

-- 
Ashutosh Narayan

http://ashutoshn.wordpress.com/
___
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] V2 Grizzly net-gateway-xxx 404

2013-04-26 Thread Heiko Krämer
Hey guys,

I'm trying to use:
/quantum net-gateway-list /

or something else of this command. I get every time 404:

/quantum net-gateway-list//
//404 Not Found//
//
//The resource could not be found.//
/
I think any extension is missing in my conf?! But i can't find any doc :(

quantum.conf:
/
core_plugin =
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2//
//service_plugins =
quantum.plugins.services.agent_loadbalancer.plugin.LoadBalancerPlugin//
//router_scheduler_driver =
quantum.scheduler.l3_agent_scheduler.ChanceScheduler/



Greetings and Thx
Heiko
___
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] Query on Openstack Nova-network

2013-04-26 Thread Sreerekha Shenoy (sresheno)
Hi,
We are a team attempting a PoC on Openstack with a single node deployment to 
start with.
It currently has Keystone, Glance and Nova enabled.

As a part of this PoC, we learnt that Openstack with Nova-network in FlatDHCP 
mode,
uses two subnets on the Host machine:
-  Public Subnet for floating IPs :
o Openstack manages the mapping of floating to fixed IPs for VMs.
o VMs are not aware of the additional public IP assigned.

-  Private Subnet for Fixed IPs:
o Openstack boots up the VM with this IP address and VM is aware of 
it
o BR100 created to manage the VMnet fabric for traffic on this 
subnet.

Few Queries:

-For applications on such a setup that use IP-sensitive protocols like SIP, how 
do we handle the scenarios?
Are we expected to have SIP ALG to do additional SIP based NAT'ng apart from 
what nova-network manages?

-Does this NAT'ng of Floating to Fixed IP not really pull down the performance 
overall?

-What if I need my VMs to be spawned on a public subnet for general 
accessibility
without any NAT'ng involved? Is there anyways Openstack can help?

Thanks,
Best Regards,
Rekha

___
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] [Announce] OpenStack Grizzly Multi Node Install Guide by Msekni Bilel

2013-04-26 Thread skible.openst...@gmail.com

Hi,

So I have been working on this with a couple of OpenStackers from all 
over the world (Tokyo, US, Germany, ..) and we are happy to present our 
guide to deploy OpenStack Grizzly in Multi Node/Single node.


https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst

This is well tested to work on Ubuntu 12.04 and 13.04 64bits ! This is 
the readme 
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide file of 
the guide if you want to know more :)


P.S: if you ever happen to hear of an open cloud operator position, you 
might wana contact me about it ! I am going homeless by the end of the 
month :p


Kind regards,
Bilel MSEKNI http://www.linkedin.com/profile/view?id=136237741trk=tab_pro
___
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] V2 Grizzly net-gateway-xxx 404

2013-04-26 Thread Akihiro MOTOKI
Hi Heiko,

net-gateway-* feature is provided by network gateway extension.
This extension is specific to Nicira NVP plugin and not supported by other
plugins (in Grizzly release).

Thanks,
Akihiro



2013/4/26 Heiko Krämer i...@honeybutcher.de

  Hey guys,

 I'm trying to use:
 *quantum net-gateway-list *

 or something else of this command. I get every time 404:

 *quantum net-gateway-list**
 **404 Not Found**
 **
 **The resource could not be found.**
 *
 I think any extension is missing in my conf?! But i can't find any doc :(

 quantum.conf:
 *
 core_plugin =
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2**
 **service_plugins =
 quantum.plugins.services.agent_loadbalancer.plugin.LoadBalancerPlugin**
 **router_scheduler_driver =
 quantum.scheduler.l3_agent_scheduler.ChanceScheduler*



 Greetings and Thx
 Heiko

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




-- 
Akihiro MOTOKI amot...@gmail.com
___
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] V2 Grizzly net-gateway-xxx 404

2013-04-26 Thread Heiko Krämer
All right,

thx for the information Akihiro.

greetings
Heiko

On 26.04.2013 12:53, Akihiro MOTOKI wrote:
 Hi Heiko,

 net-gateway-* feature is provided by network gateway extension.
 This extension is specific to Nicira NVP plugin and not supported by
 other plugins (in Grizzly release).

 Thanks,
 Akihiro



 2013/4/26 Heiko Krämer i...@honeybutcher.de
 mailto:i...@honeybutcher.de

 Hey guys,

 I'm trying to use:
 /quantum net-gateway-list /

 or something else of this command. I get every time 404:

 /quantum net-gateway-list//
 //404 Not Found//
 //
 //The resource could not be found.//
 /
 I think any extension is missing in my conf?! But i can't find any
 doc :(

 quantum.conf:
 /
 core_plugin =
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2//
 //service_plugins =
 quantum.plugins.services.agent_loadbalancer.plugin.LoadBalancerPlugin//
 //router_scheduler_driver =
 quantum.scheduler.l3_agent_scheduler.ChanceScheduler/



 Greetings and Thx
 Heiko

 ___
 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




 -- 
 Akihiro MOTOKI amot...@gmail.com mailto:amot...@gmail.com

___
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] [Announce] OpenStack Grizzly Multi Node Install Guide by Msekni Bilel

2013-04-26 Thread daniels cai
thanks for your guide , Bilel , it really helps.

Daniels Cai
http://dnscai.com


On Fri, Apr 26, 2013 at 6:49 PM, skible.openst...@gmail.com 
skible.openst...@gmail.com wrote:

  Hi,

 So I have been working on this with a couple of OpenStackers from all over
 the world (Tokyo, US, Germany, ..) and we are happy to present our guide to
 deploy OpenStack Grizzly in Multi Node/Single node.


 https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst

 This is well tested to work on Ubuntu 12.04 and 13.04 64bits ! This is the
 readme https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guidefile 
 of the guide if you want to know more :)

 P.S: if you ever happen to hear of an open cloud operator position, you
 might wana contact me about it ! I am going homeless by the end of the
 month :p

 Kind regards,
 Bilel MSEKNIhttp://www.linkedin.com/profile/view?id=136237741trk=tab_pro

 ___
 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] Glance not connecting for image creation

2013-04-26 Thread aliki aliki
Hello, 

I am new to openstack and I am trying the basic installation for controller 
node following this:

http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html
 

I have reached the stage where I try to configure glance. 
glance-manage db_sync works properly

However when I try to create image with the glance image-create command I get 
the error:
Error communicating with /v1/images: [Errno 113] No route to host

This error varies between 110-113 depending on the master ip I use when running 
the keystone-endpoint.sh.

Please help, or at least tell me what the master in the keystone-endpoint.sh 
stands for, so as to understand the problem.

ps. the conf files are just as they are described in the tutorial I mentioned 
above.

Thanks in advance!

Aliki
  ___
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] [Grizzly] VMs not authorized by metadata server

2013-04-26 Thread Michaël Van de Borne

Hi there,

I've installed Grizzly on 3 servers:
compute (howard)
controller (leonard)
network (rajesh)).

Namespaces are ON
Overlapping IPs are ON

When booting, my VMs can reach the metadata server (on the controller 
node), but it responds a 500 Internal Server Error


*Here is the error from the log of nova-api:*
2013-04-26 15:35:28.149 19902 INFO nova.metadata.wsgi.server [-] (19902) 
accepted ('192.168.202.105', 54871)


2013-04-26 15:35:28.346 ERROR nova.network.quantumv2 
[req-52ffc3ae-a15e-4bf4-813c-6596618eb430 None None] _get_auth_token() 
failed
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2 Traceback 
(most recent call last):
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, 
line 40, in _get_auth_token
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2 
httpclient.authenticate()
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2   File 
/usr/lib/python2.7/dist-packages/quantumclient/client.py, line 193, in 
authenticate
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2 
content_type=application/json)
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2   File 
/usr/lib/python2.7/dist-packages/quantumclient/client.py, line 131, in 
_cs_request
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2 raise 
exceptions.Unauthorized(message=body)
2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2 Unauthorized: 
{error: {message: The request you have made requires 
authentication., code: 401, title: Not Authorized}}

2013-04-26 15:35:28.346 19902 TRACE nova.network.quantumv2
2013-04-26 15:35:28.347 ERROR nova.api.metadata.handler 
[req-52ffc3ae-a15e-4bf4-813c-6596618eb430 None None] Failed to get 
metadata for instance id: 05141f81-04cc-4493-86da-d2c05fd8a2f9
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler Traceback 
(most recent call last):
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.py, line 
179, in _handle_instance_id_request
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler 
remote_address)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/api/metadata/handler.py, line 
90, in get_metadata_by_instance_id
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler 
instance_id, address)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/api/metadata/base.py, line 417, 
in get_metadata_by_instance_id
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler return 
InstanceMetadata(instance, address)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/api/metadata/base.py, line 143, 
in __init__
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler 
conductor_api=capi)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py, line 
359, in get_instance_nw_info
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler result = 
self._get_instance_nw_info(context, instance, networks)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py, line 
367, in _get_instance_nw_info
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler nw_info = 
self._build_network_info_model(context, instance, networks)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py, line 
777, in _build_network_info_model
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler client = 
quantumv2.get_client(context, admin=True)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, 
line 67, in get_client
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler return 
_get_client(token=token)
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, 
line 49, in _get_client
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler token = 
_get_auth_token()
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, 
line 43, in _get_auth_token
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler 
LOG.exception(_(_get_auth_token() failed))
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/contextlib.py, line 24, in __exit__
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler 
self.gen.next()
2013-04-26 15:35:28.347 19902 TRACE nova.api.metadata.handler   File 
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/__init__.py, 
line 40, in 

Re: [Openstack] [Quantum] V2 Grizzly net-gateway-xxx 404

2013-04-26 Thread Heiko Krämer
So the usecase is,

i've a shared private net for shared services that can use by all tenants.

I've created a router, shared-net and subnet for this.
Now i'm trying to attach to the user-tenant router an interface with any
IP of the service-shared net, but thats not working:

quantum router-interface-add 424a4e14-54c1-4cd3-b0ef-69deeba3d24c
7e522217-4633-4def-b1eb-5be2eb3f2335
Unable to complete operation for network
39610c0f-228f-4a78-b65c-e523f49bbeed. The IP address 10.0.101.1 is in use.

It's possible to attach an interface of an other subnet to a router ?
It's to make it possible to communicate between user-tenant and
shared-tenant (not external network).

I'm using openvswitch and gre with namespaces so for each tenant one router.


I'm trying now since many hours to combine two internal networks...

Usecase:

tenant1 (10.0.0.0/24):
router1
vm1:
IP: 10.0.0.20

tenant2(10.0.1.0/24):
router2
vm2:
IP: 10.0.1.8

tenant3(10.0.2.0/24):
router3
vm3
ip: 10.0.2.9


now should it possible:
connect from vm1 and vm2 to vm3
not from vm1 to vm2

i need attach a port of the shared-net to the router of each tenant


I'm going to crazy :D


Greetings and thx
Heiko


On 26.04.2013 12:53, Akihiro MOTOKI wrote:
 Hi Heiko,

 net-gateway-* feature is provided by network gateway extension.
 This extension is specific to Nicira NVP plugin and not supported by
 other plugins (in Grizzly release).

 Thanks,
 Akihiro



 2013/4/26 Heiko Krämer i...@honeybutcher.de
 mailto:i...@honeybutcher.de

 Hey guys,

 I'm trying to use:
 /quantum net-gateway-list /

 or something else of this command. I get every time 404:

 /quantum net-gateway-list//
 //404 Not Found//
 //
 //The resource could not be found.//
 /
 I think any extension is missing in my conf?! But i can't find any
 doc :(

 quantum.conf:
 /
 core_plugin =
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2//
 //service_plugins =
 quantum.plugins.services.agent_loadbalancer.plugin.LoadBalancerPlugin//
 //router_scheduler_driver =
 quantum.scheduler.l3_agent_scheduler.ChanceScheduler/



 Greetings and Thx
 Heiko

 ___
 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




 -- 
 Akihiro MOTOKI amot...@gmail.com mailto:amot...@gmail.com

___
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] [Grizzly] cannot attach volume to instance due to wrong iscsi target

2013-04-26 Thread Michaël Van de Borne

Hi all,

I installed three nodes like this topology:
http://docs.openstack.org/trunk/openstack-network/admin/content/connectivity.html

Here are my subnets:
management: 192.168.203.X/24
data: 192.168.201.X/24
external  API: 192.168.202.X/24

I'm running ubuntu 12.04.

When I try to attach a volume to a VM, I get the following error in 
nova-compute.log:
2013-04-26 16:27:59.439 WARNING nova.virt.libvirt.volume 
[req-f5b4e121-a3ac-456d-b5cb-ba389c7fb409 
6d72da42f39648c48d3dfb4cd190107d 93a48de7ef674f07a96e169383c34399] ISCSI 
volume not yet found at: vdr. Will rescan  retry.  Try number: 0
2013-04-26 16:27:59.490 ERROR nova.compute.manager 
[req-f5b4e121-a3ac-456d-b5cb-ba389c7fb409 
6d72da42f39648c48d3dfb4cd190107d 93a48de7ef674f07a96e169383c34399] 
[instance: 05141f81-04cc-4493-86da-d2c05fd8a2f9] Failed to attach volume 
d9424219-33f6-40c8-88d9-ecba4c8aa6be at /dev/vdr
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] Traceback (most recent call last):
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2859, 
in _attach_volume
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] mountpoint)
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 
957, in attach_volume
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] disk_info)
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 
943, in volume_driver_method
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] return method(connection_info, 
*args, **kwargs)
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py, 
line 242, in inner
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] retval = f(*args, **kwargs)
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py, line 
245, in connect_volume
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] 
self._run_iscsiadm(iscsi_properties, (--rescan,))
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py, line 
179, in _run_iscsiadm
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] check_exit_code=check_exit_code)
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]   File 
/usr/lib/python2.7/dist-packages/nova/utils.py, line 239, in execute
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] cmd=' '.join(cmd))
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] ProcessExecutionError: Unexpected 
error while running command.
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] Command: sudo nova-rootwrap 
/etc/nova/rootwrap.conf iscsiadm -m node -T 
iqn.2010-10.org.openstack:volume-d9424219-33f6-40c8-88d9-ecba4c8aa6be -p 
_/*192.168.202.103*/_:3260 --rescan
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] Exit code: 255
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] Stdout: ''
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9] Stderr: 'iscsiadm: No portal found.\n'
2013-04-26 16:27:59.490 30092 TRACE nova.compute.manager [instance: 
05141f81-04cc-4493-86da-d2c05fd8a2f9]
2013-04-26 16:27:59.849 ERROR nova.openstack.common.rpc.amqp 
[req-f5b4e121-a3ac-456d-b5cb-ba389c7fb409 
6d72da42f39648c48d3dfb4cd190107d 93a48de7ef674f07a96e169383c34399] 
Exception during message handling



As we can see, the compute node tries to reach the API interface 
(192.168.202.103) of the controller node. Of course, it cannot, since 
the compute node only knows the data and the management subnets.


Is this the default behaviour and I'm missing a parameter somewhere?
I set this key in nova.conf:
iscsi_ip_address=192.168.203.103

but still no luck

any clue?

yours,

michaël


--
Michaël Van de Borne
RD 

[Openstack] OpenStack Community Weekly Newsletter (Apr 12 – 25)

2013-04-26 Thread Stefano Maffulli


   Special post-Summit issue

 * OpenStack Design Summit Havana, from a Ceilometer point of view
   http://julien.danjou.info/blog/2013/openstack-summit-havana-ceilometer
   by Julien Danjou http://julien.danjou.info/blog/
 * Havana Design Summit: Swift API Discussions
   http://swiftstack.com/blog/2013/04/24/openstack-summit-api-discussion/
   by SwiftStack Team http://swiftstack.com/
 * OpenStack Summit Portland Aftermath
   http://www.siliconloons.com/?p=448 by Kyle Mestery
   http://www.siliconloons.com/
 * OpenStack Developer Summit: Heat Followup
   
http://technicae.cogitat.io/2013/04/openstack-developer-summit-heat-followup.html
   by Duncan McGreggor http://technicae.cogitat.io/search/label/openstack
 * Havana! http://secstack.org/2013/04/havana/ by OpenStack Security
   Blog http://secstack.org/
 * Portland OpenStack Summit
   https://tropicaldevel.wordpress.com/2013/04/22/portland-openstack-summit/
   by John Bresnahan https://tropicaldevel.wordpress.com/
 * Dan’s Partial Summary of the Nova Track
   
http://www.danplanet.com/blog/2013/04/22/dans-partial-summary-of-the-nova-track/?utm_source=rssutm_medium=rssutm_campaign=dans-partial-summary-of-the-nova-track
   by Dan Smith http://www.danplanet.com/blog
 * The Rocket Ship to Havana – OpenStack Summit Spring 2013
   
http://fewbar.com/2013/04/the-rocket-ship-to-havana-openstack-summit-spring-2013/
   by Clint Byrum http://fewbar.com/
 * Women of OpenStack at the Portland Summit
   
http://www.openstack.org/blog/2013/04/women-of-openstack-at-the-portland-summit/
   by Anne Gentle http://www.openstack.org/blog
 * Michael’s surprisingly unreliable predictions for the Havana Nova
   release http://www.stillhq.com/openstack/havana/02.html by
   Michael Still http://www.stillhq.com/
 * Havana Design Summit: Extending ACLs and Metadata
   
http://swiftstack.com/blog/2013/04/17/openstack-summit-extending-swift-acls-and-metadata/
   by SwiftStack Team http://swiftstack.com/
 * Design Summit in Portland
   
http://www.enovance.com/fr/blog/5567/openstack-havana-design-summit-in-portland-day-3:
   Day 1
   
http://www.enovance.com/fr/blog/5534/openstack-havana-design-summit-in-portland-day-1,Day
   2
   
http://www.enovance.com/fr/blog/5550/openstack-havana-design-summit-in-portland-day-2,
   Day 3
   
http://www.enovance.com/fr/blog/5567/openstack-havana-design-summit-in-portland-day-3,
   Day 4
   
http://www.enovance.com/fr/blog/5594/openstack-havana-design-summit-in-portland-day-4
   by eNovance http://www.enovance.com/
 * Havana Design Summit: Swift Extensions Talk
   
http://swiftstack.com/blog/2013/04/15/openstack-summit-talks-swift-extensions/
   by SwiftStack Team http://swiftstack.com/
 * Havana Design Summit: Extending ACLs and Metadata
   
http://swiftstack.com/blog/2013/04/15/openstack-summit-extending-swift-acls-and-metadata/
   by SwiftStack Team http://swiftstack.com/
 * OpenStack Design Summit
   http://princessleia.com/journal/?p=7943days 1-2
   http://princessleia.com/journal/?p=7930, days 3-4
   http://princessleia.com/journal/?p=7943 by Elizabeth Krumbach
   http://princessleia.com/journal
 * “Stack Shop” cover of Macklemore’s Thrift Shop
   http://robhirschfeld.com/2013/04/22/stack-shop-macklemore-thrift-shop/
   by Rob http://rob/Hirschfeld
   http://robhirschfeld.com/2013/04/22/stack-shop-macklemore-thrift-shop/
   and others
 * The Making of Cloud of USB Sticks
   http://anystacker.com/2013/04/the-making-of-cloud-of-usb-sticks/
   by eglute


 OpenStack docs and tooling in 20 minutes
 
http://www.rhonabwy.com/wp/2013/04/19/openstack-docs-and-tooling-in-20-minutes/

Howto get started with all the tooling and setup needed to build, 
review, and contribute to OpenStack Documentation. By Joe Heck 
http://www.rhonabwy.com/wp.



   How It’s Made: the OpenStack API Reference Page
   
http://justwriteclick.com/2013/04/14/how-its-made-the-openstack-api-reference-page/

The site at http://api.openstack.org http://api.openstack.org/ is a 
collection of HTML pages, and one page has an especially interesting 
story about how it is built. Anne Gentle http://justwriteclick.com/ 
reveals the secret.



 Storage != Transfer
 https://tropicaldevel.wordpress.com/2013/04/24/storage-transfer/

John Bresnahan argues that concepts of data transfer and data storage 
should not be conflated into a single solution.  He believes that 
OpenStack can benefit from a new component that offloads the burden of 
optimally transferring images from existing components like nova-compute 
and swift.



   Report from Previous Events

 * 3rd Swiss OpenStack User Group Meetup
   
http://www.openstack.org/blog/2013/04/3rd-swiss-openstack-user-group-meet-up/


   Tips and Tricks

 * By Sébastien Han http://sebastien-han.fr/: Ceph and Cinder
   multi-backend
   http://sebastien-han.fr/blog/2013/04/25/ceph-and-cinder-multi-backend/
 * By Chmouel Boudjnah http://blog.chmouel.com/ :: Howto revoke a
   token with keystone and PKI (v2.0 API)
   

[Openstack] ceilometer and heat tutorial

2013-04-26 Thread Michaël Van de Borne

Hi all,

I'm looking for install and usage tutorials for ceilometer and heat. The 
best I could find so far are these:

- ceilometer: http://docs.openstack.org/developer/ceilometer/install.html
- heat: 
https://wiki.openstack.org/wiki/Heat/GettingStartedUsingMasterOnUbuntu


Unfortunately, they seem to be intended for developers. Still have to 
git clone the softwares.


I'm looking for tutorials like this one: 
http://docs.openstack.org/trunk/basic-install/content/
(using apt-get, telling how to configure everything on every node, and 
finishing with a simple use case to validate the installation).


Does anyone have something like this?

thank you,

michaël


--
Michaël Van de Borne
RD Engineer, SOA team, CETIC
Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: mikemowgli
www.cetic.be, rue des Frères Wright, 29/3, B-6041 Charleroi


___
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] Ceilometer Install

2013-04-26 Thread Doug Hellmann
It sounds like you haven't completed the installation instructions. I don't
know if the manual steps listed at
http://docs.openstack.org/developer/ceilometer/install/manual.html work
with the tarball, but they should be close.

Doug


On Fri, Apr 26, 2013 at 3:46 AM, Riki Arslan riki.ars...@cloudturk.netwrote:

 The command line I am using is: sudo /usr/local/bin/ceilometer-api.

 However, the ceilometer.ini file is missing. The version of Ceilometer I
 am using is ceilometer-2013.1~g2.tar.gz. And, I only have the following
 configuration files:

 /etc/ceilometer/ceilometer.conf
 /etc/ceilometer/policy.json
 /etc/ceilometer/sources.json

 Thanks.


 On Fri, Apr 26, 2013 at 1:10 AM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Thu, Apr 25, 2013 at 8:37 AM, Riki Arslan 
 riki.ars...@cloudturk.netwrote:

 I thought Ceilometer did not set a dependency on any DB drivers. I have
 installed the driver Mongo using sudo pip install pymongo.


 Ceilometer does use a database. You have to install the right driver. If
 you want Mongo, then it sounds like you've done the right thing. It's
 possible mako is also being used somewhere else, I'm not sure.



 Regarding the current problem; the traceback is as follows:

 Traceback (most recent call last):
   File /usr/local/bin/ceilometer-api, line 5, in module
 pkg_resources.run_script('ceilometer==0.0.0', 'ceilometer-api')
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 499, in
 run_script
 self.require(requires)[0].run_script(script_name, ns)
   File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1235,
 in run_script
 execfile(script_filename, namespace, namespace)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/EGG-INFO/scripts/ceilometer-api,
 line 38, in module
 service.prepare_service()
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/service.py,
 line 80, in prepare_service
 cfg.CONF(argv[1:], project='ceilometer')
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1024, in __call__
 self._cli_values, leftovers = self._parse_cli_opts(args)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-0.0.0-py2.7.egg/ceilometer/openstack/common/cfg.py,
 line 1527, in _parse_cli_opts
 opt._add_to_cli(self._oparser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 591, in _add_to_cli
 container = self._get_argparse_container(parser, group)
   File
 /usr/local/lib/python2.7/dist-packages/oslo.config-1.1.0-py2.7.egg/oslo/config/cfg.py,
 line 633, in _get_argparse_container
 return group._get_argparse_group(parser)
 AttributeError: 'OptGroup' object has no attribute '_get_argparse_group'


 That is coming from oslo.config. Can you post the ceilometer.ini file and
 command line you are using to start the service?

 Doug



 Thank for the help.


 On Thu, Apr 25, 2013 at 3:27 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:



 On Thursday, April 25, 2013, Riki Arslan wrote:

 I have encountered other problems too.

 First of all, when starting the Central Agent I have had Glance
 endpoint 404 not found errors. As, Julien pointed out (
 https://bugs.launchpad.net/ceilometer/+bug/1083104), I have removed
 the v1 from the Glance URLs and it worked well.

 Secondly, when starting the API Server, I have received ImportError:
 No module named mako.template error. Thus, I have installed python-mako
 module (sudo apt-get install python-mako), and the error disappeared.


 Mako is a dependency do sqlalchemy, I think. Are you using the
 sqlalchemy storage driver for ceilometer?



 Now, I am receiving another error within the API Server. The error is
 as follows:
 AttributeError: 'OptGroup' object has no attribute
 '_get_argparse_group'


 That sounds like a problem with the config module. Was there a full
 traceback? If not, try adding the --debug option when starting the service.

 Doug



 Do you think it has something to do with mod_wsgi (
 http://docs.openstack.org/developer/ceilometer/install/mod_wsgi.html)?

 I would appreciate your help on this.

 Thanks.


 On Thu, Apr 25, 2013 at 12:27 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi Doug,

 Your email helped me. It was actually glanceclient version 0.5.1 that
 was causing the conflict. After updating it, the conflict error 
 disappeared.

 I hope this would help someone else too.

 Thanks again.


 On Wed, Apr 24, 2013 at 11:49 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 24, 2013 at 9:17 AM, Riki Arslan 
 riki.ars...@cloudturk.net wrote:

 Hi,

 We are trying to install ceilometer-2013.1~g2.tar.gz which
 presumably has Folsom compatibility.

 The requirment is python-keystoneclient=0.2,0.3 and we have
 the version 2.3.

 But, still, setup quits with the following message:

 error: Installed distribution 

Re: [Openstack] [Quantum] V2 Grizzly net-gateway-xxx 404

2013-04-26 Thread Darragh O'Reilly


have a look at this
https://answers.launchpad.net/quantum/+question/227321

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


Re: [Openstack] [Grizzly] cannot attach volume to instance due to wrong iscsi target

2013-04-26 Thread Darragh O'Reilly
its not really obvious, but I believe the iscsi_ip_address needs to be set in 
the nova.conf on the **controller** - just want to check you did it there.


___
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 Training

2013-04-26 Thread Will Dennis (Live.com)
+1 on Devstack; it's a great learning (labbing) tool in itself. You can even
do a multi-node installation with it.

 

Hi Chris,

 

Do check out the recent OpenStack Operations Guide at
http://docs.openstack.org/ops/OpenStackOperationsGuide.pdf -- it's a good
resource to get you going on a real implementation.

 

Finally, (haven't yet used them but) Mirantis does hold OpenStack training
classes - see http://www.mirantis.com/openstack-training/ for details.

 

Please keep the list updated on what else you find - I'm a OS newb as well
and looking for all the training sources I can find :) I'm sure they're a
lot of us out here as well.

 

Best,

Will

 

From: Openstack
[mailto:openstack-bounces+willarddennis=live@lists.launchpad.net] On
Behalf Of John Griffith
Sent: Thursday, April 25, 2013 4:24 PM
To: ch...@christopherbartels.com
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Training

 

 

 

On Thu, Apr 25, 2013 at 2:15 PM, Chris Bartels
ch...@christopherbartels.com wrote:

Hi,

 

My experience with virtualization has been limited to the ProxmoxVE
platform, and with it I'm quite adept after working with it for a few years,
however I'm looking forward to migrating to OpenStack  would like to find a
way to learn as much about it as I can, in as efficient a manner as
possible.

 

I'm currently in the process of selling my laptop on eBay so that I can buy
a cheap used server with which to tinker with the new OpenStack Grizzly
release so I can start to learn first-hand about working with the software,
so I have that to look forward to, but I'm also on the lookout for more
opportunities to soak up information.

 

Today I found the 'OpenStack Foundation' YouTube channel, and have been
watching videos all morning. I'm happy with this to a degree. One in
particular entitled Solving The OpenStack Talent Gap turned me on to a
resource called 'Cloud Academy', which seemed promising at first, but after
getting registered with them- as far as I can tell they don't have training
content up  available yet, as their project is in its infancy apparently.

 

So I come to you all here on the list for suggestions as to whether there
exists reputable formal online training that I can sign up for somewhere-
free is better however I don't mind spending a thousand dollars for
top-notch training if it provides an industry recognized certification at
the end such as the CompTIA A+ (which I'm signed up for this fall, btw-
because it's the closest I can get to what I'm after at the local community
college).

 

What do people here know that I don't know about OpenStack learning 
training? Do any programs stand out as being great that you know of?

 

Please advise.

 

 

Kindest Regards,

-Chris


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

Hey Chris,

 

Welcome, I don't have much input regarding your questions on the best
training resources other than docs and diving in to OpenStack.

 

That being said, you might want to reconsider selling your laptop, you can
run OpenStack in a VM on your laptop just fine, and in fact checkout:
http://devstack.org for a very easy way to get started and experimenting
with OpenStack.

 

Good Luck,

John

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


Re: [Openstack] Swift container's rwx permissions

2013-04-26 Thread Clay Gerrard
Wow, so I glanced quickly at the github project to try and get some
context, but I think I actually start getting *more* confused when I see
swift in the same class name as file-system ;)

I'd like you (or maybe vaidy, hi vaidy!) to correct me if I'm wrong, but
this hadoop integration will *not* access the filesystem of the object
servers directly?  Everything will happen on a pool of processing boxes
that will talk to swift via HTTP - same as any other client?

In that case, the error message is just a leaky abstraction showing
through.  HDFS probably has permission errors that it tries to helpfully
map back to file system constructs which just don't apply when you're
trying to simulate a file system on object storage.  You'll have to get
down the the HTTP to understand what's causing the error.  Presumably a 401
from Swift, so access to swift logs would be helpful.

OTOH, if we're * actually* talking about filesystem permissions; then I'm
totally confused.  But ACL's definitely won't help.  They're just a row
sitting in a sqlite database - probably on a totally different server from
where the one replica of this object is sitting on the filesystem. Nothing
you can set in the api will change the filesystem permissions of the
directory structure or files on the object servers.

Maybe do you have some more overview info on the general approach?  I don't
really have any Hadoop experience, so maybe it'd be better if there's a
hadoop expert out there that also has some experience with swift and can
help get you on the right track...

-Clay



In


On Fri, Apr 26, 2013 at 1:11 AM, Shashank Sahni shredde...@gmail.comwrote:

 Hi everyone,

 I've been experimenting with using Swift(1.8) as Hadoop's DFS backend.

 https://github.com/DmitryMezhensky/Hadoop-and-Swift-integration

 After a few glitches, I'm able to create/access/delete objects/containers
 using hadoop's cli fs tool. But whenever I'm trying to run the job it fails
 with the following error.

 ERROR security.UserGroupInformation: PriviledgedActionException
 as:dharmesh cause:java.io.IOException: The ownership/permissions on the
 staging directory
 swift://hadooptest.rackspace/tmp/app/mapred/staging/dharmesh/.staging is
 not as expected. It is owned by and permissions are rwxrwxrwx. The
 directory must be owned by the submitter dharmesh or by dharmesh and
 permissions must be rwx--

 Note that, the local system username is dharmesh and the openstack
 account and associated tenant is dharmesh too.

 I tried setting the permissions by creating tmp container using swift
 post -r 'dharmesh:dharmesh', but unfortunately ended up with the same
 result. Is there an other way to set rwx ACLs in swift?

 --
 Shashank Sahni

 ___
 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] ceilometer and heat tutorial

2013-04-26 Thread Steven Hardy
On Fri, Apr 26, 2013 at 05:02:54PM +0200, Michaël Van de Borne wrote:
 Hi all,
 
 I'm looking for install and usage tutorials for ceilometer and heat.
 The best I could find so far are these:
 - ceilometer: http://docs.openstack.org/developer/ceilometer/install.html
 - heat: https://wiki.openstack.org/wiki/Heat/GettingStartedUsingMasterOnUbuntu
 
 Unfortunately, they seem to be intended for developers. Still have
 to git clone the softwares.
 
 I'm looking for tutorials like this one:
 http://docs.openstack.org/trunk/basic-install/content/
 (using apt-get, telling how to configure everything on every node,
 and finishing with a simple use case to validate the installation).
 
 Does anyone have something like this?

For Heat, the we don't yet have this sort of package-orientated
documentation, for Ubuntu this is because heat is not yet packaged for
Ubuntu, it is now in Debian Experimental though:

https://launchpad.net/debian/experimental/+source/heat/2013.1-1

Heat is packaged for Fedora, there are some instructions here:

http://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack

HTH,

Steve


___
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] Bridging question

2013-04-26 Thread Daniel Ellison
Hi all,

I have Nova all set up on a single server and am able to start/stop/delete VM 
instances no problem. I have a bridge at br100 which sits on eth1 and is not 
connected to anything. eth0 is connected to the Internet. Before installing 
Openstack I was using KVM and virsh to manage my VMs. In order to do the 
Openstack install with fewer working parts, I brought down all KVM instances 
and deleted the br0 bridge they were using.

Everything works beautifully with respect to nova-network. Since I can't easily 
port my KVM instances to Openstack, I wanted to start them up again under 
virsh. I recreated the br0 bridge as it was before. So far so good. I can start 
my legacy VMs and all works as expected. There's only one issue, and I don't 
even know if it's important.

Before starting a Nova VM eth0 has no IP, which is expected as it's being 
covered by br0. But when I start one of the Nova VMs that has a floating IP, 
eth0 gains its IP! Everything seems to continue working, but it doesn't make 
sense to me.

I don't know if this is expected behaviour or I simply have things configured 
wrong. Since it all still works I'm not overly concerned, but it does bug me. 
If anyone has insight into this I would be grateful.

Thanks,
Daniel
___
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] Bridging question

2013-04-26 Thread David Wittman
Daniel,

This is the expected behavior. With nova-network, FLIPs are assigned as a
secondary address on the host interface, and traffic is routed to your
instances via NAT rules. I'd recommend reading the following blog post from
Mirantis for more information:

http://www.mirantis.com/blog/configuring-floating-ip-addresses-networking-openstack-public-private-clouds/

-Dave


On Fri, Apr 26, 2013 at 4:58 PM, Daniel Ellison dan...@syrinx.net wrote:

 Hi all,

 I have Nova all set up on a single server and am able to start/stop/delete
 VM instances no problem. I have a bridge at br100 which sits on eth1 and is
 not connected to anything. eth0 is connected to the Internet. Before
 installing Openstack I was using KVM and virsh to manage my VMs. In order
 to do the Openstack install with fewer working parts, I brought down all
 KVM instances and deleted the br0 bridge they were using.

 Everything works beautifully with respect to nova-network. Since I can't
 easily port my KVM instances to Openstack, I wanted to start them up again
 under virsh. I recreated the br0 bridge as it was before. So far so good. I
 can start my legacy VMs and all works as expected. There's only one
 issue, and I don't even know if it's important.

 Before starting a Nova VM eth0 has no IP, which is expected as it's being
 covered by br0. But when I start one of the Nova VMs that has a floating
 IP, eth0 gains its IP! Everything seems to continue working, but it doesn't
 make sense to me.

 I don't know if this is expected behaviour or I simply have things
 configured wrong. Since it all still works I'm not overly concerned, but it
 does bug me. If anyone has insight into this I would be grateful.

 Thanks,
 Daniel
 ___
 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] cinder-volume ignoring rabbit config?

2013-04-26 Thread Dennis Jacobfeuerborn

Hi,
I'm trying to get the cinder-volume service working on a compute node 
but for some strange reason it seems to ignore the rabbit host 
configuration values.


In the log I see this:

2013-04-27 03:05:35DEBUG [qpid.messaging.io.raw] OPEN[31bbb00]: 
localhost:5672
2013-04-27 03:05:35ERROR [cinder.openstack.common.rpc.impl_qpid] 
Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 1 
seconds


Yet in the cinder.conf file I specified:
...
rabbit_host=10.16.171.3
rabbit_hosts=10.16.171.3:5672
...

There is no localhost or 127.0.0.1 present anywhere in that files 
and yet the service tries to connect to localhost:5672.

Any ideas what might be going on here?

Regards,
  Dennis

___
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] some sites don't work now

2013-04-26 Thread Gareth
Hi

=
[root@krugle-opensearch ~]# ping status.openstack.org
PING static.openstack.org (166.78.153.26) 56(84) bytes of data.

--- static.openstack.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

=
[root@krugle-opensearch ~]# ping logs.openstack.org
PING static.openstack.org (166.78.153.26) 56(84) bytes of data.

--- static.openstack.org ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms


-- 
Gareth

*Cloud Computing, Openstack, Fitness, Basketball
*
*OpenStack contributor*
*My promise: if you find any spelling or grammar mistakes in my email from
Mar 1 2013, notify me *
*and I'll donate $1 or ¥1 to an open organization you specify.*
___
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 failed in Jenkins: cloud-archive_folsom_version-drift #14681

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14681/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7016637483053363357.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14682

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14682/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1124983561600483384.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14683

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14683/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7237678237676362378.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14684

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14684/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6017304453994810426.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14686

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14686/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8995044678406072903.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14687

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14687/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6998354095552303688.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14688

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14688/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2202466129474442161.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14689

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14689/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3759981571301844152.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14690

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14690/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6131914866787580803.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14691

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14691/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson474099230337154569.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14692

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14692/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6387552311690035234.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14693

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14693/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson423141482153924269.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14694

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14694/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson891008620701133388.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14695

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14695/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7665204943908004442.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14698

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14698/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1938857494377329719.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14699

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14699/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson259695531367040530.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14700

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14700/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2741362552153384712.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14702

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14702/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5647200609051704003.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14703

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14703/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3275219856694.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14704

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14704/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7968828435998745970.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14705

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14705/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson4113764800406969797.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14706

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14706/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8465383269925896152.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14707

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14707/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6474162312989765443.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14708

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14708/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2542384216343927256.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14709

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14709/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1030617543168093206.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14711

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14711/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1676108115279075528.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14712

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14712/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8931752723886896170.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14713

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14713/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2960603727350243896.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14715

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14715/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8886524526742251179.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14716

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14716/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8286569942531173517.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14718

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14718/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1616328669701168144.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14719

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14719/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5183601728923515920.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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_havana_cinder_trunk #30

2013-04-26 Thread openstack-testing-bot
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/30/Project:precise_havana_cinder_trunkDate of build:Fri, 26 Apr 2013 12:01:33 -0400Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesEncode username and password in config fileby zhangchao010editcinder/volume/drivers/huawei/huawei_iscsi.pyeditcinder/tests/test_huawei.pyConsole Output[...truncated 1381 lines...]DEBUG:root:['bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']Building using working treeBuilding package in merge modeLooking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmphTu07Ybzr: ERROR: An error (1) occurred running quilt: Applying patch fix_cinder_dependencies.patchpatching file tools/pip-requiresHunk #1 FAILED at 18.1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-638fffc7-ce98-4225-9c88-837e993b5486', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-638fffc7-ce98-4225-9c88-837e993b5486', '-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/cinder/grizzly /tmp/tmphTu07Y/cindermk-build-deps -i -r -t apt-get -y /tmp/tmphTu07Y/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304261202~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [5ec17aa] Encode username and password in config filedch -a [781055b] Add stats reporting to Nexenta Driverdch -a [c03fcae] Remove duplicate method definitiondch -a [7d5787d] iscsi: Add ability to specify or autodetect block vs fileiodch -a [3727324] Rename duplicate test methoddebcommitbzr 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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-638fffc7-ce98-4225-9c88-837e993b5486', '-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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-638fffc7-ce98-4225-9c88-837e993b5486', '-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 failed in Jenkins: cloud-archive_folsom_version-drift #14720

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14720/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson9146735013785791984.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14721

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14721/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2594932599325548853.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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_havana_cinder_trunk #31

2013-04-26 Thread openstack-testing-bot
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/31/Project:precise_havana_cinder_trunkDate of build:Fri, 26 Apr 2013 12:31:36 -0400Build duration:2 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate to latest copy of OSLO incubatorby michael.kerrineditcinder/openstack/common/rpc/amqp.pyeditcinder/openstack/common/rpc/proxy.pyaddcinder/openstack/common/eventlet_backdoor.pyeditcinder/openstack/common/rpc/dispatcher.pyeditcinder/openstack/common/rpc/common.pyaddcinder/openstack/common/service.pyeditcinder/openstack/common/notifier/api.pyaddcinder/openstack/common/threadgroup.pyeditcinder/openstack/common/rpc/impl_qpid.pyaddcinder/openstack/common/loopingcall.pyeditcinder/openstack/common/gettextutils.pyeditcinder/openstack/common/rootwrap/filters.pyaddcinder/openstack/common/rootwrap/cmd.pyeditcinder/openstack/common/rpc/impl_fake.pyeditcinder/openstack/common/rpc/impl_zmq.pyeditcinder/openstack/common/log.pyeditcinder/openstack/common/jsonutils.pyaddcinder/openstack/common/rpc/zmq_receiver.pyFixes 3PAR FC driver synchronizationby james.braneneditcinder/volume/drivers/san/hp/hp_3par_fc.pyConsole Output[...truncated 1387 lines...]DEBUG:root:['bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']Building using working treeBuilding package in merge modeLooking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpZ98akibzr: ERROR: An error (1) occurred running quilt: Applying patch fix_cinder_dependencies.patchpatching file tools/pip-requiresHunk #1 FAILED at 18.1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4947a17b-f03c-4e07-a306-4ba6cdc585a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4947a17b-f03c-4e07-a306-4ba6cdc585a9', '-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/cinder/grizzly /tmp/tmpZ98aki/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpZ98aki/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304261232~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [5ec17aa] Encode username and password in config filedch -a [beacbd3] Fixes 3PAR FC driver synchronizationdch -a [781055b] Add stats reporting to Nexenta Driverdch -a [c03fcae] Remove duplicate method definitiondch -a [7d5787d] iscsi: Add ability to specify or autodetect block vs fileiodebcommitbzr 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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4947a17b-f03c-4e07-a306-4ba6cdc585a9', '-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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4947a17b-f03c-4e07-a306-4ba6cdc585a9', '-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 failed in Jenkins: cloud-archive_folsom_version-drift #14722

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14722/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5703116558889628922.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14723

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14723/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2469926468704606137.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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_havana_cinder_trunk #32

2013-04-26 Thread openstack-testing-bot
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/32/Project:precise_havana_cinder_trunkDate of build:Fri, 26 Apr 2013 13:01:36 -0400Build duration:2 min 29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesCinder wasnt filtering the backups returned to backup list APIby michael.kerrineditcinder/tests/test_backup.pyeditcinder/db/sqlalchemy/api.pyClear volumes stuck in downloadingby tynaneditcinder/volume/driver.pyeditcinder/volume/manager.pyeditcinder/tests/test_volume.pyRemove _path_exists method.by m.benchchaouieditcinder/volume/drivers/glusterfs.pyeditcinder/tests/test_nfs.pyeditcinder/tests/test_glusterfs.pyeditcinder/volume/drivers/nfs.pyConsole Output[...truncated 1386 lines...]DEBUG:root:['bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']Building using working treeBuilding package in merge modeLooking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpqV94ZWbzr: ERROR: An error (1) occurred running quilt: Applying patch fix_cinder_dependencies.patchpatching file tools/pip-requiresHunk #1 FAILED at 18.1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4bc6f950-5b3e-4472-aa2c-81917b4da2cd', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4bc6f950-5b3e-4472-aa2c-81917b4da2cd', '-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/cinder/grizzly /tmp/tmpqV94ZW/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpqV94ZW/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304261303~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [51218b2] Remove _path_exists method.dch -a [5ec17aa] Encode username and password in config filedch -a [3d18b30] Clear volumes stuck in 'downloading'dch -a [beacbd3] Fixes 3PAR FC driver synchronizationdch -a [781055b] Add stats reporting to Nexenta Driverdebcommitbzr 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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4bc6f950-5b3e-4472-aa2c-81917b4da2cd', '-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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-4bc6f950-5b3e-4472-aa2c-81917b4da2cd', '-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 failed in Jenkins: cloud-archive_folsom_version-drift #14724

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14724/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8382198278767016294.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14725

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14725/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson8484817030926419128.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #14726

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14726/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson2153945773192443443.sh
+ OS_RELEASE=folsom
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

quantum:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
glance:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.2~cloud0
nova:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 
2012.2.1+stable-20121212-a99a802e-0ubuntu1.4~cloud0
keystone:
Ubuntu: 2012.2.3+stable-20130206-82c87e56-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.3~cloud0
horizon:
Ubuntu: 2012.2.3-0ubuntu1
Cloud Archive staging: 2012.2.1-0ubuntu1~cloud0
cinder:
Ubuntu: 2012.2.3-0ubuntu2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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_havana_cinder_trunk #33

2013-04-26 Thread openstack-testing-bot
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/33/Project:precise_havana_cinder_trunkDate of build:Fri, 26 Apr 2013 14:01:36 -0400Build duration:2 min 19 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changescinder volume service keeps retrying even code exceptionby yuyangbjeditcinder/service.pyConsole Output[...truncated 1386 lines...]DEBUG:root:['bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']Building using working treeBuilding package in merge modeLooking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmp3B_W7kbzr: ERROR: An error (1) occurred running quilt: Applying patch fix_cinder_dependencies.patchpatching file tools/pip-requiresHunk #1 FAILED at 18.1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f068fef5-86d2-44ec-a9f6-0dbcdb7c6fd2', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f068fef5-86d2-44ec-a9f6-0dbcdb7c6fd2', '-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/cinder/grizzly /tmp/tmp3B_W7k/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp3B_W7k/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304261402~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [51218b2] Remove _path_exists method.dch -a [5ec17aa] Encode username and password in config filedch -a [3d18b30] Clear volumes stuck in 'downloading'dch -a [beacbd3] Fixes 3PAR FC driver synchronizationdch -a [781055b] Add stats reporting to Nexenta Driverdebcommitbzr 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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f068fef5-86d2-44ec-a9f6-0dbcdb7c6fd2', '-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 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f068fef5-86d2-44ec-a9f6-0dbcdb7c6fd2', '-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] Jenkins build is back to normal : cloud-archive_folsom_version-drift #14727

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/14727/


-- 
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_havana_glance_trunk #29

2013-04-26 Thread openstack-testing-bot
Title: precise_havana_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_glance_trunk/29/Project:precise_havana_glance_trunkDate of build:Fri, 26 Apr 2013 17:01:39 -0400Build duration:3 min 1 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesscrubber: dont print URI of image to be deletedby tom.hancockeditglance/store/scrubber.pyConsole Output[...truncated 2652 lines...]Build needed 00:01:32, 12080k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304261701~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304261701~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpnohKRF/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpnohKRF/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6e02cd147b3b22dc39344df48d3e40abf024240..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304261701~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d415611] Functional tests use a clean cached db that is only created once.dch -a [d3c5a6c] Fixes for mis-use of various exceptionsdch -a [545cb15] scrubber: dont print URI of image to be deleteddch -a [6335fdb] Eliminate the race when selecting a port for tests.dch -a [7d341de] Raise 404 while deleting a deleted imagedch -a [459e3e6] Sync with oslo-incubator copy of setup.py and version.pydch -a [6780571] Fix Qpid test casesdch -a [cd00848] Fix the deletion of a pending_delete image.dch -a [1e49329] Fix functional test 'test_scrubber_with_metadata_enc'dch -a [1c5a4d2] Call monkey_patch before other modules are loadeddch -a [6eaf42a] Improve unit tests for glance.api.middleware.cache moduledch -a [ae0f904] Add GridFS storedch -a [28b1129] Verify SSL certificates at boot timedch -a [b1ac90f] Add a policy handler to control copy-from functionalitydch -a [7155134] Add unit tests for glance.api.cached_images moduledebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.2+git201304261701~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A glance_2013.2+git201304261701~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304261701~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 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'glance_2013.2+git201304261701~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 failed in Jenkins: cloud-archive_grizzly_version-drift #5

2013-04-26 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/5/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/ws/
[cloud-archive_grizzly_version-drift] $ /bin/bash -xe 
/tmp/hudson5704745702067429180.sh
+ OS_RELEASE=grizzly
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py
 grizzly
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ 
/var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py
 -c -r grizzly
---
The following Cloud Archive packages for grizzly
have been superseded newer versions in Ubuntu!

nova:
Ubuntu: 1:2013.1-0ubuntu2
Cloud Archive staging: 1:2013.1-0ubuntu2~cloud1

--
Build step 'Execute shell' marked build as 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