Re: [Openstack] Cinder problems with usage and caching ?
Hey Ollie, yeah thx, I've found yesterday an existing bug report. https://bugs.launchpad.net/cinder/+bug/1174193 Thx and greetings Heiko On 12.06.2013 17:05, Ollie Leahy wrote: This looks like a bug, so you could raise a bug on cinder at https://bugs.launchpad.net/cinder/+filebug When you do you could include information about the version of cinder you are using, is it grizzy, folsom or are you testing on head? Also, if you can include any context information for example had that project id had used more quota in the past and deleted it? It would also be useful to search through any cinder logs for other error warnings, in case there was a failure in the past, when quota was either consumed or recovered by this project and where the operation was not completed successfully. Ollie On 12/06/13 10:02, Heiko Krämer wrote: Hi guys, I'm running in a problem raised by cinder api. I'll show you the log output it's more then my explaination :) 2013-06-12 10:50:13AUDIT [cinder.api.v1.volumes] Create volume of 30 GB 2013-06-12 10:50:13 WARNING [cinder.volume.api] Quota exceeded for d4e1c14691d841f6b53a24b6c4c42a0e, tried to create 30G volume (172G of 200G already consumed) 2013-06-12 10:50:13ERROR [cinder.api.middleware.fault] Caught error: Requested volume or snapshot exceeds allowed Gigabytes quota root@api2:~# cinder list +--++-+--+-+--+--+ | ID | Status | Display Name| Size | Volume Type | Bootable | Attached to | +--++-+--+-+--+--+ | 6ce6f626-2d2b-4a17-8933-13e196fa650c | in-use | bosh| 10 | default | false | 567a4c86-08ab-43cd-b9bc-3b220f2bf262 | | 8822b84b-595e-4b6f-9636-472dae7c33a4 | in-use | volume-64e51c64-5da4-4981-9b05-f7abfc6695b1 | 16 | None| false | 65f33296-c2b0-4824-b887-359ee0462b56 | | d56e5a86-f6d1-43ed-b125-2ff977aefa24 | in-use | volume-363573c1-05d6-4484-9aad-0919e47546e0 | 5 | None| false | fbb809d5-71f3-4a78-9cb7-4913c1e0af83 | | f7506174-4ae4-4a3c-928f-47b785bb35f5 | in-use | volume-385997c8-709c-4fa2-9d5b-ca2bba9d4e87 | 7 | None| false | 0f1ab672-043a-4361-afd5-9f2ddd818ed8 | +--++-+--+-+--+--+ root@api2:~# cinder quota-show d4e1c14691d841f6b53a24b6c4c42a0e +---+---+ | Property | Value | +---+---+ | gigabytes | 200 | | snapshots | 20 | | volumes | 30 | +---+---+ you see I consume only 38GB of 200GB and not 172GB (log). It's anything wrong with caching by cinder ? Have anyone the same problem or any hints ? Greetings Heiko ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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 problems with usage and caching ?
Thanks for taking the trouble to do that Heiko, as you can see that's been open a while and we're having trouble reproducing the problem, any information you can supply about your situation would be welcome. eg, errors in log files or the contents of your database as Duncan suggested in that bug. Ollie On Thu 13 Jun 2013 09:55:53 IST, Heiko Krämer wrote: Hey Ollie, yeah thx, I've found yesterday an existing bug report. https://bugs.launchpad.net/cinder/+bug/1174193 Thx and greetings Heiko On 12.06.2013 17:05, Ollie Leahy wrote: This looks like a bug, so you could raise a bug on cinder at https://bugs.launchpad.net/cinder/+filebug When you do you could include information about the version of cinder you are using, is it grizzy, folsom or are you testing on head? Also, if you can include any context information for example had that project id had used more quota in the past and deleted it? It would also be useful to search through any cinder logs for other error warnings, in case there was a failure in the past, when quota was either consumed or recovered by this project and where the operation was not completed successfully. Ollie On 12/06/13 10:02, Heiko Krämer wrote: Hi guys, I'm running in a problem raised by cinder api. I'll show you the log output it's more then my explaination :) 2013-06-12 10:50:13AUDIT [cinder.api.v1.volumes] Create volume of 30 GB 2013-06-12 10:50:13 WARNING [cinder.volume.api] Quota exceeded for d4e1c14691d841f6b53a24b6c4c42a0e, tried to create 30G volume (172G of 200G already consumed) 2013-06-12 10:50:13ERROR [cinder.api.middleware.fault] Caught error: Requested volume or snapshot exceeds allowed Gigabytes quota root@api2:~# cinder list +--++-+--+-+--+--+ | ID | Status | Display Name| Size | Volume Type | Bootable | Attached to | +--++-+--+-+--+--+ | 6ce6f626-2d2b-4a17-8933-13e196fa650c | in-use | bosh| 10 | default | false | 567a4c86-08ab-43cd-b9bc-3b220f2bf262 | | 8822b84b-595e-4b6f-9636-472dae7c33a4 | in-use | volume-64e51c64-5da4-4981-9b05-f7abfc6695b1 | 16 | None| false | 65f33296-c2b0-4824-b887-359ee0462b56 | | d56e5a86-f6d1-43ed-b125-2ff977aefa24 | in-use | volume-363573c1-05d6-4484-9aad-0919e47546e0 | 5 | None| false | fbb809d5-71f3-4a78-9cb7-4913c1e0af83 | | f7506174-4ae4-4a3c-928f-47b785bb35f5 | in-use | volume-385997c8-709c-4fa2-9d5b-ca2bba9d4e87 | 7 | None| false | 0f1ab672-043a-4361-afd5-9f2ddd818ed8 | +--++-+--+-+--+--+ root@api2:~# cinder quota-show d4e1c14691d841f6b53a24b6c4c42a0e +---+---+ | Property | Value | +---+---+ | gigabytes | 200 | | snapshots | 20 | | volumes | 30 | +---+---+ you see I consume only 38GB of 200GB and not 172GB (log). It's anything wrong with caching by cinder ? Have anyone the same problem or any hints ? Greetings Heiko ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Connecting to Keystone from a different port using HAproxy
Hi All, I am attempting to set up a high availability openstack cluster. Currently, using pacemaker, I create a Virtual IP for all the highly available service, launch haproxy to proxy all the requests and clone keystone to all the nodes. The idea being that the requests come into haproxy and are load balanced across all the nodes. To do this I have keystone listen on 26000 for admin, and 26001 for public. haproxy listens on 35357 and 5000 respectively (these ports are bound to the VIP). The problem with setup is that my log is filling (MB/min) with this warning: 2013-06-13 09:20:18 INFO [access] 127.0.0.1 - - [13/Jun/2013:13:20:18 +] GET http://10.80.255.1:35357/v2.0/users HTTP/1.0 200 915 2013-06-13 09:20:18 WARNING [keystone.contrib.stats.core] Unable to resolve API as either public or admin: 10.80.255.1:35357 ... ... where 10.80.255.1 is my VIP for highly available services. I traced down that module and added a few lines of code for debugging and it turns out that if checks to see if the incoming connection matches a port in the config file. In my case it does not. I can not just bind keystone to the internal ip and leave the port as their defaults because the way pacemaker checks to see if services are alive is by sending requests to service it is monitoring, and I do not want to send requests to the VIP because any instance of keystone could respond. Basically I would I have to write a pacemaker rule for each node and it would become messy quite quickly. Does anyone see something I could do differently, or a fix for my current situation? Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Connecting to Keystone from a different port using HAproxy
I may have found a solution to my problem, but I am not sure it will help you much. I created an entry in hosts that named my internal ip local-internal and then I bound keystone to that ip. Next I configured the pacemaker resource agent to check local-internal which will, of course, be different on each node. It seems to work quite well. Sorry that this probably doesn't help you, Sam On Thu, Jun 13, 2013 at 10:19 AM, Aaron Knister aaron.knis...@gmail.comwrote: Hi Sam I don't have a fix but I actually had the same problem but for a different reason. I was trying to run keystone via apache and listen on multiple ports to support regular auth and external auth. I couldn't figure out how to map additional ports within keytstone. I'm very much interested in the solution here. Sent from my iPhone On Jun 13, 2013, at 9:27 AM, Samuel Winchenbach swinc...@gmail.com wrote: Hi All, I am attempting to set up a high availability openstack cluster. Currently, using pacemaker, I create a Virtual IP for all the highly available service, launch haproxy to proxy all the requests and clone keystone to all the nodes. The idea being that the requests come into haproxy and are load balanced across all the nodes. To do this I have keystone listen on 26000 for admin, and 26001 for public. haproxy listens on 35357 and 5000 respectively (these ports are bound to the VIP). The problem with setup is that my log is filling (MB/min) with this warning: 2013-06-13 09:20:18 INFO [access] 127.0.0.1 - - [13/Jun/2013:13:20:18 +] GET http://10.80.255.1:35357/v2.0/users HTTP/1.0 200 915 2013-06-13 09:20:18 WARNING [keystone.contrib.stats.core] Unable to resolve API as either public or admin: 10.80.255.1:35357 ... ... where 10.80.255.1 is my VIP for highly available services. I traced down that module and added a few lines of code for debugging and it turns out that if checks to see if the incoming connection matches a port in the config file. In my case it does not. I can not just bind keystone to the internal ip and leave the port as their defaults because the way pacemaker checks to see if services are alive is by sending requests to service it is monitoring, and I do not want to send requests to the VIP because any instance of keystone could respond. Basically I would I have to write a pacemaker rule for each node and it would become messy quite quickly. Does anyone see something I could do differently, or a fix for my current situation? Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Leftover /tmp/openstack-disk-mount-tmp files and Windows 7 instances
Hi, I'm having an issue in OpenStack Essex on Ubuntu 12.04 using nova-compute version 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1.4 where there are many nbd disk mounts left over from booting Windows 7 virtual machines. Also, (I think) once the instance is deleted the nbd process holds onto the deleted file. Has anyone seen this before? I've done quite a bit of googling but haven't found anyone with similar issues. I thought I'd ask the list before I really dived into the code. $ mount | grep openstack /dev/mapper/nbd15p1 on /tmp/openstack-disk-mount-tmp86qoQE type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd14p1 on /tmp/openstack-disk-mount-tmpUzs31L type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd13p1 on /tmp/openstack-disk-mount-tmpGywuh7 type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd12p1 on /tmp/openstack-disk-mount-tmpCqaql2 type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd10p1 on /tmp/openstack-disk-mount-tmppdq4Mq type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd9p1 on /tmp/openstack-disk-mount-tmp7hIhDU type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) /dev/mapper/nbd8p1 on /tmp/openstack-disk-mount-tmp0AAVq7 type fuseblk SNIP! Right now on six compute nodes I have 74 of these lost mounts. Any thoughts on that? ): Thanks, Curtis. -- Twitter: @serverascode Blog: serverascode.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [OSSA 2013-015] Authentication bypass when using LDAP backend (CVE-2013-2157)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenStack Security Advisory: 2013-015 CVE: CVE-2013-2157 Date: June 13, 2013 Title: Authentication bypass when using LDAP backend Reporter: Jose Castro Leon (CERN) Products: Keystone Affects: Folsom, Grizzly Description: Jose Castro Leon from CERN reported a vulnerability in the way the Keystone LDAP backend authenticates users. When provided with an empty password, the backend would perform an anonymous LDAP bind that would result in successfully authenticating the user. An attacker could therefore easily impersonate and get valid tokens for any user. Only Keystone setups using LDAP authentication backend are affected. Havana (development branch) fix: https://review.openstack.org/#/c/32896/ Grizzly fix: https://review.openstack.org/#/c/32895/ Folsom fix: https://review.openstack.org/#/c/32894/ References: https://bugs.launchpad.net/keystone/+bug/1187305 http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2157 - -- Thierry Carrez (ttx) OpenStack Vulnerability Management Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRue20AAoJEFB6+JAlsQQjiHQP/1Jd8p9Zezo70Vdm4oZksDzH IPuFfeCRUhLvDC1ygz33/7CbRkFtmJS8C+PG+WxiG/49bsCBfIN5fHlOf3DY2X1U 9zgodo3Tm/LwKCrpdceu4VCABt7CtO/CsHnuQGWBOf06MLDTqDvz3LQKpcPXO50l 1OHiOWEX9nbCkNKRCPfK4QfrzbJM5GufEeoEEfKk8ZctivvI2M56OcSiGMdOhGK8 Xw+0bGzBBZzBMhiMq2iw7y0JqWtRLTND/AAP1eyjbHL/xDG/rTtECGaGuONXjpSk WQRpWMznJY83fBnxnVAvKvf6OxG8IW8YNicvTgfx5v9gvX0U00r59y24ClnmvBxb oRWES8bRLHmjf8vTtfZwcATEfUUFZZK+9VUsaIRsRF6+gF/fbQq39SdVESQACvks Sf9/f/Tu6u+58Je2JaTmx3LLV6u12ellP/GUr31OyihKAxFGK4Y1tdrO3v4+u2ZF lSC361D5r5cczTosmXy5HjXwfjATaGuMb1ycDKCmO+98gsluQ1exDFnIXCw38weN KWJIp5zVCdTF0rqZCr3xDBSe4aukX8niBJNnvgJwELAddIWZ6FHUuEsgl3UPs7ZD E+issrQHaGtOJpNvoj17uxxnTY2VrtJ2AjxiU7y+hmt9tHh78rx+OhAdn7zPdoeT EEJ4OWpjLDKre9HsJVxX =kubz -END PGP SIGNATURE- ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [OSSA 2013-016] Unchecked user input in Swift XML responses (CVE-2013-2161)
OpenStack Security Advisory: 2013-016 CVE: CVE-2013-2161 Date: June 13, 2013 Title: Unchecked user input in Swift XML responses Reporter: Alex Gaynor (Rackspace) Products: Swift Affects: All versions Description: Alex Gaynor from Rackspace reported a vulnerability in XML handling within Swift account servers. Account strings were unescaped in XML listings, and an attacker could potentially generate unparsable or arbitrary XML responses which may be used to leverage other vulnerabilities in the calling software. Havana (development branch) fix: https://review.openstack.org/32905 Grizzly fix: https://review.openstack.org/32909 Folsom fix: https://review.openstack.org/32911 Notes: This fix will be included in the next release. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2161 https://bugs.launchpad.net/swift/+bug/1183884 -- Jeremy Stanley (fungi) OpenStack Vulnerability Management Team signature.asc Description: Digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Ceilometer- All meters are not getting updated
Hi Everyone, When I am running ceilometer, only some of the meters are getting updated.(When I see ceilometer meter-list , I could see only cpu_util, image, instance). What can be the reason that the other meters are not getting updated.?. Thanks, Johnu ___ 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 troubleshooting
Hello all! Have installation of Grizzly and during log in to Horizon get Something went wrong! page after sent credentials. Apache log helpless. In other logs (system + other nova services) everything alright. So how I can determine what wrong with installation? I found that I can turn on verbose logging for django Horizon app, but how? -- Igor Laskovy facebook.com/igor.laskovy studiogrizzly.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack API versions and release content
On Tue, Jun 11, 2013 at 4:46 PM, Farhan Patwa farhan.pa...@utsa.edu wrote: Hi all, I am just trying to understand the motivation behind creations API versions and how that ties in to a release content. As per listed documentation ( http://docs.openstack.org/api/openstack-compute/2/content/Versions-d1e1193.html ) New Features and functionality that break API-compatibility necessitate a new version. When new API version are released older versions are marked as deprecated. My questions are: 1.) Is the assumption here that operators may update the release but opt to stay with an older API version to get bug fixes etc.? See #2 below. 2.) Do new versions have to be deployed with a new release? Keystone has V3 version, but I don't see it being available for use in devstack or Grizzly release (based on my assumption that the command 'keystone discover' will display supported API versions) Not necessarily. Keystone grizzly/2013.1 ships with a revised paste configuration which deploys the new Identity API v3 via pipeline:api_v3 [1]. You don't need to deploy this new pipeline at all, and a folsom paste configuration will deploy an Identity API v2 implementation just as it did in folsom. The output of keystone discover operates based on how the service catalog is populated, which doesn't necessarily reflect the configured pipeline or what's provided by the implementation. [1]: https://github.com/openstack/keystone/blob/64738924b87e6fb31d999e25da23f889a2658940/etc/keystone-paste.ini#L78 3.) Do versions have their own release schedule (so Keystone V3 is part of Grizzly code but the implementation is not yet complete or supported??) There's no such thing as Keystone v3, although that's a common misnomer. The Identity API (v2.0 - v3.0 - v3.1) is versioned independently from it's implementation, Keystone (... essex/2012.1 - folsom/2012.2 - grizzly/2013.1 - etc). Several releases of keystone could be made without incrementing the API version. A release of keystone may contain an experimental/unstable/partial and unrecommended/undocumented implementation of a newer API. A release of keystone may even skip an API version if there was reason to do so. So, for example: - diablo supports Identity API v2.0 and was extensible to support a non-OpenStack Identity API (v1.1) - essex supports Identity API v2.0 - folsom supports Identity API v2.0 - grizzly supports Identity API v2.0 and Identity API v3.0 - havana will support Identity API v2.0 and Identity API v3.1 - icehouse will support Identity API v2.0 and at least Identity API v3.1 (if not v3.2) - J*release is not guaranteed to support Identity API v2.0 and will support at least Identity API v3.1 (if not v3.3) (where minor version bumps, e.g. v3.0 - v3.1 are backwards compatible) In reality, if we ship a recommended API implementation, that API version is effectively feature frozen. So, while we could have continued to develop Identity API v3.0 past 2013.1, we documented it in the default configuration (keystone.conf.sample, devstack, etc) and shipped it with grizzly and are now working towards introducing backwards-compatible features under a minor version bump to the API that will ship with havana. I would really appreciate if someone can shed light on this. Thanks for your time, -Farhan Patwa. ___ 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] Can I run qemu-kvm in an OpenStack Instance
Hi all, I want to use veewee to create custom images for use in OpenStack. The catch here is that I want to run veewee in an OpenStack VM. I almost have everything working. The only catch is that qemu-kvm won't run. I've done lots of research and I believe I need what's called nested KVM. I get Y when I do a cat /sys/module/kvm_intel/parameters/nested on the host machine, so it's already enabled. libvirtd is already running on the guest. Is there anything else I need to do to get this going? When I try to manually start qemu-kvm it simple says start: Job failed to start. A sudo modprobe kvm comes back with FATAL: Module kvm not found. Same for kvm_intel. This is obviously a case of ignorance on my part. But I've spent the whole day trying to get this running. Can someone point me in the right direction? I know this isn't strictly an OpenStack issue, but I'm hoping someone here has come across this issue in the past. Thanks, Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On Jun 13, 2013, at 4:36 PM, Daniel Ellison dan...@syrinx.net wrote: libvirtd is already running on the guest. One more data point: the guest does have the vmx capability enabled: cpu match='exact' modelPenryn/model vendorIntel/vendor feature policy='require' name='hypervisor'/ feature policy='require' name='vmx'/ feature policy='require' name='ss'/ feature policy='require' name='vme'/ feature policy='disable' name='sse4.1'/ /cpu Dan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
What is the guest OS? It seems the error Module kvm not found points to the missing kernel module rather than it not loading. Is the guest kernel 2.6.23? Can you find a kvm.ko and kvm-intel.ko on the guest file system? I'd recommend looking at this for RHEL/CentOS/Fedora: http://kashyaspc.wordpress.com/2013/02/12/nested-virtualization-with-kvm-and-intel-on-fedora-18/ Hope this helps. On Thu, Jun 13, 2013 at 9:53 PM, Daniel Ellison dan...@syrinx.net wrote: On Jun 13, 2013, at 4:36 PM, Daniel Ellison dan...@syrinx.net wrote: libvirtd is already running on the guest. One more data point: the guest does have the vmx capability enabled: cpu match='exact' modelPenryn/model vendorIntel/vendor feature policy='require' name='hypervisor'/ feature policy='require' name='vmx'/ feature policy='require' name='ss'/ feature policy='require' name='vme'/ feature policy='disable' name='sse4.1'/ /cpu Dan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Openstack-operators] Horizon troubleshooting
On 13 June 2013 20:54, Igor Laskovy igor.lask...@gmail.com wrote: So how I can determine what wrong with installation? I found that I can turn on verbose logging for django Horizon app, but how? Debug logs are your friend. Start with setting DEBUG = True in horizon's local_settings.py file. That'll give you your first clue. From there you'll need to enable debug in each subsequent service down the path (and restart the services to have it take effect) to find the source of the problem. ___ 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] nova agent-* subcommands
Hi All agent-createCreates a new agent build. agent-deleteDeletes an existing agent build. agent-list List all builds agent-modifyModify an existing agent build. What is the purpose of these commands? Which documentation should I read to learn more about these agnets? Thanks Chris ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On Jun 13, 2013, at 5:05 PM, laclasse lacla...@gmail.com wrote: What is the guest OS? It seems the error Module kvm not found points to the missing kernel module rather than it not loading. Is the guest kernel 2.6.23? Can you find a kvm.ko and kvm-intel.ko on the guest file system? I did do a search for the kernel modules on the guest and they were not found. The guest OS was generated from the ubuntu-precise-server-cloudimg-amd64 image available from Ubuntu. uname -a says (in part) Linux image 3.2.0-45-virtual. I've installed libvirt-bin libvirt-dev kvm qemu qemu-kvm, and they brought in things like bridge-utils, etc. Thanks, Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
No. You can't use KVM in a guest since it requires hardware virtualization. Instead you need to use qemu in emulation mode. Refer to the devstack code for how to set this up, since devatack will work in Amazon EC2. On Thu, Jun 13, 2013 at 4:54 PM, Daniel Ellison dan...@syrinx.net wrote: On Jun 13, 2013, at 4:36 PM, Daniel Ellison dan...@syrinx.net wrote: libvirtd is already running on the guest. One more data point: the guest does have the vmx capability enabled: cpu match='exact' modelPenryn/model vendorIntel/vendor feature policy='require' name='hypervisor'/ feature policy='require' name='vmx'/ feature policy='require' name='ss'/ feature policy='require' name='vme'/ feature policy='disable' name='sse4.1'/ /cpu Dan ___ 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] Can I run qemu-kvm in an OpenStack Instance
On Jun 13, 2013, at 5:19 PM, Parrott, Robert parr...@g.harvard.edu wrote: No. You can't use KVM in a guest since it requires hardware virtualization. Instead you need to use qemu in emulation mode. Refer to the devstack code for how to set this up, since devatack will work in Amazon EC2. I will probably take a look at the devstack code, then. But the purpose of nested KVM is to allow direct access to the cpu virtualization extensions of the host machine from a properly-configured guest. That would be ideal. But all I REALLY want to do is create KVM images, not actually run them. If there's another way to do that, I'll be happy. Thanks, Dan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On Jun 13, 2013, at 5:24 PM, David Stearns dstea...@gnip.com wrote: There's no reason using nested KVM shouldn't work so long as the hardware supports it. Do you know what kind of hardware support is required? Obviously my host already supports CPU virtualization extensions. :) Looks like http://dachary.org/?p=1318 provides a pretty good walkthrough on getting it working on openstack. That looks like a great reference! I'll go through it and see if I did anything wrong or left anything out. Thanks, David. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On 14 June 2013 09:18, Daniel Ellison dan...@syrinx.net wrote: On Jun 13, 2013, at 5:05 PM, laclasse lacla...@gmail.com wrote: What is the guest OS? It seems the error Module kvm not found points to the missing kernel module rather than it not loading. Is the guest kernel 2.6.23? Can you find a kvm.ko and kvm-intel.ko on the guest file system? I did do a search for the kernel modules on the guest and they were not found. The guest OS was generated from the ubuntu-precise-server-cloudimg-amd64 image available from Ubuntu. uname -a says (in part) Linux image 3.2.0-45-virtual. install linux-image-generic, it will bring in linux-image-extra-$version-generic which has kvm. Cheers, Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Cloud Services ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On Thu, Jun 13, 2013 at 4:19 PM, Parrott, Robert parr...@g.harvard.eduwrote: No. You can't use KVM in a guest since it requires hardware virtualization. Instead you need to use qemu in emulation mode. Refer to the devstack code for how to set this up, since devatack will work in Amazon EC2. It *is* possible to do KVM in KVM, actually. I just set it up today (but it was my manually created KVM hosting a devstack launching KVM guests, not the same situation as Daniel). I've heard this you can't do KVM in KVM thing from a few different people and I want to make sure that it's clear that you actually can, given the correct hardware support. -- IRC: radix Christopher Armstrong Rackspace ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
On Jun 13, 2013, at 5:34 PM, Robert Collins robe...@robertcollins.net wrote: install linux-image-generic, it will bring in linux-image-extra-$version-generic which has kvm. That did it! I'm now creating a CentOS KVM image in an Ubuntu OpenStack VM. I'll wait until it finishes before celebrating, but there are no errors so far. Just to clarify, I first installed linux-image-generic but it didn't automatically bring in linux-image-extra-$version-generic. I did an apt-cache search and found linux-image-extra-virtual. I installed that and it brought in KVM. I subsequently had to start qemu-kvm manually, but it did start. I'll update this thread if and when the CentOS image is created successfully. Thanks, Robert! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance
If you really want to go crazy, why not run OpenStack in an OpenStack instance to launch your qemu machines: http://devstack.org/guides/single-vm.html - Joseph From: Openstack [openstack-bounces+joseph.quinn=rackspace@lists.launchpad.net] on behalf of Daniel Ellison [dan...@syrinx.net] Sent: Thursday, June 13, 2013 4:54 PM To: Robert Collins Cc: OpenStack Users Subject: Re: [Openstack] Can I run qemu-kvm in an OpenStack Instance On Jun 13, 2013, at 5:34 PM, Robert Collins robe...@robertcollins.net wrote: install linux-image-generic, it will bring in linux-image-extra-$version-generic which has kvm. That did it! I'm now creating a CentOS KVM image in an Ubuntu OpenStack VM. I'll wait until it finishes before celebrating, but there are no errors so far. Just to clarify, I first installed linux-image-generic but it didn't automatically bring in linux-image-extra-$version-generic. I did an apt-cache search and found linux-image-extra-virtual. I installed that and it brought in KVM. I subsequently had to start qemu-kvm manually, but it did start. I'll update this thread if and when the CentOS image is created successfully. Thanks, Robert! ___ 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] Another basic Swift question
When a new server is added to an existing cluster, and I now update the ring with the new device, but at the same time, I do NOT rebalance, will things work correctly? I am assuming if I don't rebalance, but I do update the ring, the ring has the new partition scheme with the new device information, so new data will go to the new device. But at the same time, an existing object which previously hashed to a specific partition on a specific server can possibly hash to a different partition on a different server, so how do old objects get accessed? I do understand I should do the rebalance, and I will at a certain point in time, but I wanted to understand the behavior if I update the ring and don't do the rebalance Cheers, -- Mark ___ 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] Security Group of Quantum ovs plugin (Folsom) is not working
Hello, I'm trying to use security group of Quantum ovs plugin(Folsom) in CentOS 6.3 (2012.2.3-1.el6@epel). Everything looks good, except security group, and there are no error message in /var/log/nova/compute.log file. After I created VM, I can see the bridges and interfaces have been created normally. [root@compute1 ~]# brctl show bridge name bridge id STP enabled interfaces br-int .3eca2e714b4d no qvo756ead5d-32 br-tun .824651aab541 no qbr756ead5d-32 .ca57ea41484c no qvb756ead5d-32 vnet0 The chain rules in filter table of iptables can reflect security group rules correctly too. Chain nova-compute-inst-749 (1 references) num target prot opt source destination 1DROP all -- 0.0.0.0/00.0.0.0/0 state INVALID 2ACCEPT all -- 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 3nova-compute-provider all -- 0.0.0.0/00.0.0.0/0 4ACCEPT udp -- 10.0.0.2 0.0.0.0/0 udp spt:67 dpt:68 5ACCEPT all -- 10.0.0.0/24 0.0.0.0/0 6nova-compute-sg-fallback all -- 0.0.0.0/00.0.0.0/0 Obviously, the packets do not follow these rules correctly. Please advise me how to resolve this problem. Thanks a lot, Chandler ___ 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] Another basic Swift question
Hi Mark, Well, the ring without rebalance will not effect anything. With a update, there're no partitions been assigned to the new devices.Result of partition numbers of a new device will be 0. Which means no any object will be calculated for these new devices. In the case of adding a new server (devices) to the ring, it should still work properly. What you need is to understand the mechanism of replicator and the theory of partions in Swift. I have to point out a key concept of partition. It's a logic partition in swift layer instead of a real partition on disk. When a partition been assigned to a new device. it's much more like that your parking slot changed from first floor to second floor. Your can won't be destroyed but wait for moving to new place. :) Hope it help. Cheers +Hugo Kuo+ h...@swiftstack.com tonyt...@gmail.com +886 935004793 2013/6/14 Mark Brown ntdeveloper2...@yahoo.com When a new server is added to an existing cluster, and I now update the ring with the new device, but at the same time, I do NOT rebalance, will things work correctly? I am assuming if I don't rebalance, but I do update the ring, the ring has the new partition scheme with the new device information, so new data will go to the new device. But at the same time, an existing object which previously hashed to a specific partition on a specific server can possibly hash to a different partition on a different server, so how do old objects get accessed? I do understand I should do the rebalance, and I will at a certain point in time, but I wanted to understand the behavior if I update the ring and don't do the rebalance Cheers, -- Mark ___ 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] Can I run qemu-kvm in an OpenStack Instance
Yes, the Ubuntu cloud image is made to run as a guest atop an hypervisor and it makes sense to optimize it by removing the unlikely needed modules that usually require hardware to run (nested virt is not yet common). Scott Moser may confirm/infirm. Maybe you can try installing the 'normal' kernel on your guest that has the vmx flag exported in its vm config and try loading it again. On that Ubuntu guest, you can also install cpu-checker that gives you a 'kvm-ok' cli: # kvm-ok INFO: /dev/kvm exists KVM acceleration can be used Hope this helps. On Thu, Jun 13, 2013 at 10:18 PM, Daniel Ellison dan...@syrinx.net wrote: On Jun 13, 2013, at 5:05 PM, laclasse lacla...@gmail.com wrote: What is the guest OS? It seems the error Module kvm not found points to the missing kernel module rather than it not loading. Is the guest kernel 2.6.23? Can you find a kvm.ko and kvm-intel.ko on the guest file system? I did do a search for the kernel modules on the guest and they were not found. The guest OS was generated from the ubuntu-precise-server-cloudimg-amd64 image available from Ubuntu. uname -a says (in part) Linux image 3.2.0-45-virtual. I've installed libvirt-bin libvirt-dev kvm qemu qemu-kvm, and they brought in things like bridge-utils, etc. Thanks, Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack-qa-team] Script to prepare the stack for full tempest run.
Hi, We wish to create some tool for automated preparation of stack for full tempest run. We need it to be able to work with deployment that has been prepared by Packstack [1]. Packstack can give as an output some answer file, which is actually an ini file. We can parse that file, take some other values as input, for example images locations, ... and create a tempest.conf accordingly. The questions now are: * Should this be a part of Tempest? * Should this be a separate project? * Should this be a part of the Packstack? * What about other deploying tools - should that tool have several frond-ends? * Does anybody have something already? Any comments? [1] https://wiki.openstack.org/wiki/Packstack PS: As Attila Fazekas pointed, most things we can find dynamically from the keystone/nova. True, but I don't quite like the idea to ssh to nova host to get nova SQL password and tricks like that. Jaroslav Henner -- Mailing list: https://launchpad.net/~openstack-qa-team Post to : openstack-qa-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-qa-team More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_havana_cinder_trunk #147
Title: precise_havana_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/147/Project:precise_havana_cinder_trunkDate of build:Thu, 13 Jun 2013 02:01:14 -0400Build duration:6 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesFixes 3PAR drivers terminate_connection issue.by viraj.hardikareditcinder/tests/test_hp3par.pyeditcinder/volume/drivers/san/hp/hp_3par_iscsi.pyeditcinder/volume/drivers/san/hp/hp_3par_fc.pyConsole Output[...truncated 4525 lines...]Build-Time: 108Distribution: precise-havanaFail-Stage: buildHost Architecture: amd64Install-Time: 64Job: cinder_2013.2+git201306130201~precise-0ubuntu1.dscMachine Architecture: amd64Package: cinderPackage-Time: 200Source-Version: 1:2013.2+git201306130201~precise-0ubuntu1Space: 27120Status: attemptedVersion: 1:2013.2+git201306130201~precise-0ubuntu1Finished at 20130613-0207Build needed 00:03:20, 27120k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'cinder_2013.2+git201306130201~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'cinder_2013.2+git201306130201~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/havana /tmp/tmpfOzggR/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpfOzggR/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D precise --newversion 1:2013.2+git201306130201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.2+git201306130201~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A cinder_2013.2+git201306130201~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'cinder_2013.2+git201306130201~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'cinder_2013.2+git201306130201~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: test_tempest_smoke #146
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/146/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 02:47:10 -0400Build duration:45 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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_python-swiftclient_stable #39
Title: raring_grizzly_python-swiftclient_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-swiftclient_stable/39/Project:raring_grizzly_python-swiftclient_stableDate of build:Thu, 13 Jun 2013 04:01:16 -0400Build duration:4 min 6 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20Changespython3: Introduce py33 to tox.iniby Chuck Shortedittox.iniConsole Output[...truncated 1103 lines...]Download error on http://pypi.python.org/simple/pbr/: timed out -- Some packages may not be found!Couldn't find index page for 'pbr' (maybe misspelled?)Download error on http://pypi.python.org/simple/: timed out -- Some packages may not be found!No local packages or download links found for pbrTraceback (most recent call last): File "setup.py", line 21, in d2to1=True) File "/usr/lib/python2.7/distutils/core.py", line 112, in setup_setup_distribution = dist = klass(attrs) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 221, in __init__self.fetch_build_eggs(attrs.pop('setup_requires')) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in fetch_build_eggsparse_requirements(requires), installer=self.fetch_build_egg File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 586, in resolvedist = best[req.key] = env.best_match(req, self, installer) File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 831, in best_matchreturn self.obtain(req, installer) # try and download/install File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 843, in obtainreturn installer(requirement) File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 295, in fetch_build_eggreturn cmd.easy_install(req) File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 611, in easy_installraise DistutilsError(msg)distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr')ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'raring-amd64-df2fce4b-fd8a-4a99-aa50-706d26048219', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'raring-amd64-df2fce4b-fd8a-4a99-aa50-706d26048219', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-swiftclient/grizzly /tmp/tmp47lSEf/python-swiftclientmk-build-deps -i -r -t apt-get -y /tmp/tmp47lSEf/python-swiftclient/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'raring-amd64-df2fce4b-fd8a-4a99-aa50-706d26048219', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'raring-amd64-df2fce4b-fd8a-4a99-aa50-706d26048219', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: test_tempest_smoke #147
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/147/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 04:08:56 -0400Build duration:52 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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_python-keystoneclient_stable #115
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: saucy_havana_horizon_trunk #65
Title: saucy_havana_horizon_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_horizon_trunk/65/Project:saucy_havana_horizon_trunkDate of build:Thu, 13 Jun 2013 06:31:15 -0400Build duration:4 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesEnable Start Instance and Shut Off Instance buttonsby niceditopenstack_dashboard/dashboards/project/instances/tables.pyeditopenstack_dashboard/api/nova.pyConsole Output[...truncated 3152 lines...]Source-Version: 1:2013.2+git201306130631~saucy-0ubuntu1Space: 0Status: failedVersion: 1:2013.2+git201306130631~saucy-0ubuntu1Finished at 20130613-0634Build needed 00:00:00, 0k disc spaceE: Core build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'horizon_2013.2+git201306130631~saucy-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'horizon_2013.2+git201306130631~saucy-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/havana /tmp/tmpGwnHNx/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpGwnHNx/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log c123e2abb48b8e72b279258d272d661a5146ebb8..HEAD --no-merges --pretty=format:[%h] %sdch -b -D saucy --newversion 1:2013.2+git201306130631~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a [87facce] Enable "Start Instance" and "Shut Off Instance" buttonsdch -a [188314b] Remove explicit distribute depend.dch -a [8a069db] Add HACKING.rstdch -a [7309bcb] Edit some load balancers titlesdch -a [aae31bb] Quota summary graphs, added styling to indicate percentage fulldch -a [8a0b4c7] Mix snapshots and images tables togetherdch -a [3f19461] Refactoring url_for to remove admin parameterdch -a [a6d72d7] New tox environment for testing with Django 1.4debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC horizon_2013.2+git201306130631~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A horizon_2013.2+git201306130631~saucy-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'horizon_2013.2+git201306130631~saucy-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'horizon_2013.2+git201306130631~saucy-0ubuntu1.dsc']' 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: test_tempest_smoke #148
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/148/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 08:39:47 -0400Build duration:48 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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: saucy_havana_horizon_trunk #66
Title: saucy_havana_horizon_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_horizon_trunk/66/Project:saucy_havana_horizon_trunkDate of build:Thu, 13 Jun 2013 09:01:17 -0400Build duration:4 min 55 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUpdate my mailmapby joe.gordon0edit.mailmapConsole Output[...truncated 7356 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key)"Checking signature on .changesGood signature on /tmp/tmpw_C6Ec/horizon_2013.2+git201306130901~saucy-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpw_C6Ec/horizon_2013.2+git201306130901~saucy-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading horizon_2013.2+git201306130901~saucy-0ubuntu1.dsc: done. Uploading horizon_2013.2+git201306130901~saucy.orig.tar.gz: done. Uploading horizon_2013.2+git201306130901~saucy-0ubuntu1.debian.tar.gz: done. Uploading horizon_2013.2+git201306130901~saucy-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'saucy-havana', 'horizon_2013.2+git201306130901~saucy-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/h/horizon/openstack-dashboard-ubuntu-theme_2013.2+git201306130202~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/openstack-dashboard_2013.2+git201306130202~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-horizon_2013.2+git201306130202~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-openstack_2013.2+git201306130202~saucy-0ubuntu1_all.debINFO:root:Storing current commit for next build: 79c56eb7839b76061dd2d3bf29ea360fcbdd974dINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/havana /tmp/tmpw_C6Ec/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpw_C6Ec/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log c123e2abb48b8e72b279258d272d661a5146ebb8..HEAD --no-merges --pretty=format:[%h] %sdch -b -D saucy --newversion 1:2013.2+git201306130901~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a [79c56eb] Update my mailmapdch -a [87facce] Enable "Start Instance" and "Shut Off Instance" buttonsdch -a [188314b] Remove explicit distribute depend.dch -a [8a069db] Add HACKING.rstdch -a [7309bcb] Edit some load balancers titlesdch -a [aae31bb] Quota summary graphs, added styling to indicate percentage fulldch -a [8a0b4c7] Mix snapshots and images tables togetherdch -a [3f19461] Refactoring url_for to remove admin parameterdch -a [a6d72d7] New tox environment for testing with Django 1.4debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC horizon_2013.2+git201306130901~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A horizon_2013.2+git201306130901~saucy-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/havana horizon_2013.2+git201306130901~saucy-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include saucy-havana horizon_2013.2+git201306130901~saucy-0ubuntu1_amd64.changesEmail 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: test_tempest_smoke #149
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/149/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 09:09:25 -0400Build duration:30 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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: saucy_havana_keystone_trunk #65
Title: saucy_havana_keystone_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_keystone_trunk/65/Project:saucy_havana_keystone_trunkDate of build:Thu, 13 Jun 2013 10:31:35 -0400Build duration:5 min 29 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 5741 lines...]Status: successfulVersion: 1:2013.2+git201306131031~saucy-0ubuntu1Finished at 20130613-1036Build needed 00:03:32, 16096k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/havanaDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/havana', 'keystone_2013.2+git201306131031~saucy-0ubuntu1_source.changes']gpg: Signature made Thu Jun 13 10:33:27 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Thu Jun 13 10:33:26 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmprMH_nE/keystone_2013.2+git201306131031~saucy-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmprMH_nE/keystone_2013.2+git201306131031~saucy-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading keystone_2013.2+git201306131031~saucy-0ubuntu1.dsc: done. Uploading keystone_2013.2+git201306131031~saucy.orig.tar.gz: done. Uploading keystone_2013.2+git201306131031~saucy-0ubuntu1.debian.tar.gz: done. Uploading keystone_2013.2+git201306131031~saucy-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'saucy-havana', 'keystone_2013.2+git201306131031~saucy-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/k/keystone/keystone-doc_2013.2+git201306111502~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/keystone_2013.2+git201306111502~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/python-keystone_2013.2+git201306111502~saucy-0ubuntu1_all.debINFO:root:Storing current commit for next build: a56b82b0aa3a23ff076914b97a382efe98cd0de5INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/havana /tmp/tmprMH_nE/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmprMH_nE/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D saucy --newversion 1:2013.2+git201306131031~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.2+git201306131031~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A keystone_2013.2+git201306131031~saucy-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/havana keystone_2013.2+git201306131031~saucy-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include saucy-havana keystone_2013.2+git201306131031~saucy-0ubuntu1_amd64.changesEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: precise_havana_python-quantumclient_trunk #31
Title: precise_havana_python-quantumclient_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_python-quantumclient_trunk/31/Project:precise_havana_python-quantumclient_trunkDate of build:Thu, 13 Jun 2013 11:31:49 -0400Build duration:1 min 41 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 1552 lines...]Finished at 20130613-1133Build needed 00:00:40, 1996k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/havanaDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/havana', 'python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_source.changes']gpg: Signature made Thu Jun 13 11:32:46 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Thu Jun 13 11:32:46 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmpOrMrGF/python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpOrMrGF/python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1.dsc: done. Uploading python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise.orig.tar.gz: done. Uploading python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1.debian.tar.gz: done. Uploading python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-havana', 'python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-quantumclient/python-quantumclient_2.2.2a.6.g068cf76+git201306091031~precise-0ubuntu1_all.debINFO:root:Storing current commit for next build: 5326cc713a428d5ec3905a1bffa2848ad80cdfbeINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/havana /tmp/tmpOrMrGF/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmpOrMrGF/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 92811c76f3a8308b36f81e61451ec17d227b453b..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 2:2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [5326cc7] Rename README to README.rstdch -a [ae2a91f]Rename requires files to standard names.dch -a [b950006] Set default columns in ext-listdch -a [2815be0] CLI support for disabling SNATdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/havana python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-havana python-quantumclient_2.2.2a.8.g53adca5+git201306131131~precise-0ubuntu1_amd64.changesEmail 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-n
[Openstack-ubuntu-testing-notifications] Build Still Failing: test_tempest_smoke #150
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/150/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 11:41:05 -0400Build duration:41 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to FAILUREEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: precise_havana_cinder_trunk #148
Title: precise_havana_cinder_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/148/Project:precise_havana_cinder_trunkDate of build:Thu, 13 Jun 2013 13:31:17 -0400Build duration:5 min 38 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesFix some unittest cases failed on osxby haomaieditcinder/tests/test_scality.pyConsole Output[...truncated 6759 lines...]Finished at 20130613-1336Build needed 00:02:53, 53104k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/havanaDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/havana', 'cinder_2013.2+git201306131331~precise-0ubuntu1_source.changes']gpg: Signature made Thu Jun 13 13:33:52 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Thu Jun 13 13:33:51 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmpQuK_ZK/cinder_2013.2+git201306131331~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpQuK_ZK/cinder_2013.2+git201306131331~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading cinder_2013.2+git201306131331~precise-0ubuntu1.dsc: done. Uploading cinder_2013.2+git201306131331~precise.orig.tar.gz: done. Uploading cinder_2013.2+git201306131331~precise-0ubuntu1.debian.tar.gz: done. Uploading cinder_2013.2+git201306131331~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-havana', 'cinder_2013.2+git201306131331~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/cinder/cinder-api_2013.2+git201306122331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-backup_2013.2+git201306122331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-common_2013.2+git201306122331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-scheduler_2013.2+git201306122331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-volume_2013.2+git201306122331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/python-cinder_2013.2+git201306122331~precise-0ubuntu1_all.debINFO:root:Storing current commit for next build: 99f08868b8c5227622b3ac84c8863a25a161953dINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/havana /tmp/tmpQuK_ZK/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpQuK_ZK/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D precise --newversion 1:2013.2+git201306131331~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.2+git201306131331~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A cinder_2013.2+git201306131331~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/havana cinder_2013.2+git201306131331~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-havana cinder_2013.2+git201306131331~precise-0ubuntu1_amd64.changesEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: saucy_havana_quantum_trunk #138
Title: saucy_havana_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/138/Project:saucy_havana_quantum_trunkDate of build:Thu, 13 Jun 2013 13:38:05 -0400Build duration:6 min 31 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesImported Translations from Transifexby Jenkinseditquantum/locale/ru/LC_MESSAGES/quantum.poeditquantum/locale/vi_VN/LC_MESSAGES/quantum.poeditquantum/locale/pt_BR/LC_MESSAGES/quantum.poeditquantum/locale/quantum.poteditquantum/locale/cs/LC_MESSAGES/quantum.poeditquantum/locale/zh_TW/LC_MESSAGES/quantum.poeditquantum/locale/ro/LC_MESSAGES/quantum.poeditquantum/locale/zh_CN/LC_MESSAGES/quantum.poeditquantum/locale/ko_KR/LC_MESSAGES/quantum.poeditquantum/locale/bg_BG/LC_MESSAGES/quantum.poeditquantum/locale/fr/LC_MESSAGES/quantum.poeditquantum/locale/da/LC_MESSAGES/quantum.poeditquantum/locale/fi_FI/LC_MESSAGES/quantum.poeditquantum/locale/it/LC_MESSAGES/quantum.poeditquantum/locale/de/LC_MESSAGES/quantum.poeditquantum/locale/ja/LC_MESSAGES/quantum.poeditquantum/locale/es/LC_MESSAGES/quantum.poeditquantum/locale/ka_GE/LC_MESSAGES/quantum.poConsole Output[...truncated 1237 lines...]Get:104 http://archive.ubuntu.com/ubuntu/ saucy/main libxinerama1 amd64 2:1.1.2-1+deb7u1 [8082 B]Get:105 http://archive.ubuntu.com/ubuntu/ saucy/main libxrandr2 amd64 2:1.4.0-1ubuntu2 [19.4 kB]Get:106 http://archive.ubuntu.com/ubuntu/ saucy/main shared-mime-info amd64 1.1-0ubuntu2 [412 kB]Get:107 http://archive.ubuntu.com/ubuntu/ saucy/main libgtk2.0-0 amd64 2.24.18-0ubuntu2 [1728 kB]Get:108 http://archive.ubuntu.com/ubuntu/ saucy/main libxft2 amd64 2.3.1-1 [43.4 kB]Get:109 http://archive.ubuntu.com/ubuntu/ saucy/main libpangoxft-1.0-0 amd64 1.32.5-5ubuntu1 [14.3 kB]Get:110 http://archive.ubuntu.com/ubuntu/ saucy/main libyaml-0-2 amd64 0.1.4-2build1 [57.3 kB]Get:111 http://archive.ubuntu.com/ubuntu/ saucy/main libpangox-1.0-0 amd64 0.0.2-4 [41.3 kB]Get:112 http://archive.ubuntu.com/ubuntu/ saucy/main hicolor-icon-theme all 0.12-1ubuntu2 [10.2 kB]Get:113 http://archive.ubuntu.com/ubuntu/ saucy/main libgtk2.0-bin amd64 2.24.18-0ubuntu2 [9598 B]Get:114 http://archive.ubuntu.com/ubuntu/ saucy/main libpango1.0-0 amd64 1.32.5-5ubuntu1 [2982 B]Get:115 http://archive.ubuntu.com/ubuntu/ saucy/main python-beautifulsoup all 3.2.1-1 [34.6 kB]Get:116 http://archive.ubuntu.com/ubuntu/ saucy/main python-cairo amd64 1.8.8-1ubuntu4 [50.5 kB]Get:117 http://archive.ubuntu.com/ubuntu/ saucy/main python-gobject-2 amd64 2.28.6-12 [239 kB]Get:118 http://archive.ubuntu.com/ubuntu/ saucy/main python-gtk2 amd64 2.24.0-3ubuntu1 [896 kB]Get:119 http://archive.ubuntu.com/ubuntu/ saucy/main python-junitxml all 0.6-1ubuntu1 [9212 B]Get:120 http://archive.ubuntu.com/ubuntu/ saucy/main python-openid all 2.2.5-3ubuntu1 [118 kB]Get:121 http://archive.ubuntu.com/ubuntu/ saucy/main python-openssl amd64 0.13-2ubuntu3 [103 kB]Get:122 http://archive.ubuntu.com/ubuntu/ saucy/main python-scgi amd64 1.13-1ubuntu2 [20.4 kB]Get:123 http://archive.ubuntu.com/ubuntu/ saucy/main python-sqlalchemy-ext amd64 0.7.9-1 [14.2 kB]Get:124 http://archive.ubuntu.com/ubuntu/ saucy/main python-yaml amd64 3.10-4build2 [113 kB]Failed to fetch http://localhost/ubuntu/pool/main/k/keystone/python-keystone_2013.2+git201306131031~saucy-0ubuntu1_all.deb 404 Not FoundFetched 15.0 MB in 9s (1504 kB/s)E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?install call failedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-0ed16f90-6ffb-4a13-9482-69c5a739593d', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpBaU64v/quantum/debian/control']' returned non-zero exit status 100ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-0ed16f90-6ffb-4a13-9482-69c5a739593d', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpBaU64v/quantum/debian/control']' returned non-zero exit status 100INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/havana /tmp/tmpBaU64v/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpBaU64v/quantum/debian/controlTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-0ed16f90-6ffb-4a13-9482-69c5a739593d', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpBaU64v/quantum/debian/control']' returned non-zero exit status 100Error 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
[Openstack-ubuntu-testing-notifications] Build Still Failing: test_tempest_smoke #151
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/151/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 15:11:35 -0400Build duration:48 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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: saucy_havana_quantum_trunk #139
Title: saucy_havana_quantum_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/139/Project:saucy_havana_quantum_trunkDate of build:Thu, 13 Jun 2013 15:01:17 -0400Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUpdate with latest OSLO codeby gkottoneditquantum/openstack/common/notifier/no_op_notifier.pyeditquantum/openstack/common/log.pyeditquantum/openstack/common/exception.pyeditquantum/openstack/common/rpc/matchmaker.pyeditquantum/openstack/common/fileutils.pyeditquantum/openstack/common/rpc/service.pyeditquantum/openstack/common/notifier/rpc_notifier2.pyeditquantum/openstack/common/rpc/impl_kombu.pyeditquantum/openstack/common/rpc/proxy.pyeditquantum/openstack/common/timeutils.pyeditquantum/openstack/common/rpc/matchmaker_redis.pyeditquantum/openstack/common/notifier/log_notifier.pyedittools/patch_tox_venv.pyeditquantum/openstack/common/lockutils.pyeditquantum/openstack/common/rpc/matchmaker_ring.pyeditquantum/openstack/common/importutils.pyeditquantum/openstack/common/rpc/common.pyeditquantum/openstack/common/processutils.pyeditquantum/openstack/common/context.pyeditquantum/openstack/common/rpc/serializer.pyeditquantum/openstack/common/service.pyeditquantum/openstack/common/notifier/rpc_notifier.pyeditquantum/openstack/common/notifier/api.pyeditquantum/openstack/common/threadgroup.pyeditquantum/openstack/common/gettextutils.pyeditquantum/openstack/common/rpc/impl_zmq.pyeditquantum/openstack/common/rpc/amqp.pyeditquantum/openstack/common/network_utils.pyeditquantum/openstack/common/rpc/impl_fake.pyConsole Output[...truncated 19609 lines...]DEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'saucy-havana', 'quantum_2013.2+git201306131501~saucy-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/q/quantum/python-quantum_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-common_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-dhcp-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-l3-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-lbaas-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-metadata-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-bigswitch_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-brocade_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-cisco_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-hyperv_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-linuxbridge-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-linuxbridge_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-metaplugin_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-midonet_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-nec-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-nec_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-nicira_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-openvswitch-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-openvswitch_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-plumgrid_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-ryu-agent_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-ryu_2013.2+git201306130731~saucy-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-server_2013.2+git201306130731~saucy-0ubuntu1_all.debINFO:root:Storing current commit for next build: 828d83a09570a7f22aa849816f69590f85b6a1e8INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/havana /tmp/tmpqg_iur/quantummk-build-deps -i -r -t apt-get -y
[Openstack-ubuntu-testing-notifications] Build Still Failing: test_tempest_smoke #152
Title: test_tempest_smoke General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/152/Project:test_tempest_smokeDate of build:Thu, 13 Jun 2013 16:12:18 -0400Build duration:44 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 478 lines...]Setting up python-anyjson (0.3.3-0ubuntu1) ...Setting up python-boto (2.3.0-1) ...Setting up python-chardet (2.0.1-2build1) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-cmd2 (0.6.4-1) ...Setting up python-pyparsing (1.5.7+dfsg1-0ubuntu2) ...Setting up python-cliff (1.3.1-0ubuntu1) ...Setting up python-crypto (2.6-4) ...Setting up python-httplib2 (0.7.7-1) ...Setting up python-keyring (0.9.2-1ubuntu2) ...Setting up python-lxml (3.1.0-1) ...Setting up python-netaddr (0.7.7-1) ...Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.13.0-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1ubuntu1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up python-keystoneclient (1:0.2.3-0ubuntu2.2) ...Setting up python-glanceclient (1:0.9.0-0ubuntu1.1) ...Setting up python-quantumclient (1:2.2.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[ERROR] Could not locate generated Tempest config @ /var/lib/jenkins/jobs/test_tempest_smoke/workspace/openstack-ubuntu-testing/etc/tests/tempest_templates/tempest.master.conf[run_tempest.sh] Running cleanup scripts in tests/tempest.**Removing Tempest users and tenants in Keystone.**ERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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_python-cinderclient_stable #58
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_python-ceilometerclient_stable #6
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19257
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19257/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson6762243669418928705.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19258
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19258/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson5362000874248488207.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19259
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19259/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson2918907954709118278.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19260
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19260/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson7630157025419281629.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19261
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19261/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson7917463417891048766.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19262
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19262/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson7190688515553177208.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_grizzly_version-drift #55
See http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/55/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_grizzly_version-drift/ws/ [cloud-archive_grizzly_version-drift] $ /bin/bash -xe /tmp/hudson8087852324378575650.sh + OS_RELEASE=grizzly + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py grizzly INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r grizzly --- The following Cloud Archive packages for grizzly have been superseded newer versions in Ubuntu! keystone: Ubuntu: 1:2013.1.1-0ubuntu2.1 Cloud Archive staging: 1:2013.1.1-0ubuntu2~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19263
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19263/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson4733418442986535407.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19264
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19264/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson4052761074853632962.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19265
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19265/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson1926655792898363559.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19266
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19266/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson2794358383474365439.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19267
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19267/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson2257638325270646077.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19268
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19268/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson5646294516336421804.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_havana_nova_trunk #361
Title: precise_havana_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/361/Project:precise_havana_nova_trunkDate of build:Fri, 14 Jun 2013 01:31:21 -0400Build duration:9 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesRefactor libvirt driver exception handlingby hanlindeditnova/virt/libvirt/driver.pyRegister libvirt driver with closed connection callbackby dillamaneditnova/virt/libvirt/driver.pyeditnova/tests/virt/libvirt/test_libvirt.pyConsole Output[...truncated 9070 lines...]Build-Time: 251Distribution: precise-havanaFail-Stage: buildHost Architecture: amd64Install-Time: 67Job: nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dscMachine Architecture: amd64Package: novaPackage-Time: 335Source-Version: 1:2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1Space: 87656Status: attemptedVersion: 1:2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1Finished at 20130614-0140Build needed 00:05:35, 87656k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/havana /tmp/tmp8Tes9n/novamk-build-deps -i -r -t apt-get -y /tmp/tmp8Tes9n/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D precise --newversion 1:2013.2.a1225.gc9cb610+git201306140132~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.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'nova_2013.2.a1225.gc9cb610+git201306140132~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #19269
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/19269/ -- Started by timer Building remotely on pkg-builder in workspace http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/ [cloud-archive_folsom_version-drift] $ /bin/bash -xe /tmp/hudson6881816337999145825.sh + OS_RELEASE=folsom + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/gather-versions.py folsom INFO:root:Querying package list and versions from staging PPA. INFO:root:Initializing connection to LP... INFO:root:Querying Ubuntu versions for all packages. INFO:root:Scraping Packages list for CA pocket: proposed INFO:root:Scraping Packages list for CA pocket: updates + /var/lib/jenkins/tools/ubuntu-reports/server/cloud-archive/version-tracker/ca-versions.py -c -r folsom --- The following Cloud Archive packages for folsom have been superseded newer versions in Ubuntu! keystone: Ubuntu: 2012.2.4-0ubuntu3.1 Cloud Archive staging: 2012.2.4-0ubuntu3~cloud0 -- Build step 'Execute shell' marked build as failure -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp