Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios
Robert, yes, I'm sure in certain configurations and with certain tuning, one can potentially place all services on a single device, and Quantum supports that just fine as well. For the sake of documentation, we wanted to show the case where the two were separated, as this tends to be what we see deployed. Dan On Thu, Nov 8, 2012 at 6:56 PM, Robert Garron robert.gar...@access3000.netwrote: Dan, I see your point about throughput and I/O, but if you have a multi-core server, greater than say 4 cores, and thus likely you would have multiple NICs, 2 or More, your assumptions fall apart about the cpu usage and I/o. For example, using XEN or Qemu or in the older systems where this concept originated - VMS OS (from Digital Equipment Corp. - see Galaxy product and similar) you can assign affinity to CPUs or even dedicate CPU's to tasks or VM's. In addition, using Cisco networking or similar you can dedicated I/O paths, and within a system, you can even dedicated a NIC Card or Port to a path. So the deployment of OpenStack on one physical server or several should not even be a consideration except to the installer and their budget; and whether or not High Availability is a concern. What I think is important is the consistency of the network design, I/O design for multiple VM's and the related load and intended usage of the individual cores of a server. But the most important consistency is having installation guides that work over and over for installations on different hardware and OS's. Myself, if I can get past my current nova and horizon issues, I will then be in a position to contribute in this and many other areas Regards, Robert On 11/8/12 4:06 PM, Skible OpenStack wrote: Thank you Dan for shedding light on this matter. However, there is something concerns me and a lot of other people trying to deploy OpenStack is that most Servers has 2 NICs which creates a problem because your Demo is a great one but the necessary hardware is just not always met ! I have been struggling to find a solution out of it, can you suggest some please ? Le 08/11/2012 21:38, Dan Wendlandt a écrit : Hi, The Quantum Admin Guide indicates that you can choose to combine all services onto a single node, or have separate nodes: http://docs.openstack.org/trunk/openstack-network/admin/content/services.html I will update the text to indicate that that the main reason to use a dedicated network gateway node is if you plan on having VMs send substantial amounts of traffic through that node, and thus would not want that CPU usage to conflict with other openstack services running on your controller node. dan On Thu, Nov 8, 2012 at 11:06 AM, Skible OpenStack skible.openst...@gmail.com wrote: Can someone please enlighten us about the goods of having a separated network node ? I honestly work in production envirnoments (over 30 nodes) and i really give computing resources more credit than networking ones ! Am i doing it the wrong way here ? Le 08/11/2012 18:49, balaji patnala a écrit : Hi Openers, One doubt i have is like, as we see in the demo setup in the Quantum Admin guide available in openstack.org, we have Network Node as a seperate physical node connected to Controller Node and Compute Node. But i see that the openstack community who is actively using Folsom is not discussing more on this kind of setup. Not sure if iam missing any key information on this like that the Network Node setup may not be widely used in current deployment scenarios or it is too early to use Network Node as a seperate physical host for openstack. Open comments on this will be more helpful for openstack community to understand better on the features of folsom. regards, balaji On Thu, Nov 8, 2012 at 7:09 PM, Skible OpenStack skible.openst...@gmail.com wrote: OpenStack Folsom install guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst You will find what you want and even more ;) Le 08/11/2012 14:30, Veera Reddy a écrit : Hi Skible, Can you please send me below configuration files of three setups you have mentioned. - ovs_quantum_plugin.ini (For controller and node) - nova.conf (For controller and node) Thanks in advance Regards, Veera. On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hello Stackers ! I am currently trying to create pictures of my OpenStack deployment architecture as a part of my OpenStack Folsom install guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstand i would like to ask a favorite. Could you be kind and please take a look at these Pics below and report back if there is a missing or wrong thing. Thank you. ==Quantum on VLAN + 3 NICs on controller node http://i.imgur.com/Ueh5Z.jpg
[Openstack] [Nova] Question about instance_metadata and instance_system_metadata
Hi, all Recently, I find out that when the instance with some metadata or system_metadata was deleted, but instance_metadata and instance_system_metadata these two tables are still keep the metadata and system_metadata deleted=0 (means these datas are not deleted). I am a little confused about this. Is this a bug or other somethings ? Thanks very much. 2012-11-01 hzyangtk___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] snapshots, backups of running VMs and compute node recovery
I try to implement a simple way to automate the backup mechanism (eg. every day): https://blueprints.launchpad.net/nova/+spec/backup-schedule And I though of a solution to respond to your needs: when a node fails (for any reasons), I disable it, I delete all servers was running on it and I restart them from the last available backup. Édouard. On Fri, Nov 9, 2012 at 8:45 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: The libvirt driver has actually gotten quite good at rebuilding all of the data for instances. This only thing it can't do right now is redownload base images from glance. With current state if you simply back up the instances directory (usually /var/lib/nova/instances) then you can recover by bringing back the whole directory and doing a nova reboot uuid for each instance. You could just stick the whole thing on an lvm and snaphot it regularly for dr. The _base directory can be regenerated with images from glance so you could also write a script to regenerate it and not have to worry about backing it up. The code to add to nova to make it automatically re-download the image from glance if it isn't there shouldn't be too bad either, which would mean you could safely ignore the _base directory for backups. Additionally using qcow images in glance and the config option `force_raw_images=False` will keep this directory much smaller. Vish On Nov 9, 2012, at 2:51 AM, Jānis Ģeņģeris janis.genge...@gmail.com wrote: Hello all, I would like to know the available solutions that are used regarding to backing up and/or snapshotting running instances on compute nodes. Documentation does not mention anything related to this. With snapshots I don't mean the current snapshot mechanism, that imports image of the running VM into glance. I'm using KVM, but this is significant for any hypervisor. Why is this important? Consider simple scenario when hardware on compute node fails and the node goes down immediately and is not recoverable in reasonable time. The images of the running instances are also lost. Shared file system is not considered here as it may cause IO bottlenecks and adds another layer of complexity. There have been a few discussions on the the list about this problem, but none have really answered the question. The documentation speaks of disaster recovery when power loss have happened and failed compute node recovery from shared file system. But don't cover the case without shared file system. I can think of few solutions currently (for KVM): a) using LVM images for VMs, and making LVM logical volume snapshots, but then the current nova snapshot mechanism will not work (from the docs - 'current snapshot mechanism in OpenStack Compute works only with instances backed with Qcow2 images'); b) snapshot machines with OpenStack snapshotting mechanism, but this doesn't fit somehow, because it has other goal than creating backups, will be slow and pollute the glance image space; Regards --janis ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] snapshots, backups of running VMs and compute node recovery
On Fri, Nov 9, 2012 at 9:45 PM, Vishvananda Ishaya vishvana...@gmail.comwrote:
The libvirt driver has actually gotten quite good at rebuilding all of the
data for instances. This only thing it can't do right now is redownload
base images from glance. With current state if you simply back up the
instances directory (usually /var/lib/nova/instances) then you can recover
by bringing back the whole directory and doing a nova reboot uuid for
each instance.
What about image corruption, If I start backing up '/var/lib/instances'
when the instances are running? Should they be paused or suspended while
doing that?
You could just stick the whole thing on an lvm and snaphot it regularly
for dr. The _base directory can be regenerated with images from glance so
you could also write a script to regenerate it and not have to worry about
backing it up. The code to add to nova to make it automatically re-download
the image from glance if it isn't there shouldn't be too bad either, which
would mean you could safely ignore the _base directory for backups.
Additionally using qcow images in glance and the config option
`force_raw_images=False` will keep this directory much smaller.
If I put everything on LVM, I will not be able to regular snapshots
anymore. Is there a workaround to this. I want to get some understanding
and confidence before I start rebuild my current setup.
With image regeneration you meant image download from glance ('glance
image-download')?
Vish
On Nov 9, 2012, at 2:51 AM, Jānis Ģeņģeris janis.genge...@gmail.com
wrote:
Hello all,
I would like to know the available solutions that are used regarding to
backing up and/or snapshotting running
instances on compute nodes. Documentation does not mention anything
related to this. With snapshots I don't mean
the current snapshot mechanism, that imports image of the running VM into
glance. I'm using KVM, but this is
significant for any hypervisor.
Why is this important?
Consider simple scenario when hardware on compute node fails and the node
goes down immediately and is not recoverable
in reasonable time. The images of the running instances are also lost.
Shared file system is not considered here as it
may cause IO bottlenecks and adds another layer of complexity.
There have been a few discussions on the the list about this problem, but
none have really answered the question.
The documentation speaks of disaster recovery when power loss have
happened and failed compute node recovery from
shared file system. But don't cover the case without shared file system.
I can think of few solutions currently (for KVM):
a) using LVM images for VMs, and making LVM logical volume snapshots, but
then the current nova snapshot mechanism
will not work (from the docs - 'current snapshot mechanism in OpenStack
Compute works only with instances backed
with Qcow2 images');
b) snapshot machines with OpenStack snapshotting mechanism, but this
doesn't fit somehow, because it has
other goal than creating backups, will be slow and pollute the glance
image space;
Regards
--janis
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
--janis
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] snapshots, backups of running VMs and compute node recovery
Hi, What do you mean with deleting all servers? If the node is down, then all the VM data is gone too, or you are talking about DB entries? On Mon, Nov 12, 2012 at 11:08 AM, Édouard Thuleau thul...@gmail.com wrote: I try to implement a simple way to automate the backup mechanism (eg. every day): https://blueprints.launchpad.net/nova/+spec/backup-schedule And I though of a solution to respond to your needs: when a node fails (for any reasons), I disable it, I delete all servers was running on it and I restart them from the last available backup. Édouard. On Fri, Nov 9, 2012 at 8:45 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: The libvirt driver has actually gotten quite good at rebuilding all of the data for instances. This only thing it can't do right now is redownload base images from glance. With current state if you simply back up the instances directory (usually /var/lib/nova/instances) then you can recover by bringing back the whole directory and doing a nova reboot uuid for each instance. You could just stick the whole thing on an lvm and snaphot it regularly for dr. The _base directory can be regenerated with images from glance so you could also write a script to regenerate it and not have to worry about backing it up. The code to add to nova to make it automatically re-download the image from glance if it isn't there shouldn't be too bad either, which would mean you could safely ignore the _base directory for backups. Additionally using qcow images in glance and the config option `force_raw_images=False` will keep this directory much smaller. Vish On Nov 9, 2012, at 2:51 AM, Jānis Ģeņģeris janis.genge...@gmail.com wrote: Hello all, I would like to know the available solutions that are used regarding to backing up and/or snapshotting running instances on compute nodes. Documentation does not mention anything related to this. With snapshots I don't mean the current snapshot mechanism, that imports image of the running VM into glance. I'm using KVM, but this is significant for any hypervisor. Why is this important? Consider simple scenario when hardware on compute node fails and the node goes down immediately and is not recoverable in reasonable time. The images of the running instances are also lost. Shared file system is not considered here as it may cause IO bottlenecks and adds another layer of complexity. There have been a few discussions on the the list about this problem, but none have really answered the question. The documentation speaks of disaster recovery when power loss have happened and failed compute node recovery from shared file system. But don't cover the case without shared file system. I can think of few solutions currently (for KVM): a) using LVM images for VMs, and making LVM logical volume snapshots, but then the current nova snapshot mechanism will not work (from the docs - 'current snapshot mechanism in OpenStack Compute works only with instances backed with Qcow2 images'); b) snapshot machines with OpenStack snapshotting mechanism, but this doesn't fit somehow, because it has other goal than creating backups, will be slow and pollute the glance image space; Regards --janis ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- --janis ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !
Hi,I suggest you reading my script [1] which helps to create virtual networking in Folsom with OVS Plugin for you use case.[1] https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.shRegards,Emilien Macchi// eNovance Inc. http://enovance.com// ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80// 10 rue de la Victoire 75009 ParisDe: "Skible OpenStack" skible.openst...@gmail.comÀ: "gong yong sheng" gong...@linux.vnet.ibm.comCc: openstack@lists.launchpad.netEnvoyé: Lundi 12 Novembre 2012 06:12:15Objet: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Thank you for responding back but i think when you configure the l3 agent to use one router the other tenant won't be able to connect to internet because their routers are not configured ! i repeat : i wish to have a router for each of my tenants and they all connect to the internet Le 12/11/2012 01:31, gong yong sheng a écrit: There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a écrit: Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 10 nov. 2012 à 17:57, Skible OpenStack skible.openst...@gmail.com a écrit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___Mailing list: https://launchpad.net/~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] Strange network behavior
Hi Vish et al. I still can't make head nor tail of it. ICMP works in both directions fine, but when I try to ssh out from the VM (even with the dmz_cidr flags) the SYN gets through un-snatted ok, then my desktop SYN-ACKs back, but the virt never gets to see it. Instead, the snat layer sends a RST. I don't want any NAT at all. I just want the virts bridged on to the VLAN. Is there a way to do that? Kind regards -- joe. On 9 November 2012 19:56, Vishvananda Ishaya vishvana...@gmail.com wrote: What is the ip address of your workstation? You may be running into something similar to this issue: http://lists.openstack.org/pipermail/openstack-dev/2012-September/001212.html I suspect either: a) Traffic not getting snatted when it should. This is usually due to overlapping ranges between your internal network and fixed_range this would be fixed by limiting fixed_range in your config file to just the instances range: (fixed_range=10.0.41.0/24 ?) or b) Traffic getting snatted when it shouldn't. This is usually because your workstation ip is on an ip that is internally routable but not routable from the external network of the compute host, so it can't get back to the snatted ip this is fixed by stopping snatting to the workstation by setting dmz_cidr to a value that includes your workstation network: (dmz_cidr=10.0.0.0/24?) Vish On Nov 9, 2012, at 9:14 AM, Joe Warren-Meeks joe.warren.me...@gmail.com wrote: Hi all, I've managed to get Openstack pretty much up and running as I wanted it. I do have, however, a rather strange networking issue. I created the network with nova-manage network create --fixed_range_v4=10.0.41.0/24 --num_networks=1 --bridge=br41 --bridge_interface=eth0 --label=development --gateway=10.0.41.1 --dns1=10.0.0.2 --vlan=41 --project_id=XXX And i can boot instances fine. I've configured the default security group to allow port 22, 80 and ICMP -1 in and I can ping from my work station to the virtual instance ok: joe@kaneda:~$ ping 10.0.41.3 PING 10.0.41.3 (10.0.41.3) 56(84) bytes of data. 64 bytes from 10.0.41.3: icmp_req=1 ttl=63 time=1.18 ms And i can ping from the virt back too: ubuntu@test:~$ ping 10.0.0.240 PING 10.0.0.240 (10.0.0.240) 56(84) bytes of data. 64 bytes from 10.0.0.240: icmp_req=1 ttl=64 time=0.713 ms I can SSH out from the virt to a host in the outside world fine: ubuntu@test:~$ ssh joe@X joe@XX password: -bash: fortune: command not found joe@dixon:~ $ BUT I can't ssh from the virt to my workstation, nor from my workstation to the Virt. Neither does http work. What I am seeing in Tcpdump is a lot of incorrect cksums. This happens with all Tcp connections. 17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF], proto TCP (6), length 60) 10.0.0.240.56791 10.0.41.3.22: Flags [S], cksum 0x3e21 (incorrect - 0x6de2), seq 2650163743, win 14600, options [mss 1460,sackOK,TS val 28089204 ecr 0,nop,wscale 6], length 0 17:12:38.585279 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) 10.0.41.3.22 10.0.0.240.56791: Flags [S.], cksum 0x3e21 (incorrect - 0xe5c5), seq 1530502549, ack 3098447117, win 14480, options [mss 1460,sackOK,TS val 340493 ecr 28089204,nop,wscale 3], length 0 Anyone come across this before? -- joe. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Bridge mappings in folsom
Hi All, I have few questions regarding bridge mapping in folsom release. In the quantum configuration file, there is a config param for bridge mapping: bridge_mappings=default:br-eth1 (ListOpt) Comma-separated list of physical_network:bridge tuples mapping physical network names to agent's node-specific OVS bridge names. Each bridge must exist, and should have physical network # interface configured as a port. Can anyone elaborate on this parameter? What are these physical network names and why they mapped to ovs bridge names ? Please help me in understanding network setup using folsom. Thanks in advance. -- Thanks Regards Neelakantam Gaddam ___ 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] Essex Dashboard: KeyError at /nova/instances_and_volumes/
Hey all,
since quite some weeks I am getting an error page instead of the Instances
and Volumes page in the
Essex Horizon Dashboard with the above title and the below detailed error
output:
Environment:
Request Method: GETRequest URL:
http://controller.rz.dawanda.com/nova/instances_and_volumes/
Django Version: 1.3.1Python Version: 2.7.3Installed Applications:
['openstack_dashboard', 'django.contrib.sessions',
'django.contrib.messages', 'django.contrib.staticfiles', 'django_nose',
'horizon', 'horizon.dashboards.nova', 'horizon.dashboards.syspanel',
'horizon.dashboards.settings']Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'openstack_dashboard.middleware.DashboardLogUnhandledExceptionsMiddleware',
'horizon.middleware.HorizonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.locale.LocaleMiddleware')
Traceback:File
/usr/lib/python2.7/dist-packages/django/core/handlers/base.py in
get_response 111. response = callback(request,
*callback_args, **callback_kwargs)File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 40.
return view_func(request, *args, **kwargs)File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 55.
return view_func(request, *args, **kwargs)File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 40.
return view_func(request, *args, **kwargs)File
/usr/lib/python2.7/dist-packages/django/views/generic/base.py in view
47. return self.dispatch(request, *args, **kwargs)File
/usr/lib/python2.7/dist-packages/django/views/generic/base.py in dispatch
68. return handler(request, *args, **kwargs)File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in get 105.
handled = self.construct_tables()File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in
construct_tables 96. handled = self.handle_table(table)File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in handle_table
68. data = self._get_data_dict()File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in _get_data_dict
37. self._data[table._meta.name] = data_func()File
/usr/lib/python2.7/dist-packages/horizon/dashboards/nova/instances_and_volumes/views.py
in get_volumes_data 74. att['instance'] =
instances[att['server_id']]
Exception Type: KeyError at /nova/instances_and_volumes/Exception Value:
u'8aa2989e-85ea-4975-b81b-04d06dbf8013'
--
--
now I wonder in how far that is a bug in the software and/or whether I have
an invalid entry in my nova database that
I can fix by hand.
if so, does anyone know how to actually work around this? I do really need
this (now not working) page :-)
Regards,
Christian Parpart.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !
You have to create multiple routers. You have one provider level router that will be your external network router, You can then create a router either for each tenant or for all tenants to support the internal network depending on your needs/topology. Logan From: openstack-bounces+logan_mcleod=dell@lists.launchpad.net [mailto:openstack-bounces+logan_mcleod=dell@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Monday, November 12, 2012 3:58 AM To: Skible OpenStack Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Hi, I suggest you reading my script [1] which helps to create virtual networking in Folsom with OVS Plugin for you use case. [1] https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.shhttp://[1]%20https:/github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.sh Regards, Emilien Macchi // eNovance Inc. http://enovance.com // ✉ emil...@enovance.commailto:emil...@enovance.com ☎ +33 (0)1 49 70 99 80 // 10 rue de la Victoire 75009 Paris De: Skible OpenStack skible.openst...@gmail.com À: gong yong sheng gong...@linux.vnet.ibm.com Cc: openstack@lists.launchpad.net Envoyé: Lundi 12 Novembre 2012 06:12:15 Objet: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Thank you for responding back but i think when you configure the l3 agent to use one router the other tenant won't be able to connect to internet because their routers are not configured ! i repeat : i wish to have a router for each of my tenants and they all connect to the internet Le 12/11/2012 01:31, gong yong sheng a écrit : There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a écrit : Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:image001.jpg@01CDC0AD.2EBFF660] Le 10 nov. 2012 à 17:57, Skible OpenStack skible.openst...@gmail.commailto:skible.openst...@gmail.com a écrit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp inline: image001.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] how to configure l3_agent when you have Per-tenant Routers !
This means that each tenant router should be linked to the external network router ? is that what you mean Logan ? Le 12/11/2012 15:10, logan_mcl...@dell.com a crit: You have to create multiple routers. You have one provider level router that will be your external network router, You can then create a router either for each tenant or for all tenants to support the internal network depending on your needs/topology. Logan From: openstack-bounces+logan_mcleod=dell@lists.launchpad.net [mailto:openstack-bounces+logan_mcleod=dell@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Monday, November 12, 2012 3:58 AM To: Skible OpenStack Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Hi, I suggest you reading my script [1] which helps to create virtual networking in Folsom with OVS Plugin for you use case. [1] https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.sh Regards, Emilien Macchi // eNovance Inc. http://enovance.com // emil...@enovance.com +33 (0)1 49 70 99 80 // 10 rue de la Victoire 75009 Paris De: "Skible OpenStack" skible.openst...@gmail.com : "gong yong sheng" gong...@linux.vnet.ibm.com Cc: openstack@lists.launchpad.net Envoy: Lundi 12 Novembre 2012 06:12:15 Objet: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Thank you for responding back but i think when you configure the l3 agent to use one router the other tenant won't be able to connect to internet because their routers are not configured ! i repeat : i wish to have a router for each of my tenants and they all connect to the internet Le 12/11/2012 01:31, gong yong sheng a crit: There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a crit: Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 10 nov. 2012 17:57, Skible OpenStack skible.openst...@gmail.com a crit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one
Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !
I haven’t tried it yet, but yes. You should be able to add internal network interfaces from the external router setup to a common internal network to which each of the tenant routers is also connected to. Setting the external network gateway of the tenant routers to that of the ext_net router should then complete the connection… Logan From: openstack-bounces+logan_mcleod=dell@lists.launchpad.net [mailto:openstack-bounces+logan_mcleod=dell@lists.launchpad.net] On Behalf Of Skible OpenStack Sent: Monday, November 12, 2012 8:21 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! This means that each tenant router should be linked to the external network router ? is that what you mean Logan ? Le 12/11/2012 15:10, logan_mcl...@dell.commailto:logan_mcl...@dell.com a écrit : You have to create multiple routers. You have one provider level router that will be your external network router, You can then create a router either for each tenant or for all tenants to support the internal network depending on your needs/topology. Logan From: openstack-bounces+logan_mcleod=dell@lists.launchpad.netmailto:openstack-bounces+logan_mcleod=dell@lists.launchpad.net [mailto:openstack-bounces+logan_mcleod=dell@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Monday, November 12, 2012 3:58 AM To: Skible OpenStack Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Hi, I suggest you reading my script [1] which helps to create virtual networking in Folsom with OVS Plugin for you use case. [1] https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.shhttp://[1]%20https:/github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.sh Regards, Emilien Macchi // eNovance Inc. http://enovance.com // ✉ emil...@enovance.commailto:emil...@enovance.com ☎ +33 (0)1 49 70 99 80 // 10 rue de la Victoire 75009 Paris De: Skible OpenStack skible.openst...@gmail.commailto:skible.openst...@gmail.com À: gong yong sheng gong...@linux.vnet.ibm.commailto:gong...@linux.vnet.ibm.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Envoyé: Lundi 12 Novembre 2012 06:12:15 Objet: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers ! Thank you for responding back but i think when you configure the l3 agent to use one router the other tenant won't be able to connect to internet because their routers are not configured ! i repeat : i wish to have a router for each of my tenants and they all connect to the internet Le 12/11/2012 01:31, gong yong sheng a écrit : There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a écrit : Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:image001.jpg@01CDC0B8.1FD7E350] Le 10 nov. 2012 à 17:57, Skible OpenStack skible.openst...@gmail.commailto:skible.openst...@gmail.com a écrit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More
Re: [Openstack] Quantum Debug
Hello again, I had some progress now. I followed another guide and now using VLAN+bridge interface ( https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst ) Now I can ping the instances (after configuring the interface manually logging via VNC) - They dont get DHCP service at all. I run udhcpc and it stays in Sending discover... for ever. - I cannot ping anything but the instances one to each other. Not the quantum router (which I think it should be in 10.10.10.1) Now this is my Quantum configuration in the *cloud controller* node: root@folsom-cc01:/etc/quantum# cat *dhcp_agent*.ini | grep -v '#' [DEFAULT] state_path = /var/lib/quantum interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq use_namespaces = True root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf root@folsom-cc01:/etc/quantum# cat *l3_agent*.ini | grep -v '#' [DEFAULT] debug = True interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver auth_url = http://ccontroller:35357/v2.0 auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = password root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf use_namespaces = True metadata_ip = 192.168.253.172 root@folsom-cc01:/etc/quantum# cat quantum.conf | grep -v '#' [DEFAULT] verbose = True debug = True bind_host = 0.0.0.0 bind_port = 9696 core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 auth_strategy = keystone fake_rabbit = False rabbit_password = password api_paste_config = /etc/quantum/api-paste.ini control_exchange = quantum notification_driver = quantum.openstack.common.notifier.list_notifier list_notifier_drivers = quantum.openstack.common.notifier.rabbit_notifier [QUOTAS] root@folsom-cc01:/etc/quantum# cat plugins/openvswitch/*ovs_quantum_plugin*.ini | grep -v '#' [DATABASE] sql_connection = mysql://quantum:password@ccontroller:3306/quantum reconnect_interval = 2 reconnect_interval = 2 [OVS] tenant_network_type=vlan network_vlan_ranges = physnet1:1:4094 bridge_mappings = physnet1:br-eth1 [AGENT] polling_interval = 2 root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf Now in the *Compute Node*: root@folsom-cn1:/var/log/openvswitch# cat /etc/quantum/*quantum*.conf | grep -v '#' [DEFAULT] verbose = True debug = True bind_host = 0.0.0.0 bind_port = 9696 core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 auth_strategy = keystone fake_rabbit = False rabbit_host = ccontroller rabbit_password = password api_paste_config = /etc/quantum/api-paste.ini control_exchange = quantum notification_driver = quantum.openstack.common.notifier.list_notifier list_notifier_drivers = quantum.openstack.common.notifier.rabbit_notifier [QUOTAS] root@folsom-cn1:/etc/quantum# cat plugins/openvswitch/*ovs_quantum_plugin*.ini | grep -v '#' [DATABASE] sql_connection = mysql://quantum:password@ccontroller:3306/quantum reconnect_interval = 2 [OVS] tenant_network_type=vlan network_vlan_ranges = physnet1:1:4094 bridge_mappings = physnet1:br-eth1 [AGENT] polling_interval = 2 root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf Some more information: root@folsom-cn1:/etc/quantum# ovs-vsctl show ba9aad32-efd0-4891-b78d-feec74ea8b03 Bridge br-int Port qvo591594a6-e9 tag: 1 Interface qvo591594a6-e9 Port qvo8c296e5d-bf tag: 1 Interface qvo8c296e5d-bf Port br-int Interface br-int type: internal Port qvo1b57b973-42 tag: 1 Interface qvo1b57b973-42 Port qvob0aef54a-03 tag: 1 Interface qvob0aef54a-03 Port qvo5936a539-a1 tag: 2 Interface qvo5936a539-a1 Port int-br-eth1 Interface int-br-eth1 Port qvo1d27e91c-a0 tag: 1 Interface qvo1d27e91c-a0 Bridge br-eth1 Port phy-br-eth1 Interface phy-br-eth1 Port eth1 Interface eth1 Port br-eth1 Interface br-eth1 type: internal ovs_version: 1.4.0+build0 root@folsom-cc01:/etc/init.d# ovs-vsctl show 4a1a49ba-b6cb-465d-87f1-9d1dbe9c6f81 Bridge br-eth1 Port br-eth1 Interface br-eth1 type: internal Port phy-br-eth1 Interface phy-br-eth1 Port eth1 Interface eth1 Bridge br-int Port qr-3c159389-9e tag: 1 Interface qr-3c159389-9e type: internal Port br-int Interface br-int type: internal Port int-br-eth1 Interface int-br-eth1 Port tap24284d5b-2b tag: 1 Interface tap24284d5b-2b type: internal Bridge br-ex Port
Re: [Openstack] Strange network behavior
Hey guys, Ignore this q. I didn't really have my head around how Openstack works and I think I get it now. Thanks for all your help. -- joe. On 12 November 2012 10:12, Joe Warren-Meeks joe.warren.me...@gmail.comwrote: Hi Vish et al. I still can't make head nor tail of it. ICMP works in both directions fine, but when I try to ssh out from the VM (even with the dmz_cidr flags) the SYN gets through un-snatted ok, then my desktop SYN-ACKs back, but the virt never gets to see it. Instead, the snat layer sends a RST. I don't want any NAT at all. I just want the virts bridged on to the VLAN. Is there a way to do that? Kind regards -- joe. On 9 November 2012 19:56, Vishvananda Ishaya vishvana...@gmail.comwrote: What is the ip address of your workstation? You may be running into something similar to this issue: http://lists.openstack.org/pipermail/openstack-dev/2012-September/001212.html I suspect either: a) Traffic not getting snatted when it should. This is usually due to overlapping ranges between your internal network and fixed_range this would be fixed by limiting fixed_range in your config file to just the instances range: (fixed_range=10.0.41.0/24 ?) or b) Traffic getting snatted when it shouldn't. This is usually because your workstation ip is on an ip that is internally routable but not routable from the external network of the compute host, so it can't get back to the snatted ip this is fixed by stopping snatting to the workstation by setting dmz_cidr to a value that includes your workstation network: (dmz_cidr=10.0.0.0/24?) Vish On Nov 9, 2012, at 9:14 AM, Joe Warren-Meeks joe.warren.me...@gmail.com wrote: Hi all, I've managed to get Openstack pretty much up and running as I wanted it. I do have, however, a rather strange networking issue. I created the network with nova-manage network create --fixed_range_v4=10.0.41.0/24--num_networks=1 --bridge=br41 --bridge_interface=eth0 --label=development --gateway=10.0.41.1 --dns1=10.0.0.2 --vlan=41 --project_id=XXX And i can boot instances fine. I've configured the default security group to allow port 22, 80 and ICMP -1 in and I can ping from my work station to the virtual instance ok: joe@kaneda:~$ ping 10.0.41.3 PING 10.0.41.3 (10.0.41.3) 56(84) bytes of data. 64 bytes from 10.0.41.3: icmp_req=1 ttl=63 time=1.18 ms And i can ping from the virt back too: ubuntu@test:~$ ping 10.0.0.240 PING 10.0.0.240 (10.0.0.240) 56(84) bytes of data. 64 bytes from 10.0.0.240: icmp_req=1 ttl=64 time=0.713 ms I can SSH out from the virt to a host in the outside world fine: ubuntu@test:~$ ssh joe@X joe@XX password: -bash: fortune: command not found joe@dixon:~ $ BUT I can't ssh from the virt to my workstation, nor from my workstation to the Virt. Neither does http work. What I am seeing in Tcpdump is a lot of incorrect cksums. This happens with all Tcp connections. 17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF], proto TCP (6), length 60) 10.0.0.240.56791 10.0.41.3.22: Flags [S], cksum 0x3e21 (incorrect - 0x6de2), seq 2650163743, win 14600, options [mss 1460,sackOK,TS val 28089204 ecr 0,nop,wscale 6], length 0 17:12:38.585279 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) 10.0.41.3.22 10.0.0.240.56791: Flags [S.], cksum 0x3e21 (incorrect - 0xe5c5), seq 1530502549, ack 3098447117, win 14480, options [mss 1460,sackOK,TS val 340493 ecr 28089204,nop,wscale 3], length 0 Anyone come across this before? -- joe. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Horizon] Error in /var/log/apache2/error.log
Hi,
I created a custom page in horizon. Most of the new page is working fine.
But, when I wanted to load some custom 'quantum' DB table data in horizon,
I am getting the following error in '*/var/log/apache2/error.log*':
*Traceback (most recent call last):
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/horizon/dashboards/nova/services/configs/tabs.py,
line 42, in get_context_data
[Mon Nov 12 15:52:58 2012] [error] config =
api.quantum.dhcp_config_get(self.request, config_id)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/horizon/api/quantum.py, line 247, in
dhcp_config_get
[Mon Nov 12 15:52:58 2012] [error] **params).get('config')
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 102,
in with_params
[Mon Nov 12 15:52:58 2012] [error] ret = self.function(instance, *args,
**kwargs)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 330,
in show_config
[Mon Nov 12 15:52:58 2012] [error] return self.get(self.config_path %
(config), params=_params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 620,
in get
[Mon Nov 12 15:52:58 2012] [error] headers=headers, params=params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 605,
in retry_request
[Mon Nov 12 15:52:58 2012] [error] headers=headers, params=params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 550,
in do_request
[Mon Nov 12 15:52:58 2012] [error]
self._handle_fault_response(status_code, replybody)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 523,
in _handle_fault_response
[Mon Nov 12 15:52:58 2012] [error] exception_handler_v20(status_code,
des_error_body)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 82,
in exception_handler_v20
[Mon Nov 12 15:52:58 2012] [error] message=message)
[Mon Nov 12 15:52:58 2012] [error] QuantumClientException: 404 Not Found
[Mon Nov 12 15:52:58 2012] [error]
[Mon Nov 12 15:52:58 2012] [error] The resource could not be found.*
Can anybody, please suggest me, what is the error and the fix?
Thanks in advance.
--
Srikanth.
___
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] Essex Dashboard: KeyError at /nova/instances_and_volumes/
That is actually the manifestation of a bug in Nova that was addressed very
late in Folsom. The short version is that Nova inconsistently scoped the
ownership of volumes vs. instances so it was possible for an admin user to view
a mixed set of resources which could lead to the scenario you hit where things
are in one list but not the other. I'm not sure if there's any plans to
backport the fixes from Nova. A patch could probably be worked up for the
stable/essex Horizon branch that would avoid the keyerror (see the state of
that code in Folsom:
https://github.com/openstack/horizon/blob/stable/folsom/horizon/dashboards/nova/volumes/views.py#L68
), but it would be papering over what is inherently a broken situation in Nova.
My advice from back in the Essex days was that you should be wary of using an
admin user in the Project dashboard since the underlying APIs didn't handle
it correctly.
Alternatively, the Folsom Horizon release is actually backwards-compatible to
an Essex stack, so you could try running Folsom Horizon which is less subject
to many issues.
Hope one of these suggestions helps!
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Behalf Of Christian Parpart
Sent: Monday, November 12, 2012 3:37 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Essex Dashboard: KeyError at /nova/instances_and_volumes/
Hey all,
since quite some weeks I am getting an error page instead of the Instances and
Volumes page in the
Essex Horizon Dashboard with the above title and the below detailed error
output:
Environment:
Request Method: GET
Request URL: http://controller.rz.dawanda.com/nova/instances_and_volumes/
Django Version: 1.3.1
Python Version: 2.7.3
Installed Applications:
['openstack_dashboard',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django_nose',
'horizon',
'horizon.dashboards.nova',
'horizon.dashboards.syspanel',
'horizon.dashboards.settings']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'openstack_dashboard.middleware.DashboardLogUnhandledExceptionsMiddleware',
'horizon.middleware.HorizonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.locale.LocaleMiddleware')
Traceback:
File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py in
get_response
111. response = callback(request, *callback_args,
**callback_kwargs)
File /usr/lib/python2.7/dist-packages/horizon/decorators.py in dec
40. return view_func(request, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/horizon/decorators.py in dec
55. return view_func(request, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/horizon/decorators.py in dec
40. return view_func(request, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/django/views/generic/base.py in view
47. return self.dispatch(request, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/django/views/generic/base.py in dispatch
68. return handler(request, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/horizon/tables/views.py in get
105. handled = self.construct_tables()
File /usr/lib/python2.7/dist-packages/horizon/tables/views.py in
construct_tables
96. handled = self.handle_table(table)
File /usr/lib/python2.7/dist-packages/horizon/tables/views.py in handle_table
68. data = self._get_data_dict()
File /usr/lib/python2.7/dist-packages/horizon/tables/views.py in
_get_data_dict
37. self._data[table._meta.namehttp://meta.name] =
data_func()
File
/usr/lib/python2.7/dist-packages/horizon/dashboards/nova/instances_and_volumes/views.py
in get_volumes_data
74. att['instance'] = instances[att['server_id']]
Exception Type: KeyError at /nova/instances_and_volumes/
Exception Value: u'8aa2989e-85ea-4975-b81b-04d06dbf8013'
now I wonder in how far that is a bug in the software and/or whether I have an
invalid entry in my nova database that
I can fix by hand.
if so, does anyone know how to actually work around this? I do really need this
(now not working) page :-)
Regards,
Christian Parpart.
___
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] [Cinder] Cinder snapshots
Top posting to give some general history and some thoughts. Snapshots, as implemented currently in cinder, are derived from the EBS definition of a snapshot. This is more of a consistent block level backup of a volume. New volumes can be created from any given snapshot. This is *not* usually what a snapshot is in a traditional storage system, though snapshots are usually used in the process. My concern with trying to expose more general snapshot, cloning, etc functionalities in the api is that they are very backend dependent, and will have different capabilities and properties. Trying to define a generic API for these cases that works across all backends is going to be problematic, which is why I've always been supportive of having these implemented as extensions specific to each backend. -- Chuck On Sun, Nov 11, 2012 at 11:09 PM, Avishay Traeger avis...@il.ibm.com wrote: John Griffith john.griff...@solidfire.com wrote on 11/11/2012 17:01:37: Hey Avishay, I guess I'm still confused about what a snapshot is in OpenStack. Currently you can't really do anything with them via OpenStack. Sure you can, you can use them to create a new volume. They make a good backup mechanism IMO. Right - you can either make a new volume (=clone) or figure out somehow what name Cinder gave to the snapshot and make a backup on your own. [ Off topic question: How can a user determine the name of a volume/snapshot on the back-end for a given volume/snapshot? ] I guess my question to you in your definition then is 'what's the difference between a snapshot and a clone'? IMHO, a clone is a full, independent copy of the volume. It would copy all data (either in foreground or background) and leave the user with a volume - as if he created a new volume and used dd to copy all the data. A snapshot is something that depends on the original volume and in most implementations would contain only changed blocks. Clone definitely has other meanings - what's your definition? Also, it Seems to me if we go with the idea of adding snapshot- restore, and a true clone feature you get everything that you're asking for here and more... so I'm not sure of the problem? Maybe you could help me understand why defining snapshot and clone in the manner described doesn't seem appropriate? So as I stated above, clone would give me a full copy, which can be wasteful. I should be able to read and write to snapshots within the context of Cinder. FWIW, I think a R/O attach is something that would be good to have as an option regardless. It's a necessity IMO. R/W is less common, but also very important. It's obvious that Cinder can't support features found in some storage controllers, but even LVM2 supports R/W snapshots (released almost 10 years ago). Don't get me wrong - LVM is awesome - but if ubiquitous, freely-available software supports a feature that controllers also generally support, I think Cinder should support it too. Thanks, John Thank you, Avishay ___ 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] [Horizon] Error in /var/log/apache2/error.log
Your Quantum API route is returning a 404. Whether this is because you have
your route wrong or Quantum is misconfigured or [something else] I could tell
you. I would recommend narrowing down your possibilities by trying to make the
call directly with quantumclient or using curl to make the request directly and
to look at your Quantum logs to see if there's something evidently amiss.
All the best,
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Behalf Of Srikanth Kumar Lingala
Sent: Monday, November 12, 2012 8:00 AM
To: openstack@lists.launchpad.net; openstack-...@lists.openstack.org
Subject: [Openstack] [Horizon] Error in /var/log/apache2/error.log
Hi,
I created a custom page in horizon. Most of the new page is working fine.
But, when I wanted to load some custom 'quantum' DB table data in horizon, I am
getting the following error in '/var/log/apache2/error.log':
Traceback (most recent call last):
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/horizon/dashboards/nova/services/configs/tabs.py,
line 42, in get_context_data
[Mon Nov 12 15:52:58 2012] [error] config =
api.quantum.dhcp_config_get(self.request, config_id)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/horizon/api/quantum.py, line 247, in
dhcp_config_get
[Mon Nov 12 15:52:58 2012] [error] **params).get('config')
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 102, in
with_params
[Mon Nov 12 15:52:58 2012] [error] ret = self.function(instance, *args,
**kwargs)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 330, in
show_config
[Mon Nov 12 15:52:58 2012] [error] return self.get(self.config_path %
(config), params=_params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 620, in
get
[Mon Nov 12 15:52:58 2012] [error] headers=headers, params=params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 605, in
retry_request
[Mon Nov 12 15:52:58 2012] [error] headers=headers, params=params)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 550, in
do_request
[Mon Nov 12 15:52:58 2012] [error] self._handle_fault_response(status_code,
replybody)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 523, in
_handle_fault_response
[Mon Nov 12 15:52:58 2012] [error] exception_handler_v20(status_code,
des_error_body)
[Mon Nov 12 15:52:58 2012] [error] File
/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py, line 82, in
exception_handler_v20
[Mon Nov 12 15:52:58 2012] [error] message=message)
[Mon Nov 12 15:52:58 2012] [error] QuantumClientException: 404 Not Found
[Mon Nov 12 15:52:58 2012] [error]
[Mon Nov 12 15:52:58 2012] [error] The resource could not be found.
Can anybody, please suggest me, what is the error and the fix?
Thanks in advance.
--
Srikanth.
___
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] [Horizon] tables.DeleteAction not working
Hi, I created a custom table in Quantum DB, and getting rows from that, and show as Table in Horizon. For each row, I put only action 'Delete', and called subsequent class for eg. 'DeleteRow(tables.DeleteAction)'. In this, I wrote 'delete' function, in which I am calling quantum API to delete the row from DB. But, however, If I click DeleteRow button in horizon, 'delete()' function in the class is not triggering. And, as a result, row is not deleting from DB. I am not getting any kind of error logs in nova-api.log, apache error logs ..etc. Can anyone suggest, what went wrong? Thanks in advance. -- Srikanth. ___ 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] [Horizon] tables.DeleteAction not working
For questions like that it would be *very* helpful if you could post your code somewhere (github/gerrit). Debugging them otherwise is basically shooting in the dark. - Gabriel From: Srikanth Kumar Lingala [mailto:srikanthkumar.ling...@gmail.com] Sent: Monday, November 12, 2012 11:51 AM To: openstack@lists.launchpad.net; openstack-...@lists.openstack.org Subject: [openstack-dev] [Horizon] tables.DeleteAction not working Hi, I created a custom table in Quantum DB, and getting rows from that, and show as Table in Horizon. For each row, I put only action 'Delete', and called subsequent class for eg. 'DeleteRow(tables.DeleteAction)'. In this, I wrote 'delete' function, in which I am calling quantum API to delete the row from DB. But, however, If I click DeleteRow button in horizon, 'delete()' function in the class is not triggering. And, as a result, row is not deleting from DB. I am not getting any kind of error logs in nova-api.log, apache error logs ..etc. Can anyone suggest, what went wrong? Thanks in advance. -- Srikanth. ___ 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] Plans for Trusted Computing in OpenStack
Nicolae- We've been working under the assumption you have trust the IaaS provider (individual nodes might have been compromised somehow but you trust the provider itself). I think what you are looking at is adding a 3rd party CA which is significantly increasing the complexity of the solution and potentially exposing the IaaS's infrastructure to a 3rd party, probably not desirable to the IaaS provider. I've added some others to the thread who can chime in with their opinions. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 From: Nicolae Paladi [mailto:n.pal...@gmail.com] Sent: Wednesday, November 07, 2012 7:42 AM To: Dugger, Donald D Cc: openstack Subject: Re: [Openstack] Plans for Trusted Computing in OpenStack Hi, so basically my questions/thoughts about support for TC in OpenStack are based on a somewhat different attack model where the IaaS is actually not trusted. That is in contrast with the Trusted Compute Pools, where the scheduler/trusted_filter is assumed to reject the host as a candidate for running the VM if it does not have a corresponding trust value. However, nothing prevents a really evil IaaS deployment to ignore this trust value and go ahead, launch the VM and return it to the client. So there's an improvement suggestion focusing on that part. The model that I have in mind assumes both no trust in the IaaS setup/provider. So the gist is that: 1. Client could upload a secret encrypted with the public key of the authentication service (possible to include in the extra_specs) 2. The Attestation Service, after verifying the compute host could bind the secret to the hosts trusted configuration, so that the host can inject the secret into the VM With this approach, a malicious IaaS provider can still launch the VM on an untrusted host, but now he client can verify that the VM has been started on a 'trusted' host. So the questions around this are -- 1. Is the scenario of an untrusted IaaS deployment considered for Trusted Compute Pools? 2. Is there any work ongoing to extend Trusted Compute Polls for storage as well? Or otherwise put, what about the storage, is the solution to encrypt all data on the compute host prior to storing it in the object store? 3. Is there any work ongoing on the evaluation side, namely the evaluation of the trust attributes obtained from the host -- and do Trusted Compute Pools consider a binary value (trusted/untrusted) or a scale of security profiles? Cheers, /Nico. On 6 November 2012 19:07, Dugger, Donald D donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote: Nico- This is the appropriate place for discussions about Trusted Compute Pools under OpenStack. Feel free to send out any ideas you have, I know I and others would be very interested in what you have. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786tel:303%2F443-3786 From: openstack-bounces+donald.d.dugger=intel@lists.launchpad.netmailto:intel@lists.launchpad.net [mailto:openstack-bounces+donald.d.duggermailto:openstack-bounces%2Bdonald.d.dugger=intel@lists.launchpad.netmailto:intel@lists.launchpad.net] On Behalf Of Nicolae Paladi Sent: Tuesday, November 06, 2012 8:35 AM To: openstack Subject: [Openstack] Plans for Trusted Computing in OpenStack Hi, I am involved in a project that aims to use TPM modules to ensure that the compute nodes run a 'trusted' software stack in a public IaaS deployment. I've read about trusted computing pools (http://wiki.openstack.org/TrustedComputingPools) checked out the OpenAttestation project and seen a presentation from the OpenStack summit (Putting Trust in OpenStackhttp://www.openstack.org/summit/san-diego-2012/openstack-summit-sessions/presentation/putting-trust-in-openstack) in order to get a better understading of where OpenStack is heading towards wrt TPM support. Are there any more resources, discussions, mailing lists that I could check out and where I could potentially bounce ideas? Cheers, /Nico. ___ 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] [Horizon] tables.DeleteAction not working
Ok .. I will post there ... Srikanth. On Mon, Nov 12, 2012 at 2:06 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: For questions like that it would be **very** helpful if you could post your code somewhere (github/gerrit). Debugging them otherwise is basically shooting in the dark. ** ** **- **Gabriel ** ** *From:* Srikanth Kumar Lingala [mailto:srikanthkumar.ling...@gmail.com] *Sent:* Monday, November 12, 2012 11:51 AM *To:* openstack@lists.launchpad.net; openstack-...@lists.openstack.org *Subject:* [openstack-dev] [Horizon] tables.DeleteAction not working ** ** Hi, I created a custom table in Quantum DB, and getting rows from that, and show as Table in Horizon. For each row, I put only action 'Delete', and called subsequent class for eg. 'DeleteRow(tables.DeleteAction)'. In this, I wrote 'delete' function, in which I am calling quantum API to delete the row from DB. But, however, If I click DeleteRow button in horizon, 'delete()' function in the class is not triggering. And, as a result, row is not deleting from DB. I am not getting any kind of error logs in nova-api.log, apache error logs ..etc. Can anyone suggest, what went wrong? Thanks in advance. -- Srikanth. ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Srikanth. ___ 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] Cannot start nova-api service
Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error error: [Errno 98] Address already in use. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines are present in nova.conf. volume_api_class=nova.volume.cinder.API enabled_apis=ec2,osapi_compute,metadata Do I need to re-sync the db, or add any additional lines to nova.conf? No that is it. Are you sure a) you don't have another nova-api or nova-metadata or nova-api-os-compute process running? and b) that your nova.conf is being read properly? Vish As far as I can tell, no other nova-api, nova-metadata, nova-api-os-compute is running. If there another way to confirm besides running ps aux. And how can I tell if nova.conf is being read properly? root@bodega:~# ps aux | grep nova nova 914 0.0 0.0 37952 1312 ?Ss 16:01 0:00 su -s /bin/sh -c exec nova-novncproxy --config-file=/etc/nova/nova.conf nova nova 916 0.0 0.2 122976 24108 ?S16:01 0:01 /usr/bin/python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf nova 1235 0.0 0.0 37952 1312 ?Ss 16:01 0:00 su -s /bin/sh -c exec nova-cert --config-file=/etc/nova/nova.conf nova nova 1243 0.0 0.0 37952 1308 ?Ss 16:01 0:00 su -s /bin/sh -c exec nova-consoleauth --config-file=/etc/nova/nova.conf nova nova 1244 0.2 0.6 122996 51232 ?S16:01 1:12 /usr/bin/python /usr/bin/nova-cert --config-file=/etc/nova/nova.conf nova 1249 0.2 0.6 122992 51252 ?S16:01 1:13 /usr/bin/python /usr/bin/nova-consoleauth --config-file=/etc/nova/nova.conf nova 1252 0.0 0.0 37952 1312 ?Ss 16:01 0:00 su -s /bin/sh -c exec nova-network --config-file=/etc/nova/nova.conf nova nova 1255 0.0 0.0 37952 1308 ?Ss 16:01 0:00 su -s /bin/sh -c exec nova-scheduler --config-file=/etc/nova/nova.conf nova nova 1259 0.3 0.6 124964 53100 ?S16:01
Re: [Openstack] Cannot start nova-api service
By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- Ahmed Al-Mehdi ah...@coraid.com To Sent by: Vishvananda Ishaya openstack-bounces vishvana...@gmail.com, +gengjh=cn.ibm.co cc m@lists.launchpad openstack@lists.launchpad.net .net openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start 11/13/2012 09:32 nova-api service AM Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error error: [Errno 98] Address already in use. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. From: Ahmed Al-Mehdi ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines are present in nova.conf. volume_api_class=nova.volume.cinder.API enabled_apis=ec2,osapi_compute,metadata Do I need to re-sync the db, or add any additional lines to nova.conf? No
Re: [Openstack] Cannot start nova-api service
On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com *Ahmed Al-Mehdi ah...@coraid.com* Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.com, cc openstack@lists.launchpad.net openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start nova-api service Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error *error: [Errno 98] Address already in use*. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. *From: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Date: *Friday, November 9, 2012 12:45 AM* To: *Vishvananda Ishaya *vishvana...@gmail.com* vishvana...@gmail.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net * openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service *From: *Vishvananda Ishaya *vishvana...@gmail.com*vishvana...@gmail.com * Date: *Thursday, November 8, 2012 8:18 PM* To: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net *openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi *ah...@coraid.com*ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines are present in nova.conf. volume_api_class=nova.volume.cinder.API enabled_apis=ec2,osapi_compute,metadata Do I need to re-sync the db, or add any additional lines to nova.conf? No that is it. Are you sure a) you don't have another nova-api or nova-metadata or nova-api-os-compute process running? and b) that your nova.conf is being read properly? Vish As far as I can tell, no other nova-api, nova-metadata, nova-api-os-compute is running. If there another way to confirm besides running ps aux. And how can I tell if nova.conf is being read properly? root@bodega:~# ps aux | grep nova nova 914 0.0 0.0
Re: [Openstack] Cannot start nova-api service
From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [cid:1__=c7bbf026df9980448f9e8a93df...@cn.ibm.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com, cc openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start nova-api service Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error error: [Errno 98] Address already in use. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service From: Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com Date: Thursday, November 8, 2012 8:18 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines
[Openstack] [Swift] retrieve tenant-level, account-level and container-level usage information
Hello All, Is there any Swift (GUI or command line) tool that can retrieve the tenant-level, account-level and container-level usage information (e.g. how large space has been used under an account, how large space has been used under a tenant) and also works with keystone? Thanks, Ning ___ 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] Cannot start nova-api service
On Mon, Nov 12, 2012 at 7:34 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: From: John Griffith john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.com *Ahmed Al-Mehdi ah...@coraid.com* Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.com, cc openstack@lists.launchpad.net openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start nova-api service Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error *error: [Errno 98] Address already in use*. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. *From: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Date: *Friday, November 9, 2012 12:45 AM* To: *Vishvananda Ishaya *vishvana...@gmail.com* vishvana...@gmail.com * Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net * openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service *From: *Vishvananda Ishaya *vishvana...@gmail.com*vishvana...@gmail.com * Date: *Thursday, November 8, 2012 8:18 PM* To: *Ahmed Al-Mehdi *ah...@coraid.com* ah...@coraid.com* Cc: **openstack@lists.launchpad.net* openstack@lists.launchpad.net *openstack@lists.launchpad.net* openstack@lists.launchpad.net* Subject: *Re: [Openstack] Cannot start nova-api service On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi *ah...@coraid.com*ah...@coraid.com wrote: Vish, I am running cinder-api. The following two lines are present in nova.conf. volume_api_class=nova.volume.cinder.API enabled_apis=ec2,osapi_compute,metadata Do I need to re-sync the db, or add any additional lines to nova.conf?
Re: [Openstack] Cannot start nova-api service
From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:47 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 7:34 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: From: John Griffith john.griff...@solidfire.commailto:john.griff...@solidfire.com Date: Monday, November 12, 2012 7:17 PM To: Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com Cc: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:openstack-bounces+gengjh=cn.ibm@lists.launchpad.net, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot start nova-api service On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng gen...@cn.ibm.commailto:gen...@cn.ibm.com wrote: By default both cinder and nova-api are listening on the same port 8776 (this should be a bug I think), you can try to change the default value in the cinder.conf like: osapi_volume_listen_port = 8777 if you are running the cinder and nova-api on the same machine. -- Best regard, David Geng -- [cid:1__=c7bbf026df9980448f9e8a93df...@cn.ibm.com]Ahmed Al-Mehdi ---11/13/2012 09:32:21 AM---Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.netmailto:cn.ibm@lists.launchpad.net 11/13/2012 09:32 AM To Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com, cc openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject Re: [Openstack] Cannot start nova-api service Hello, Can someone please help me with a nova-api issue. After install all the nova services, all seem to be running fine, except for nova-api. I even reboot my controller node, no luck. After reboot all services are running, except nova-api. When I manually start nova-api, nova-api crashes with the following error error: [Errno 98] Address already in use. I installed nova-volume earlier during the install process, but later on installed cinder, and made the necessary modifications (as far as I can tell) to nova-api.conf to use cinder for block storage. Should I uninstall nova-volume? 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting keystone auth_token middleware 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using /var/lib/nova/keystone-signing as cache directory for signing certificate 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last): 2012-11-12 14:46:24 TRACE nova File /usr/bin/nova-api, line 50, in module 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 584, in __init__ 2012-11-12 14:46:24 TRACE nova port=self.port) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/nova/wsgi.py, line 72, in __init__ 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host, port), backlog=backlog) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/dist-packages/eventlet/convenience.py, line 38, in listen 2012-11-12 14:46:24 TRACE nova sock.bind(addr) 2012-11-12 14:46:24 TRACE nova File /usr/lib/python2.7/socket.py, line 224, in meth 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args) 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use 2012-11-12 14:46:24 TRACE nova 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died unexpectedly, exiting 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server. Would highly appreciate any pointers to understanding or resolving the issue. Regards, Ahmed. From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Friday, November 9, 2012 12:45 AM To:
[Openstack] [Swift] account-level and container-level usage information
Hello All, Is there any Swift (GUI or command line) tool that can retrieve the account-level and container-level usage information (e.g. how large space has been used under an account, how large space has been used under a tenant) and also works with keystone? Thanks, Ning ___ 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-level and container-level usage information
Hi， The python-swiftclient(https://github.com/openstack/python-swiftclient) can retrieve the account-level and container-level usage infomation. To retrieve the account usage information: $ swift -V 2 -A http://127.0.0.1:5000/v2.0 -U tenant1:swift_user -K 19561212 stat Account: AUTH_70b51a6d180f4f1da78d80316c69e85c Containers: 10 Objects: 0 Bytes: 0 Meta Quota: L1 Accept-Ranges: bytes X-Timestamp: 1352735608.55267 X-Trans-Id: tx72878dfcba9948298a6f4efb4e51e569 To retrieve the container usage information: $ swift -V 2 -A http://127.0.0.1:5000/v2.0 -U tenant1:swift_user -K 19561212 stat c1 No handlers could be found for logger keystoneclient.v2_0.client Account: AUTH_70b51a6d180f4f1da78d80316c69e85c Container: c1 Objects: 0 Bytes: 0 Read ACL: Write ACL: Sync To: Sync Key: Accept-Ranges: bytes X-Timestamp: 1352735637.83676 X-Trans-Id: tx7968942b927b4f1fba0c40fb1372adba You can also use the REST API, http://docs.openstack.org/cli/quick-start/content/swift_client_commands.html But the bytes and objects of account is not accurate. You can get the accurate result by retrieve all the containers and add them up. 2012/11/13 Ning Zhang n...@zmanda.com Hello All, Is there any Swift (GUI or command line) tool that can retrieve the account-level and container-level usage information (e.g. how large space has been used under an account, how large space has been used under a tenant) and also works with keystone? Thanks, Ning ___ 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
Re: [Openstack] [Cinder] Cinder snapshots
Chuck Thier cth...@gmail.com wrote on 12/11/2012 21:25:32: Top posting to give some general history and some thoughts. Snapshots, as implemented currently in cinder, are derived from the EBS definition of a snapshot. This is more of a consistent block level backup of a volume. New volumes can be created from any given snapshot. This is *not* usually what a snapshot is in a traditional storage system, though snapshots are usually used in the process. My concern with trying to expose more general snapshot, cloning, etc functionalities in the api is that they are very backend dependent, and will have different capabilities and properties. Trying to define a generic API for these cases that works across all backends is going to be problematic, which is why I've always been supportive of having these implemented as extensions specific to each backend. Hey Chuck, Thanks for your input. I agree with you that features that are specific to one/few back-ends should not be in the general API. Also, implementation details should be left to drivers (e.g., if snapshots are full copies, CoW, etc.). However, I think there are some snapshot features that all back-ends support that will give OpenStack users a better experience. One big one is read-only access to snapshots. I don't think a back-end exists that takes snapshots but doesn't allow reading from it. :) In terms of clones, I guess (John, correct me if I'm wrong) a clone gives you a new volume (with all its capabilities) which is a copy of the original. Back-ends that can do this operation efficiently can do so, while others can simply create a new volume and copy the data. I think that the important thing is to keep the API limited to features that are important and that all back-ends can implement, but not specify how they should be implemented. Thanks, Avishay ___ 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] Essex Dashboard: KeyError at /nova/instances_and_volumes/
This bug is reported at https://bugs.launchpad.net/horizon/+bug/1053488,
one potential way to fix it is proposed at
https://review.openstack.org/14801
2012/11/13 Gabriel Hurley gabriel.hur...@nebula.com
That is actually the manifestation of a bug in Nova that was addressed
very late in Folsom. The short version is that Nova inconsistently scoped
the ownership of volumes vs. instances so it was possible for an admin user
to view a mixed set of resources which could lead to the scenario you hit
where things are in one list but not the other. I’m not sure if there’s any
plans to backport the fixes from Nova. A patch could probably be worked up
for the stable/essex Horizon branch that would avoid the keyerror (see the
state of that code in Folsom:
https://github.com/openstack/horizon/blob/stable/folsom/horizon/dashboards/nova/volumes/views.py#L68),
but it would be papering over what is inherently a broken situation in
Nova.
** **
My advice from back in the Essex days was that you should be wary of using
an “admin” user in the “Project” dashboard since the underlying APIs didn’t
handle it correctly.
** **
Alternatively, the Folsom Horizon release is actually backwards-compatible
to an Essex stack, so you could try running Folsom Horizon which is less
subject to many issues.
** **
Hope one of these suggestions helps!
** **
**- **Gabriel
** **
*From:*
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
Behalf Of *Christian Parpart
*Sent:* Monday, November 12, 2012 3:37 AM
*To:* openstack@lists.launchpad.net
*Subject:* [Openstack] Essex Dashboard: KeyError at
/nova/instances_and_volumes/
** **
Hey all,
** **
since quite some weeks I am getting an error page instead of the
Instances and Volumes page in the
Essex Horizon Dashboard with the above title and the below detailed error
output:
** **
Environment: ** ** Request Method: GET Request URL:
http://controller.rz.dawanda.com/nova/instances_and_volumes/ ** ** Django
Version: 1.3.1 Python Version: 2.7.3 Installed Applications:
['openstack_dashboard', 'django.contrib.sessions',
'django.contrib.messages', 'django.contrib.staticfiles',
'django_nose', 'horizon', 'horizon.dashboards.nova',
'horizon.dashboards.syspanel', 'horizon.dashboards.settings']
Installed
Middleware: ('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'openstack_dashboard.middleware.DashboardLogUnhandledExceptionsMiddleware',
'horizon.middleware.HorizonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.locale.LocaleMiddleware') ** ** ** ** Traceback:**
** File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py
in get_response 111. response =
callback(request, *callback_args, **callback_kwargs) File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 40.
return view_func(request, *args, **kwargs) File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 55.
return view_func(request, *args, **kwargs) File
/usr/lib/python2.7/dist-packages/horizon/decorators.py in dec 40.
return view_func(request, *args, **kwargs) File
/usr/lib/python2.7/dist-packages/django/views/generic/base.py in view***
* 47. return self.dispatch(request, *args, **kwargs) File
/usr/lib/python2.7/dist-packages/django/views/generic/base.py in dispatch
68. return handler(request, *args, **kwargs) File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in get
105. handled = self.construct_tables() File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in
construct_tables 96. handled = self.handle_table(table)*
*** File /usr/lib/python2.7/dist-packages/horizon/tables/views.py in
handle_table 68. data = self._get_data_dict() File
/usr/lib/python2.7/dist-packages/horizon/tables/views.py in _get_data_dict
37. self._data[table._meta.name] = data_func() File
/usr/lib/python2.7/dist-packages/horizon/dashboards/nova/instances_and_volumes/views.py
in get_volumes_data 74. att['instance'] =
instances[att['server_id']] ** ** Exception Type: KeyError at
/nova/instances_and_volumes/ Exception Value:
u'8aa2989e-85ea-4975-b81b-04d06dbf8013'
** **
now I wonder in how far that is a bug in the software and/or whether I
Re: [Openstack-volume] Netapp: migrate Essex datasets to Folsom - missing metadata in DFM
On Fri, Nov 9, 2012 at 4:55 PM, Swartzlander, Ben ben.swartzlan...@netapp.com wrote: This sounds less like an Essex-Folsom upgrade issue and more like an old version-new version issue. We made some changes to the driver in the Folsom timeframe and backported those changes to Essex, but we never provided an upgrade path for users of the old driver to move to the new driver. True. You would have the same problem when upgrading from Essex-created datasets to any post-Essex release. This check is on Folsom branch and (Cinder) master. It is not present on Essex branch. https://github.com/openstack/nova/blob/stable/folsom/nova/volume/netapp.py#L254 What's needed is for a script to go through all the datasets and set the metadata field for the OpenStack project appropriately. I wrote a simple script to make few SOAP calls (attached) to update dataset meta-data. If there are few enough datasets, this could be done manually I suppose. I would be interested to know how can you do it with existing tools ?? Regards, Brano Zarnovican PS: Even if the driver worked after metadata fix, I still could not get snapshots. We are missing flex_clone licence :( -- Mailing list: https://launchpad.net/~openstack-volume Post to : openstack-volume@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-volume More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #30
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/30/Project:precise_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 08:31:21 -0500Build duration:1 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds tests to attribute.convert_to_intby zhongyue.naheditquantum/tests/unit/test_attributes.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b6e7be00-28a1-4201-98a1-70b2db72060a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b6e7be00-28a1-4201-98a1-70b2db72060a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpuUmpQv/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpuUmpQv/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211120831~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [6fbc89a] Removing unsed code for Cisco Quantum Plugin V1dch -a [12674de] Add QUANTUM_ prefix for env used by quantum-debugdch -a [aafba4d] Make tox.ini run pep8 checks on bin.dch -a [014e0b4] Explicitly include versioninfo in tarball.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-b6e7be00-28a1-4201-98a1-70b2db72060a', '-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-b6e7be00-28a1-4201-98a1-70b2db72060a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #31
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/31/Project:precise_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 12:01:21 -0500Build duration:1 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds tests for attributes.is_attr_setby zhongyue.naheditquantum/api/v2/attributes.pyeditquantum/tests/unit/test_attributes.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ce78edfe-4e99-455f-9360-fbbe47840486', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ce78edfe-4e99-455f-9360-fbbe47840486', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpdgejF4/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpdgejF4/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [6fbc89a] Removing unsed code for Cisco Quantum Plugin V1dch -a [12674de] Add QUANTUM_ prefix for env used by quantum-debugdch -a [aafba4d] Make tox.ini run pep8 checks on bin.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-ce78edfe-4e99-455f-9360-fbbe47840486', '-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-ce78edfe-4e99-455f-9360-fbbe47840486', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #32
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/32/Project:precise_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 13:01:22 -0500Build duration:1 min 40 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds test scripts for _validate_stringby zhongyue.naheditquantum/api/v2/attributes.pyeditquantum/tests/unit/test_attributes.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f3a1968c-53e8-490b-80c5-a1439256fbe4', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f3a1968c-53e8-490b-80c5-a1439256fbe4', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpIECxHY/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpIECxHY/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121301~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [6fbc89a] Removing unsed code for Cisco Quantum Plugin V1dch -a [12674de] Add QUANTUM_ prefix for env used by quantum-debugdebcommitbzr 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-f3a1968c-53e8-490b-80c5-a1439256fbe4', '-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-f3a1968c-53e8-490b-80c5-a1439256fbe4', '-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_quantum_trunk #30
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/30/Project:raring_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 13:01:21 -0500Build duration:6 min 48 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesAdds test scripts for _validate_stringby zhongyue.naheditquantum/tests/unit/test_attributes.pyeditquantum/api/v2/attributes.pyConsole Output[...truncated 6503 lines...]Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 52Job: quantum_2013.1+git201211121301~raring-0ubuntu1.dscMachine Architecture: amd64Package: quantumPackage-Time: 258Source-Version: 2013.1+git201211121301~raring-0ubuntu1Space: 43532Status: attemptedVersion: 2013.1+git201211121301~raring-0ubuntu1Finished at 20121112-1308Build needed 00:04:18, 43532k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121301~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121301~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/raring-grizzly-proposed /tmp/tmplV__0M/quantummk-build-deps -i -r -t apt-get -y /tmp/tmplV__0M/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/quantum/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121301~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.1+git201211121301~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A quantum_2013.1+git201211121301~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', 'quantum_2013.1+git201211121301~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', 'quantum_2013.1+git201211121301~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_quantum_trunk #31
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/31/Project:raring_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 13:31:22 -0500Build duration:8 min 20 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesAdds test scripts for _validate_rangeby zhongyue.naheditquantum/tests/unit/test_attributes.pyeditquantum/api/v2/attributes.pyConsole Output[...truncated 6504 lines...]Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 68Job: quantum_2013.1+git201211121331~raring-0ubuntu1.dscMachine Architecture: amd64Package: quantumPackage-Time: 300Source-Version: 2013.1+git201211121331~raring-0ubuntu1Space: 43528Status: attemptedVersion: 2013.1+git201211121331~raring-0ubuntu1Finished at 20121112-1339Build needed 00:05:00, 43528k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121331~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121331~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/raring-grizzly-proposed /tmp/tmpsonhKR/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpsonhKR/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/quantum/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121331~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.1+git201211121331~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A quantum_2013.1+git201211121331~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', 'quantum_2013.1+git201211121331~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', 'quantum_2013.1+git201211121331~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #72
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/72/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 13:31:24 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMove host aggregate operations to VirtAPIby danmseditnova/compute/manager.pyeditnova/virt/xenapi/host.pyeditnova/tests/test_xenapi.pyeditnova/virt/xenapi/vmops.pyeditnova/virt/virtapi.pyeditnova/virt/fake.pyeditnova/virt/xenapi/pool.pyeditnova/virt/xenapi/driver.pyeditnova/virt/xenapi/pool_states.pyMove security groups and firewall ops to VirtAPIby danmseditnova/virt/libvirt/firewall.pyeditnova/virt/xenapi/vmops.pyeditnova/virt/virtapi.pyeditnova/virt/firewall.pyeditnova/tests/test_libvirt.pyeditnova/virt/libvirt/driver.pyeditnova/virt/fake.pyeditnova/virt/xenapi/firewall.pyeditnova/compute/manager.pyAdd some xenapi Bittorrent testsby danmseditnova/tests/xenapi/test_vm_utils.pyMake instance_system_metadata load with instanceby danmseditnova/db/sqlalchemy/api.pyAvoid unnecessary system_metadata db lookupby danmseditnova/virt/xenapi/vm_utils.pyConsole Output[...truncated 31139 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211121232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211121232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211121232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121232~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121232~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 9fbc478b5bb8d140d4154e472f81b3e76fe01040INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmp9qx0vi/novamk-build-deps -i -r -t apt-get -y /tmp/tmp9qx0vi/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121332~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121332~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121332~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121332~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121332~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #74
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/74/Project:raring_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 13:31:25 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMove host aggregate operations to VirtAPIby danmseditnova/virt/xenapi/host.pyeditnova/virt/xenapi/pool_states.pyeditnova/virt/xenapi/pool.pyeditnova/virt/xenapi/driver.pyeditnova/compute/manager.pyeditnova/virt/xenapi/vmops.pyeditnova/tests/test_xenapi.pyeditnova/virt/fake.pyeditnova/virt/virtapi.pyMove security groups and firewall ops to VirtAPIby danmseditnova/compute/manager.pyeditnova/virt/libvirt/driver.pyeditnova/virt/xenapi/firewall.pyeditnova/virt/virtapi.pyeditnova/virt/libvirt/firewall.pyeditnova/virt/xenapi/vmops.pyeditnova/virt/fake.pyeditnova/virt/firewall.pyeditnova/tests/test_libvirt.pyAdd some xenapi Bittorrent testsby danmseditnova/tests/xenapi/test_vm_utils.pyMake instance_system_metadata load with instanceby danmseditnova/db/sqlalchemy/api.pyAvoid unnecessary system_metadata db lookupby danmseditnova/virt/xenapi/vm_utils.pyConsole Output[...truncated 32466 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211121232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211121232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211121232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121232~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 488.INFO:root:Storing current commit for next build: 9fbc478b5bb8d140d4154e472f81b3e76fe01040INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmplacaDw/novamk-build-deps -i -r -t apt-get -y /tmp/tmplacaDw/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121332~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121332~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211121332~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121332~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211121332~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #34
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/34/Project:precise_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 14:01:38 -0500Build duration:2 min 31 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds tests for attribute._validate_uuidby zhongyue.naheditquantum/tests/unit/test_attributes.pyeditquantum/api/v2/attributes.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-c7087bbd-67c6-4e6d-800e-69571ab55334', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-c7087bbd-67c6-4e6d-800e-69571ab55334', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmp500RkN/quantummk-build-deps -i -r -t apt-get -y /tmp/tmp500RkN/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121401~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ade8d96] Adds tests for attribute._validate_uuiddch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [09f70dc] Adds test scripts for _validate_rangedebcommitbzr 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-c7087bbd-67c6-4e6d-800e-69571ab55334', '-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-c7087bbd-67c6-4e6d-800e-69571ab55334', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #73
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/73/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 14:01:30 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesimprove session handling around quotasby devananda.vdveditnova/db/sqlalchemy/api.pyeditnova/tests/test_quota.pyimprove sessions for reservationby devananda.vdveditnova/db/sqlalchemy/api.pyimprove session handling around virtual_interfacesby devananda.vdveditnova/db/sqlalchemy/api.pyConsole Output[...truncated 31209 lines...]git log -n1 --no-merges --pretty=format:%Hgit log 9fbc478b5bb8d140d4154e472f81b3e76fe01040..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121402~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [f0cd357] Switch from FLAGS to CONF in testsdch -a [3e34867] Switch from FLAGS to CONF in nova.dbdch -a [3757ba9] Fixes a bug in api.metadata.base.lookup() on Windowsdch -a [f8e3ee7] improve session handling of dnsdomain_listdch -a [da1b387] Avoid unnecessary system_metadata db lookupdch -a [0ea8a37] Make instance_system_metadata load with instancedch -a [0e6f300] Add some xenapi Bittorrent testsdch -a [8322588] Move security groups and firewall ops to VirtAPIdch -a [a51d60f] Move host aggregate operations to VirtAPIdch -a [c63880c] Fix incorrect LOG.error usage in _compare_cpudch -a [b415d67] Removes unnecessary db query for instance typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121402~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121402~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121402~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121402~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #75
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/75/Project:raring_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 14:01:24 -0500Build duration:17 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesimprove session handling around quotasby devananda.vdveditnova/tests/test_quota.pyeditnova/db/sqlalchemy/api.pyimprove sessions for reservationby devananda.vdveditnova/db/sqlalchemy/api.pyimprove session handling around virtual_interfacesby devananda.vdveditnova/db/sqlalchemy/api.pyConsole Output[...truncated 32522 lines...]git log -n1 --no-merges --pretty=format:%Hgit log 9fbc478b5bb8d140d4154e472f81b3e76fe01040..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121402~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [f0cd357] Switch from FLAGS to CONF in testsdch -a [3e34867] Switch from FLAGS to CONF in nova.dbdch -a [3757ba9] Fixes a bug in api.metadata.base.lookup() on Windowsdch -a [f8e3ee7] improve session handling of dnsdomain_listdch -a [da1b387] Avoid unnecessary system_metadata db lookupdch -a [0ea8a37] Make instance_system_metadata load with instancedch -a [0e6f300] Add some xenapi Bittorrent testsdch -a [8322588] Move security groups and firewall ops to VirtAPIdch -a [a51d60f] Move host aggregate operations to VirtAPIdch -a [c63880c] Fix incorrect LOG.error usage in _compare_cpudch -a [b415d67] Removes unnecessary db query for instance typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121402~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211121402~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121402~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211121402~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_glance_trunk #9
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/9/Project:precise_grizzly_glance_trunkDate of build:Mon, 12 Nov 2012 14:31:22 -0500Build duration:1 min 56 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMake tox.ini run pep8 checks on bin.by dprinceedittox.iniConsole Output[...truncated 2233 lines...]Hunk #9 succeeded at 361 (offset 3 lines).Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9707e216-c6a1-4e2c-9495-6dd4885b7deb', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9707e216-c6a1-4e2c-9495-6dd4885b7deb', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmphnXYjb/glancemk-build-deps -i -r -t apt-get -y /tmp/tmphnXYjb/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121431~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [4039f3a] Make tox.ini run pep8 checks on bin.dch -a [859fd1c] Pep8 fixes to bin/glance* scripts.dch -a [b591304] Ensure authorization before deleting from storedch -a [231de61] Port uuidutils to Glancedch -a [6ab0992] Delete from store after registry delete.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9707e216-c6a1-4e2c-9495-6dd4885b7deb', '-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-9707e216-c6a1-4e2c-9495-6dd4885b7deb', '-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 #76
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/76/Project:raring_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 15:01:24 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMove agent_build_get_by_triple to VirtAPIby revieweditnova/virt/fake.pyeditnova/compute/manager.pyeditnova/virt/virtapi.pyeditnova/virt/xenapi/vmops.pyConsole Output[...truncated 32497 lines...]bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpGMv5sP/novamk-build-deps -i -r -t apt-get -y /tmp/tmpGMv5sP/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log d4a042962425b1f5e6c6a3a1560870dc0f56c8dc..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121502~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [e77136d] Move agent_build_get_by_triple to VirtAPIdch -a [9fbc478] Switch from FLAGS to CONF in nova.computedch -a [f0cd357] Switch from FLAGS to CONF in testsdch -a [3e34867] Switch from FLAGS to CONF in nova.dbdch -a [3757ba9] Fixes a bug in api.metadata.base.lookup() on Windowsdch -a [da1b387] Avoid unnecessary system_metadata db lookupdch -a [0ea8a37] Make instance_system_metadata load with instancedch -a [0e6f300] Add some xenapi Bittorrent testsdch -a [8322588] Move security groups and firewall ops to VirtAPIdch -a [a51d60f] Move host aggregate operations to VirtAPIdch -a [b415d67] Removes unnecessary db query for instance typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121502~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211121502~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121502~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211121502~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_swift_trunk #20
Title: precise_grizzly_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/20/Project:precise_grizzly_swift_trunkDate of build:Mon, 12 Nov 2012 15:31:22 -0500Build duration:4 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesfix bug1039861, remove license header in doc/source/conf.py.by mail.zhang.yeeeditdoc/source/conf.pyConsole Output[...truncated 2834 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 105Source-Version: 1.7.6+git201211121531~precise-0ubuntu1Space: 17660Status: attemptedVersion: 1.7.6+git201211121531~precise-0ubuntu1Finished at 20121112-1535Build needed 00:01:45, 17660k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211121531~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211121531~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-grizzly-proposed /tmp/tmpnWEkLo/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpnWEkLo/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-grizzly --forcedch -b -D precise --newversion 1.7.6+git201211121531~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [53ab2e1] fix bug1039861, remove license header in doc/source/conf.py.dch -a [8a8ea8f] fix error with setting max age and incorrect testsdch -a [24f9fe9] Make swift-bench use less memory with large object sizes.dch -a [34ca0f0] give swob default content-typedch -a [237a440] Make DELETE requests to expired objects return 404.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211121531~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A swift_1.7.6+git201211121531~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211121531~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'swift_1.7.6+git201211121531~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #75
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/75/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 15:33:56 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRename config to vconfigby yunmaoeditnova/virt/libvirt/driver.pyFix misuse of exists()by yunmaoeditnova/volume/driver.pyAdd missing exception NetworkDuplicatedby yunmaoeditnova/exception.pyConsole Output[...truncated 31190 lines...]DEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 8e3876c5a36402068d4e30a3dd0f07f3968cb678INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpqWhpsE/novamk-build-deps -i -r -t apt-get -y /tmp/tmpqWhpsE/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e77136dcd1c6d91e0f819b0c294470c6d516f893..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121534~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [8e3876c] Add missing exception NetworkDuplicateddch -a [c4b1a64] Fix misuse of exists()dch -a [5d4cd7e] Rename config to vconfigdch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121534~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121534~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121534~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121534~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #76
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/76/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 16:01:28 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix getattr usageby yunmaoeditnova/virt/vmwareapi/vim.pyAdd missing webob to excby yunmaoeditnova/api/openstack/compute/contrib/deferred_delete.pyConsole Output[...truncated 31205 lines...]INFO:root:Storing current commit for next build: d6d0a67c5cbbee6cabd90ed563b9b9c35d724a94INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpwF_Q1d/novamk-build-deps -i -r -t apt-get -y /tmp/tmpwF_Q1d/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 8e3876c5a36402068d4e30a3dd0f07f3968cb678..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121602~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [d6d0a67] Add missing webob to excdch -a [c4b1a64] Fix misuse of exists()dch -a [5d4cd7e] Rename config to vconfigdch -a [e77136d] Move agent_build_get_by_triple to VirtAPIdch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [9ff6819] Fix getattr usagedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121602~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121602~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121602~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121602~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #78
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/78/Project:raring_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 16:01:22 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix getattr usageby yunmaoeditnova/virt/vmwareapi/vim.pyAdd missing webob to excby yunmaoeditnova/api/openstack/compute/contrib/deferred_delete.pyConsole Output[...truncated 32533 lines...]INFO:root:Storing current commit for next build: d6d0a67c5cbbee6cabd90ed563b9b9c35d724a94INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpD6xx85/novamk-build-deps -i -r -t apt-get -y /tmp/tmpD6xx85/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 8e3876c5a36402068d4e30a3dd0f07f3968cb678..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121602~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [d6d0a67] Add missing webob to excdch -a [c4b1a64] Fix misuse of exists()dch -a [5d4cd7e] Rename config to vconfigdch -a [e77136d] Move agent_build_get_by_triple to VirtAPIdch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [9ff6819] Fix getattr usagedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121602~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211121602~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121602~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211121602~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_glance_trunk #11
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/11/Project:precise_grizzly_glance_trunkDate of build:Mon, 12 Nov 2012 16:31:21 -0500Build duration:2 min 4 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesPrevent infinite respawn of child processesby bcwaldoneditglance/common/wsgi.pyeditglance/tests/functional/test_bin_glance_control.pyConsole Output[...truncated 2233 lines...]Hunk #9 succeeded at 361 (offset 3 lines).Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-68e12f4c-be09-4e41-ae9d-d4ca7a91504f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-68e12f4c-be09-4e41-ae9d-d4ca7a91504f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmpHScOoU/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpHScOoU/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121631~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [9669067] Prevent infinite respawn of child processesdch -a [6e99270] Make run_tests.sh run pep8 checks on bin.dch -a [4039f3a] Make tox.ini run pep8 checks on bin.dch -a [859fd1c] Pep8 fixes to bin/glance* scripts.dch -a [b591304] Ensure authorization before deleting from storedebcommitbzr 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-68e12f4c-be09-4e41-ae9d-d4ca7a91504f', '-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-68e12f4c-be09-4e41-ae9d-d4ca7a91504f', '-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_quantum_trunk #33
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/33/Project:raring_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 16:31:22 -0500Build duration:8 min 24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesTreat case when pid is Noneby gkottoneditquantum/agent/linux/dhcp.pyeditquantum/tests/unit/test_linux_dhcp.pyConsole Output[...truncated 6520 lines...]Machine Architecture: amd64Package: quantumPackage-Time: 330Source-Version: 2013.1+git201211121631~raring-0ubuntu1Space: 43532Status: attemptedVersion: 2013.1+git201211121631~raring-0ubuntu1Finished at 20121112-1639Build needed 00:05:30, 43532k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121631~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211121631~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/raring-grizzly-proposed /tmp/tmpSrtL1P/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpSrtL1P/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 2299cddcbd5a8fc2d3e44f816fb60a8aaff3b853..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121631~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [ade8d96] Adds tests for attribute._validate_uuiddch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [09f70dc] Adds test scripts for _validate_rangedch -a [b1c35c2] Treat case when pid is Nonedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.1+git201211121631~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A quantum_2013.1+git201211121631~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', 'quantum_2013.1+git201211121631~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', 'quantum_2013.1+git201211121631~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #35
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/35/Project:precise_grizzly_quantum_trunkDate of build:Mon, 12 Nov 2012 16:39:47 -0500Build duration:2 min 14 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesTreat case when pid is Noneby gkottoneditquantum/agent/linux/dhcp.pyeditquantum/tests/unit/test_linux_dhcp.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-d59ebc48-c1d8-41c4-bd5b-7d8f004d17e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-d59ebc48-c1d8-41c4-bd5b-7d8f004d17e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpCYhhiY/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpCYhhiY/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121639~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ade8d96] Adds tests for attribute._validate_uuiddch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [09f70dc] Adds test scripts for _validate_rangedebcommitbzr 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-d59ebc48-c1d8-41c4-bd5b-7d8f004d17e9', '-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-d59ebc48-c1d8-41c4-bd5b-7d8f004d17e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #77
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/77/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 16:31:23 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesBan db import from nova/virtby danmsedittools/hacking.pyeditnova/virt/xenapi/driver.pyeditnova/virt/hyperv/vmops.pyeditHACKING.rsteditnova/virt/xenapi/pool.pyeditnova/virt/virtapi.pyeditnova/virt/xenapi/host.pyConsole Output[...truncated 31232 lines...]INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpMnSZHw/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMnSZHw/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log d6d0a67c5cbbee6cabd90ed563b9b9c35d724a94..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121633~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [9471282] Ban db import from nova/virtdch -a [8e3876c] Add missing exception NetworkDuplicateddch -a [c4b1a64] Fix misuse of exists()dch -a [5d4cd7e] Rename config to vconfigdch -a [e77136d] Move agent_build_get_by_triple to VirtAPIdch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [9ff6819] Fix getattr usagedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121633~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121633~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121633~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121633~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_nova_trunk #79
Title: raring_grizzly_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/79/Project:raring_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 16:33:26 -0500Build duration:18 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesBan db import from nova/virtby danmsedittools/hacking.pyeditnova/virt/hyperv/vmops.pyeditHACKING.rsteditnova/virt/xenapi/driver.pyeditnova/virt/virtapi.pyeditnova/virt/xenapi/pool.pyeditnova/virt/xenapi/host.pyConsole Output[...truncated 32500 lines...]deleting and forgetting pool/main/n/nova/nova-compute-xen_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-novncproxy_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121602~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121602~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 488.INFO:root:Storing current commit for next build: 9471282626e004296351a4a97fb51209a53e7f42INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpApxpPC/novamk-build-deps -i -r -t apt-get -y /tmp/tmpApxpPC/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log d6d0a67c5cbbee6cabd90ed563b9b9c35d724a94..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211121635~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [9471282] Ban db import from nova/virtdch -a [8e3876c] Add missing exception NetworkDuplicateddch -a [c4b1a64] Fix misuse of exists()dch -a [5d4cd7e] Rename config to vconfigdch -a [e77136d] Move agent_build_get_by_triple to VirtAPIdch -a [d4a0429] improve session handling around virtual_interfacesdch -a [a2acdde] improve sessions for reservationdch -a [2fac760] improve session handling around quotasdch -a [9ff6819] Fix getattr usagedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121635~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211121635~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121635~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211121635~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 Still Failing: precise_grizzly_glance_trunk #12
Title: precise_grizzly_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/12/Project:precise_grizzly_glance_trunkDate of build:Mon, 12 Nov 2012 17:01:24 -0500Build duration:2 min 4 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate uuidutils from openstack commonby alex.meadeeditglance/openstack/common/uuidutils.pyConsole Output[...truncated 2233 lines...]Hunk #9 succeeded at 361 (offset 3 lines).Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9a901a90-84d9-42d5-ad8b-fe2768c6bc42', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9a901a90-84d9-42d5-ad8b-fe2768c6bc42', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmpXIikoP/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpXIikoP/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121701~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [4ce79ab] Update uuidutils from openstack commondch -a [9669067] Prevent infinite respawn of child processesdch -a [6e99270] Make run_tests.sh run pep8 checks on bin.dch -a [4039f3a] Make tox.ini run pep8 checks on bin.dch -a [859fd1c] Pep8 fixes to bin/glance* scripts.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-9a901a90-84d9-42d5-ad8b-fe2768c6bc42', '-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-9a901a90-84d9-42d5-ad8b-fe2768c6bc42', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #78
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/78/Project:precise_grizzly_nova_trunkDate of build:Mon, 12 Nov 2012 17:01:23 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix a bug in XenAPISessions use of virtapiby danmseditnova/virt/xenapi/driver.pyeditnova/tests/test_xenapi.pyConsole Output[...truncated 31205 lines...]deleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121633~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121633~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 6615b32983ad6c708b795c5ded4cd974a814d327INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpCzbGYz/novamk-build-deps -i -r -t apt-get -y /tmp/tmpCzbGYz/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 9471282626e004296351a4a97fb51209a53e7f42..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211121702~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [6615b32] Fix a bug in XenAPISession's use of virtapidch -a [d6d0a67] Add missing webob to excdch -a [9ff6819] Fix getattr usagedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211121702~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211121702~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121702~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121702~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'raring_grizzly_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #80
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/80/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 00:31:24 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMove libvirt specific cgroups setup code out of nova.virt.disk.apiby berrangeeditnova/virt/libvirt/driver.pyeditnova/virt/disk/api.pyUse base image for rescue instance.by rconradharriseditnova/compute/manager.pyeditnova/virt/xenapi/vmops.pyConsole Output[...truncated 31219 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211130002~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211130002~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211130002~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211130002~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211130002~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 426315ff0396bc87b05da77021f7368a38ee085bINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmp_tVY57/novamk-build-deps -i -r -t apt-get -y /tmp/tmp_tVY57/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211130032~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211130032~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211130032~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211130032~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211130032~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'raring_grizzly_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #81
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/81/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 01:01:24 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesmake libvirt with Xen more workableby berendteditnova/virt/libvirt/driver.pyeditnova/virt/libvirt/vif.pyMake xenapi shutdown mode explicitby andrew.laskieditnova/virt/xenapi/vm_utils.pyeditnova/virt/xenapi/vmops.pyConsole Output[...truncated 31207 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211130032~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211130032~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211130032~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211130032~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211130032~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: 426315ff0396bc87b05da77021f7368a38ee085bINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpRcIXLk/novamk-build-deps -i -r -t apt-get -y /tmp/tmpRcIXLk/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211130102~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211130102~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211130102~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211130102~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211130102~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'raring_grizzly_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #36
Title: precise_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/36/Project:precise_grizzly_quantum_trunkDate of build:Tue, 13 Nov 2012 02:01:21 -0500Build duration:1 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesValidate L3 inputs.by gkottoneditquantum/extensions/l3.pyConsole Output[...truncated 2505 lines...]patching file etc/quantum.confHunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniPatch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bc43f276-3f41-494b-98dc-766004801d4d', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bc43f276-3f41-494b-98dc-766004801d4d', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmp8m5EdF/quantummk-build-deps -i -r -t apt-get -y /tmp/tmp8m5EdF/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211130201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [ade8d96] Adds tests for attribute._validate_uuiddch -a [2299cdd] Adds tests to attribute.convert_to_intdch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [09f70dc] Adds test scripts for _validate_rangedebcommitbzr 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-bc43f276-3f41-494b-98dc-766004801d4d', '-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-bc43f276-3f41-494b-98dc-766004801d4d', '-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_quantum_trunk #35
Title: raring_grizzly_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/35/Project:raring_grizzly_quantum_trunkDate of build:Tue, 13 Nov 2012 02:01:22 -0500Build duration:7 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesValidate L3 inputs.by gkottoneditquantum/extensions/l3.pyConsole Output[...truncated 6523 lines...]Package: quantumPackage-Time: 290Source-Version: 2013.1+git201211130201~raring-0ubuntu1Space: 43528Status: attemptedVersion: 2013.1+git201211130201~raring-0ubuntu1Finished at 20121113-0209Build needed 00:04:50, 43528k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211130201~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211130201~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/raring-grizzly-proposed /tmp/tmpirvXUc/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpirvXUc/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 2299cddcbd5a8fc2d3e44f816fb60a8aaff3b853..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211130201~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [ade8d96] Adds tests for attribute._validate_uuiddch -a [4df4f7e] Adds tests for attributes.is_attr_setdch -a [372314c] Adds test scripts for _validate_stringdch -a [09f70dc] Adds test scripts for _validate_rangedch -a [2b23c6c] Validate L3 inputs.dch -a [b1c35c2] Treat case when pid is Nonedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.1+git201211130201~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A quantum_2013.1+git201211130201~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', 'quantum_2013.1+git201211130201~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', 'quantum_2013.1+git201211130201~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
