Re: [Openstack] Images are not shown up for some tenants in Horizon
It appeared that I needed to increase the default value of limit_param_default in /etc/glance/glance-registry.conf (default value is 25). It helped to fix the problem. On Mon, Feb 18, 2013 at 6:51 PM, Andrii Loshkovskyi loshkovs...@gmail.comwrote: Hello, I have a few tenants and several images listed in Horizon. Strange, but some images are not shown up in one tenant. I've checked everything I could: users, roles, permissions, etc. I store images in Swift. I am able to list all images using the nova and glance command line tools or create VMs from those images and view them in Horizon. I know that you won't be checking my configuration. What I am trying to understand is how Horizon builds the images list. From the nova-registy debug log, it seems to be an SQL query which is a really large one. Could someone please point me out which function or SQL query in the Horizon code is responsible for building the images list? How does this feature work? I installed Horizon from the Ubuntu 12.04 repositories and its verision is: 2012.1-0ubuntu8 I would be greatful for any help. Thank you. -- Kind regards, Andrii Loshkovskyi -- Kind regards, Andrii Loshkovskyi ___ 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] Floating IP DNS
Hi all, is there some documentation about the openstack nova dns? (floating_ip_dns) How is it configured in nova.conf ? Best, Davide. ___ 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]A design draft of Storage Quota
I haven't had the chance to do a full reviews but here is a few toughts : - the account quota goes along this review: https://review.openstack.org/#/c/21563/ so we can get easily have account metadatas from middlewares. - I am not sure I fancy much the json blob in the ini config (why not a new config file?) - I have already an implementation that mostly follow the same structure as (the already merged) container quota middleware but I am waiting on the other review for account info metadata to send it for reviews. - Down the line but probably not for the v1 I like to be able to notify somewhere about the account being over quota ideally it would be an option to get to ceilometer or other plugged in system. Chmouel. On Wed, Feb 20, 2013 at 11:11 AM, Alex Yang alex890...@gmail.com wrote: Storage Quotas Designhttps://docs.google.com/document/d/1b5hkT_E8PyzaAPjNImW0SF-yyh8vGrN_DNjMChol4_Q/edit This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu ___ 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] [Quantum] Need suggestion on networking
Hi, I did Openstack(Folsom+Quantum) setup, with one controller node ( also running networking services) and 8 compute nodes. Both controller node and compute nodes have 2 NIC each, one on public network (internet) and one on private network. My requirement is that for each tenant, every VM should be connected to private network as well as it should also have public IP address, so that user can directly access that machine over internet. I might add some more compute node as well, and my VM counts can grow in range of 200-300+. You can assume that we do have these many public IP's available. My plan is to create vlan based private network for each tenant, but i am confused on the public network part of it. Shell i use provider network or use router/floating ip based networking. I want to user openvswtich (vlan) plugin for networking.Any suggestions? Thanks Anil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Help with VMs
The FreeBSD install using default boot loader. Assuming this is the right docs to refer to. http://www.freebsd.org/doc/handbook/serialconsole-setup.html Switching to grub boot loader within FreeBSD not done before. From: Ritesh Nanda riteshnand...@gmail.com To: harvey.w...@btinternet.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Tuesday, 19 February 2013, 18:44 Subject: Re: [Openstack] Help with VMs Harvey , To get console.log in ubuntu we need to make some changes in grub config Below steps works in ubuntu, hope only the file location would be different rest would be the same. Write /etc/default/grub GRUB_CMDLINE_LINUX=console=tty0 console=ttyS0,115200 then save and run update-grub2 update-grub On Wed, Feb 20, 2013 at 12:07 AM, Jonathan Proulx j...@jonproulx.com wrote: On Tue, Feb 19, 2013 at 1:25 PM, Harvey West harvey.w...@btinternet.com wrote: This boots ok. kvm -m 2048 -hda freeBSD.img -boot c (note: did not use virtio mods. Assumed these were just optimized NIC/SCSI drivers. Which I can live without for the time being) I ran into the same isssue with FreeBSD images. These are paravirtualized drivers which are absolutely required to get the VM to work. Linux images usually have them already but for FreeBSD (and Windows) you need to install them by hand. note that when using kvm by hand you can specify the driver emulation required so this is why it boots by hand but not via openstack (you could also configure openstack to use different kvm settings, but the virtio driver is faster and installing the drivers on FreeBSD isn't too hard. I'm not much of a *BSD guy but I managed) -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- With Regards Ritesh Nanda___ 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]A design draft of Storage Quota
Hi, you might also have a look at https://github.com/cschwede/swquota Account quota is stored in account metadata and set by a reseller account. I changed the code slightly to make it more consistent to the already merged container quota. @chmouel: I might create a pull request to swift itself - what do you think? Christian Am Mittwoch, den 20.02.2013, 11:11 +0100 schrieb Alex Yang alex890...@gmail.com: Storage Quotas Design [1] This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota [2] ___ 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] security releases
Matthew Thode wrote: Is there any plan to have security releases for the supported versions of the various Openstack components? Like having a 2012.2.3.3 for keystone (the last number being the security release). We provide hotfixes in the advisories, and the fixes are included in our next source code point releases (2012.2.4). Most distributions provide packages which include recent security fixes. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Horizon Keystone Endpoint Issue
192.168.202.103 = public controller iface
192.168.203.103 = private controller iface
anyway, I still get the login problem using any of those values
Le 20/02/2013 06:59, Kieran Spear a écrit :
On 20 February 2013 03:40, Michaël Van de Borne
michael.vandebo...@cetic.be mailto:michael.vandebo...@cetic.be wrote:
Same problem here. Running Grizzly. Dashboard keeps prompting me
for my credentials. Pretty sure dashboard sends wrong tenant name
to keystone.
Here's the relevant section in
/etc/openstack-dashboard/local-settings.py:
OPENSTACK_HOST = 192.168.202.103
OPENSTACK_KEYSTONE_URL = http://%s:5000/v2.0;
http://%s:5000/v2.0 % OPENSTACK_HOST
#OPENSTACK_KEYSTONE_DEFAULT_ROLE = Member
OPENSTACK_KEYSTONE_DEFAULT_ROLE = admin
Is that 202 a typo? You used 192.168.203.103 later.
Cheers,
Kieran
michaël
Le 13/02/2013 16:13, Razique Mahroua a écrit :
Is the dash configured to talk with the Keystone backend?
can you run something like $ keystone endoint-list
thanks
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com mailto:razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15 tel:%2B33%209%2072%2037%2094%2015
Le 12 févr. 2013 à 16:54, Logan McNaughton lo...@bacoosta.com
mailto:lo...@bacoosta.com a écrit :
I've had this problem before, in my experience it's not a
problem with keystone, it's a problem with nova (by the looks of
the traceback). I believe it's a bug in Horizon because you'll
find a lot of people with this issue if you Google it. I don't
have an answer on how to fix it, other than don't fixate on the
EndpointNotFound, look to your nova configs for a solution.
On Tue, Feb 12, 2013 at 5:03 AM, Trinath Somanchi
trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com
wrote:
Hi Stackers-
I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as
credentials, I get this error.
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error] unable to
retrieve service catalog with token
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error] Traceback
(most recent call last):
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py,
line 132, in _extract_service_catalog
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error]
endpoint_type='adminURL')
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py,
line 62, in url_for
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Feb 12 10:03:16 2013 tel:16%202013] [error]
EndpointNotFound: Endpoint not found.
[Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized:
n/a (HTTP 401)\x1b[0m
[Tue Feb 12 10:03:17 2013] [error] Traceback (most recent
call last):
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py,
line 93, in summarize
[Tue Feb 12 10:03:17 2013] [error] self.usage_list =
self.get_usage_list(start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py,
line 128, in get_usage_list
[Tue Feb 12 10:03:17 2013] [error] return
api.usage_list(self.request, start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/api/nova.py, line
418, in usage_list
[Tue Feb 12 10:03:17 2013] [error] return [Usage(u) for
u in novaclient(request).usage.list(start, end, True)]
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py,
line 35, in list
[Tue Feb 12 10:03:17 2013] [error] tenant_usages)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/base.py, line
62, in _list
[Tue Feb 12 10:03:17 2013] [error] _resp, body =
self.api.client.get(url)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py,
line 239, in get
[Tue Feb 12 10:03:17 2013] [error] return
self._cs_request(url, 'GET', **kwargs)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py,
line 236, in _cs_request
[Tue Feb 12 10:03:17 2013] [error] raise ex
[Tue Feb 12 10:03:17 2013] [error] Unauthorized: n/a (HTTP 401)
It says , I missed some End point Configuration.
But then, I have configured it correctly.
Can any one guide me resolving this issue.
Thanks
Re: [Openstack] Horizon Keystone Endpoint Issue
Also, on quick think to look is the apache error log while you access the
horizon.
look at the log as, tail -f /var/log/apache/error.log.
On Wed, Feb 20, 2013 at 5:07 PM, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
192.168.202.103 = public controller iface
192.168.203.103 = private controller iface
anyway, I still get the login problem using any of those values
Le 20/02/2013 06:59, Kieran Spear a écrit :
On 20 February 2013 03:40, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
Same problem here. Running Grizzly. Dashboard keeps prompting me for my
credentials. Pretty sure dashboard sends wrong tenant name to keystone.
Here's the relevant section in /etc/openstack-dashboard/local-settings.py:
OPENSTACK_HOST = 192.168.202.103
OPENSTACK_KEYSTONE_URL = http://%s:5000/v2.0; % OPENSTACK_HOST
#OPENSTACK_KEYSTONE_DEFAULT_ROLE = Member
OPENSTACK_KEYSTONE_DEFAULT_ROLE = admin
Is that 202 a typo? You used 192.168.203.103 later.
Cheers,
Kieran
michaël
Le 13/02/2013 16:13, Razique Mahroua a écrit :
Is the dash configured to talk with the Keystone backend?
can you run something like $ keystone endoint-list
thanks
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 12 févr. 2013 à 16:54, Logan McNaughton lo...@bacoosta.com a écrit
:
I've had this problem before, in my experience it's not a problem with
keystone, it's a problem with nova (by the looks of the traceback). I
believe it's a bug in Horizon because you'll find a lot of people with this
issue if you Google it. I don't have an answer on how to fix it, other than
don't fixate on the EndpointNotFound, look to your nova configs for a
solution.
On Tue, Feb 12, 2013 at 5:03 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi Stackers-
I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as credentials, I get
this error.
[Tue Feb 12 10:03:16 2013 16%202013] [error] unable to retrieve
service catalog with token
[Tue Feb 12 10:03:16 2013 16%202013] [error] Traceback (most recent
call last):
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py, line 132,
in _extract_service_catalog
[Tue Feb 12 10:03:16 2013 16%202013] [error]
endpoint_type='adminURL')
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py, line
62, in url_for
[Tue Feb 12 10:03:16 2013 16%202013] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Feb 12 10:03:16 2013 16%202013] [error] EndpointNotFound:
Endpoint not found.
[Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized: n/a (HTTP
401)\x1b[0m
[Tue Feb 12 10:03:17 2013] [error] Traceback (most recent call last):
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py, line 93, in
summarize
[Tue Feb 12 10:03:17 2013] [error] self.usage_list =
self.get_usage_list(start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py, line 128, in
get_usage_list
[Tue Feb 12 10:03:17 2013] [error] return
api.usage_list(self.request, start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/api/nova.py, line 418, in
usage_list
[Tue Feb 12 10:03:17 2013] [error] return [Usage(u) for u in
novaclient(request).usage.list(start, end, True)]
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py, line 35, in
list
[Tue Feb 12 10:03:17 2013] [error] tenant_usages)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in _list
[Tue Feb 12 10:03:17 2013] [error] _resp, body =
self.api.client.get(url)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py, line 239, in get
[Tue Feb 12 10:03:17 2013] [error] return self._cs_request(url,
'GET', **kwargs)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py, line 236, in
_cs_request
[Tue Feb 12 10:03:17 2013] [error] raise ex
[Tue Feb 12 10:03:17 2013] [error] Unauthorized: n/a (HTTP 401)
It says , I missed some End point Configuration.
But then, I have configured it correctly.
Can any one guide me resolving this issue.
Thanks in advance.
--
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
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] folsom basic installtion
We are more or less through with Folsom Basic installation. We are following the basic installation guide on openstack website. But we are encountering many networking and installation errors. 1) Installation errors occur on the controller node. 2) I think we are doing the networking wrong. We have connected the management network through a switch, and the same with the Data network. The IP addresses are all set to the given values of the manual itself, using the interfaces file. I didn't understand about the bridges for the External and API networks. I mean we have connected it directly to the internet, which in-turn comes from a switch. Is that correct? 3) After having the network set-up, i am unable to ping to the other computers. On both Management and Data networks.How should i fix that? How can i know that the network is up and running properly? Thanks ___ 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] Account or User or Account_User?
Unless tester3 is given explicit permissions he can't do anything. To be of any use the 'test' user (who is an admin) would need to grant 'test3' read/write access to a container. Permissions are granted using the X-Container-Read and X-Container-Write headers on containers, http://docs.openstack.org/folsom/openstack-object-storage/admin/content/authentication-and-access-permissions.html. Adrian On 20 February 2013 05:34, Kun Huang academicgar...@gmail.com wrote: In tempauth of SAIO, what's the meaning of user_test_tester3 = testing3 not account is test tester3 is a user of that account, but tester3 is not admin or reseller admin. Could testers get(GET,HEAD) information from account:test? In the current code, the answer is no. I'm not sure what can tester3 do in this case? ___ 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] [openstack-dev] Restart devstack errors
you need analyze your keystone log to get the reason why keystone fails, they are in /opt/stack/logs/screen/ thanks, lyon 在 2013-2-20 下午1:39，harryxiyou harryxi...@gmail.com写道： Hi all, When i reboot my OS, i have to install devstack again. But i caught following errors during the restart + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.3:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start + exit 1 + clean + local r=1 ++ jobs -p + kill + exit 1 Could anyone give me some suggestions? Thanks a lot. -- Thanks Harry Wei ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ 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] [cloudxy] Re: [openstack-dev] Restart devstack errors
On Wed, Feb 20, 2013 at 8:00 PM, Liang Liang lyon.lian...@gmail.com wrote: you need analyze your keystone log to get the reason why keystone fails, they are in /opt/stack/logs/screen/ I cannot find /opt/stack/logs dir. -- Thanks Harry Wei ___ 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] Minutes from the Technical Committee meeting (Feb 19)
The OpenStack Technical Committee (TC) met in #openstack-meeting at 20:00 UTC yesterday. Here is a quick summary of the outcome of this meeting: * The TC approved the graduation of the Heat project (to be integrated in common Havana release) * The TC considered the suggestion of the Board of Directors to hold a common meeting on April 14. It's difficult to predict how many TC members will be able to make it (some members already have conflicting plane tickets), especially considering that almost all of the TC members will be renewed in upcoming elections in March. If confirmed on Sunday, the joint meeting should be very optional. Alternatives include a short meeting during one of the mornings (+ breakfast) or evenings (+ dinner) of the Summit days (outside regular summit hours). See details and full logs at: http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-19-20.02.html More information on the Technical Committee at: http://wiki.openstack.org/Governance/TechnicalCommittee -- Thierry Carrez (ttx) Chair, OpenStack Technical Committee ___ 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] Cant ping private or floating IP
Le 20/02/2013 14:04, Chathura M. Sarathchandra Magurawalage a écrit : There are apparently two instances running in the compute node but nova just see only one. Probably when I have deleted an instance earlier it had not deleted the instance properly. root@controller:~# nova list +--+++---+ | ID | Name | Status | Networks | +--+++---+ | 42e18cd5-de6f-4181-b238-320fe37ef6f1 | master | ACTIVE | demo-net=10.5.5.3 | +--+++---+ virsh -c qemu+ssh://root@computenode/system list root@computenode's password: IdName State 14instance-002c running 18instance-001e running You should have seen at 'sudo virsh list --all', plus looking at /etc/libvirt/qemu/*.xml to check how many instances were defined. I do suspect also that for some reason (probably nova-compute down), a clean-up of 2c probably didn't work. Anyway, this is fixed as you mention. Then I have deleted all instances and created a new one. But still cant ping or ssh the new VM. interface type='bridge' mac address='fa:16:3e:a2:6e:02'/ source bridge='qbrff8933bf-ba'/ model type='virtio'/ filterref filter='nova-instance-instance-0035-fa163ea26e02' parameter name='DHCPSERVER' value='10.5.5.2'/ parameter name='IP' value='10.5.5.3'/ parameter name='PROJMASK' value='255.255.255.0'/ parameter name='PROJNET' value='10.5.5.0'/ /filterref address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'\ / /interface Starting network... udhcpc (v1.18.5) started Sending discover... Sending select for 10.5.5.3... Lease of 10.5.5.3 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 8.8.8.8 The DHCP reply is correctly received by the instance from the network node to the compute node. This is not a network issue (at least for IP assignation). I would be more concerned about the SIOCDELRT error above. Do you try to manually remove a network route at bootup ? Seems like the 'route del' is failing because the route is not already existing. As already said, you absolutely need VNC support for investigating. Could you please fix your VNC setup which is incorrect ? graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-u\ s' listen type='address' address='0.0.0.0'/ /graphics Try in nova-compute.conf : vncserver_proxyclient_address=compute node mgmt IP vncserver_listen=compute node mgmt IP and in nova.conf : novncproxy_base_url=http://controler node mgmt IP:6080/vnc_auto.html and restart nova-compute. On 20 February 2013 11:57, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Could you please paste : - /etc/libvirt/qemu/your_instance_id.xml - ip a show vnet0 - brctl show Sounds like your virtual device is not created. Could you please launch a new VM and paste /var/log/nova/nova-compute.log ? Thanks, -Sylvain ___ 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] Keystone LDAP integration
Hi Folks, we're trying to set up keystone with ldap. so far, so good. we can authenticate. but we can not give the admin-user 'god'-rights. Through tweaks of the policy.json-file it's possible that the admin-user sees all tenants, but he doesn't get the 'admin' tab in horizon. Any help is really appreciated. Wolfgang ___ 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] Metadata service route from a VM
Hi, Previously using nova-network, all my VMs were having : # route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 00 eth0 0.0.0.0 10.0.0.10.0.0.0 UG0 00 eth0 Now, this setup seems incorrect with Quantum, as the ARP query goes directly from the network node trying to resolve 169.254.169.254 : [root@toto ~]# curl http://169.254.169.254/ curl: (7) couldn't connect to host sylvain@folsom02:~$ sudo tcpdump -i qr-f76e4668-fa -nn not ip6 and not udp and host 169.254.169.254 -e tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qr-f76e4668-fa, link-type EN10MB (Ethernet), capture size 65535 bytes 15:47:46.009548 fa:16:3e:bf:0b:f6 ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.169.254 tell 10.0.0.5, length 28 15:47:47.009076 fa:16:3e:bf:0b:f6 ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 169.254.169.254 tell 10.0.0.5, length 28 The only way for me to fix it is to remove the 169.254.0.0/16 route on the VM (or for some reason I doesn't understand, by restarting quantum-dhcp-agent on the network node) and then L3 routing is working correctly : [root@toto ~]# route del -net 169.254.0.0/16 [root@toto ~]# curl http://169.254.169.254/ 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04 sylvain@folsom02:~$ sudo tcpdump -i qg-f2397006-20 -nn not ip6 and not udp and host 10.0.0.5 and not port 22 -e tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qg-f2397006-20, link-type EN10MB (Ethernet), capture size 65535 bytes 15:52:58.479234 fa:16:3e:e1:95:20 e0:46:9a:2c:f4:7d, ethertype IPv4 (0x0800), length 74: 10.0.0.5.55428 192.168.1.71.8775: Flags [S], seq 3032859044, win 14600, options [mss 1460,sackOK,TS val 2548891 ecr 0,nop,wscale 5], length 0 15:52:58.480987 e0:46:9a:2c:f4:7d fa:16:3e:e1:95:20, ethertype IPv4 (0x0800), length 74: 192.168.1.71.8775 10.0.0.5.55428: Flags [S.], seq 3888257357, ack 3032859045, win 14480, options [mss 1460,sackOK,TS val 16404712 ecr 2548891,nop,wscale 7], length 0 15:52:58.482211 fa:16:3e:e1:95:20 e0:46:9a:2c:f4:7d, ethertype IPv4 (0x0800), length 66: 10.0.0.5.55428 192.168.1.71.8775: Flags [.], ack 1, win 457, options [nop,nop,TS val 2548895 ecr 16404712], length 0 I can't understand what's wrong with my setup. Could you help me ? I would have to undergo a post-up statement for all my images... :( Thanks, -Sylvain ___ 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] security releases
On 02/20/13 05:40, Thierry Carrez wrote: Matthew Thode wrote: Is there any plan to have security releases for the supported versions of the various Openstack components? Like having a 2012.2.3.3 for keystone (the last number being the security release). We provide hotfixes in the advisories, and the fixes are included in our next source code point releases (2012.2.4). Most distributions provide packages which include recent security fixes. Regards, Ya, that's what I'm doing, just didn't know if you were going to go the other way, thanks for the answer. -- -- Matthew Thode signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift]A design draft of Storage Quota
Hi Schwede, I have already read your codes. To implement the authentication of updating metadata in the middleware is good for maintainance. But the account usage is not accurate because of the eventual consistency. So I do the usage quota based on container. I will refactor my implementation collaborate with your work and Boudjnah's work. Thanks! . 2013/2/20 Christian Schwede i...@cschwede.de Hi, you might also have a look at https://github.com/cschwede/**swquotahttps://github.com/cschwede/swquota Account quota is stored in account metadata and set by a reseller account. I changed the code slightly to make it more consistent to the already merged container quota. @chmouel: I might create a pull request to swift itself - what do you think? Christian Am Mittwoch, den 20.02.2013, 11:11 +0100 schrieb Alex Yang alex890...@gmail.com: Storage Quotas Design [1] This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/**StackLab-swift/tree/dev-quotahttps://github.com/AlexYangYu/StackLab-swift/tree/dev-quota[2] -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu ___ 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]A design draft of Storage Quota
2013/2/20 Chmouel Boudjnah chmo...@chmouel.com I haven't had the chance to do a full reviews but here is a few toughts : - the account quota goes along this review: https://review.openstack.org/#/c/21563/ so we can get easily have account metadatas from middlewares. Yes, I also want quota-level to be stored in memcache through the account_info() function. - I am not sure I fancy much the json blob in the ini config (why not a new config file?) It's a good suggestion. - I have already an implementation that mostly follow the same structure as (the already merged) container quota middleware but I am waiting on the other review for account info metadata to send it for reviews. - Down the line but probably not for the v1 I like to be able to notify somewhere about the account being over quota ideally it would be an option to get to ceilometer or other plugged in system. Chmouel. On Wed, Feb 20, 2013 at 11:11 AM, Alex Yang alex890...@gmail.com wrote: Storage Quotas Designhttps://docs.google.com/document/d/1b5hkT_E8PyzaAPjNImW0SF-yyh8vGrN_DNjMChol4_Q/edit This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 杨雨 Email: alex890...@gmail.com GitHub: https://github.com/AlexYangYu Blog:http://alexyang.sinaapp.com Weibo: http://www.weibo.com/alexyangyu ___ 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] Fwd: Fwd: Initial quantum network state broken
Hey Anil, thanks for responding. Here's the output: root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-vsctl show 9d9f7949-2b80-40c8-a9e0-6a116200ed96 Bridge br-int Port br-int Interface br-int type: internal Port int-br-eth1 Interface int-br-eth1 Bridge br-eth1 Port phy-br-eth1 Interface phy-br-eth1 Port br-eth1 Interface br-eth1 type: internal Port eth1 Interface eth1 ovs_version: 1.4.3 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-dpctl show system@br-eth1: lookups: hit:5227 missed:24022 lost:0 flows: 1 port 0: br-eth1 (internal) port 1: eth1 port 6: phy-br-eth1 system@br-int: lookups: hit:2994 missed:13754 lost:0 flows: 1 port 0: br-int (internal) port 2: int-br-eth1 root@kvm-cs-sn-10i:/var/lib/nova/instances# brctl show bridge name bridge id STP enabled interfaces br-eth1 .bc305befedd1 no eth1 phy-br-eth1 br-int .8ae31e5f7941 no int-br-eth1 qbr5334a0cb-64 8000.76fb293fe9cf no qvb5334a0cb-64 vnet0 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=75251.156s, table=0, n_packets=16581, n_bytes=3186436, priority=2,in_port=2 actions=drop cookie=0x0, duration=75251.527s, table=0, n_packets=0, n_bytes=0, priority=1 actions=NORMAL Thanks! I have until tomorrow to get this working, then my boss has mandating that I try Cloudstack. Argh, but I'm so close! On Wed, Feb 20, 2013 at 10:29 AM, Anil Vishnoi vishnoia...@gmail.comwrote: Hi Greg, Can you paste the output of following command from your compute node. ovs-vsctl show ovs-dpctl show brctl show ovs-ofctl dump-flows br-int ovs-ofctl dump-flows br-eth1 Because i think first issue we need to resolve here is why DHCP packet is not leaving your compute host. Anil On Wed, Feb 20, 2013 at 6:48 AM, Greg Chavez greg.cha...@gmail.comwrote: From my perspective, it seems that the OVS bridges are not being brought up correctly. As you can see in my earlier post, the integration bridge (int) and the physical interface bridges (br-ex and br-eth1) are downed. I've tried to bring them up in promiscuous mode in the case of br-int, and with the physical interfaces ported to the bridge in the case of br-ex and br-eth1. I've had no luck unfortunately. It seems that nothing is getting past br-int. I can see BOOTP packets on the VM side of br-int, and I can see VTP packets on the physical side of br-int. But that's where it ends. For example, when I reboot my VM, I see this: root@kvm-cs-sn-10i:/var/lib/nova/instances# tcpdump -i qvo5334a0cb-64 tcpdump: WARNING: qvo5334a0cb-64: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qvo5334a0cb-64, link-type EN10MB (Ethernet), capture size 65535 bytes 13:42:08.099061 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:08.101675 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:08.161728 IP6 :: ff02::1:ff06:4809: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe06:4809, length 24 13:42:08.373745 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:11.102528 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:14.105850 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 But that's as far as it goes. The dhcp agent never get this. Ive tried deleting and recreating the bridges, rebooting the systems, but nothing seems to work. Maybe it's just the right combination of things. I don't know. Help! On Tue, Feb 19, 2013 at 5:23 AM, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi Greg, I did have trouble with DHCP assignation (see my previous post in this list), which was being fixed by deleting ovs bridges on network node, recreating them and restarting OVS plugin and L3/DHCP agents (which were all on the same physical node). Maybe it helps. Anyway, when DHCP'ing from your VM (asking for an IP), could you please tcpdump : 1. your virtual network interface on compute node 2. your physical network interface on compute node 3. your physical network interface on network node and see BOOTP/DHCP packets ? On the physical layer, you should see GRE packets (provided you correctly followed the mentioned guide) encapsulating your BOOTP/DHCP packets. If that's OK, could you please issue the below commands (on the network node) : - brctl show - ip a - ovs-vsctl show - route -n Thanks, -Sylvain Le 19/02/2013 00:55, Greg Chavez a écrit : Third time I'm replying to my own message. It seems like the initial network state is a problem for many first time openstackers.
Re: [Openstack] Fwd: Initial quantum network state broken
Here's the last command output you asked for: root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-ofctl dump-flows br-eth1 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=78793.694s, table=0, n_packets=6, n_bytes=468, priority=2,in_port=6 actions=drop cookie=0x0, duration=78794.033s, table=0, n_packets=17355, n_bytes=3335788, priority=1 actions=NORMAL On Wed, Feb 20, 2013 at 10:57 AM, Greg Chavez greg.cha...@gmail.com wrote: Hey Anil, thanks for responding. Here's the output: root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-vsctl show 9d9f7949-2b80-40c8-a9e0-6a116200ed96 Bridge br-int Port br-int Interface br-int type: internal Port int-br-eth1 Interface int-br-eth1 Bridge br-eth1 Port phy-br-eth1 Interface phy-br-eth1 Port br-eth1 Interface br-eth1 type: internal Port eth1 Interface eth1 ovs_version: 1.4.3 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-dpctl show system@br-eth1: lookups: hit:5227 missed:24022 lost:0 flows: 1 port 0: br-eth1 (internal) port 1: eth1 port 6: phy-br-eth1 system@br-int: lookups: hit:2994 missed:13754 lost:0 flows: 1 port 0: br-int (internal) port 2: int-br-eth1 root@kvm-cs-sn-10i:/var/lib/nova/instances# brctl show bridge name bridge id STP enabled interfaces br-eth1 .bc305befedd1 no eth1 phy-br-eth1 br-int .8ae31e5f7941 no int-br-eth1 qbr5334a0cb-64 8000.76fb293fe9cf no qvb5334a0cb-64 vnet0 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=75251.156s, table=0, n_packets=16581, n_bytes=3186436, priority=2,in_port=2 actions=drop cookie=0x0, duration=75251.527s, table=0, n_packets=0, n_bytes=0, priority=1 actions=NORMAL Thanks! I have until tomorrow to get this working, then my boss has mandating that I try Cloudstack. Argh, but I'm so close! On Wed, Feb 20, 2013 at 10:29 AM, Anil Vishnoi vishnoia...@gmail.comwrote: Hi Greg, Can you paste the output of following command from your compute node. ovs-vsctl show ovs-dpctl show brctl show ovs-ofctl dump-flows br-int ovs-ofctl dump-flows br-eth1 Because i think first issue we need to resolve here is why DHCP packet is not leaving your compute host. Anil On Wed, Feb 20, 2013 at 6:48 AM, Greg Chavez greg.cha...@gmail.comwrote: From my perspective, it seems that the OVS bridges are not being brought up correctly. As you can see in my earlier post, the integration bridge (int) and the physical interface bridges (br-ex and br-eth1) are downed. I've tried to bring them up in promiscuous mode in the case of br-int, and with the physical interfaces ported to the bridge in the case of br-ex and br-eth1. I've had no luck unfortunately. It seems that nothing is getting past br-int. I can see BOOTP packets on the VM side of br-int, and I can see VTP packets on the physical side of br-int. But that's where it ends. For example, when I reboot my VM, I see this: root@kvm-cs-sn-10i:/var/lib/nova/instances# tcpdump -i qvo5334a0cb-64 tcpdump: WARNING: qvo5334a0cb-64: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qvo5334a0cb-64, link-type EN10MB (Ethernet), capture size 65535 bytes 13:42:08.099061 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:08.101675 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:08.161728 IP6 :: ff02::1:ff06:4809: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe06:4809, length 24 13:42:08.373745 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:11.102528 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:14.105850 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 But that's as far as it goes. The dhcp agent never get this. Ive tried deleting and recreating the bridges, rebooting the systems, but nothing seems to work. Maybe it's just the right combination of things. I don't know. Help! On Tue, Feb 19, 2013 at 5:23 AM, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi Greg, I did have trouble with DHCP assignation (see my previous post in this list), which was being fixed by deleting ovs bridges on network node, recreating them and restarting OVS plugin and L3/DHCP agents (which were all on the same physical node). Maybe it helps. Anyway, when DHCP'ing from your VM (asking for an IP), could you please tcpdump : 1. your virtual network interface on compute node 2. your physical network interface on compute node 3. your physical network interface on network node and see BOOTP/DHCP packets ? On the
Re: [Openstack] [cloudxy] Re: [openstack-dev] Restart devstack errors
2013/2/20 harryxiyou harryxi...@gmail.com On Wed, Feb 20, 2013 at 8:00 PM, Liang Liang lyon.lian...@gmail.com wrote: you need analyze your keystone log to get the reason why keystone fails, they are in /opt/stack/logs/screen/ I cannot find /opt/stack/logs dir. Use screen to see the logging output: $screen -d -m -S screen-name -t shell -s /bin/bash $ screen -x stack -- Thanks Harry Wei -- 您收到此邮件是因为您订阅了 Google 网上论坛的“cloudxy”论坛。 要退订此论坛并停止接收此论坛的电子邮件，请发送电子邮件到 cloudxy+unsubscr...@googlegroups.com。 要查看更多选项，请访问 https://groups.google.com/groups/opt_out。 -- --Ben Trystack.cn By Stacker, for Stacker! Mobile: +86 15921531026 WEIBO: http://weibo.com/u/1716287123http://www.weibo.com/u/1716287123?from=profilewvr=4loc=infweihao TWITTER: https://twitter.com/ben_Duyujie LINKEDIN: cn.linkedin.com/in/duyujie http://about.me/Yujie.Du ___ 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]A design draft of Storage Quota
On Wed, 2013-02-20 at 18:11 +0800, Alex Yang wrote: Storage Quotas Design This is the design draft of Storage Quota. Implementation of this design is https://github.com/AlexYangYu/StackLab-swift/tree/dev-quota I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately, I'm not able to work on Boson at the moment due to higher-priority tasks… -- Kevin L. Mitchell kevin.mitch...@rackspace.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] external dhcp server instead of dnsmasq
Thanks Mark, I tried it and it works, would like to appreciate the idea behind it. As i am using vlan manager in nova-network , i would like to create a new domain for each tenant created in keystone.That tenant would be having a seprate network. I can understand the process , i would even try that , but can you give me more brief idea , how to do that. On Wed, Feb 20, 2013 at 5:01 AM, Mark Lehrer m...@tpsit.com wrote: Or is there any way in openstack i can implement dynamic dns in openstack. If you want your VM's to automatically get a DNS entry, I have a MyDNS add-on that can do it. MyDNS is a DNS server that uses a database instead of zone files. You just have to pick a domain or subdomain, and then make a union between the standard MyDNS RR table and the Openstack instances table. I made a .deb of it that includes MyDNS and documentation on how to create the union, you can grab it at: http://knm.org/mydns-mysql_1.**2.8.31_amd64.debhttp://knm.org/mydns-mysql_1.2.8.31_amd64.deb I was planning to update it for Grizzly and I also wanted to maybe try PowerDNS, but I have been using this system since May and it works pretty well. Let me know if you have any questions. Mark -- * With Regards * * Ritesh Nanda * *** * http://www.ericsson.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] Horizon Keystone Endpoint Issue
I solved the problem by downgrading the horizon for packages below
apt-get install \
openstack-dashboard=2012.1.3+stable~20120815-691dd2-0ubuntu1.1 \
openstack-dashboard-ubuntu-theme=2012.1.3+stable~20120815-691dd2-0ubuntu1.1
\
python-django-horizon=2012.1.3+stable~20120815-691dd2-0ubuntu1.1
att
Alex Vitola
2013/2/20 Trinath Somanchi trinath.soman...@gmail.com
Also, on quick think to look is the apache error log while you access the
horizon.
look at the log as, tail -f /var/log/apache/error.log.
On Wed, Feb 20, 2013 at 5:07 PM, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
192.168.202.103 = public controller iface
192.168.203.103 = private controller iface
anyway, I still get the login problem using any of those values
Le 20/02/2013 06:59, Kieran Spear a écrit :
On 20 February 2013 03:40, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
Same problem here. Running Grizzly. Dashboard keeps prompting me for
my credentials. Pretty sure dashboard sends wrong tenant name to keystone.
Here's the relevant section in
/etc/openstack-dashboard/local-settings.py:
OPENSTACK_HOST = 192.168.202.103
OPENSTACK_KEYSTONE_URL = http://%s:5000/v2.0; % OPENSTACK_HOST
#OPENSTACK_KEYSTONE_DEFAULT_ROLE = Member
OPENSTACK_KEYSTONE_DEFAULT_ROLE = admin
Is that 202 a typo? You used 192.168.203.103 later.
Cheers,
Kieran
michaël
Le 13/02/2013 16:13, Razique Mahroua a écrit :
Is the dash configured to talk with the Keystone backend?
can you run something like $ keystone endoint-list
thanks
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 12 févr. 2013 à 16:54, Logan McNaughton lo...@bacoosta.com a
écrit :
I've had this problem before, in my experience it's not a problem with
keystone, it's a problem with nova (by the looks of the traceback). I
believe it's a bug in Horizon because you'll find a lot of people with this
issue if you Google it. I don't have an answer on how to fix it, other than
don't fixate on the EndpointNotFound, look to your nova configs for a
solution.
On Tue, Feb 12, 2013 at 5:03 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi Stackers-
I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as credentials, I get
this error.
[Tue Feb 12 10:03:16 2013 16%202013] [error] unable to retrieve
service catalog with token
[Tue Feb 12 10:03:16 2013 16%202013] [error] Traceback (most recent
call last):
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py, line 132,
in _extract_service_catalog
[Tue Feb 12 10:03:16 2013 16%202013] [error]
endpoint_type='adminURL')
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py, line
62, in url_for
[Tue Feb 12 10:03:16 2013 16%202013] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Feb 12 10:03:16 2013 16%202013] [error] EndpointNotFound:
Endpoint not found.
[Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized: n/a (HTTP
401)\x1b[0m
[Tue Feb 12 10:03:17 2013] [error] Traceback (most recent call last):
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py, line 93, in
summarize
[Tue Feb 12 10:03:17 2013] [error] self.usage_list =
self.get_usage_list(start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py, line 128, in
get_usage_list
[Tue Feb 12 10:03:17 2013] [error] return
api.usage_list(self.request, start, end)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/api/nova.py, line 418, in
usage_list
[Tue Feb 12 10:03:17 2013] [error] return [Usage(u) for u in
novaclient(request).usage.list(start, end, True)]
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py, line 35, in
list
[Tue Feb 12 10:03:17 2013] [error] tenant_usages)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in _list
[Tue Feb 12 10:03:17 2013] [error] _resp, body =
self.api.client.get(url)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py, line 239, in get
[Tue Feb 12 10:03:17 2013] [error] return self._cs_request(url,
'GET', **kwargs)
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py, line 236, in
_cs_request
[Tue Feb 12 10:03:17 2013] [error] raise ex
[Tue Feb 12 10:03:17 2013] [error] Unauthorized: n/a (HTTP 401)
It says , I missed some End point Configuration.
But then, I have configured it correctly.
Can any one guide me resolving this issue.
Thanks in advance.
--
Regards,
--
Trinath Somanchi,
+91 9866 235
Re: [Openstack] Horizon Keystone Endpoint Issue
I did the update of all services (new, cinder, glance, horizon, keystone),
and let all the options of the * default. conf, just changing the filter
and sql session: authtoken.
And now it works again
0.2-1ubuntu1~cloud0 - python-jsonschema
0.6-1ubuntu1~cloud0 - python-prettytable
0.7.8-1ubuntu1~cloud0 - python-sqlalchemy
0.7.8-1ubuntu1~cloud0 - python-sqlalchemy-ext
0.8.0-2ubuntu1~cloud0 - python-mock
0.9.17-0ubuntu1.1~cloud0 - python-eventlet
1:0.1.3-0ubuntu1.1~cloud0 - python-keystoneclient
1:0.5.1-0ubuntu1~cloud0 - python-glanceclient
1:1.0.0-0ubuntu1~cloud0 - python-cinderclient
1:2.1-0ubuntu1~cloud0 - python-quantumclient
1:2.9.0-0ubuntu1~cloud0 - python-novaclient
2012.2.1-0ubuntu1.1~cloud0 - glance
2012.2.1-0ubuntu1.1~cloud0 - glance-api
2012.2.1-0ubuntu1.1~cloud0 - glance-common
2012.2.1-0ubuntu1.1~cloud0 - glance-registry
2012.2.1-0ubuntu1.1~cloud0 - keystone
2012.2.1-0ubuntu1.1~cloud0 - python-glance
2012.2.1-0ubuntu1.1~cloud0 - python-keystone
2012.2.1-0ubuntu1~cloud0 - cinder-api
2012.2.1-0ubuntu1~cloud0 - cinder-common
2012.2.1-0ubuntu1~cloud0 - cinder-scheduler
2012.2.1-0ubuntu1~cloud0 - cinder-volume
2012.2.1-0ubuntu1~cloud0 - openstack-dashboard
2012.2.1-0ubuntu1~cloud0 - openstack-dashboard-ubuntu-theme
2012.2.1-0ubuntu1~cloud0 - python-cinder
2012.2.1-0ubuntu1~cloud0 - python-django-horizon
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-api
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-cert
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-common
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-consoleauth
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-network
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-novncproxy
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - nova-scheduler
2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 - python-nova
2013/2/20 Trinath Somanchi trinath.soman...@gmail.com
Also, on quick think to look is the apache error log while you access the
horizon.
look at the log as, tail -f /var/log/apache/error.log.
On Wed, Feb 20, 2013 at 5:07 PM, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
192.168.202.103 = public controller iface
192.168.203.103 = private controller iface
anyway, I still get the login problem using any of those values
Le 20/02/2013 06:59, Kieran Spear a écrit :
On 20 February 2013 03:40, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
Same problem here. Running Grizzly. Dashboard keeps prompting me for
my credentials. Pretty sure dashboard sends wrong tenant name to keystone.
Here's the relevant section in
/etc/openstack-dashboard/local-settings.py:
OPENSTACK_HOST = 192.168.202.103
OPENSTACK_KEYSTONE_URL = http://%s:5000/v2.0; % OPENSTACK_HOST
#OPENSTACK_KEYSTONE_DEFAULT_ROLE = Member
OPENSTACK_KEYSTONE_DEFAULT_ROLE = admin
Is that 202 a typo? You used 192.168.203.103 later.
Cheers,
Kieran
michaël
Le 13/02/2013 16:13, Razique Mahroua a écrit :
Is the dash configured to talk with the Keystone backend?
can you run something like $ keystone endoint-list
thanks
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 12 févr. 2013 à 16:54, Logan McNaughton lo...@bacoosta.com a
écrit :
I've had this problem before, in my experience it's not a problem with
keystone, it's a problem with nova (by the looks of the traceback). I
believe it's a bug in Horizon because you'll find a lot of people with this
issue if you Google it. I don't have an answer on how to fix it, other than
don't fixate on the EndpointNotFound, look to your nova configs for a
solution.
On Tue, Feb 12, 2013 at 5:03 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi Stackers-
I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as credentials, I get
this error.
[Tue Feb 12 10:03:16 2013 16%202013] [error] unable to retrieve
service catalog with token
[Tue Feb 12 10:03:16 2013 16%202013] [error] Traceback (most recent
call last):
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py, line 132,
in _extract_service_catalog
[Tue Feb 12 10:03:16 2013 16%202013] [error]
endpoint_type='adminURL')
[Tue Feb 12 10:03:16 2013 16%202013] [error] File
/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py, line
62, in url_for
[Tue Feb 12 10:03:16 2013 16%202013] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Feb 12 10:03:16 2013 16%202013] [error] EndpointNotFound:
Endpoint not found.
[Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized: n/a (HTTP
401)\x1b[0m
[Tue Feb 12 10:03:17 2013] [error] Traceback (most recent call last):
[Tue Feb 12 10:03:17 2013] [error] File
/usr/lib/python2.7/dist-packages/horizon/usage/base.py, line 93, in
summarize
[Tue Feb 12 10:03:17 2013] [error] self.usage_list =
[Openstack] Ongoing post-migration wiki cleanup
This is just a reminder that we appreciate everyone's assistance so far, polishing the end result of the wiki migration which took place last weekend. It's looking great, but there's always room for further improvement of course! To aid in any remaining cleanup, the old wiki is available at... http://old-wiki.openstack.org/ This should make it possible to compare the current pages with their previous incarnations, in the event that you suspect any data was lost in the move. Also, if you do happen to spot something significant missing in the new wiki (as opposed to simple formatting issues since we're already aware of those), please follow up to the list and let us know. We've also started a helper page for migration tips, documenting how to fix some of the basic formatting problems encountered... https://wiki.openstack.org/wiki/WikiMigration The old wiki will be taken offline on Friday, March 1st. Hopefully that should be long enough to assist with any significant migration errors. As always, feel free to reply to this message or find us in #openstack-infra on the freenode IRC network if you have any related questions. -- Jeremy Stanley ___ 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] [cloudxy] Re: [openstack-dev] Restart devstack errors
On Thu, Feb 21, 2013 at 12:44 AM, Yujie Du duyujie@gmail.com wrote: 2013/2/20 harryxiyou harryxi...@gmail.com [...] Use screen to see the logging output: $screen -d -m -S screen-name -t shell -s /bin/bash $ screen -x stack After executed $ screen -d -m -S stack -t shell -s /bin/bash $ screen -x stack I saw nothing logs. -- Thanks Harry Wei ___ 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]A design draft of Storage Quota
Hi Kevin, On Wed, Feb 20, 2013 at 5:26 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately, I'm not able to work on Boson at the moment due to higher-priority tasks… From a quick look of it why can't we do the same as Boson without synaps[1]+ceilometer+swift_container_update. I don't know very well those but from the look of it you could have synaps generating alerts based on resources collection from ceilometer and set the enforcement using the native service mechanism? Chmouel, [1] when properly working with a proper API. ___ 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]A design draft of Storage Quota
On Wed, 2013-02-20 at 21:09 +0100, Chmouel Boudjnah wrote: On Wed, Feb 20, 2013 at 5:26 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately, I'm not able to work on Boson at the moment due to higher-priority tasks… From a quick look of it why can't we do the same as Boson without synaps[1]+ceilometer+swift_container_update. I don't know very well those but from the look of it you could have synaps generating alerts based on resources collection from ceilometer and set the enforcement using the native service mechanism? I do not understand your question. Quotas have nothing to do with notifications, as far as I understand it; quotas limit the maximum amount of a given resource a given user can have, while ceilometer just notifies other consumers about actions, right? -- Kevin L. Mitchell kevin.mitch...@rackspace.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] [Swift]A design draft of Storage Quota
I was guessing this is the part of what synaps do but from looking at https://wiki.openstack.org/wiki/Synaps it may just provide only notifications and not enforcements. Chmouel. On Wed, Feb 20, 2013 at 9:17 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Wed, 2013-02-20 at 21:09 +0100, Chmouel Boudjnah wrote: On Wed, Feb 20, 2013 at 5:26 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: I'll also point out Boson: https://wiki.openstack.org/wiki/Boson and https://github.com/klmitch/boson with some initial work. Unfortunately, I'm not able to work on Boson at the moment due to higher-priority tasks… From a quick look of it why can't we do the same as Boson without synaps[1]+ceilometer+swift_container_update. I don't know very well those but from the look of it you could have synaps generating alerts based on resources collection from ceilometer and set the enforcement using the native service mechanism? I do not understand your question. Quotas have nothing to do with notifications, as far as I understand it; quotas limit the maximum amount of a given resource a given user can have, while ceilometer just notifies other consumers about actions, right? -- Kevin L. Mitchell kevin.mitch...@rackspace.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 ___ 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] Fwd: Initial quantum network state broken
Hi Greg, I would like to understand a little bit better your setup. I scrolled through the thread, but I'm not sure if you've already provided the information I'm asking. On the compute node, the pair phy-br-eth1/int-br-eth1 is a veth pair or a OVS patch port? I'm assuming you're using the OVS plugin (I think I'm not wrong here, but please correct me in case I am). It might worth knowing if you're doing vlan or gre-based isolation with it. Salvatore On 20 February 2013 17:35, Greg Chavez greg.cha...@gmail.com wrote: Here's the last command output you asked for: root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-ofctl dump-flows br-eth1 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=78793.694s, table=0, n_packets=6, n_bytes=468, priority=2,in_port=6 actions=drop cookie=0x0, duration=78794.033s, table=0, n_packets=17355, n_bytes=3335788, priority=1 actions=NORMAL On Wed, Feb 20, 2013 at 10:57 AM, Greg Chavez greg.cha...@gmail.com wrote: Hey Anil, thanks for responding. Here's the output: root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-vsctl show 9d9f7949-2b80-40c8-a9e0-6a116200ed96 Bridge br-int Port br-int Interface br-int type: internal Port int-br-eth1 Interface int-br-eth1 Bridge br-eth1 Port phy-br-eth1 Interface phy-br-eth1 Port br-eth1 Interface br-eth1 type: internal Port eth1 Interface eth1 ovs_version: 1.4.3 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-dpctl show system@br-eth1: lookups: hit:5227 missed:24022 lost:0 flows: 1 port 0: br-eth1 (internal) port 1: eth1 port 6: phy-br-eth1 system@br-int: lookups: hit:2994 missed:13754 lost:0 flows: 1 port 0: br-int (internal) port 2: int-br-eth1 root@kvm-cs-sn-10i:/var/lib/nova/instances# brctl show bridge name bridge id STP enabled interfaces br-eth1 .bc305befedd1 no eth1 phy-br-eth1 br-int .8ae31e5f7941 no int-br-eth1 qbr5334a0cb-64 8000.76fb293fe9cf no qvb5334a0cb-64 vnet0 root@kvm-cs-sn-10i:/var/lib/nova/instances# ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=75251.156s, table=0, n_packets=16581, n_bytes=3186436, priority=2,in_port=2 actions=drop cookie=0x0, duration=75251.527s, table=0, n_packets=0, n_bytes=0, priority=1 actions=NORMAL Thanks! I have until tomorrow to get this working, then my boss has mandating that I try Cloudstack. Argh, but I'm so close! On Wed, Feb 20, 2013 at 10:29 AM, Anil Vishnoi vishnoia...@gmail.com wrote: Hi Greg, Can you paste the output of following command from your compute node. ovs-vsctl show ovs-dpctl show brctl show ovs-ofctl dump-flows br-int ovs-ofctl dump-flows br-eth1 Because i think first issue we need to resolve here is why DHCP packet is not leaving your compute host. Anil On Wed, Feb 20, 2013 at 6:48 AM, Greg Chavez greg.cha...@gmail.com wrote: From my perspective, it seems that the OVS bridges are not being brought up correctly. As you can see in my earlier post, the integration bridge (int) and the physical interface bridges (br-ex and br-eth1) are downed. I've tried to bring them up in promiscuous mode in the case of br-int, and with the physical interfaces ported to the bridge in the case of br-ex and br-eth1. I've had no luck unfortunately. It seems that nothing is getting past br-int. I can see BOOTP packets on the VM side of br-int, and I can see VTP packets on the physical side of br-int. But that's where it ends. For example, when I reboot my VM, I see this: root@kvm-cs-sn-10i:/var/lib/nova/instances# tcpdump -i qvo5334a0cb-64 tcpdump: WARNING: qvo5334a0cb-64: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qvo5334a0cb-64, link-type EN10MB (Ethernet), capture size 65535 bytes 13:42:08.099061 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:08.101675 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:08.161728 IP6 :: ff02::1:ff06:4809: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe06:4809, length 24 13:42:08.373745 IP6 :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 13:42:11.102528 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 13:42:14.105850 IP 0.0.0.0.bootpc 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:06:48:09 (oui Unknown), length 280 But that's as far as it goes. The dhcp agent never get this. Ive tried deleting and recreating the bridges, rebooting the systems, but nothing seems to work. Maybe it's just the right combination of things. I don't know. Help! On Tue, Feb 19, 2013 at 5:23 AM, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi Greg, I did have
Re: [Openstack] [Swift]A design draft of Storage Quota
On 2/20/13 1:28 PM, Tim Bell tim.b...@cern.ch wrote: We also feel an integrated approach such as Boson is the way forward for quota rather than each project have its own (and potentially differing) implementations on areas such as delegation. +1 to an integrated approach. It's easy to envision a need for quotas in Glance as well, in both public and private cloud scenarios. Cc'ing some other potentially interested parties. Everett ___ 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] Mirror in Online the VM
hi all i have a question i am working to make a mirror or live replication bretween 2 PC for OpenSTack, so if 1 server down, the other will take over, and i hope the user dont know it. i got also vmotion in vmware, can we do it in openstack? thx for the help F ___ 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] Mirror in Online the VM
Hi Frans,so basically, what you are looking for is a mirroring solution for your OpenStack deployment that has been made on two servers?Are both All-in-One (eg they both provide all the OpenStack services and configured ISO?)thanks Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15 Le 20 févr. 2013 à 22:07, Frans Thamura fr...@meruvian.org a écrit :hi alli have a questioni am working to make a mirror or live replication bretween 2 PC forOpenSTack, so if 1 server down, the other will take over, and i hopethe user dont know it.i got also vmotion in vmware,can we do it in openstack?thx for the helpF___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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] Fwd: Initial quantum network state broken
It's great to see that things are starting to run properly! I'm sorry I did not read you were running a provider network. That would have been the typical symptom of a missing mapping. Some more comments inline on the 'new' issues. Salvatore On 20 February 2013 21:57, Greg Chavez greg.cha...@gmail.com wrote: Anil, Thanks a lot for your help. Although I had the trunking configured on the ports properly, I forgot to actually add the VLAN to the vlan database (set vlan 1024, and I was done). As soon as that was done, the VM got its IP address. Can't ping or ssh though! Argh. I still think the instructions I've been following are leaving something out on the way the physical and bridged interfaces needs to be configured on startup (these instructions: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst). For example, even after rebooting the network node after installation, the br-int, br-ex, and br-eth1 interfaces were all down. And I wasn't able to troubleshoot the VLAN tagging until added those interfaces to /etc/network/interfaces and restarted networking. Yes, Quantum does not persist the configuration for you. Actually, Quantum is polite and does not want to mess with your host's network configuration. Indeed the typical workflow is that the admin configures those bridges, and then tells quantum to use them. The symptoms now are: * Whereas before I was able to ping the tenant's router and dhcp IPs from the controller, I can't now. The controller usually does not have a route to the tenant network. For instance it might be running in some management network (say 10.127.1.0/24) whereas your tenant network is 10.0.0.0/24. * The VNC console inside Horizon fails to connect (it could before). Unfortunately I do not have an explanation for that. It might be related to the fact that you're using a provider network, and hence there might be an underlying bug. I am unfortunately unable to setup a repro environment now. * External VNC connections work, however. Once inside, I can see that the VM interface is now configured with 192.168.1.3/24. It can ping the DHCP server (192.168.1.2) but not the default router (192.168.1.1). Can you check the interface is up and running on the l3-agent. You should see a qr-partofrouteruuid iface configured with 1ip 92.168.1.1 I have all the salient configs paste-binned here: http://pastebin.com/ZZAuaH4u Suggestions? I'm tempted to re-install at this point, I've mucked around with manual network changes so much. Thanks again! On Wed, Feb 20, 2013 at 1:44 PM, Anil Vishnoi vishnoia...@gmail.com wrote: so if the packet is going out from compute node -eth1 interface and not reaching network node eth1 interface, then the only element in between these two interface is physical switch. Both the switch ports should be trunked, so that they allow all the vlan traffic on both the ports where network node and compute node are connected. Process for VLAN trunking depends on the switch vendor. AFAIK in cisco switch all the ports are by default trunk-ed, but thats not the case with all vendors. You might want to re-check the switch configuration and test whether its really passing the tagged traffic or not. On Wed, Feb 20, 2013 at 11:54 PM, Greg Chavez greg.cha...@gmail.com wrote: I'm seeing three BOOTP/DHCP packets on the eth1 interface of the compute node, but it doesn't make it to the network node. So I may have a VLAN tagging issue. The segmentation id for the VM network is 1024 (same as what's in the github instructions). The segmentation id for the public network is 3001. root@kcon-cs-gen-01i:/etc/init.d# quantum net-show 654a49a3-f042-45eb-a937-0dcd6fcaa84c | grep seg | provider:segmentation_id | 3001 | root@kcon-cs-gen-01i:/etc/init.d# quantum net-show c9c6a895-8bc1-4319-a207-30422d0d1a27 | grep seg | provider:segmentation_id | 1024 The physical switch ports for the eth1 interfaces of the compute and network node are set to trunk and are allowing both 3001 and 1024. Here are the interfaces on the compute node: root@kvm-cs-sn-10i:/etc/network/if-up.d# ip add show | egrep ^[0-9]+ 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 3: eth1: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 4: eth2: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000 5: eth3: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000 6: br-eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN 12: qvo5334a0cb-64: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 13: qvb5334a0cb-64: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 29: br-int: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu
Re: [Openstack] Mirror in Online the VM
On Thu, Feb 21, 2013 at 4:17 AM, Razique Mahroua razique.mahr...@gmail.comwrote: Hi Frans, so basically, what you are looking for is a mirroring solution for your OpenStack deployment that has been made on two servers? Are both All-in-One (eg they both provide all the OpenStack services and configured ISO?) thanks yes, we can call it online mirror-ing what do u mean of all in one? F *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 Le 20 févr. 2013 à 22:07, Frans Thamura fr...@meruvian.org a écrit : hi all i have a question i am working to make a mirror or live replication bretween 2 PC for OpenSTack, so if 1 server down, the other will take over, and i hope the user dont know it. i got also vmotion in vmware, can we do it in openstack? thx for the help F ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp NUAGECO-LOGO-Fblan_petit.jpg___ 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] Cant ping private or floating IP
Thanks. I would be more concerned about the SIOCDELRT error above. Do you try to manually remove a network route at bootup ? Seems like the 'route del' is failing because the route is not already existing. I am not doing doing anything that I am aware of. As already said, you absolutely need VNC support for investigating. Could you please fix your VNC setup which is incorrect ? But VNC works fine. Its just that it VM hangs on the boot up it wont come to the log in prompt, I can't log into it. :( On 20 February 2013 13:46, Sylvain Bauza sylvain.ba...@digimind.com wrote: Le 20/02/2013 14:04, Chathura M. Sarathchandra Magurawalage a écrit : There are apparently two instances running in the compute node but nova just see only one. Probably when I have deleted an instance earlier it had not deleted the instance properly. root@controller:~# nova list +--+++---+ | ID | Name | Status | Networks | +--+++---+ | 42e18cd5-de6f-4181-b238-320fe37ef6f1 | master | ACTIVE | demo-net=10.5.5.3 | +--+++---+ virsh -c qemu+ssh://root@computenode/system list root@computenode's password: IdName State 14instance-002c running 18instance-001e running You should have seen at 'sudo virsh list --all', plus looking at /etc/libvirt/qemu/*.xml to check how many instances were defined. I do suspect also that for some reason (probably nova-compute down), a clean-up of 2c probably didn't work. Anyway, this is fixed as you mention. Then I have deleted all instances and created a new one. But still cant ping or ssh the new VM. interface type='bridge' mac address='fa:16:3e:a2:6e:02'/ source bridge='qbrff8933bf-ba'/ model type='virtio'/ filterref filter='nova-instance-instance-0035-fa163ea26e02' parameter name='DHCPSERVER' value='10.5.5.2'/ parameter name='IP' value='10.5.5.3'/ parameter name='PROJMASK' value='255.255.255.0'/ parameter name='PROJNET' value='10.5.5.0'/ /filterref address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'\ / /interface Starting network... udhcpc (v1.18.5) started Sending discover... Sending select for 10.5.5.3... Lease of 10.5.5.3 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 8.8.8.8 The DHCP reply is correctly received by the instance from the network node to the compute node. This is not a network issue (at least for IP assignation). I would be more concerned about the SIOCDELRT error above. Do you try to manually remove a network route at bootup ? Seems like the 'route del' is failing because the route is not already existing. As already said, you absolutely need VNC support for investigating. Could you please fix your VNC setup which is incorrect ? graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-u\ s' listen type='address' address='0.0.0.0'/ /graphics Try in nova-compute.conf : vncserver_proxyclient_address=compute node mgmt IP vncserver_listen=compute node mgmt IP and in nova.conf : novncproxy_base_url=http://controler node mgmt IP:6080/vnc_auto.html and restart nova-compute. On 20 February 2013 11:57, Sylvain Bauza sylvain.ba...@digimind.comwrote: Could you please paste : - /etc/libvirt/qemu/your_instance_id.xml - ip a show vnet0 - brctl show Sounds like your virtual device is not created. Could you please launch a new VM and paste /var/log/nova/nova-compute.log ? Thanks, -Sylvain ___ 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] Wading through nova.conf options
Hi all, I am trying to get a better grasp on which nova.conf options are needed for a given setup. I have found this list: http://docs.openstack.org/folsom/openstack-compute/admin/content/list-of-compute-config-options.htmlbut it doesn't really answer what is needed and when. For example if I am using quantum to do the network management by setting network_api_class, I imagine that has a profound impact on which variables are required from table Table 5.15. Description of nova.conf file configuration options for networking options . Also, if I am using cinder does that render the variables related for nova-volume obsolete? I have noticed that many of the other services have Developer Documentation such as this page for keystone: http://docs.openstack.org/developer/keystone/configuration.html has many of the options listed, what values are expected, etc. Does nova have any such documentation? Thanks, Sam ___ 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] Wading through nova.conf options
Looks like you found the reference listings but really want config info, which I can point you to. As you have noted, you have choices for networking and volumes: quantum or nova-network, cinder or nova-volume. Here are pointers to specific docs. Quantum config: http://docs.openstack.org/trunk/openstack-network/admin/content/nova_with_quantum.html Cinder config: http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html nova-volume: http://docs.openstack.org/trunk/openstack-compute/admin/content/install-nova-volume.html nova-network: http://docs.openstack.org/trunk/openstack-compute/admin/content/networking-options.html Since this is trunk documentation it changes daily, but these links offer you more conceptual background info, which I think is what you'll need at this point in your journey. Anne P.S. For a complete reference listing of all current nova.conf options, refer to https://github.com/openstack/nova/blob/master/etc/nova/nova.conf.sample. Those are what the docs folks will bring into the reference listing for Grizzly. On Wed, Feb 20, 2013 at 7:20 PM, Samuel Winchenbach swinc...@gmail.comwrote: Hi all, I am trying to get a better grasp on which nova.conf options are needed for a given setup. I have found this list: http://docs.openstack.org/folsom/openstack-compute/admin/content/list-of-compute-config-options.htmlbut it doesn't really answer what is needed and when. For example if I am using quantum to do the network management by setting network_api_class, I imagine that has a profound impact on which variables are required from table Table 5.15. Description of nova.conf file configuration options for networking options . Also, if I am using cinder does that render the variables related for nova-volume obsolete? I have noticed that many of the other services have Developer Documentation such as this page for keystone: http://docs.openstack.org/developer/keystone/configuration.html has many of the options listed, what values are expected, etc. Does nova have any such documentation? Thanks, Sam ___ 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] Restart devstack errors
On Wed, Feb 20, 2013 at 3:14 PM, Hirendra Rathor
hirendra.rat...@gmail.com wrote:
Hi Hirendra Rathor,
I was getting same error when I picked up devstack for the first time few
days ago. I could have tried troubleshooting it but I wasn't particularly
happy with the fact that I had to launch stack.sh every time on reboot. The
script updates the source code and then compiles it which means that the
product behavior could be different after running the script. This is not
necessarily a problem but I felt less in control.
I, therefore, modified my local copy of stack.sh to _not_ do operations that
should be required for the first run. Examples of such operations include
creating user accounts, configuration files, mysql database etc. The result
was a script that just launches the openstack processes. Running this lean
script resulted in successful launch of keystone process, so I didn't have
to troubleshoot the original problem!
I am not clear about how you can solve 'keystone did not start'.
Cloud you please attach your modified stack.sh, which solved this problem.
Now, i can get some logs for my 'keystone did not start' like following.
$ screen -S stack -p key -X stuff
$ screen -x stack
jiawei@jiawei:~/workshop1/devstack$ cd /opt/stack/keystone
/opt/stack/keystone/bin/keystone-all --config-file
/etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
--debug || touch /opt/stack/status/stack/key.failure
Traceback (most recent call last):
File /opt/stack/keystone/bin/keystone-all, line 22, in module
from paste import deploy
File
/usr/local/lib/python2.7/dist-packages/Paste-1.7.5.1-py2.7.egg/paste/__init__.py,
line 4, in module
import pkg_resources
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2727,
in module
add_activation_listener(lambda dist: dist.activate())
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 700,
in subscribe
callback(dist)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2727,
in lambda
add_activation_listener(lambda dist: dist.activate())
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2227,
in activate
self.insert_on(path)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2334,
in insert_on
self.check_version_conflict()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2373,
in check_version_conflict
for modname in self._get_metadata('top_level.txt'):
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2221,
in _get_metadata
for line in self.get_metadata_lines(name):
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1209,
in get_metadata_lines
return yield_lines(self.get_metadata(name))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1201,
in get_metadata
return self._get(self._fn(self.egg_info,name))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1316, in _get
stream = open(path, 'rb')
IOError: [Errno 13] Permission denied:
'/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg/EGG-INFO/top_level.txt'
Could anyone give me some suggestions to this problem? Thanks
in advance.
--
Thanks
Harry Wei
___
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] Restart devstack errors
[Removed the dev list -- no need to cross-post.]
It looks like you have broken permissions on
'/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg' and/or
subdirectories. Make sure everything is world readable.
- Chris
On Feb 20, 2013, at 7:48 PM, harryxiyou harryxi...@gmail.com wrote:
On Wed, Feb 20, 2013 at 3:14 PM, Hirendra Rathor
hirendra.rat...@gmail.com wrote:
Hi Hirendra Rathor,
I was getting same error when I picked up devstack for the first time few
days ago. I could have tried troubleshooting it but I wasn't particularly
happy with the fact that I had to launch stack.sh every time on reboot. The
script updates the source code and then compiles it which means that the
product behavior could be different after running the script. This is not
necessarily a problem but I felt less in control.
I, therefore, modified my local copy of stack.sh to _not_ do operations that
should be required for the first run. Examples of such operations include
creating user accounts, configuration files, mysql database etc. The result
was a script that just launches the openstack processes. Running this lean
script resulted in successful launch of keystone process, so I didn't have
to troubleshoot the original problem!
I am not clear about how you can solve 'keystone did not start'.
Cloud you please attach your modified stack.sh, which solved this problem.
Now, i can get some logs for my 'keystone did not start' like following.
$ screen -S stack -p key -X stuff
$ screen -x stack
jiawei@jiawei:~/workshop1/devstack$ cd /opt/stack/keystone
/opt/stack/keystone/bin/keystone-all --config-file
/etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
--debug || touch /opt/stack/status/stack/key.failure
Traceback (most recent call last):
File /opt/stack/keystone/bin/keystone-all, line 22, in module
from paste import deploy
File
/usr/local/lib/python2.7/dist-packages/Paste-1.7.5.1-py2.7.egg/paste/__init__.py,
line 4, in module
import pkg_resources
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2727,
in module
add_activation_listener(lambda dist: dist.activate())
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 700,
in subscribe
callback(dist)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2727,
in lambda
add_activation_listener(lambda dist: dist.activate())
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2227,
in activate
self.insert_on(path)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2334,
in insert_on
self.check_version_conflict()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2373,
in check_version_conflict
for modname in self._get_metadata('top_level.txt'):
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2221,
in _get_metadata
for line in self.get_metadata_lines(name):
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1209,
in get_metadata_lines
return yield_lines(self.get_metadata(name))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1201,
in get_metadata
return self._get(self._fn(self.egg_info,name))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 1316, in _get
stream = open(path, 'rb')
IOError: [Errno 13] Permission denied:
'/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg/EGG-INFO/top_level.txt'
Could anyone give me some suggestions to this problem? Thanks
in advance.
--
Thanks
Harry Wei
___
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] Restart devstack errors
On Thu, Feb 21, 2013 at 12:14 PM, Chris Behrens cbehr...@codestud.com wrote: [Removed the dev list -- no need to cross-post.] It looks like you have broken permissions on '/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg' nd/or subdirectories. Make sure everything is world readable. You are right. After sudo chmod -R 777 dist-packages/ I could solve this problem successfully. Thanks. -- Thanks Harry Wei ___ 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] Restart devstack errors
Well, you probably don't want world writeable, but :) 755 on dirs and 644 on files is probably more appropriate! But at least you know the issue. - Chris On Feb 20, 2013, at 9:21 PM, harryxiyou harryxi...@gmail.com wrote: On Thu, Feb 21, 2013 at 12:14 PM, Chris Behrens cbehr...@codestud.com wrote: [Removed the dev list -- no need to cross-post.] It looks like you have broken permissions on '/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg' nd/or subdirectories. Make sure everything is world readable. You are right. After sudo chmod -R 777 dist-packages/ I could solve this problem successfully. Thanks. -- Thanks Harry Wei ___ 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] Restart devstack errors
On Thu, Feb 21, 2013 at 1:35 PM, Chris Behrens cbehr...@codestud.com wrote: Well, you probably don't want world writeable, but :) 755 on dirs and 644 on files is probably more appropriate! Ah..., this may be better ;-) But at least you know the issue. Yup, thanks. -- Thanks Harry Wei ___ 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] Create Sheepdog Volume by Openstack Dashboard error
Hi, $ screen -r than navigate to c-vol with Ctrl+A then N To detach from screen : Ctrl+A then D Regards, Jean-Baptiste RANSY Envoyé de mon ASUS Pad harryxiyou harryxi...@gmail.com a écrit : Hi all, I have tested OpenStack with Sheepdog like follwoing 1, Install Ubuntu 12.04 (Precise) or Fedora 16 2, Install Sheepdog to the appropriate location on your system 3, Start Sheepdog and format it (See Getting Started) 4, Download DevStack $ git clone git://github.com/openstack-dev/devstack.git 5, Start the install $ cd devstack; CINDER_DRIVER=sheepdog ./stack.sh After up steps, i create volume by Openstack Dashboard but the Volume *Status* is Error(See attach picture for details). How could i get the logs of creaeing a volume by Openstack dashboard? I also wanna create volume by Cinder command. Has anyone tried this way? Could anyone give me some suggestions? Thanks in advance. -- Thanks Harry Wei ___ 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-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_cinder_trunk #167
Title: precise_grizzly_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/167/Project:precise_grizzly_cinder_trunkDate of build:Wed, 20 Feb 2013 04:01:08 -0500Build duration:1 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd a volume driver in Cinder for Scality SOFSby jean.marc.saffroyeditetc/cinder/rootwrap.d/volume.filtersaddcinder/volume/drivers/scality.pyaddcinder/tests/test_scality.pyeditetc/cinder/cinder.conf.sampleHandle maxclonepervolume/node limits in SF driver.by john.griffitheditcinder/volume/drivers/solidfire.pyConsole Output[...truncated 2580 lines...]Patch fix-ubuntu-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-24d82e50-f168-4d00-8078-53b46e789b77', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-24d82e50-f168-4d00-8078-53b46e789b77', '-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/tmp88mfZv/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp88mfZv/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6134269a124037be1453f3a716c4cbfe8d1d54d..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a184.geed5aac+git201302200401~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [737468e] Handle maxclonepervolume/node limits in SF driver.dch -a [d5a17b4] Use oslo-config-2013.1b3dch -a [008adb2] Fix syntax error in cinder-volume-usage-auditdch -a [83e2053] HP 3PAR Fibre Channel Driver and iSCSI Updatesdch -a [af64eac] Fibre Channel base class for Cinder driversdch -a [91ccd15] Add a safe_minidom_parse_string function.dch -a [e5b1d51] Add a volume driver in Cinder for Scality SOFSdch -a [8466bb3] Fix create volume from image.dch -a [b0cdbdf] XenAPINFS: fix capacity reportingdch -a [b3e64b8] Update Storwize/SVC driver for Grizzly.dch -a [187b349] Set rootwrap_config in cinder.conf sample.dch -a [64a1a32] Skip tests if cinder is not installeddch -a [256b423] Fix PEP8 violation (again)dch -a [6c708d1] Update cinder-volume to enable multi volume supportdch -a [2443e35] Install rtslib when installing cinderdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-24d82e50-f168-4d00-8078-53b46e789b77', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-24d82e50-f168-4d00-8078-53b46e789b77', '-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 Failure: raring_grizzly_nova_trunk #733
text/html; charset=UTF-8: Unrecognized -- 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 : folsom_coverage #480
See http://10.189.74.7:8080/job/folsom_coverage/480/ -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_deploy #30
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/30/Project:raring_grizzly_deployDate of build:Wed, 20 Feb 2013 04:54:26 -0500Build duration:56 minBuild cause:Started by command line by jenkinsStarted by command line by jenkinsStarted by command line by jenkinsStarted by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 13866 lines...]INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_cinder_trunk #168
Title: precise_grizzly_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/168/Project:precise_grizzly_cinder_trunkDate of build:Wed, 20 Feb 2013 06:01:08 -0500Build duration:1 min 35 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate cinder-manage to use FLAGS.log_dir.by dprinceeditbin/cinder-manageConsole Output[...truncated 2583 lines...]ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bb894997-bf54-4f9e-98b1-2862909a2106', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bb894997-bf54-4f9e-98b1-2862909a2106', '-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/tmp_YwQk4/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp_YwQk4/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6134269a124037be1453f3a716c4cbfe8d1d54d..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a186.gd5ac3cb+git201302200601~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [737468e] Handle maxclonepervolume/node limits in SF driver.dch -a [d5a17b4] Use oslo-config-2013.1b3dch -a [008adb2] Fix syntax error in cinder-volume-usage-auditdch -a [83e2053] HP 3PAR Fibre Channel Driver and iSCSI Updatesdch -a [af64eac] Fibre Channel base class for Cinder driversdch -a [5f2a36c] Update cinder-manage to use FLAGS.log_dir.dch -a [91ccd15] Add a safe_minidom_parse_string function.dch -a [e5b1d51] Add a volume driver in Cinder for Scality SOFSdch -a [8466bb3] Fix create volume from image.dch -a [b0cdbdf] XenAPINFS: fix capacity reportingdch -a [b3e64b8] Update Storwize/SVC driver for Grizzly.dch -a [187b349] Set rootwrap_config in cinder.conf sample.dch -a [64a1a32] Skip tests if cinder is not installeddch -a [256b423] Fix PEP8 violation (again)dch -a [6c708d1] Update cinder-volume to enable multi volume supportdch -a [2443e35] Install rtslib when installing cinderdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bb894997-bf54-4f9e-98b1-2862909a2106', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bb894997-bf54-4f9e-98b1-2862909a2106', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_cinder_trunk #171
Title: raring_grizzly_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/171/Project:raring_grizzly_cinder_trunkDate of build:Wed, 20 Feb 2013 06:01:09 -0500Build duration:2 min 50 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate cinder-manage to use FLAGS.log_dir.by dprinceeditbin/cinder-manageConsole Output[...truncated 3241 lines...]ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-af504b47-8f55-498b-b491-e6e8cfc0ba22', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-af504b47-8f55-498b-b491-e6e8cfc0ba22', '-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/tmpUUPsgA/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpUUPsgA/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6134269a124037be1453f3a716c4cbfe8d1d54d..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a186.gd5ac3cb+git201302200601~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [737468e] Handle maxclonepervolume/node limits in SF driver.dch -a [d5a17b4] Use oslo-config-2013.1b3dch -a [008adb2] Fix syntax error in cinder-volume-usage-auditdch -a [83e2053] HP 3PAR Fibre Channel Driver and iSCSI Updatesdch -a [af64eac] Fibre Channel base class for Cinder driversdch -a [5f2a36c] Update cinder-manage to use FLAGS.log_dir.dch -a [91ccd15] Add a safe_minidom_parse_string function.dch -a [e5b1d51] Add a volume driver in Cinder for Scality SOFSdch -a [8466bb3] Fix create volume from image.dch -a [b0cdbdf] XenAPINFS: fix capacity reportingdch -a [b3e64b8] Update Storwize/SVC driver for Grizzly.dch -a [187b349] Set rootwrap_config in cinder.conf sample.dch -a [64a1a32] Skip tests if cinder is not installeddch -a [256b423] Fix PEP8 violation (again)dch -a [6c708d1] Update cinder-volume to enable multi volume supportdch -a [2443e35] Install rtslib when installing cinderdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-af504b47-8f55-498b-b491-e6e8cfc0ba22', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-af504b47-8f55-498b-b491-e6e8cfc0ba22', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #734
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/734/Project:raring_grizzly_nova_trunkDate of build:Wed, 20 Feb 2013 08:31:13 -0500Build duration:3 min 53 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFix inaccuracies in the development environment doc.by anneeditdoc/README.rsteditdoc/source/devref/development.environment.rstFix network list and show with quantum.by vishvanandaeditnova/api/openstack/compute/contrib/os_tenant_networks.pyeditnova/network/quantumv2/api.pyeditnova/api/openstack/compute/contrib/os_networks.pyDocumentation cleanups for nova devrefby fifieldtdeletedoc/source/image_src/multinic_1.odgeditdoc/source/devref/network.rsteditdoc/source/devref/index.rstdeletedoc/source/devref/multinic.rstdeletedoc/source/images/multinic_flat.pngdeletedoc/source/devref/cloudpipe.rstdeletedoc/source/devref/down.shdeletedoc/source/devref/interfacesdeletedoc/source/images/multinic_vlan.pngdeletedoc/source/devref/server.conf.templatedeletedoc/source/image_src/multinic_3.odgdeletedoc/source/images/multinic_dhcp.pngdeletedoc/source/devref/up.shdeletedoc/source/image_src/multinic_2.odgMake ComputeTestCase.test_state_revert fasterby jogoeditnova/tests/compute/test_compute.pyFix hacking test to handle namespace packages.by vishvanandaedittools/hacking.pyConsole Output[...truncated 6259 lines...]dpkg-buildpackage: error: dpkg-source -b nova-2013.1.a4529.gadfb921+git201302200831~raring gave error exit status 2debuild: fatal error at line 1357:dpkg-buildpackage -rfakeroot -d -us -uc -sa -S failedbzr: ERROR: The build failed.ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-d412b643-b0e1-48df-8aec-9f8ba1ea1865', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-d412b643-b0e1-48df-8aec-9f8ba1ea1865', '-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/nova/grizzly /tmp/tmpgpxBlE/novamk-build-deps -i -r -t apt-get -y /tmp/tmpgpxBlE/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 24f6c62ad776dc0fc85ce29eb34e7e0a1f270d07..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a4529.gadfb921+git201302200831~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [f619da2] Multi-tenancy isolation with aggregatesdch -a [3b64942] Fix hacking test to handle namespace packages.dch -a [706a137] Use oslo-config-2013.1b4dch -a [b93d543] Make ComputeTestCase.test_state_revert fasterdch -a [a9add7d] Add support for network adapter hotplug.dch -a [9c9aefc] Handle lifecycle events in the compute managerdch -a [d63f7c1] Add support for lifecycle events in the libvirt driverdch -a [d8c3a6d] Add basic infrastructure for compute driver async eventsdch -a [e79811b] Documentation cleanups for nova devrefdch -a [7547697] Add support for instance CPU consumption control.dch -a [86e6f34] Add support for instance disk IO control.dch -a [a28d8e1] Fix network list and show with quantum.dch -a [4faa62e] Fix inaccuracies in the development environment doc.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-d412b643-b0e1-48df-8aec-9f8ba1ea1865', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-d412b643-b0e1-48df-8aec-9f8ba1ea1865', '-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 :
[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_nova_trunk #737
Title: raring_grizzly_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/737/Project:raring_grizzly_nova_trunkDate of build:Wed, 20 Feb 2013 11:31:12 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesAllow exit code 21 for iscsiadm -m session.by dprinceeditnova/virt/libvirt/volume.pyConsole Output[...truncated 21219 lines...]deleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1.a4509.g785513d+git201302200303~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1.a4509.g785513d+git201302200303~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1.a4509.g785513d+git201302200303~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1.a4509.g785513d+git201302200303~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 559.INFO:root:Storing current commit for next build: 13eee3d1d7b40bc334d663b7cea7c65a8f960dfeINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpV2yBSY/novamk-build-deps -i -r -t apt-get -y /tmp/tmpV2yBSY/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 24f6c62ad776dc0fc85ce29eb34e7e0a1f270d07..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a4541.gf7b0cf3+git201302201131~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [13eee3d] Allow exit code 21 for 'iscsiadm -m session'.dch -a [170efef] Log lifecycle events to log INFO (not ERROR)dch -a [b5fe418] Sync latest install_venv_common.pydch -a [f619da2] Multi-tenancy isolation with aggregatesdch -a [7ca39a6] Fix broken logging imports.dch -a [3b64942] Fix hacking test to handle namespace packages.dch -a [706a137] Use oslo-config-2013.1b4dch -a [b93d543] Make ComputeTestCase.test_state_revert fasterdch -a [a9add7d] Add support for network adapter hotplug.dch -a [9c9aefc] Handle lifecycle events in the compute managerdch -a [d63f7c1] Add support for lifecycle events in the libvirt driverdch -a [3769633] Enhance IPAdresses migration testsdch -a [d8c3a6d] Add basic infrastructure for compute driver async eventsdch -a [e79811b] Documentation cleanups for nova devrefdch -a [e3fe55d] Fix leak of loop/nbd devices in injection using localfsdch -a [7547697] Add support for instance CPU consumption control.dch -a [86e6f34] Add support for instance disk IO control.dch -a [a28d8e1] Fix network list and show with quantum.dch -a [4faa62e] Fix inaccuracies in the development environment doc.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1.a4541.gf7b0cf3+git201302201131~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1.a4541.gf7b0cf3+git201302201131~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1.a4541.gf7b0cf3+git201302201131~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1.a4541.gf7b0cf3+git201302201131~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_deploy #31
Title: raring_grizzly_deploy General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/31/Project:raring_grizzly_deployDate of build:Wed, 20 Feb 2013 11:45:29 -0500Build duration:25 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 6132 lines...] -> Relation: cinder:ceph <-> ceph:client -> Relation: openstack-dashboard:identity-service <-> keystone:identity-service -> Relation: nova-compute:shared-db <-> mysql:shared-db -> Relation: nova-compute:amqp <-> rabbitmq:amqp -> Relation: nova-compute:image-service <-> glance:image-service -> Relation: nova-compute:cloud-compute <-> nova-cloud-controller:cloud-compute -> Relation: nova-compute:ceph <-> ceph:client- Sleeping for 60 before ensuring relation state.- Deployment complete in 1483 seconds.- Juju command log:juju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:nova-compute nova-compute -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:nova-cloud-controller nova-cloud-controller -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:ceph ceph -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:keystone keystone -e raringjuju deploy -n 1 --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:rabbitmq-server rabbitmq -e raringjuju deploy -n 1 --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:mysql mysql -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:openstack-dashboard openstack-dashboard -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:cinder cinder -e raringjuju deploy -n 1 --config=/tmp/tmpatvpCA --repository=/var/lib/jenkins/jobs/raring_grizzly_deploy/workspace local:glance glance -e raringjuju add-relation keystone:shared-db mysql:shared-db -e raringjuju add-relation nova-cloud-controller:shared-db mysql:shared-db -e raringjuju add-relation nova-cloud-controller:amqp rabbitmq:amqp -e raringjuju add-relation nova-cloud-controller:image-service glance:image-service -e raringjuju add-relation nova-cloud-controller:identity-service keystone:identity-service -e raringjuju add-relation glance:shared-db mysql:shared-db -e raringjuju add-relation glance:identity-service keystone:identity-service -e raringjuju add-relation glance:ceph ceph:client -e raringjuju add-relation cinder:shared-db mysql:shared-db -e raringjuju add-relation cinder:amqp rabbitmq:amqp -e raringjuju add-relation cinder:cinder-volume-service nova-cloud-controller:cinder-volume-service -e raringjuju add-relation cinder:identity-service keystone:identity-service -e raringjuju add-relation cinder:ceph ceph:client -e raringjuju add-relation openstack-dashboard:identity-service keystone:identity-service -e raringjuju add-relation nova-compute:shared-db mysql:shared-db -e raringjuju add-relation nova-compute:amqp rabbitmq:amqp -e raringjuju add-relation nova-compute:image-service glance:image-service -e raringjuju add-relation nova-compute:cloud-compute nova-cloud-controller:cloud-compute -e raringjuju add-relation nova-compute:ceph ceph:client -e raring+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build folsom_coverage+ exit 0Email was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_nova_trunk #739
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/739/Project:raring_grizzly_nova_trunkDate of build:Wed, 20 Feb 2013 13:05:45 -0500Build duration:2 min 47 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesAdd API Sample tests for Hypervisors extension.by reviewadddoc/api_samples/os-hypervisors/hypervisors-statistics-resp.xmladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-search-resp.json.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-uptime-resp.xml.tpladddoc/api_samples/os-hypervisors/hypervisors-list-resp.xmladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-statistics-resp.xml.tpladddoc/api_samples/os-hypervisors/hypervisors-show-resp.xmladddoc/api_samples/os-hypervisors/hypervisors-search-resp.jsonaddnova/tests/integrated/api_samples/os-hypervisors/hypervisors-show-resp.xml.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-detail-resp.json.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-show-resp.json.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-servers-resp.json.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-list-resp.xml.tpleditnova/tests/integrated/test_api_samples.pyadddoc/api_samples/os-hypervisors/hypervisors-servers-resp.jsonadddoc/api_samples/os-hypervisors/hypervisors-uptime-resp.xmladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-search-resp.xml.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-servers-resp.xml.tpladddoc/api_samples/os-hypervisors/hypervisors-statistics-resp.jsonadddoc/api_samples/os-hypervisors/hypervisors-detail-resp.jsonadddoc/api_samples/os-hypervisors/hypervisors-uptime-resp.jsonaddnova/tests/integrated/api_samples/os-hypervisors/hypervisors-list-resp.json.tpladddoc/api_samples/os-hypervisors/hypervisors-search-resp.xmladddoc/api_samples/os-hypervisors/hypervisors-list-resp.jsonadddoc/api_samples/os-hypervisors/hypervisors-detail-resp.xmladddoc/api_samples/os-hypervisors/hypervisors-show-resp.jsonaddnova/tests/integrated/api_samples/os-hypervisors/hypervisors-uptime-resp.json.tpladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-detail-resp.xml.tpladddoc/api_samples/os-hypervisors/hypervisors-servers-resp.xmladdnova/tests/integrated/api_samples/os-hypervisors/hypervisors-statistics-resp.json.tplConsole Output[...truncated 1250 lines...]Get:91 http://archive.ubuntu.com/ubuntu/ raring/main libfreetype6 amd64 2.4.11-0ubuntu1 [346 kB]Get:92 http://archive.ubuntu.com/ubuntu/ raring/main libjpeg-turbo8 amd64 1.2.1-0ubuntu2 [114 kB]Get:93 http://archive.ubuntu.com/ubuntu/ raring/main liblcms1 amd64 1.19.dfsg-1.2ubuntu2 [106 kB]Get:94 http://archive.ubuntu.com/ubuntu/ raring/main libpaper1 amd64 1.1.24+nmu2ubuntu2 [14.6 kB]Get:95 http://archive.ubuntu.com/ubuntu/ raring/main libyaml-0-2 amd64 0.1.4-2build1 [57.3 kB]Get:96 http://archive.ubuntu.com/ubuntu/ raring/main docutils-doc all 0.10-0ubuntu1 [1307 kB]Get:97 http://archive.ubuntu.com/ubuntu/ raring/main libjpeg8 amd64 8c-2ubuntu7 [2112 B]Get:98 http://archive.ubuntu.com/ubuntu/ raring/main libpaper-utils amd64 1.1.24+nmu2ubuntu2 [9164 B]Get:99 http://archive.ubuntu.com/ubuntu/ raring/main libtidy-0.99-0 amd64 20091223cvs-1.2 [147 kB]Get:100 http://archive.ubuntu.com/ubuntu/ raring/main python-dingus all 0.3.4-1 [8918 B]Get:101 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging-compat all 1.1.7+1.7.8-1ubuntu2 [5628 B]Get:102 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging amd64 1.1.7+1.7.8-1ubuntu2 [304 kB]Get:103 http://archive.ubuntu.com/ubuntu/ raring/main python-libxml2 amd64 2.9.0+dfsg1-4ubuntu1 [190 kB]Get:104 http://archive.ubuntu.com/ubuntu/ raring/main python-nose all 1.1.2-3ubuntu4 [135 kB]Get:105 http://archive.ubuntu.com/ubuntu/ raring/main python-openid all 2.2.5-3ubuntu1 [118 kB]Get:106 http://archive.ubuntu.com/ubuntu/ raring/main python-pastescript all 1.7.5-2 [118 kB]Get:107 http://archive.ubuntu.com/ubuntu/ raring/main python-scgi amd64 1.13-1ubuntu2 [20.4 kB]Get:108 http://archive.ubuntu.com/ubuntu/ raring/main python-stompy all 0.2.9-1ubuntu1 [11.2 kB]Get:109 http://archive.ubuntu.com/ubuntu/ raring/main python-utidylib all 0.2-8build1 [9370 B]Get:110 http://archive.ubuntu.com/ubuntu/ raring/main python-yaml amd64 3.10-4build2 [113 kB]Get:111 http://archive.ubuntu.com/ubuntu/ raring/main sphinx-doc all 1.1.3+dfsg-7ubuntu1 [855 kB]Failed to fetch http://localhost/ubuntu/pool/main/p/python-cinderclient/python-cinderclient_1.0.2.25.g4c37593+git201302190631~raring-0ubuntu1_all.deb 404 Not FoundFetched 20.1 MB in 16s (1213 kB/s)E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?install call failedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c',
[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_glance_trunk #129
Title: precise_grizzly_glance_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/129/Project:precise_grizzly_glance_trunkDate of build:Wed, 20 Feb 2013 15:31:09 -0500Build duration:12 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesAdding new common image propertiesby brian.rosmaitaadddoc/source/common-image-properties.rsteditdoc/source/index.rsteditetc/schema-image.jsonConsole Output[...truncated 7393 lines...]Checking signature on .dscGood signature on /tmp/tmpKF9F2y/glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1.dsc: done. Uploading glance_2013.1.a118.gd706143+git201302201531~precise.orig.tar.gz: done. Uploading glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1.debian.tar.gz: done. Uploading glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1.a115.g095102e+git201302191703~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/precise-grizzly']Pushed up to revision 237.INFO:root:Storing current commit for next build: d70614378177b15767ca473e57878d4afba4a33cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpKF9F2y/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpKF9F2y/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log b0360709bd80df9756a41089ac0c6a4eb19109df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a118.gd706143+git201302201531~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d706143] Adding new common image propertiesdch -a [9855237] Use oslo-config-2013.1b3dch -a [60be713] Create connection for each qpid notification.dch -a [9db0f05] Add an update option to run_tests.shdch -a [fcf0dca] Use install_venv_common.py from oslo.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly glance_2013.1.a118.gd706143+git201302201531~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_deploy #34
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/34/Project:raring_grizzly_deployDate of build:Wed, 20 Feb 2013 14:46:48 -0500Build duration:56 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 13257 lines...]INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #8610
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8610/ -- 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/hudson1915178092731748166.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8611
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8611/ -- 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/hudson7079516584043650126.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8612
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8612/ -- 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/hudson8281125562317227896.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8613
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8613/ -- 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/hudson920901702871093860.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8615
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8615/ -- 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/hudson119492900933035187.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8616
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8616/ -- 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/hudson1323764522315915370.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8617
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8617/ -- 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/hudson8154682983211398814.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.1-0ubuntu1.2 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 #8618
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8618/ -- 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/hudson6576491347854529912.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8619
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8619/ -- 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/hudson7405083296218039938.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8620
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8620/ -- 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/hudson1210245456207643661.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8621
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8621/ -- 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/hudson4960335459296832142.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8622
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8622/ -- 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/hudson2939452138005339213.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8623
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8623/ -- 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/hudson8052716203752955373.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8624
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8624/ -- 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/hudson7060427068034482728.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8625
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8625/ -- 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/hudson8673280991960074700.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8626
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8626/ -- 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/hudson1411832323088829424.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8627
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8627/ -- 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/hudson2798262147879468045.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8628
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8628/ -- 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/hudson7650073287493106977.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 Failure: raring_grizzly_deploy #41
Title: raring_grizzly_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/41/Project:raring_grizzly_deployDate of build:Wed, 20 Feb 2013 21:21:34 -0500Build duration:56 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 13160 lines...]WARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #8629
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8629/ -- 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/hudson322587887980090461.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8630
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8630/ -- 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/hudson6040162547702025896.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8631
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8631/ -- 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/hudson55568734109168782.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 Failure: precise_grizzly_glance_trunk #131
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/131/Project:precise_grizzly_glance_trunkDate of build:Wed, 20 Feb 2013 23:01:10 -0500Build duration:9 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFilter images by status and add visibility sharedby iccha.sethieditglance/tests/unit/test_db.pyeditglance/tests/unit/v2/test_images_resource.pyeditglance/api/v2/images.pyeditglance/db/__init__.pyeditglance/db/sqlalchemy/api.pyeditglance/tests/functional/v2/test_images.pyeditglance/tests/functional/db/base.pyeditglance/db/simple/api.pyConsole Output[...truncated 5914 lines...]Host Architecture: amd64Install-Time: 40Job: glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 480Source-Version: 2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1Space: 22040Status: attemptedVersion: 2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1Finished at 20130220-2310Build needed 00:08:00, 22040k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~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/tmpKfsC6j/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpKfsC6j/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log b1da386afb23694521fb65b1ba15c09835d997b8..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ac1c9ac] Filter images by status and add visibility shareddch -a [d706143] Adding new common image propertiesdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_glance_trunk #146
Title: raring_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/146/Project:raring_grizzly_glance_trunkDate of build:Wed, 20 Feb 2013 23:01:10 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFilter images by status and add visibility sharedby iccha.sethieditglance/tests/functional/v2/test_images.pyeditglance/tests/unit/test_db.pyeditglance/db/simple/api.pyeditglance/db/__init__.pyeditglance/db/sqlalchemy/api.pyeditglance/api/v2/images.pyeditglance/tests/functional/db/base.pyeditglance/tests/unit/v2/test_images_resource.pyConsole Output[...truncated 7051 lines...]Host Architecture: amd64Install-Time: 36Job: glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 705Source-Version: 2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1Space: 22048Status: attemptedVersion: 2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1Finished at 20130220-2315Build needed 00:11:45, 22048k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpcI_2_J/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpcI_2_J/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log b1da386afb23694521fb65b1ba15c09835d997b8..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [ac1c9ac] Filter images by status and add visibility shareddch -a [d706143] Adding new common image propertiesdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1.a122.g8e43e39+git201302202301~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #8632
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8632/ -- 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/hudson8181676279953809498.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8633
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8633/ -- 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/hudson548335365407150431.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8634
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8634/ -- 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/hudson8741125287569314065.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8635
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8635/ -- 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/hudson4489326264022479341.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 Failure: precise_grizzly_cinder_trunk #176
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_cinder_trunk #179
text/html; charset=UTF-8: Unrecognized -- 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 #8636
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8636/ -- 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/hudson5447895101923137559.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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: raring_grizzly_cinder_trunk #180
text/html; charset=UTF-8: Unrecognized -- 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 #8639
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8639/ -- 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/hudson6576141475174471861.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8640
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8640/ -- 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/hudson1232963201910827863.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8641
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8641/ -- 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/hudson9068463508783754896.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8642
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8642/ -- 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/hudson131836304249098063.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8644
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8644/ -- 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/hudson4696703151675812583.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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 #8645
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/8645/ -- 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/hudson4922020413820399663.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ca-versions/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/ca-versions/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! euca2ools: Ubuntu: 2.0.2-1ubuntu2.1 Cloud Archive staging: 2.0.2-1ubuntu2~cloud0 cinder: Ubuntu: 2012.2.1-0ubuntu1.1 Cloud Archive staging: 2012.2.1-0ubuntu1~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
