Re: [Openstack-doc-core] inviting Ying Chun Guo to join openstack-doc-core

2012-08-05 Thread Razique Mahroua
Make sure you didn't pick a wrong translator Tom,I heard some failed on thathttp://epic-chinese-tattoo-fails.tumblr.com/Razique
Nuage  Co - Razique Mahrouarazique.mahr...@gmail.com

Le 6 août 2012 à 07:04, Tom Fifield fifie...@unimelb.edu.au a écrit :欢迎光临!你已经工作努力了-谢谢 ;)Regards,TomOn 02/08/12 04:54, Lorin Hochstein wrote:Welcome to the team, Daisy!Take care,Lorin--Lorin HochsteinLead Architect - Cloud ServicesNimbis Services, Inc.www.nimbisservices.com https://www.nimbisservices.com/On Jul 28, 2012, at 9:12 AM, Ying Chun Guo guoyi...@cn.ibm.commailto:guoyi...@cn.ibm.com wrote:Thank you for your invitation, Anne. I'd love to ! I will try my best to work for openstack documents.My English may be not as good as Chinese. But I have good experiencein programming.Besides translation and bug fixing, I also can contribute to doc toolsdevelopment.For example, I plan to work with CI team to automate documentpublishing process and translation processas much as possible.RegardsYing Chun Guo (Daisy)annegen...@justwriteclick.com mailto:annegen...@justwriteclick.comwrote on 07/28/2012 03:08:38 AM: Anne Gentle a...@openstack.org mailto:a...@openstack.org Sent by: annegen...@justwriteclick.commailto:annegen...@justwriteclick.com 07/28/2012 03:08 AM To openstack-doc-core@lists.launchpad.netmailto:openstack-doc-core@lists.launchpad.net, Ying ChunGuo/China/IBM@IBMCN, cc Subject inviting Ying Chun Guo to join openstack-doc-core Hi all - I'd like to invite Ying Chun Guo (Daisy) to join our team, she has worked both on doc bugs and on a process for translating documentation. Hi Daisy - I hope you'll accept the invitation to join openstack-doc-core. Your contributions have been extremely helpful. Thanks, Anne--Mailing list: https://launchpad.net/~openstack-doc-corePost to : openstack-doc-core@lists.launchpad.netmailto:openstack-doc-core@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstack-doc-coreMore help : https://help.launchpad.net/ListHelp-- Mailing list: https://launchpad.net/~openstack-doc-corePost to : openstack-doc-core@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstack-doc-coreMore help : https://help.launchpad.net/ListHelp-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova list error ERROR: n/a (HTTP 400)

2012-08-05 Thread Xavier Limodin
Hi,

2012/8/4 sarath zacharia sarathzacha...@gmail.com

 Hai,

   I am running the openstack on ubuntu 12.04  for getting the vnc
 console url

 nova get-vnc-console

 and

 *nova --debug list*
 *
 *
 but we are getting error mentioned below


 connect: (localhost, 5000)
 send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
 localhost:5000\r\nContent-Length: 113\r\ncontent-type:
 application/json\r\naccept-encoding: gzip, deflate\r\naccept:
 application/json\r\nuser-agent: python-novaclient\r\n\r\n{auth:
 {tenantName: admin, passwordCredentials: {username: admin,
 password: admin}}}'
 reply: 'HTTP/1.1 200 OK\r\n'

Keystone auth seems good, you should check credentials in
/etc/nova/api-paste.ini and Keystone endpoints.
Use IP or FQDN instead of localhost.

