Re: [Openstack] compute_nodes DB table
On 06/08/12 16:47, Trinath Somanchi wrote: Hi- Can any one guide me on understanding the process that updates the compute_nodes table in nova database. nova-compute on each compute node sends a regular message to the nova-scheduler on the scheduler node with an update of its status. These are saved into that table. You can see these updates in your log: 2012-08-06 17:25:59 DEBUG nova.scheduler.host_manager [req-4549b72e-83e5-4617-9a6b-81c17609c83e None None] Received compute service update from molokai. from (pid=5003) update_service_capabilities /usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py:273 Cheers, Mikal ___ 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] compute_nodes DB table
thanks a lot for the guidance... On Mon, Aug 6, 2012 at 12:57 PM, Michael Still michael.st...@canonical.comwrote: On 06/08/12 16:47, Trinath Somanchi wrote: Hi- Can any one guide me on understanding the process that updates the compute_nodes table in nova database. nova-compute on each compute node sends a regular message to the nova-scheduler on the scheduler node with an update of its status. These are saved into that table. You can see these updates in your log: 2012-08-06 17:25:59 DEBUG nova.scheduler.host_manager [req-4549b72e-83e5-4617-9a6b-81c17609c83e None None] Received compute service update from molokai. from (pid=5003) update_service_capabilities /usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py:273 Cheers, Mikal -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] No handlers could be found for logger keystoneclient.v2_0.client (HTTP 404)？？？
On 08/03/2012 09:37 AM, 王鹏 wrote: Everyone: Hi! When I install keystone alone, find a error, that’s make me crazy !the situation as follow: This is my conf [DEFAULT] bind_host = 0.0.0.0 public_port = 5000 admin_port = 35357 admin_token = admin compute_port = 8774 verbose = True debug = True log_config = /etc/keystone/logging.conf # = Syslog Options # Send logs to syslog (/dev/log) instead of to file specified # by `log-file` use_syslog = False # Facility to use. If unset defaults to LOG_USER. # syslog_log_facility = LOG_LOCAL0 [sql] #connection = sqlite:var/lib/keystone/keystone.db connection = mysql://keystone:***@172.18.32.7/keystone http://172.18.32.7/keystone idle_timeout = 200 [ldap] #url = ldap://localhost #tree_dn = dc=example,dc=com #user_tree_dn = ou=Users,dc=example,dc=com #role_tree_dn = ou=Roles,dc=example,dc=com #tenant_tree_dn = ou=Groups,dc=example,dc=com #user = dc=Manager,dc=example,dc=com #password = freeipa4all #suffix = cn=example,cn=com [identity] driver = keystone.identity.backends.sql.Identity [catalog] driver = keystone.catalog.backends.sql.Catalog [token] driver = keystone.token.backends.sql.Token # Amount of time a token should remain valid (in seconds) expiration = 86400 [policy] driver = keystone.policy.backends.rules.Policy [ec2] driver = keystone.contrib.ec2.backends.sql.Ec2 [filter:debug] paste.filter_factory = keystone.common.wsgi:Debug.factory [filter:token_auth] paste.filter_factory = keystone.middleware:TokenAuthMiddleware.factory [filter:admin_token_auth] paste.filter_factory = keystone.middleware:AdminTokenAuthMiddleware.factory [filter:xml_body] paste.filter_factory = keystone.middleware:XmlBodyMiddleware.factory [filter:json_body] paste.filter_factory = keystone.middleware:JsonBodyMiddleware.factory [filter:crud_extension] paste.filter_factory = keystone.contrib.admin_crud:CrudExtension.factory [filter:ec2_extension] paste.filter_factory = keystone.contrib.ec2:Ec2Extension.factory [app:public_service] paste.app_factory = keystone.service:public_app_factory [app:admin_service] paste.app_factory = keystone.service:admin_app_factory [pipeline:public_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension public_service [pipeline:admin_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension crud_extension admin_service [app:public_version_service] paste.app_factory = keystone.service:public_version_app_factory [app:admin_version_service] paste.app_factory = keystone.service:admin_version_app_factory [pipeline:public_version_api] pipeline = xml_body public_version_service [pipeline:admin_version_api] pipeline = xml_body admin_version_service [composite:main] use = egg:Paste#urlmap /v2.0 = public_api / = public_version_api [composite:admin] use = egg:Paste#urlmap /v2.0 = admin_api / = admin_version_api When I restart keystone Add tenant and user : root@keystone:~# keystone user-create --tenant_id e87f632d2c4e4f2b8dfe1fd2691d229d --name admin --pass admin --enabled true No handlers could be found for logger keystoneclient.v2_0.client Unable to communicate with identity service: 404 Not Found The resource could not be found. . (HTTP 404) Why? What can I miss? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Just a guess: Are you using public service (port 5000) instead of the admin (port 35357)? Anyway, you should add credentials you are using for that command in order to people can help you. Bye ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] 回复： glance error
Have you used keystone as auth server? If yes, please share your glance and keystone logs to figure out the root cause. Regards, Willfu 发件人： 王鹏 breakwin...@gmail.com 收件人： openstack@lists.launchpad.net 发送日期： 2012年8月6日, 星期一, 上午 11:22 主题: [Openstack] glance error hello,everyone: when I over glance install and config ,and test glance index: 爎oot@openstack-controller:~# glance index Failed to show index. Got error: There was an error connecting to a server Details: [Errno 111] Connection refused about config I just change the token could you help me ? why this error happen? thank you. ___ 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] compute_nodes DB table
Hi, The interval can be managed via the periodic_interval flag in nova.conf, which is by default 60 sec Cheers! On Mon, Aug 6, 2012 at 9:40 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: thanks a lot for the guidance... On Mon, Aug 6, 2012 at 12:57 PM, Michael Still michael.st...@canonical.com wrote: On 06/08/12 16:47, Trinath Somanchi wrote: Hi- Can any one guide me on understanding the process that updates the compute_nodes table in nova database. nova-compute on each compute node sends a regular message to the nova-scheduler on the scheduler node with an update of its status. These are saved into that table. You can see these updates in your log: 2012-08-06 17:25:59 DEBUG nova.scheduler.host_manager [req-4549b72e-83e5-4617-9a6b-81c17609c83e None None] Received compute service update from molokai. from (pid=5003) update_service_capabilities /usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py:273 Cheers, Mikal -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] No handlers could be found for logger keystoneclient.v2_0.client (HTTP 404)？？？
Have you exported vars as the guide: export SERVICE_ENDPOINT=http://localhost:35357/v2.0; export SERVICE_TOKEN=admin Best Il giorno 03/ago/2012, alle ore 09:37, 王鹏 breakwin...@gmail.com ha scritto: Everyone: Hi! When I install keystone alone, find a error, that’s make me crazy !the situation as follow: This is my conf [DEFAULT] bind_host = 0.0.0.0 public_port = 5000 admin_port = 35357 admin_token = admin compute_port = 8774 verbose = True debug = True log_config = /etc/keystone/logging.conf # = Syslog Options # Send logs to syslog (/dev/log) instead of to file specified # by `log-file` use_syslog = False # Facility to use. If unset defaults to LOG_USER. # syslog_log_facility = LOG_LOCAL0 [sql] #connection = sqlite:var/lib/keystone/keystone.db connection = mysql://keystone:***@172.18.32.7/keystone idle_timeout = 200 [ldap] #url = ldap://localhost #tree_dn = dc=example,dc=com #user_tree_dn = ou=Users,dc=example,dc=com #role_tree_dn = ou=Roles,dc=example,dc=com #tenant_tree_dn = ou=Groups,dc=example,dc=com #user = dc=Manager,dc=example,dc=com #password = freeipa4all #suffix = cn=example,cn=com [identity] driver = keystone.identity.backends.sql.Identity [catalog] driver = keystone.catalog.backends.sql.Catalog [token] driver = keystone.token.backends.sql.Token # Amount of time a token should remain valid (in seconds) expiration = 86400 [policy] driver = keystone.policy.backends.rules.Policy [ec2] driver = keystone.contrib.ec2.backends.sql.Ec2 [filter:debug] paste.filter_factory = keystone.common.wsgi:Debug.factory [filter:token_auth] paste.filter_factory = keystone.middleware:TokenAuthMiddleware.factory [filter:admin_token_auth] paste.filter_factory = keystone.middleware:AdminTokenAuthMiddleware.factory [filter:xml_body] paste.filter_factory = keystone.middleware:XmlBodyMiddleware.factory [filter:json_body] paste.filter_factory = keystone.middleware:JsonBodyMiddleware.factory [filter:crud_extension] paste.filter_factory = keystone.contrib.admin_crud:CrudExtension.factory [filter:ec2_extension] paste.filter_factory = keystone.contrib.ec2:Ec2Extension.factory [app:public_service] paste.app_factory = keystone.service:public_app_factory [app:admin_service] paste.app_factory = keystone.service:admin_app_factory [pipeline:public_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension public_service [pipeline:admin_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension crud_extension admin_service [app:public_version_service] paste.app_factory = keystone.service:public_version_app_factory [app:admin_version_service] paste.app_factory = keystone.service:admin_version_app_factory [pipeline:public_version_api] pipeline = xml_body public_version_service [pipeline:admin_version_api] pipeline = xml_body admin_version_service [composite:main] use = egg:Paste#urlmap /v2.0 = public_api / = public_version_api [composite:admin] use = egg:Paste#urlmap /v2.0 = admin_api / = admin_version_api When I restart keystone Add tenant and user : root@keystone:~# keystone user-create --tenant_id e87f632d2c4e4f2b8dfe1fd2691d229d --name admin --pass admin --enabled true No handlers could be found for logger keystoneclient.v2_0.client Unable to communicate with identity service: 404 Not Found The resource could not be found. . (HTTP 404) Why? What can I miss? ___ 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] Change Ephemeral Disk FS
Hi, Is there a way to change the default file system of the ephemeral disk attached to an instance? By default it's ext3. Thanks, Jerico ___ 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] Change Ephemeral Disk FS
Hi, I think this only way is to edit the code like so: - go to the line 66 of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py - and change to 'default=mkfs.ext4 -L %(fs_label)s -F %(target)s', Make sure to purge your /var/lib/nova/instances/_base It worked for me :) Let me know if it's ok :) Cheers! On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote jerico.rev...@monash.eduwrote: Hi, Is there a way to change the default file system of the ephemeral disk attached to an instance? By default it's ext3. Thanks, Jerico ___ 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] Change Ephemeral Disk FS
Hi, Are you using Essex or Folsom when it worked for you? Regards, Jerico On 06/08/2012, at 8:48 PM, Sébastien Han han.sebast...@gmail.com wrote: Cool ;) On Mon, Aug 6, 2012 at 12:47 PM, Jerico Revote jerico.rev...@monash.edu wrote: Thanks Sebastien, I'll give it a shot. Jerico On 06/08/2012, at 8:02 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi, I think this only way is to edit the code like so: go to the line 66 of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py and change to 'default=mkfs.ext4 -L %(fs_label)s -F %(target)s', Make sure to purge your /var/lib/nova/instances/_base It worked for me :) Let me know if it's ok :) Cheers! On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote jerico.rev...@monash.edu wrote: Hi, Is there a way to change the default file system of the ephemeral disk attached to an instance? By default it's ext3. Thanks, Jerico ___ 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] Change Ephemeral Disk FS
I'm using Essex. Where did you make the code change? You must put the change on each nova-compute node. Enable the --verbose flag in nova.conf on your compute nodes, purge /var/lib/nova/instances/_base/'ephemeral_something', boot a new vm and watch the log. Grep for a line matching 'mkfs' My logs: nova.service [-] virt_mkfs : ['default=mkfs.ext4 -L %(fs_label)s -F %(target)s', 'linux=mkfs.ext3 -L %(fs_label)s -F %(target)s', 'windows=mkfs.ntfs --force --fast --label %(fs_label)s %(target)s'] from (pid=2343) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 nova.utils [req-4559f0ea-df70-4d86-b61d-91d0798e3e93 359076e3189b4658a4dd1b83d6313cc9 5172f50226f647ebb03ca4e4e82d056d] Running cmd (subprocess): mkfs.ext4 -L ephemeral0 -F /var/lib/nova/instances/_base/ephemeral_0_20_None from (pid=2343) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 On Mon, Aug 6, 2012 at 1:51 PM, Jerico Revote jerico.rev...@monash.eduwrote: Hi, Are you using Essex or Folsom when it worked for you? Regards, Jerico On 06/08/2012, at 8:48 PM, Sébastien Han han.sebast...@gmail.com wrote: Cool ;) On Mon, Aug 6, 2012 at 12:47 PM, Jerico Revote jerico.rev...@monash.eduwrote: Thanks Sebastien, I'll give it a shot. Jerico On 06/08/2012, at 8:02 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi, I think this only way is to edit the code like so: - go to the line 66 of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py - and change to 'default=mkfs.ext4 -L %(fs_label)s -F %(target)s', Make sure to purge your /var/lib/nova/instances/_base It worked for me :) Let me know if it's ok :) Cheers! On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote jerico.rev...@monash.eduwrote: Hi, Is there a way to change the default file system of the ephemeral disk attached to an instance? By default it's ext3. Thanks, Jerico ___ 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] KVM live block migration: stability, future, docs
Hi all, KVM block migration support in OpenStack (https://blueprints.launchpad.net/nova/+spec/kvm-block-migration) seems to be somewhat of a secret - there's almost nothing in the docs/guides (which to the contrary state that live migration is only possible with shared storage) and only a couple of mentions on list, yet it's been around since Diablo. Should this be taken to mean it's considered unstable, or just that no-one interested in documenting it understands the significance of such a feature to deployment architects? After all, decent shared storage is an expensive prospect with a pile of associated design and management overhead! I'd be happy to contribute some documentation patches (starting with the admin guide) that cover this. But first I'd like to get some confirmation that it's here to stay, which will be significant for our own large deployment. We've tested with Essex on Ubuntu Precise and seen a bit of weird file-system behaviour, which we currently suspect might be a consequence of using ext3 in the guest. But also, there seems to be some associated lag with interactive services (e.g. active VNC session) in the guest, not yet sure how this compares to the non-block live migration case. We'd really appreciate anybody actively using this feature to speak up and comment on their mileage, especially with respect to ops. I'm slightly concerned that KVM may drop this going forward (http://www.spinics.net/lists/kvm/msg72228.html), though that would be unlikely to affect anybody deploying on Precise. -- Cheers, ~Blairo ___ 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] glance error
Your glance-api server probably can't talk to your glance-registry server. Make sure glance-registry is running and that glance-api is correctly configured with its IP and port. On Aug 5, 2012, at 8:22 PM, 王鹏 breakwin...@gmail.com wrote: hello,everyone: when I over glance install and config ,and test glance index: root@openstack-controller:~# glance index Failed to show index. Got error: There was an error connecting to a server Details: [Errno 111] Connection refused about config I just change the token could you help me ? why this error happen? thank you. ___ 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] Interested in ISCSI CHAP
Hi everyone, I remember that once in a Cinder IRC meeting, John mentioned the implementation of CHAP. Is it related to this blueprint: https://blueprints.launchpad.net/cinder/+spec/iscsi-chap ? I am interested in this topic, and not sure whether someone is already doing it. If no one has taken this job, can it be assigned to me? Best wishes. Vincent Hou (侯胜博) Software Engineer, Standards Growth Team, Emerging Technology Institute, IBM China Software Development Lab Tel: 86-10-82450778 Fax: 86-10-82453660 Notes ID: Sheng Bo Hou/China/IBM@IBMCNE-mail: sb...@cn.ibm.com Address:3F Ring, Building 28 Zhongguancun Software Park, 8 Dongbeiwang West Road, Haidian District, Beijing, P.R.C.100193 ___ 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] Change Ephemeral Disk FS
Oh I didn't know that one! Thanks ;) On Mon, Aug 6, 2012 at 6:07 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: No need to edit code, there is a config option for this: ## (MultiStrOpt) mkfs commands for ephemeral device. The format is os_type=mkfs command Put the following in nova.conf: virt_mkfs=default=mkfs.ext4 -L %(fs_label)s -F %(target)s On Aug 6, 2012, at 3:02 AM, Sébastien Han han.sebast...@gmail.com wrote: Hi, I think this only way is to edit the code like so: - go to the line 66 of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py - and change to 'default=mkfs.ext4 -L %(fs_label)s -F %(target)s', Make sure to purge your /var/lib/nova/instances/_base It worked for me :) Let me know if it's ok :) Cheers! On Mon, Aug 6, 2012 at 10:47 AM, Jerico Revote jerico.rev...@monash.eduwrote: Hi, Is there a way to change the default file system of the ephemeral disk attached to an instance? By default it's ext3. Thanks, Jerico ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-dev] [Quantum] Multi-host implementation
Hi Nachi, I've reviewed the code and added comments. I'd like to see at least a basic spec describing the proposed approach (need only be a couple paragraphs, perhaps with a diagram) linked to the blueprint so we can have a design discussion around it. Thanks, Dan On Fri, Aug 3, 2012 at 1:03 PM, Nachi Ueno na...@nttmcl.com wrote: Hi folks Sorry. I added openstack-...@lists.openstack.org in this discussion. 2012/8/3 Nati Ueno nati.u...@gmail.com: Hi folks Gary Thank you for your comment. I wanna discuss your point on the mailing list. Yusuke pushed Multi-host implementation for review. https://review.openstack.org/#/c/10766/2 This patch changes only quantum-dhcp-agent side. Gary's point is we should have host attribute on the port for scheduling. I agree with Gary. In the nova, vm has available_zone for scheduling. So Instead of using host properties. How about use available_zone for port? Format of availability_zone is something like this available_zone=zone_name:host. We can also add availability_zone attribute for the network as a default value of port. We can write this until next Monday. However I'm not sure quantum community will accept this or not, so I'm asking here. If there are no objections, we will push zone version for review. Thanks Nachi ___ 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-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Quantum] Update policy of device_id
On Fri, Aug 3, 2012 at 12:33 PM, Nati Ueno nati.u...@gmail.com wrote: Hi folks I report this bug recently. device_id should not be updated twice https://bugs.launchpad.net/quantum/+bug/1031473 Now, a user can update device_id which may cause problem. Yeah, ideally this field could only be updated by the 'service' user (i.e., nova or another openstack service). This is related to port id spec for nova boot. https://bugs.launchpad.net/nova/+bug/1031096 My question is how we should deal with port on the failure or deletion. My patch will delete the port on failure or deletion https://review.openstack.org/#/c/10639/ Another spec could be update port device_id for None. But this is depends on how we solve bug 1031473. Updating to empty-string/None is more what I had been thinking of, but I don't have my head fully wrapped around this. As I mentioned when we chatted about this in person, Amazon's elastic network interfaces (ENIs) are similar to quantum ports, and they have a specific flag that indicates whether the ENI should be deleted when the instance is deleted or not: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/using-eni.html#change_term_behavior There are some use cases when we would want to keep it around, and just reattach it to a new virtual server. Dan Any thought? -- Nachi Ueno email:nati.u...@gmail.com twitter:http://twitter.com/nati ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Netstack] [openstack-dev] [Quantum] Multi-host implementation
Hi Dan Thank you for pointing this. Yusuke updated design spec. https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp 2012/8/6 Dan Wendlandt d...@nicira.com: Hi Nachi, I've reviewed the code and added comments. I'd like to see at least a basic spec describing the proposed approach (need only be a couple paragraphs, perhaps with a diagram) linked to the blueprint so we can have a design discussion around it. Thanks, Dan On Fri, Aug 3, 2012 at 1:03 PM, Nachi Ueno na...@nttmcl.com wrote: Hi folks Sorry. I added openstack-...@lists.openstack.org in this discussion. 2012/8/3 Nati Ueno nati.u...@gmail.com: Hi folks Gary Thank you for your comment. I wanna discuss your point on the mailing list. Yusuke pushed Multi-host implementation for review. https://review.openstack.org/#/c/10766/2 This patch changes only quantum-dhcp-agent side. Gary's point is we should have host attribute on the port for scheduling. I agree with Gary. In the nova, vm has available_zone for scheduling. So Instead of using host properties. How about use available_zone for port? Format of availability_zone is something like this available_zone=zone_name:host. We can also add availability_zone attribute for the network as a default value of port. We can write this until next Monday. However I'm not sure quantum community will accept this or not, so I'm asking here. If there are no objections, we will push zone version for review. Thanks Nachi ___ 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-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- Mailing list: https://launchpad.net/~netstack Post to : netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack 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] Swift 1.6.0 released
I'm happy to announce that Swift 1.6.0 has been released. You can get the tarball at https://launchpad.net/swift/folsom/1.6.0. As always, you can upgrade your production Swift clusters to this new version with no downtime to your clients. The complete changelog for this release is at https://github.com/openstack/swift/blob/master/CHANGELOG, but I'd like to highlight a few of the more significant changes. First, the bin/swift CLI client and swift/common/client.py have been moved to the new python-swiftclient OpenStack project. This change allows other projects to use an officially supported client without having to install all of Swift. Most immediately, Glance and Horizon will be able to use this. The python-swiftclient project is also helpful to non-OpenStack projects wanting to integrate with Swift. Note that Swift now depends on the new python-swiftclient project. Secondly, Swift now includes the Keystone middleware keystoneauth. This now matches the pattern set by other OpenStack projects and is the logical place to support this part of the Swift-Keystone integration. Lastly, the swift-dispersion-report now works with a replica count other than three. While this allows the tool to be more useful, it does necessitate a format change to the JSON returned. Therefore existing tools using the output of swift-dispersion-report will need to be updated. There are many other updates and bugfixes in this release. I encourage you to read the entire changelog. On the contributor side, this Swift release is the result of the work of 16 contributors (`git shortlog --no-merges -nes 1.5.0..1.6.0 | wc -l`), 5 of whom are new to Swift. This brings the total contributor count for Swift to 71. The 5 new contributors to swift are: - François Charlier (francois.charl...@enovance.com) - Iryoung Jeong (iryo...@gmail.com) - Tsuyuzaki Kota (tsuyuzaki.k...@lab.ntt.co.jp) - Dan Prince (dpri...@redhat.com) - Vincent Untz (vu...@suse.com) Thank you to everyone who contributed for your hard work and commitment to making Swift the most reliable, open, and production-ready object storage system in the world. --John smime.p7s Description: S/MIME cryptographic 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] Can't ssh to anything not on control node
https://answers.launchpad.net/nova/+question/204852 Can anyone help me? I'm banging my head against a brick wall. I can't ever get an instance on anything but the control node to be accessible. Thanks Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] LBaaS IRC meeting notes
Hi, Below are the meeting notes from the IRC meeting about LBaaS which took place on Aug 2. The logs can be found at http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-17.00.log.html [19:18:27 .. 19:56:41] === Status on our side === https://github.com/Mirantis/openstack-lbaas * HAproxy and ACE implemented to some level. * F5 to be finished in 6 weeks. By that time driver API will be stable. * Support for device capabilities (drivers report them, users request them) on its way to master. === Discussion with Dan Went of Quantum === Dan said: * Quantum is moving up the stack: L2 in essex, L3 in folsom, and in Grizzly we'll be moving into L4-L7 * Many people in Quantum are generally interested in LBaaS * We need to make sure we're not duplicating effort by developing our own CLI/GUI for LBaaS. We should at least integrate with the Quantum CLI framework and generally collaborate with the Quantum community (circulate blueprints and POC). The next meeting will take place Aug 9, 19:00 UTC at #openstack-meeting. -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov ___ 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] Configuring with devstack for multiple hardware nodes
Hi, I just posted the following at http://forums.openstack.org/viewtopic.php?f=15t=1435, then realized this mailing list might be a better place to ask the question. In summary, I've cobbled together devstack-based nodes to exercise quantum/openvswitch (when I say cobbled, I mean my result is the combination of information from wiki and from devstack, and elsewhere to create my localrc files, since there is no one definitive template that I could use, and it seems that devstack examples are not current with what is happening on Folsom). One node is a controller, one is a compute node. I can launch using horizon on the controller, VMs launched on the controller are pingable, but ones launched on the compute node are not. The big difference I can see is a missing gateway interface on the controller (on gw-* displayed when I run ifconfig). By inspection of the logs, I can see that the VMs are unable to establish a network, and I think the missing gateway interface may be the root cause for that. Below are details: Two hosts, one configured as a controller, the other configured as a compute node. Each host is dual homed, network for eth0 is connected to the local intranet, network for eth1 is configured as a local net 192.168.3.0 On the controller host, I used devstack with the following localrc (which is an aggregation of stuff I found on the devstack site, and stuff I found recently on the quantum wiki -- it would be nice if complete templates for a controller and compute node supporting devstack and openvswitch were published on the devstack site or the wiki, perhaps since we are not yet at Folsom it makes sense they don't exist, if I get something working, I will share my configuration in the entirety at whatever is the most appropriate place). Anyway, controller host localrc is: HOST_IP=192.168.3.1 FLAT_INTERFACE=eth1 FIXED_RANGE=10.4.128.0/20 FIXED_NETWORK_SIZE=4096 FLOATING_RANGE=192.168.3.128/25 MULTI_HOST=True LOGFILE=/opt/stack/logs/stack.sh.log ADMIN_PASSWORD=password MYSQL_PASSWORD=password RABBIT_PASSWORD=password SERVICE_PASSWORD=password SERVICE_TOKEN=xyzpdqlazydog ENABLED_SERVICES=g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,mysql,rabbit,openstackx,q-svc,quantum,q-agt,q-dhcp Q_PLUGIN=openvswitch Q_AUTH_STRATEGY=noauth If I run stack on this host, I get the following nova.conf: [DEFAULT] verbose=True auth_strategy=keystone allow_resize_to_same_host=True root_helper=sudo /usr/local/bin/nova-rootwrap /etc/nova/rootwrap.conf compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler dhcpbridge_flagfile=/etc/nova/nova.conf fixed_range=10.4.128.0/20 s3_host=192.168.3.1 s3_port= network_manager=nova.network.quantum.manager.QuantumManager quantum_connection_host=localhost quantum_connection_port=9696 quantum_use_dhcp=True libvirt_vif_type=ethernet libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions my_ip=192.168.3.1 public_interface=br100 vlan_interface=eth0 flat_network_bridge=br100 flat_interface=eth1 sql_connection=mysql://root:password@localhost/nova?charset=utf8 libvirt_type=kvm libvirt_cpu_mode=none instance_name_template=instance-%08x novncproxy_base_url=http://192.168.3.1:6080/vnc_auto.html xvpvncproxy_base_url=http://192.168.3.1:6081/console vncserver_listen=127.0.0.1 vncserver_proxyclient_address=127.0.0.1 api_paste_config=/etc/nova/api-paste.ini image_service=nova.image.glance.GlanceImageService ec2_dmz_host=192.168.3.1 rabbit_host=localhost rabbit_password=password glance_api_servers=192.168.3.1:9292 force_dhcp_release=True multi_host=True send_arp_for_ha=True logging_context_format_string=%(asctime)s %(color)s%(levelname)s %(name)s [^[[01;36m%(request_id)s ^[[00;36m%(user_name)s %(project_name)s%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m logging_default_format_string=%(asctime)s %(color)s%(levelname)s %(name)s [^[[00;36m-%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m logging_debug_format_suffix=^[[00;33mfrom (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d^[[00m logging_exception_prefix=%(color)s%(asctime)s TRACE %(name)s ^[[01;35m%(instance)s^[[00m compute_driver=libvirt.LibvirtDriver firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver enabled_apis=ec2,osapi_compute,osapi_volume,metadata If I run horizon, I can launch vms and ping them. If I look at the logs generated by the VMs, they are able to get a network. Furthermore, I get the following network interface in addition to the tap interfaces generated for each VM: gw-4f16e8db-20 Link encap:Ethernet HWaddr fa:16:3e:08:e0:2d inet addr:10.4.128.1 Bcast:10.4.143.255 Mask:255.255.240.0 inet6 addr: fe80::f816:3eff:fe08:e02d/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0
Re: [Openstack] Configuring with devstack for multiple hardware nodes
Hi Syd, There should not be an additional gateway interface on the compute nodes, only the node that has n-net in ENABLED_SERVICES. I'm assuming you want to use the OVSQuantumPlugin? Can you also attach /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini from your two nodes? Also if you are interested in trying out the folsom quantum code the following link should help you get running: http://wiki.openstack.org/RunningQuantumV2Api Aaron On Mon, Aug 6, 2012 at 4:30 PM, Syd (Sydney) Logan slo...@broadcom.comwrote: Hi, ** ** I just posted the following at http://forums.openstack.org/viewtopic.php?f=15t=1435, then realized this mailing list might be a better place to ask the question. ** ** In summary, I’ve cobbled together devstack-based nodes to exercise quantum/openvswitch (when I say cobbled, I mean my result is the combination of information from wiki and from devstack, and elsewhere to create my localrc files, since there is no one definitive template that I could use, and it seems that devstack examples are not current with what is happening on Folsom). One node is a controller, one is a compute node. I can launch using horizon on the controller, VMs launched on the controller are pingable, but ones launched on the compute node are not. The big difference I can see is a missing gateway interface on the controller (on gw-* displayed when I run ifconfig). By inspection of the logs, I can see that the VMs are unable to establish a network, and I think the missing gateway interface may be the root cause for that. ** ** Below are details: ** ** Two hosts, one configured as a controller, the other configured as a compute node. Each host is dual homed, network for eth0 is connected to the local intranet, network for eth1 is configured as a local net 192.168.3.0 On the controller host, I used devstack with the following localrc (which is an aggregation of stuff I found on the devstack site, and stuff I found recently on the quantum wiki -- it would be nice if complete templates for a controller and compute node supporting devstack and openvswitch were published on the devstack site or the wiki, perhaps since we are not yet at Folsom it makes sense they don't exist, if I get something working, I will share my configuration in the entirety at whatever is the most appropriate place). Anyway, controller host localrc is: ** ** HOST_IP=192.168.3.1 FLAT_INTERFACE=eth1 FIXED_RANGE=10.4.128.0/20 FIXED_NETWORK_SIZE=4096 FLOATING_RANGE=192.168.3.128/25 MULTI_HOST=True LOGFILE=/opt/stack/logs/stack.sh.log ADMIN_PASSWORD=password MYSQL_PASSWORD=password RABBIT_PASSWORD=password SERVICE_PASSWORD=password SERVICE_TOKEN=xyzpdqlazydog ENABLED_SERVICES=g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,mysql,rabbit,openstackx,q-svc,quantum,q-agt,q-dhcp Q_PLUGIN=openvswitch Q_AUTH_STRATEGY=noauth ** ** If I run stack on this host, I get the following nova.conf: ** ** [DEFAULT] verbose=True auth_strategy=keystone allow_resize_to_same_host=True root_helper=sudo /usr/local/bin/nova-rootwrap /etc/nova/rootwrap.conf compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler** ** dhcpbridge_flagfile=/etc/nova/nova.conf fixed_range=10.4.128.0/20 s3_host=192.168.3.1 s3_port= network_manager=nova.network.quantum.manager.QuantumManager quantum_connection_host=localhost quantum_connection_port=9696 quantum_use_dhcp=True libvirt_vif_type=ethernet libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver** ** osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions my_ip=192.168.3.1 public_interface=br100 vlan_interface=eth0 flat_network_bridge=br100 flat_interface=eth1 sql_connection=mysql://root:password@localhost/nova?charset=utf8 libvirt_type=kvm libvirt_cpu_mode=none instance_name_template=instance-%08x novncproxy_base_url=http://192.168.3.1:6080/vnc_auto.html xvpvncproxy_base_url=http://192.168.3.1:6081/console vncserver_listen=127.0.0.1 vncserver_proxyclient_address=127.0.0.1 api_paste_config=/etc/nova/api-paste.ini image_service=nova.image.glance.GlanceImageService ec2_dmz_host=192.168.3.1 rabbit_host=localhost rabbit_password=password glance_api_servers=192.168.3.1:9292 force_dhcp_release=True multi_host=True send_arp_for_ha=True logging_context_format_string=%(asctime)s %(color)s%(levelname)s %(name)s [^[[01;36m%(request_id)s ^[[00;36m%(user_name)s %(project_name)s%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m logging_default_format_string=%(asctime)s
[Openstack] why [Errno 111] ECONNREFUSED ????please help me
Hi,every: That is my first install swift,I according to objectstorage-adminguide-essex.pdf from www.openstack.org. when I after install ,Verify the Installation, use swift -V 2 -A http://AUTH_HOSTNAME:5000/v2.0 -U adminUser:admin -K 012345SECRET99TOKEN012345 stat [Errno 111] ECONNREFUSED why? before this error ,everything is ok. there are not erroe in syslog why ? what can i do for it what'mean -U option? system user?or keystone tenant admin ? please help me! ___ 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] why [Errno 111] ECONNREFUSED ????please help me
Replace AUTH_HOSTNAME with the IP/hostname port of your keystone server (e.g. 127.0.0.1:35357). -Dolph On Mon, Aug 6, 2012 at 9:15 PM, 王鹏 breakwin...@gmail.com wrote: Hi,every: That is my first install swift,I according to objectstorage-adminguide-essex.pdf from www.openstack.org. when I after install ,Verify the Installation, use swift -V 2 -A http://AUTH_HOSTNAME:5000/v2.0 -U adminUser:admin -K 012345SECRET99TOKEN012345 stat [Errno 111] ECONNREFUSED why? before this error ,everything is ok. there are not erroe in syslog why ? what can i do for it what'mean -U option? system user?or keystone tenant admin ? please help me! ___ 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] Networking error while creating VM
Hi- I'm seeing these errors in the COMPUTE-NODE nova-compute.log while bringing up the virtual machines. 2012-08-07 04:45:46 DEBUG nova.rpc.amqp [req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8 a17de6f647b14739acb33f09d246f72e] Pool creating new connection from (pid=27708) create /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:60 2012-08-07 04:45:46 INFO nova.rpc.common [req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8 a17de6f647b14739acb33f09d246f72e] Connected to AMQP server on 10.232.90.82:5672 2012-08-07 04:45:48 ERROR nova.compute.manager [req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8 a17de6f647b14739acb33f09d246f72e] [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] Instance failed network setup 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] Traceback (most recent call last): 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 565, in _allocate_network 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] requested_networks=requested_networks) 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/network/api.py, line 170, in allocate_for_instance 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] 'args': args}) 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/rpc/__init__.py, line 68, in call 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] return _get_impl().call(context, topic, msg, timeout) 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 674, in call 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] return rpc_amqp.call(context, topic, msg, timeout, Connection.pool) 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 343, in call 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] rv = list(rv) 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 311, in __iter__ 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] raise result 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] RemoteError: Remote error: TypeError 'NoneType' object has no attribute '__getitem__' 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] [u'Traceback (most recent call last):\n', u' File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 252, in _process_data\nrval = node_func(context=ctxt, **node_args)\n', u' File /usr/lib/python2.7/dist-packages/nova/network/quantum/manager.py, line 357, in allocate_for_instance\nvif_rec, network[\'net_tenant_id\'])\n', u' File /usr/lib/python2.7/dist-packages/nova/utils.py, line 945, in inner\nretval = f(*args, **kwargs)\n', u' File /usr/lib/python2.7/dist-packages/nova/network/quantum/manager.py, line 456, in enable_dhcp\nsubnet[\'network_id\'], project_id)\n', u' File /usr/lib/python2.7/dist-packages/nova/network/quantum/manager.py, line 663, in get_dhcp_hosts_text\nips = self.ipam.get_allocated_ips(context, subnet_id, project_id)\n', u' File /usr/lib/python2.7/dist-packages/nova/network/quantum/nova_ipam_lib.py, line 238, in get_allocated_ips\nallocated_ips.append((ip[\'address\'], vif[\'uuid\']))\n', uTypeError: 'NoneType' object has no attribute '__getitem__'\n]. 2012-08-07 04:45:48 TRACE nova.compute.manager [instance: e0d0aa4b-6865-46da-a8f4-9257dd838ab4] 2012-08-07 04:45:48 ERROR nova.rpc.amqp [req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8 a17de6f647b14739acb33f09d246f72e] Exception during message handling 2012-08-07 04:45:48 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-08-07 04:45:48 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 253, in _process_data 2012-08-07 04:45:48 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-08-07 04:45:48 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-08-07 04:45:48 TRACE nova.rpc.amqp return f(*args, **kw) 2012-08-07 04:45:48 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 183, in decorated_function
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #312
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/312/Project:quantal_folsom_nova_trunkDate of build:Mon, 06 Aug 2012 10:01:54 -0400Build duration:3 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesOnly log deprecated config warnings once.by dprinceeditnova/common/deprecated.pyeditnova/tests/test_deprecated.pyConsole Output[...truncated 4930 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-08098b00-6380-4dc7-9654-90d8dfc9032b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpyx6ZAR/novamk-build-deps -i -r -t apt-get -y /tmp/tmpyx6ZAR/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log be6d2253d61fae63b5c829960cbf163c50c2efeb..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061003~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061003~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-08098b00-6380-4dc7-9654-90d8dfc9032b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-08098b00-6380-4dc7-9654-90d8dfc9032b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_keystone_trunk #25
Title: quantal_folsom_keystone_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/25/Project:quantal_folsom_keystone_trunkDate of build:Mon, 06 Aug 2012 12:01:58 -0400Build duration:4 min 46 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUse user home dir as default for cacheby ayoungeditkeystone/middleware/auth_token.pyConsole Output[...truncated 5011 lines...]Build-Time: 74Distribution: quantal-folsomFail-Stage: buildInstall-Time: 49Job: keystone_2012.2+git201208061202~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 143Source-Version: 2012.2+git201208061202~quantal-0ubuntu1Space: 8452Status: attemptedVersion: 2012.2+git201208061202~quantal-0ubuntu1Finished at 20120806-1206Build needed 00:02:23, 8452k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061202~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmpKNDAYV/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpKNDAYV/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061202~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061202~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201208061202~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201208061202~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061202~quantal-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.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061202~quantal-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: quantal_folsom_nova_trunk #314
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/314/Project:quantal_folsom_nova_trunkDate of build:Mon, 06 Aug 2012 13:01:58 -0400Build duration:2 min 55 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds per-user-quotas support for more detailed quotas managementby kylin7.sgeditnova/quota.pyeditnova/exception.pyaddnova/db/sqlalchemy/migrate_repo/versions/115_make_user_quotas_key_and_value.pyeditnova/tests/policy.jsoneditnova/db/sqlalchemy/models.pyeditbin/nova-manageeditnova/api/openstack/compute/contrib/quotas.pyeditnova/db/api.pyeditnova/api/openstack/compute/limits.pyeditnova/tests/test_quota.pyeditnova/db/sqlalchemy/api.pyeditetc/nova/policy.jsonConsole Output[...truncated 4942 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8a719494-71d0-40c1-b83a-8e3aa0e8b4ee', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpvfxvEj/novamk-build-deps -i -r -t apt-get -y /tmp/tmpvfxvEj/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log be6d2253d61fae63b5c829960cbf163c50c2efeb..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061302~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061302~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8a719494-71d0-40c1-b83a-8e3aa0e8b4ee', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8a719494-71d0-40c1-b83a-8e3aa0e8b4ee', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #325
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/325/Project:precise_folsom_nova_trunkDate of build:Mon, 06 Aug 2012 15:01:55 -0400Build duration:2 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove old exception typeby stanislaw.pituchaeditnova/db/sqlalchemy/migration.pyRemove unused InstanceInfo class.by dprinceeditnova/virt/fake.pyeditnova/virt/baremetal/driver.pyeditnova/virt/driver.pyeditnova/virt/libvirt/driver.pyConsole Output[...truncated 4115 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-3b386108-be13-4610-b017-f6b5d6c03137', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmphBmlM3/novamk-build-deps -i -r -t apt-get -y /tmp/tmphBmlM3/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log be6d2253d61fae63b5c829960cbf163c50c2efeb..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208061502~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208061502~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-3b386108-be13-4610-b017-f6b5d6c03137', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-3b386108-be13-4610-b017-f6b5d6c03137', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #317
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/317/Project:quantal_folsom_nova_trunkDate of build:Mon, 06 Aug 2012 15:02:00 -0400Build duration:3 min 40 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove old exception typeby stanislaw.pituchaeditnova/db/sqlalchemy/migration.pyRemove unused InstanceInfo class.by dprinceeditnova/virt/libvirt/driver.pyeditnova/virt/driver.pyeditnova/virt/baremetal/driver.pyeditnova/virt/fake.pyConsole Output[...truncated 4965 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9b7adb7b-3ff0-4dbf-bc67-888a382e48f5', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpJgUGNe/novamk-build-deps -i -r -t apt-get -y /tmp/tmpJgUGNe/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log be6d2253d61fae63b5c829960cbf163c50c2efeb..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061503~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061503~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9b7adb7b-3ff0-4dbf-bc67-888a382e48f5', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9b7adb7b-3ff0-4dbf-bc67-888a382e48f5', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: quantal_folsom_python-glanceclient_trunk #53
Title: quantal_folsom_python-glanceclient_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-glanceclient_trunk/53/Project:quantal_folsom_python-glanceclient_trunkDate of build:Mon, 06 Aug 2012 15:45:59 -0400Build duration:2 min 41 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 2231 lines...]Finished at 20120806-1548Build needed 00:01:12, 1284k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/folsom-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/folsom-trunk-testing', 'python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_source.changes']gpg: Signature made Mon Aug 6 15:47:18 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Aug 6 15:47:18 2012 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/tmp_Hy46U/python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp_Hy46U/python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1.dsc: done. Uploading python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal.orig.tar.gz: done. Uploading python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1.debian.tar.gz: done. Uploading python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-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', 'quantal-folsom', 'python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-glanceclient/python-glanceclient_0.2.0.6.a511e6a+git201208021401~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom']Pushed up to revision 16.INFO:root:Storing current commit for next build: a511e6a05e0f8763fb57dea3af86602a7883604cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom-proposed /tmp/tmp_Hy46U/python-glanceclientmk-build-deps -i -r -t apt-get -y /tmp/tmp_Hy46U/python-glanceclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom --forcedch -b -D quantal --newversion 1:0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1:0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom python-glanceclient_0.2.0.10.18543b1+git201208061546~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsomEmail 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: quantal_folsom_python-swiftclient_trunk #15
Title: quantal_folsom_python-swiftclient_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-swiftclient_trunk/15/Project:quantal_folsom_python-swiftclient_trunkDate of build:Mon, 06 Aug 2012 15:54:38 -0400Build duration:1 min 41 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 1708 lines...]Finished at 20120806-1556Build needed 00:00:36, 1004k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/folsom-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/folsom-trunk-testing', 'python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_source.changes']gpg: Signature made Mon Aug 6 15:55:33 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Aug 6 15:55:33 2012 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/tmp8IvIqo/python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp8IvIqo/python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1.dsc: done. Uploading python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal.orig.tar.gz: done. Uploading python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1.debian.tar.gz: done. Uploading python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-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', 'quantal-folsom', 'python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-swiftclient/python-swiftclient_2012.2+git201206271601~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-swiftclient/quantal-folsom']Pushed up to revision 10.INFO:root:Storing current commit for next build: 7618feaeb12c4128ebe31ed7af3110d15746d0d7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-swiftclient/quantal-folsom-proposed /tmp/tmp8IvIqo/python-swiftclientmk-build-deps -i -r -t apt-get -y /tmp/tmp8IvIqo/python-swiftclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-swiftclient/quantal-folsom --forcedch -b -D quantal --newversion 1:1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1:1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom python-swiftclient_1.1.1.7.1f6096e+git201208061554~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-swiftclient/quantal-folsomEmail 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: quantal_folsom_keystone_trunk #28
Title: quantal_folsom_keystone_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/28/Project:quantal_folsom_keystone_trunkDate of build:Mon, 06 Aug 2012 16:52:19 -0400Build duration:4 min 46 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5011 lines...]Build-Time: 75Distribution: quantal-folsomFail-Stage: buildInstall-Time: 52Job: keystone_2012.2+git201208061652~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 144Source-Version: 2012.2+git201208061652~quantal-0ubuntu1Space: 8452Status: attemptedVersion: 2012.2+git201208061652~quantal-0ubuntu1Finished at 20120806-1657Build needed 00:02:24, 8452k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061652~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmpqHZnde/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpqHZnde/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061652~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061652~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201208061652~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201208061652~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061652~quantal-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.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061652~quantal-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: quantal_folsom_keystone_trunk #31
Title: quantal_folsom_keystone_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/31/Project:quantal_folsom_keystone_trunkDate of build:Mon, 06 Aug 2012 17:08:32 -0400Build duration:4 min 3 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5011 lines...]Build-Time: 62Distribution: quantal-folsomFail-Stage: buildInstall-Time: 39Job: keystone_2012.2+git201208061708~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 115Source-Version: 2012.2+git201208061708~quantal-0ubuntu1Space: 8452Status: attemptedVersion: 2012.2+git201208061708~quantal-0ubuntu1Finished at 20120806-1712Build needed 00:01:55, 8452k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061708~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmpHPRxD6/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpHPRxD6/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061708~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061708~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201208061708~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201208061708~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061708~quantal-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.getcwdu(), 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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061708~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_deploy #193
Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/193/Project:precise_folsom_deployDate of build:Mon, 06 Aug 2012 18:42:30 -0400Build duration:43 secBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 416 lines...]DEBUG: Adding option to 'glance-release' to deploy config: glanceDEBUG: Using the following config:{u'glance': {u'glance-release': u'qa-precise-folsom'}, u'keystone': {u'admin-password': u'openstack', u'admin-token': u'ubuntutesting', u'keystone-release': u'qa-precise-folsom'}, u'nova-cloud-controller': {u'config-flags': u'quota_instances=1000,quota_cores=20,quota-ram=20,quota_volumes=1000,quota_gigabytes=1,quota_floating_ips=1000',u'network-manager': u'FlatDHCPManager',u'nova-release': u'qa-precise-folsom'}, u'nova-compute': {u'config-flags': u'auto_assign_floating_ip=True', u'nova-release': u'qa-precise-folsom'}, u'nova-volume': {u'nova-release': u'qa-precise-folsom', u'overwrite': u'true'}}DEBUG: Calling 'juju status'...DEBUG: Deploying with timeout 2700 sec.DEBUG: Calling: juju deploy --config=/tmp/tmp3NIGhx --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computeERROR: Juju command returned non-zero: juju deploy --config=/tmp/tmp3NIGhx --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-compute- Deploying nova-compute in group 1/1Traceback (most recent call last): File "/var/lib/jenkins/tools/juju-deployer/deployer.py", line 202, in juju_call(cmd) File "/var/lib/jenkins/tools/juju-deployer/utils.py", line 142, in juju_callraise ExceptionException+ rc=1+ echo 'Deployer returned: 1'Deployer returned: 1+ [[ 1 != 0 ]]+ echo 'Collating logs...'Collating logs...+ /var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py -o logs2012-08-06 18:43:07,347 INFO Connecting to environment...2012-08-06 18:43:08,180 INFO Connected to environment.2012-08-06 18:43:08,366 INFO 'status' command finished successfullyINFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail 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_folsom_deploy #194
Title: precise_folsom_deploy General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/194/Project:precise_folsom_deployDate of build:Mon, 06 Aug 2012 18:44:19 -0400Build duration:13 minBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 2374 lines...] -> Relation: nova-cloud-controller:identity-service <-> keystone:identity-service -> Relation: glance:shared-db <-> mysql:shared-db -> Relation: glance:identity-service <-> keystone:identity-service -> Relation: nova-volume:shared-db <-> mysql:shared-db -> Relation: nova-volume:amqp <-> rabbitmq:amqp -> Relation: openstack-dashboard:identity-service <-> keystone:identity-service -> Relation: nova-compute:shared-db <-> mysql:shared-db -> Relation: nova-compute:amqp <-> rabbitmq:amqp -> Relation: nova-compute:image-service <-> glance:image-service -> Relation: nova-compute:network-manager <-> nova-cloud-controller:network-manager -> Relation: nova-compute:identity-service <-> keystone:identity-service- Ensuring relation state- Deployment complete in 807 seconds.- Juju command log:juju deploy --config=/tmp/tmpI_Iwhl --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computejuju deploy --config=/tmp/tmpI_Iwhl --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumejuju deploy --config=/tmp/tmpI_Iwhl --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerjuju deploy --config=/tmp/tmpI_Iwhl --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystonejuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmqjuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:mysql mysqljuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:openstack-dashboard openstack-dashboardjuju deploy --config=/tmp/tmpI_Iwhl --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:glance glancejuju add-relation keystone:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:amqp rabbitmq:amqpjuju add-relation nova-cloud-controller:image-service glance:image-servicejuju add-relation nova-cloud-controller:identity-service keystone:identity-servicejuju add-relation glance:shared-db mysql:shared-dbjuju add-relation glance:identity-service keystone:identity-servicejuju add-relation nova-volume:shared-db mysql:shared-dbjuju add-relation nova-volume:amqp rabbitmq:amqpjuju add-relation openstack-dashboard:identity-service keystone:identity-servicejuju add-relation nova-compute:shared-db mysql:shared-dbjuju add-relation nova-compute:amqp rabbitmq:amqpjuju add-relation nova-compute:image-service glance:image-servicejuju add-relation nova-compute:network-manager nova-cloud-controller:network-managerjuju add-relation nova-compute:identity-service keystone:identity-service+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build precise_folsom_coverage+ exit 0Archiving artifactsEmail 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: quantal_folsom_keystone_trunk #32
Title: quantal_folsom_keystone_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/32/Project:quantal_folsom_keystone_trunkDate of build:Mon, 06 Aug 2012 19:13:15 -0400Build duration:4 min 58 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 4792 lines...]Build-Time: 77Distribution: quantal-folsomFail-Stage: buildInstall-Time: 50Job: keystone_2012.2+git201208061913~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 143Source-Version: 2012.2+git201208061913~quantal-0ubuntu1Space: 8488Status: attemptedVersion: 2012.2+git201208061913~quantal-0ubuntu1Finished at 20120806-1918Build needed 00:02:23, 8488k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061913~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmpRYRvZt/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpRYRvZt/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208061913~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208061913~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201208061913~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201208061913~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in build.push_testing_branch()subprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061913~quantal-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.getcwdu(), 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 135, in build.push_testing_branch()subprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201208061913~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #197
Title: precise_folsom_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/197/Project:precise_folsom_deployDate of build:Mon, 06 Aug 2012 20:14:04 -0400Build duration:46 minBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 8858 lines...]INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-08.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-08.os.magners.qa.lexingtonINFO:root:Setting up connection to test-11.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-10.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 91, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #198
Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/198/Project:precise_folsom_deployDate of build:Mon, 06 Aug 2012 21:00:13 -0400Build duration:36 secBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 305 lines...]copying files for distro: precise-i386trying hardlink /var/www/cobbler/ks_mirror/precise-i386/linux -> /var/www/cobbler/images/precise-i386/linuxtrying hardlink /var/www/cobbler/ks_mirror/precise-i386/initrd.gz -> /var/www/cobbler/images/precise-i386/initrd.gzcopying files for distro: quantal-x86_64trying hardlink /var/www/cobbler/ks_mirror/quantal-x86_64/linux -> /var/www/cobbler/images/quantal-x86_64/linuxtrying hardlink /var/www/cobbler/ks_mirror/quantal-x86_64/initrd.gz -> /var/www/cobbler/images/quantal-x86_64/initrd.gzcopying files for distro: precise-i386-maas-ephemeraltrying hardlink /var/lib/maas/ephemeral/precise/ephemeral/i386/20120424/kernel -> /var/www/cobbler/images/precise-i386-maas-ephemeral/kerneltrying hardlink /var/lib/maas/ephemeral/precise/ephemeral/i386/20120424/initrd -> /var/www/cobbler/images/precise-i386-maas-ephemeral/initrdcopying files for distro: maverick-x86_64trying hardlink /var/www/cobbler/ks_mirror/maverick-x86_64/linux -> /var/www/cobbler/images/maverick-x86_64/linuxtrying hardlink /var/www/cobbler/ks_mirror/maverick-x86_64/initrd.gz -> /var/www/cobbler/images/maverick-x86_64/initrd.gzcopying files for distro: lucid-x86_64trying hardlink /var/www/cobbler/ks_mirror/lucid-x86_64/linux -> /var/www/cobbler/images/lucid-x86_64/linuxtrying symlink /var/www/cobbler/ks_mirror/lucid-x86_64/linux -> /var/www/cobbler/images/lucid-x86_64/linuxrunning: /usr/bin/sha1sum /var/www/cobbler/ks_mirror/lucid-x86_64/linuxreceived on stdout: 88e20362dba5e9f6a41ed432bbf81928f8257de9 /var/www/cobbler/ks_mirror/lucid-x86_64/linuxreceived on stderr: trying to create cache file /var/www/cobbler/images/.link_cache/88e20362dba5e9f6a41ed432bbf81928f8257de9copying: /var/www/cobbler/ks_mirror/lucid-x86_64/linux -> /var/www/cobbler/images/.link_cache/88e20362dba5e9f6a41ed432bbf81928f8257de9trying cachelink /var/www/cobbler/ks_mirror/lucid-x86_64/linux -> /var/www/cobbler/images/.link_cache/88e20362dba5e9f6a41ed432bbf81928f8257de9 -> /var/www/cobbler/images/lucid-x86_64/linuxcopying: /var/www/cobbler/ks_mirror/lucid-x86_64/linux -> /var/www/cobbler/images/lucid-x86_64/linuxException occured: Exception value: [Errno 2] No such file or directory: '/var/www/cobbler/images/lucid-x86_64/linux'Exception Info: File "/usr/lib/python2.7/dist-packages/cobbler/remote.py", line 89, in runrc = self._run(self) File "/usr/lib/python2.7/dist-packages/cobbler/remote.py", line 184, in runnerreturn self.remote.api.sync(self.options.get("verbose",False),logger=self.logger) File "/usr/lib/python2.7/dist-packages/cobbler/api.py", line 701, in syncreturn sync.run() File "/usr/lib/python2.7/dist-packages/cobbler/action_sync.py", line 123, in runself.settings.webdir,True) File "/usr/lib/python2.7/dist-packages/cobbler/pxegen.py", line 178, in copy_single_distro_filesapi=self.api, logger=self.logger) File "/usr/lib/python2.7/dist-packages/cobbler/utils.py", line 1195, in linkfilereturn copyfile(src, dst, api=api, logger=logger) File "/usr/lib/python2.7/dist-packages/cobbler/utils.py", line 1206, in copyfileif not os.path.samefile(src,dst): File "/usr/lib/python2.7/posixpath.py", line 154, in samefiles2 = os.stat(f2)!!! TASK FAILED !!!+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure--
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #200
Title: precise_folsom_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/200/Project:precise_folsom_deployDate of build:Mon, 06 Aug 2012 21:59:34 -0400Build duration:46 minBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 8947 lines...]INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-11.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-11.os.magners.qa.lexingtonINFO:root:Setting up connection to test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-10.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last): File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 91, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail 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