nova --debug list
connect: (192.168.1.250, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
192.168.1.250:5000\r\nContent-Length:
103\r\ncontent-type: application/json\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n{auth: {tenantName: admin,
passwordCredentials: {username: admin, password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Sun, 05 Aug 2012 09:50:26 GMT
header: Transfer-Encoding: chunked
connect: (host.example.com, 8774)
send: u'GET /v2/ee676f7fc3e44fbc9af31f5c5c201e32/servers/detail
HTTP/1.1\r\nHost: host.example.com:8774\r\nx-auth-project-id:
admin\r\nx-auth-token: 65962404926f4e5a867354f7e733381d\r\naccept-encoding:
gzip, deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-b3baf138-f3f5-4e64-be27-57cc1ec8626a
header: Content-Type: application/json
header: Content-Length: 15
header: Date: Sun, 05 Aug 2012 09:50:36 GMT
++--++--+
| ID | Name | Status | Networks |
++--++--+



 header: Content-Type: application/json
 header: Vary: X-Auth-Token
 header: Date: Sat, 04 Aug 2012 06:04:58 GMT
 header: Transfer-Encoding: chunked

DEBUG (shell:416) n/a (HTTP 400)
 Traceback (most recent call last):
   File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 413,
 in main
 OpenStackComputeShell().main(sys.argv[1:])
   File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 364,
 in main
 args.func(self.cs, args)
   File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line
 520, in do_list
 utils.print_list(cs.servers.list(search_opts=search_opts), columns,
   File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
 279, in list
 return self._list(/servers%s%s % (detail, query_string), servers)
   File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in
 _list
 resp, body = self.api.client.get(url)
   File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136,
 in get
 return self._cs_request(url, 'GET', **kwargs)
   File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124,
 in _cs_request
 **kwargs)
   File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107,
 in request
 raise exceptions.from_response(resp, body)
 BadRequest: n/a (HTTP 400)
 ERROR: n/a (HTTP 400)

 and our credentials exported successfulle as given below



  OS_TENANT_NAME=admin
  OS_USERNAME=admin
  OS_PASSWORD=admin
  OS_AUTH_URL=http://localhost:5000/v2.0/;

 You don't need to export SERVICE_ENDPOINT and SERVICE_TOKEN, OS_...
variables are sufficient.



  please help me 

 --
 with Thanks and Regards

 Sarath Zacharia

 ___
 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] OpenStack Community Weekly Newsletter (July 27-Aug 3)

2012-08-05 Thread Stefano Maffulli

  
  
Highlights of the week

  
 
  

  
OpenStack
Foundation Board  2012 Election Candidates
See the current list of nominees for the OpenStack
  Foundation 2012 Board Member Elections who have received
  at least one nomination. A candidate must receive at least
  10 nominations to appear on the ballot. Any active member
  of the OpenStack Foundation can support a nominee or
  nominate a new candidate http://www.openstack.org/community/openstack-foundation-board-2012-election-candidates/.
  A candidate must receive at least 10 nominations to appear
  on the ballot and must be a member of the Foundation.
The final day to nominate a candidate is Monday
August 6, 2012.
Rostyslav
Slipetskyys Thesis on OpenStack security
This is a pretty awesome bit of work done by a researcher
  in Denmark. I enjoyed reading it and I highly recommend it
  as day 1 reading for Infosec professionals and researchers
  getting into OpenStack. Slides
  and you can download
the full thesis (PDF).
API
Stability Statement
It is critical to the success of OpenStack
  that operators be willing to upgrade to new OpenStack
  releases. All OpenStack
  APIs use a versioning scheme that is completely
  independent from the named releases (Essex, Folsom, etc.).
  One obstacle to upgrading to a new OpenStack
  release is if there are incompatible API changes that
  could cause user applications to stop working. Operators
  want great new features and APIs to be the only aspect of
  the upgrade process visible to their users. Old API
  versions should continue to work. More on http://wiki.openstack.org/Governance/Approved/APIStability
OpenStack PPB defined Supporting Project
There is a new category of OpenStack projects in addition
  to Core, Incubated, Library and Gating projects:
  Supporting projects. The initial list of projects in
  this category is available on the wiki, with more details:
  http://wiki.openstack.org/Governance/Accepted/SupportingProjectDefinition.
OpenStack
Security Primer
Matt Joyce introduction to security and OpenStack. Hes
  maintaining the blog http://secstack.org,
  now available also on http://planet.openstack.org.
Tips and tricks

  By Sbastien Han:
Auto
  assign floating IP
  By Mirantis: OpenStack
  Networking Tutorial: Single-host FlatDHCPManager
  By Mark
  McLoughlin: Nova
  DB Poking
  By Alessandro
  Tagiapietra: Build
  an HA Openstack cloud (multiple parts)

  


  
Upcoming Events

  South Bay OpenStack Hackathon Aug
09, 2012  Sunnyvale, CA Details
  2012 OpenStack APEC Conference Aug
10  11, 2012  Bejing+Shanghai, China Details Openstack User Group Meetup ( Delhi
  NCR ) Aug 12, 2012  Dehli Details
  Hobart Meetup  adjacent to PyCon2012,
  An OpenStack code dojo! Aug 17, 2012  Hobart,
Australia Details
  Australian OpenStack User Group 
  Adelaide Meetup with SAGE-AU Aug 28, 2012 
Adelaide Details
  OpenStack
  Summit Oct 15  18, 2012  San Diego, CA

  


  
Other news

  Security update: CVE-2012-3426
  : Keystone does not properly implement token
  expiration
  OpenStack ProjectMeeting 2012-07-31: Summary
Meeting
  log
  OpenStack PPB Meeting 2012-07-31: Summary
and Meeting
  log

  Voted on Agreement on proposed API Stability
Statement http://wiki.openstack.org/Governance/Approved/APIStability
  Voted on Creating a supporting project official
category http://wiki.openstack.org/Governance/Accepted/SupportingProjectDefinition

  

Stats from traffic on docs.openstack.org
Statistics taken from the traffic on docs.openstack.org,
  from January 1st 2012 to July 31st.

  Country/Territory visits to
  

[Openstack] Federated Access To OpenStack

2012-08-05 Thread David Chadwick

Hi Everyone

during the last few weeks we have been working on adding federated 
access to Open Stack. The basic system is now working in our lab, and 
clients for nova, swift and glance have been modified in order to allow 
federated access through a set of federated APIs that we have designed 
and built. The specifications for the APIs and implementation have been 
uploaded to DropBox and are available here:


http://dl.dropbox.com/u/44986510/Adding%20federated%20access%20to%20OpenStack%201.pdf
http://dl.dropbox.com/u/44986510/Client%20Connection%20API%20v1.pdf
http://dl.dropbox.com/u/44986510/Federated%20Middleware%20Services-v1.pdf
http://dl.dropbox.com/u/44986510/UserGuide.pdf

All comments and feedback from the community will be gratefully received.

We currently use SAML as the federated access protocol, since a Python 
library for this already exists, but this can be changed to OpenID OAuth 
or anything else without changing the specifications or the client 
implementations (so we hope from the design). Only the federated 
middleware will need to change, and we can do this once suitable 
packages become available in Python.


We hope to have public demos available by the end of this week, once we 
can sort out the university firewall and other issues.


A use case we have for our federated access is an open source research 
repository in the cloud for the UK academic community.  Since all UK 
students and staff (up to 1 million people) already have their own 
university un/pws, they should be able to login to the cloud repository 
using their existing credentials, in order to store and share their 
research outputs with others. They should not need to obtain new un/pws 
in order to access the cloud service. Our federated access to OpenStack 
provides this functionality. Users who can successfully identify 
themselves as members of the UK academic community will be automatically 
enrolled as cloud users and given appropriate tenant IDs.


I look forward to having fruitful discussions with you about federated 
access to OpenStack.


regards

David

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


Re: [Openstack] glance error

2012-08-05 Thread Shake Chen
Hi

http://www.chenshake.com/ubuntu-12-04-openstack-essex-installation-single-node/

if you glance and keystone in same machine,  would have no any problem
according to the document.



On Mon, Aug 6, 2012 at 11:22 AM, 王鹏 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




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


[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #309

2012-08-05 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/309/Project:quantal_folsom_nova_trunkDate of build:Sun, 05 Aug 2012 08:01:56 -0400Build duration:8 min 32 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesDrop AES functions and pycrypto dependencyby stanislaw.pituchaedittools/pip-requireseditnova/crypto.pyeditnova/tests/test_crypto.pyConsole Output[...truncated 4906 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-73853511-81ce-43e1-9014-11c8db911346', '-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/tmpq1o_Cy/novamk-build-deps -i -r -t apt-get -y /tmp/tmpq1o_Cy/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+git201208050807~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208050807~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-73853511-81ce-43e1-9014-11c8db911346', '-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-73853511-81ce-43e1-9014-11c8db911346', '-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 #310

2012-08-05 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/310/Project:quantal_folsom_nova_trunkDate of build:Sun, 05 Aug 2012 15:31:55 -0400Build duration:3 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdates to the prep_resize scheduler rpc call.by rbryanteditnova/scheduler/chance.pyeditnova/scheduler/rpcapi.pyeditnova/scheduler/filter_scheduler.pyeditnova/tests/scheduler/test_rpcapi.pyeditnova/tests/scheduler/test_chance_scheduler.pyeditnova/compute/api.pyeditnova/scheduler/driver.pyeditnova/tests/scheduler/test_scheduler.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/scheduler/manager.pyRemove **kwargs from prep_resize in compute manager.by rbryanteditnova/tests/compute/test_compute.pyeditnova/compute/manager.pyConsole Output[...truncated 4918 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-65347bc2-ddb6-4283-a002-aff9b3cc1f25', '-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/tmp3jq90h/novamk-build-deps -i -r -t apt-get -y /tmp/tmp3jq90h/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+git201208051533~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208051533~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-65347bc2-ddb6-4283-a002-aff9b3cc1f25', '-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-65347bc2-ddb6-4283-a002-aff9b3cc1f25', '-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 #311

2012-08-05 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/311/Project:quantal_folsom_nova_trunkDate of build:Sun, 05 Aug 2012 20:01:54 -0400Build duration:3 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesHandle NetworkNotFound in _shutdown_instance.by mikaleditnova/tests/compute/test_compute.pyeditnova/compute/manager.pyConsole Output[...truncated 4924 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-c9c92a0f-6ec6-4d35-801d-ff4b4c407e4b', '-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/tmplwoLfx/novamk-build-deps -i -r -t apt-get -y /tmp/tmplwoLfx/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+git201208052003~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208052003~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-c9c92a0f-6ec6-4d35-801d-ff4b4c407e4b', '-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-c9c92a0f-6ec6-4d35-801d-ff4b4c407e4b', '-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 #319

2012-08-05 Thread openstack-testing-bot
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/319/Project:precise_folsom_nova_trunkDate of build:Sun, 05 Aug 2012 20:01:54 -0400Build duration:3 min 54 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesHandle NetworkNotFound in _shutdown_instance.by mikaleditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyConsole Output[...truncated 4087 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-9fd709eb-f16d-4f82-9aee-1b820d93a513', '-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/tmppRlYnX/novamk-build-deps -i -r -t apt-get -y /tmp/tmppRlYnX/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+git201208052003~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208052003~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-9fd709eb-f16d-4f82-9aee-1b820d93a513', '-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-9fd709eb-f16d-4f82-9aee-1b820d93a513', '-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