[Openstack] Volume handling

[Nicolae Paladi]

Hi,

this is likely an RTFM question, but I haven't found any relevant 'FM' so I
decided
to ask on the mailing list before digging into the code:

How are volumes mapped to the instances after they are restarted?

How can a volume created earlier be identified to be attached to a newly
spawned intance?

Are the IQNs created during volume creation exposed anywhere
else than the compute nodes?

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

Re: [Openstack] Command to find out list of compute nodes

[Narayanan, Krishnaprasad]

Hi Ahmed,

Could you check whether the log files are present in the folder 
/var/log/nova/nova-compute.log on the compute node? Can you also confirm 
regarding the status of all the necessary daemons related to nova and other 
components deployed on the cloud controller node?

Thanks
Krishnaprasad Narayanan

-Original Message-
From: Ahmed Al-Mehdi [mailto:ah...@coraid.com] 
Sent: Freitag, 16. November 2012 05:29
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: Command to find out list of compute nodes

Hi Narayanan,

Awesome, thank you.  There reason I was not seeing the nova-compute
listed is because it did not launch on the compute node.  I did a manual start 
of nova-compute on the compute node, and I do see it listed on the 
control-node but with XXX State.

root@bodega:~/ahmed/new_guide# nova-manage  service list

Binary  HostZone Status State   Updated_At
nova-networkbodega  nova enabled:-) 2012-11-15 
23:49:28
nova-scheduler  bodega  nova enabled:-) 2012-11-15 
23:49:28
nova-computesonoma  nova enabledXXX 2012-11-15 
23:46:46
= compute-node

What I don't understand is even though nova-compute is listed on the 
control-node, the service is not running on the compute node.  That does not 
seem right.

root@sonoma:~# service nova-compute status nova-compute stop/waiting 
root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08 PST 2012 
nova-compute start/running, process 2785 root@sonoma:~# service nova-compute 
status nova-compute stop/waiting root@sonoma:~# ps aux | grep nova
root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
--color=auto nova
root@sonoma:~# service  nova-compute status nova-compute stop/waiting 
root@sonoma:~# 

There are no log entries in the log files on compute-node or control-node.
 Any ideas please?


Thank you,
Ahmed.





On 11/15/12 3:29 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:

Hi Ahmed,

You can use the command nova-manage service list from the command 
line of control node to get the list of compute nodes along with the 
nova-compute service status.

Thanks
Krishnaprasad Narayanan

From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
[openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on behalf 
of Ahmed Al-Mehdi [ah...@coraid.com]
Sent: Friday, November 16, 2012 12:19 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Command to find out list of compute nodes

Hello,

Is there a command I can issue on the control node to find out the list 
of compute node(s) (nodes running nova-compute), and potentially any 
additional info about the compute node(s)?

Thank you,
Ahmed.



___
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] Command to find out list of compute nodes

[gong yong sheng]

Can u check if the time is synchronized? Times on compute node and 
control node should be synchronized.

On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:

Hi Narayanan,

Awesome, thank you.  There reason I was not seeing the nova-compute
listed is because it did not launch on the compute node.  I did a manual
start of nova-compute on the compute node, and I do see it listed on the
control-node but with XXX State.

root@bodega:~/ahmed/new_guide# nova-manage  service list

Binary  HostZone Status State   Updated_At
nova-networkbodega  nova enabled:-) 2012-11-15 
23:49:28
nova-scheduler  bodega  nova enabled:-) 2012-11-15 
23:49:28
nova-computesonoma  nova enabledXXX 2012-11-15 
23:46:46
= compute-node

What I don't understand is even though nova-compute is listed on the
control-node, the service is not running on the compute node.  That does
not seem right.

root@sonoma:~# service nova-compute status
nova-compute stop/waiting
root@sonoma:~# date;  service nova-compute start
Thu Nov 15 15:48:08 PST 2012
nova-compute start/running, process 2785
root@sonoma:~# service nova-compute status
nova-compute stop/waiting
root@sonoma:~# ps aux | grep nova
root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
--color=auto nova
root@sonoma:~# service  nova-compute status
nova-compute stop/waiting
root@sonoma:~#

There are no log entries in the log files on compute-node or control-node.
  Any ideas please?


Thank you,
Ahmed.





On 11/15/12 3:29 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:


Hi Ahmed,

You can use the command nova-manage service list from the command line
of control node to get the list of compute nodes along with the
nova-compute service status.

Thanks
Krishnaprasad Narayanan

From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
[openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on behalf
of Ahmed Al-Mehdi [ah...@coraid.com]
Sent: Friday, November 16, 2012 12:19 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Command to find out list of compute nodes

Hello,

Is there a command I can issue on the control node to find out the list
of compute node(s) (nodes running nova-compute), and potentially any
additional info about the compute node(s)?

Thank you,
Ahmed.



___
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] Fwd: [keystone] Tokens representing authorization to projects/tenants in the Keystone V3 API

[Dolph Mathews]

I'm just pointing out that the same data used for validating belongsTo on
the server-side is included in the response body (assuming a GET and not
HEAD).


-Dolph


On Thu, Nov 15, 2012 at 2:51 PM, Jorge Williams 
jorge.willi...@rackspace.com wrote:

  (inline)

  On Nov 15, 2012, at 2:06 PM, Dolph Mathews wrote:

 Without belongsTo, you can still validate the tenant scope client-side, so
 it's a bit redundant.


  Not sure what you mean.  Can you be more specific?

 However, if you're making a HEAD call to validate the token, you obviously
 need the server to do that additional validation for you.


  Right.


  -Dolph


 On Thu, Nov 15, 2012 at 8:20 AM, Jorge Williams 
 jorge.willi...@rackspace.com wrote:

 No, it's optional.

 Token validation returns what it normally does.  The only thing belongs
 to does is that you fail token validation if the given tenant is not
 covered by the scope of the token.

 -jOrGe W.

 On Nov 14, 2012, at 11:18 PM, Yee, Guang wrote:

  Is belongsTo mandatory? If not, what will token validation API return?
 
  {access: [list of tokens]}
 
  ?
 
 
  Guang
 
 
  -Original Message-
  From: Jorge Williams [mailto:jorge.willi...@rackspace.com]
  Sent: Wednesday, November 14, 2012 2:47 PM
  To: OpenStack Development Mailing List
  Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
  Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens
 representing
  authorization to projects/tenants in the Keystone V3 API
 
  From an API perspective the changes required are the following:
 
1.  The validate call returns a list of tenants instead of a
 single
  tenant.
 
  If the tenant id is in the URI of the API, then the validation
 middleware
  can assert that the tenant id is in the list of IDs.
 
  Not sure if there's any additional changes, but I don't think so.
 
  An alternative approach is to use the belongsTo query parameter in the
  validate call.  So if you know the tenantId of the resource, you can
 issue a
  validate with ?belongsTo=tenatId  and validation if the tenant is not
 in
  the list of tenatIds for the token.  The belongsTo query parameter is
 in the
  validate token call in the API today
 
 
 http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_val
 
 idateToken_v2.0_tokens__tokenId__Admin_API_Service_Developer_Operations-d1e1
  356.html
 
  And we use it quite a bit in our implementation, when we validate
 tokens --
  that is in the case where a token may have access to multiple tenants.
 
  Thoughts?
 
  -jOrGe W.
 
 
  On Nov 14, 2012, at 3:53 PM, heckj wrote:
 
  If we're going to assert it's supported, we're doing an incredible
  dis-service to writing a spec to not implement that aspect of the spec,
 as
  that kind of set up just leads to incompatibilities and confusion when
  asserting how the spec should be used to provide interoperability.
 
  If we accept this as a spec addition, then we MUST have an
 implementation
  that makes it clear how we expect to interoperate with that aspect of
 the
  specification, even if it's a configuration option that we don't
 normally
  enable. If we don't test and validate it to prove interoperability,
 then the
  spec is a worthless digital piece of paper.
 
  So under that pretext, I welcome suggestions on how to interpret the
 spec
  you're proposing to some concrete implementations that can be verified
 for
  interoperability, and that are compatible with the existing and/or
 upcoming
  implementations for V3 API.
 
  -joe
 
  On Nov 14, 2012, at 1:35 PM, Joe Savak joe.sa...@rackspace.com
 wrote:
  Hi Joe,
  If I'm working across multiple tenants, I'd prefer one token that
 I
  can securely handle that proves access rights to the tenants I'm working
  with. Handling multiple tokens increases the complexity of clients
 needing
  to provide multi-tenancy access to an authenticated identity. It also
 adds
  more calls to keystone.
 
  Again, I think that having the keystone reference implementation
 restrict
  tokens to 1 tenant is fine. We shouldn't have such arbitrary
 restrictions in
  the API contract though. It needs to be extensible and flexible to
 allow for
  the all sorts of use cases that are likely to occur.
 
  Thanks,
  joe
 
  -Original Message-
  From: heckj [mailto:he...@mac.com]
  Sent: Tuesday, November 13, 2012 3:59 PM
  To: Joe Savak
  Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
  (openstack@lists.launchpad.net)
  Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens
  representing authorization to projects/tenants in the Keystone V3 API
 
  Hey Joe:
 
  Currently a user scoped token doesn't include a service catalog -
 mostly
  because I think the service catalog generally requires tenant_id's to
  interpolate into the values to provide it. That doesn't mean we can't
 put
  in/include service catalog endpoints where that value doesn't need to be
  determined.
 
  I'm also questioning the value of 

Re: [Openstack] Command to find out list of compute nodes

[Narayanan, Krishnaprasad]

Hi Ahmed,

If I understand the email correctly from Gong Yong Sheng, he is asking you to 
check the status of ntp server on control and compute nodes.

Thanks
Krishnaprasad Narayanan

-Original Message-
From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com] 
Sent: Freitag, 16. November 2012 13:56
To: Ahmed Al-Mehdi
Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
Subject: Re: [Openstack] Command to find out list of compute nodes

Can u check if the time is synchronized? Times on compute node and control node 
should be synchronized.
On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,

 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a 
 manual start of nova-compute on the compute node, and I do see it 
 listed on the control-node but with XXX State.

 root@bodega:~/ahmed/new_guide# nova-manage  service list

 BinaryHostZone Status State   
 Updated_At
 nova-network  bodega  nova enabled:-) 2012-11-15 
 23:49:28
 nova-schedulerbodega  nova enabled:-) 
 2012-11-15 23:49:28
 nova-compute  sonoma  nova enabledXXX 2012-11-15 
 23:46:46
 = compute-node

 What I don't understand is even though nova-compute is listed on the 
 control-node, the service is not running on the compute node.  That 
 does not seem right.

 root@sonoma:~# service nova-compute status nova-compute stop/waiting 
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08 
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~# 
 service nova-compute status nova-compute stop/waiting root@sonoma:~# 
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting 
 root@sonoma:~#

 There are no log entries in the log files on compute-node or control-node.
   Any ideas please?


 Thank you,
 Ahmed.





 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad 
 naray...@uni-mainz.de
 wrote:

 Hi Ahmed,

 You can use the command nova-manage service list from the command 
 line of control node to get the list of compute nodes along with the 
 nova-compute service status.

 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on 
 behalf of Ahmed Al-Mehdi [ah...@coraid.com]
 Sent: Friday, November 16, 2012 12:19 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Command to find out list of compute nodes

 Hello,

 Is there a command I can issue on the control node to find out the 
 list of compute node(s) (nodes running nova-compute), and potentially 
 any additional info about the compute node(s)?

 Thank you,
 Ahmed.


 ___
 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] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

Hi Krishnaprasad,

Yes, there are log files present in /var/log/nova/ folder, and but no
entries created in either nova-comptue.log or nova-manage.log file on that
node.

By status of the daemons, do you mean the following info:

root@bodega:~# nova-manage  service list
Binary   Host Zone
Status State Updated_At
nova-network bodega   nova
enabled:-)   2012-11-16 17:19:56
nova-scheduler   bodega   nova
enabled:-)   2012-11-16 17:19:56
nova-compute sonoma   nova
enabledXXX   2012-11-15 23:46:46   


root@bodega:~# ps aux | grep nova
nova 15952  0.0  0.0  37952  1308 ?Ss   Nov14   0:00 su -s
/bin/sh -c exec nova-api --config-file=/etc/nova/nova.conf nova
nova 15953  0.0  0.7 135512 57380 ?SNov14   0:00
/usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 15958  0.0  0.2  95820 22804 ?SNov14   0:00
/usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 15959  0.0  0.9 247752 76880 ?SNov14   0:03
/usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 15960  0.0  0.6 135512 54352 ?SNov14   0:00
/usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 15979  0.0  0.0  37952  1308 ?Ss   Nov14   0:00 su -s
/bin/sh -c exec nova-network --config-file=/etc/nova/nova.conf nova
nova 15980  0.2  0.6 206536 56664 ?SNov14   8:07
/usr/bin/python /usr/bin/nova-network --config-file=/etc/nova/nova.conf
nova 16031  0.0  0.0  37952  1312 ?Ss   Nov14   0:00 su -s
/bin/sh -c exec nova-novncproxy --config-file=/etc/nova/nova.conf nova
nova 16032  0.0  0.2 122976 24108 ?SNov14   0:08
/usr/bin/python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf
nova 16043  0.0  0.0  37952  1308 ?Ss   Nov14   0:00 su -s
/bin/sh -c exec nova-scheduler --config-file=/etc/nova/nova.conf nova
nova 16044  0.2  0.7 231820 61112 ?SNov14   8:12
/usr/bin/python /usr/bin/nova-scheduler --config-file=/etc/nova/nova.conf
root 22062  0.0  0.0   9388   924 pts/2S+   09:23   0:00 grep
--color=auto nova
root@bodega:~# service nova-api status
nova-api start/running, process 15952
root@bodega:~# service nova-network status
nova-network start/running, process 15979
root@bodega:~# service nova-vncproxy status
nova-vncproxy: unrecognized service
root@bodega:~# service nova-scheduler  status
nova-scheduler start/running, process 16043
root@bodega:~# 

If you need additional info on the daemons, can you please met know the
command to issue.


Regards,
Ahmed.





On 11/16/12 2:21 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:

Hi Ahmed,

Could you check whether the log files are present in the folder
/var/log/nova/nova-compute.log on the compute node? Can you also confirm
regarding the status of all the necessary daemons related to nova and
other components deployed on the cloud controller node?

Thanks
Krishnaprasad Narayanan

-Original Message-
From: Ahmed Al-Mehdi [mailto:ah...@coraid.com]
Sent: Freitag, 16. November 2012 05:29
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: Command to find out list of compute nodes

Hi Narayanan,

Awesome, thank you.  There reason I was not seeing the nova-compute
listed is because it did not launch on the compute node.  I did a manual
start of nova-compute on the compute node, and I do see it listed on
the control-node but with XXX State.

root@bodega:~/ahmed/new_guide# nova-manage  service list

Binary HostZone Status State   
Updated_At
nova-network   bodega  nova enabled:-) 2012-11-15 
23:49:28
nova-scheduler bodega  nova enabled:-) 
2012-11-15 23:49:28
nova-compute   sonoma  nova enabledXXX 2012-11-15 
23:46:46
= compute-node

What I don't understand is even though nova-compute is listed on the
control-node, the service is not running on the compute node.  That does
not seem right.

root@sonoma:~# service nova-compute status nova-compute stop/waiting
root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08 PST
2012 nova-compute start/running, process 2785 root@sonoma:~# service
nova-compute status nova-compute stop/waiting root@sonoma:~# ps aux |
grep nova
root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
--color=auto nova
root@sonoma:~# service  nova-compute status nova-compute stop/waiting
root@sonoma:~# 

There are no log entries in the log files on compute-node or control-node.
 Any ideas please?


Thank you,
Ahmed.





On 11/15/12 3:29 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:

Hi Ahmed,

You can use the command nova-manage service list from the command
line of control node to get the list of compute nodes along 

Re: [Openstack] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

Hello,

The two servers time clock is off by 2 seconds, so obvious not time
synced.  I will work on getting that fixed.  The compute node is ahead by
about 2 seconds.  Would that cause such a problem?

Regards,
Ahmed.


On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:

Hi Ahmed,

If I understand the email correctly from Gong Yong Sheng, he is asking
you to check the status of ntp server on control and compute nodes.

Thanks
Krishnaprasad Narayanan

-Original Message-
From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
Sent: Freitag, 16. November 2012 13:56
To: Ahmed Al-Mehdi
Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
Subject: Re: [Openstack] Command to find out list of compute nodes

Can u check if the time is synchronized? Times on compute node and
control node should be synchronized.
On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,

 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.

 root@bodega:~/ahmed/new_guide# nova-manage  service list

 Binary   HostZone Status State   
 Updated_At
 nova-network bodega  nova enabled:-) 
 2012-11-15 23:49:28
 nova-scheduler   bodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-compute sonoma  nova enabledXXX 
 2012-11-15 23:46:46
 = compute-node

 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.

 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#

 There are no log entries in the log files on compute-node or
control-node.
   Any ideas please?


 Thank you,
 Ahmed.





 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:

 Hi Ahmed,

 You can use the command nova-manage service list from the command
 line of control node to get the list of compute nodes along with the
 nova-compute service status.

 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on
 behalf of Ahmed Al-Mehdi [ah...@coraid.com]
 Sent: Friday, November 16, 2012 12:19 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Command to find out list of compute nodes

 Hello,

 Is there a command I can issue on the control node to find out the
 list of compute node(s) (nodes running nova-compute), and potentially
 any additional info about the compute node(s)?

 Thank you,
 Ahmed.


 ___
 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] Volume handling

[John Griffith]

On Fri, Nov 16, 2012 at 3:17 AM, Nicolae Paladi n.pal...@gmail.com wrote:

 Hi,

 this is likely an RTFM question, but I haven't found any relevant 'FM' so
 I decided
 to ask on the mailing list before digging into the code:

 How are volumes mapped to the instances after they are restarted?


In terms of a reboot of the instance, I believe this is handled via the BDM
table in the DB, it's checked on a reboot and the attach is verified.



 How can a volume created earlier be identified to be attached to a newly
 spawned intance?


Not sure I see the question here, use the same process nova volume-attach
server-uuid volume-uuid path


 Are the IQNs created during volume creation exposed anywhere
 else than the compute nodes?


Nope, not really.  You can find what they are either by checking the DB or
checking the persistence file info for the volume
(/var/lib/cinder/volumes/xxx, or devstack:
/opt/stack/data/cinder/volumes/)


 Thanks,
 /Nico.

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


___
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] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

I have time sync'ed the control and compute node.  Still see the XXX.  I
copied the ntp.conf file from the control-node and compute-node onto paste
bin - http://pastebin.com/HsnzcRHr.

There are a few things that I find really confusing:

1. Why does nova-manage service-list display the service nova-compute
(be with status XXX) on compute-node when it is not even running on
compute-node.  Is it because the data being displayed is stale, possibly
fetched from the db?

root@bodega:~# nova-manage  service list===  control-node
Binary  HostZone Status State Updated_At
nova-networkbodega  nova enabled:-)   2012-11-16 18:23:00
nova-scheduler  bodega  nova enabled:-)   2012-11-16
18:23:00
nova-computesonoma  nova enabledXXX   2012-11-15
23:46:46  ===
nova-cert   bodega  nova enabled:-)   2012-11-16 18:22:59
nova-consoleauth bodega   nova
enabled:-)   2012-11-16 18:22:59

root@sonoma:/var/log/nova# ps aux | grep nova  === compute-node

root  5013  0.0  0.0   9384   924 pts/0S+   10:54   0:00 grep
--color=auto nova
root@sonoma:/var/log/nova# service  nova-compute status
nova-compute stop/waiting
root@sonoma:/var/log/nova#



2. The other thing that is totally confusing me is why I cannot start
nova-compute on the compute-node, and I am not getting any log messages in
any of the log files on the control-node or compute node.  Can you please
help.

root@sonoma:/var/log/nova# ls -l /var/log/nova/*log
-rw-r--r-- 1 nova nova 0 Nov 16 06:40 /var/log/nova/nova-compute.log
-rw-r--r-- 1 nova nova 0 Nov 16 06:40 /var/log/nova/nova-manage.log
root@sonoma:/var/log/nova#
root@sonoma:/var/log/nova#
root@sonoma:/var/log/nova# service nova-compute statu
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service nova-compute statu

The script you are attempting to invoke has been converted to an Upstart
job, but statu is not supported for Upstart jobs.
root@sonoma:/var/log/nova# service nova-compute status
nova-compute stop/waiting
root@sonoma:/var/log/nova#
root@sonoma:/var/log/nova# service nova-compute start
nova-compute start/running, process 5064
root@sonoma:/var/log/nova#
root@sonoma:/var/log/nova# service nova-compute status
nova-compute stop/waiting
root@sonoma:/var/log/nova# ls -l /var/log/nova/*log
-rw-r--r-- 1 nova nova 0 Nov 16 06:40 /var/log/nova/nova-compute.log
-rw-r--r-- 1 nova nova 0 Nov 16 06:40 /var/log/nova/nova-manage.log
root@sonoma:/var/log/nova#


(Don't worry about the log file being 0 bytes, as they just rolled over
this am.)

Can you please help me understand what is going on.  Would appreciate any
help / pointers.  I copied the nova.conf file from the control and compute
node onto the pastebin site.

Thank you,
Ahmed.


On 11/16/12 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

Hello,

The two servers time clock is off by 2 seconds, so obvious not time
synced.  I will work on getting that fixed.  The compute node is ahead by
about 2 seconds.  Would that cause such a problem?

Regards,
Ahmed.


On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
wrote:

Hi Ahmed,

If I understand the email correctly from Gong Yong Sheng, he is asking
you to check the status of ntp server on control and compute nodes.

Thanks
Krishnaprasad Narayanan

-Original Message-
From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
Sent: Freitag, 16. November 2012 13:56
To: Ahmed Al-Mehdi
Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
Subject: Re: [Openstack] Command to find out list of compute nodes

Can u check if the time is synchronized? Times on compute node and
control node should be synchronized.
On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,

 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.

 root@bodega:~/ahmed/new_guide# nova-manage  service list

 Binary  HostZone Status State   
 Updated_At
 nova-networkbodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-scheduler  bodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-computesonoma  nova enabledXXX 
 2012-11-15 23:46:46
 = compute-node

 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.

 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384  

Re: [Openstack] Command to find out list of compute nodes

[Vishvananda Ishaya]

nova-compute is crashing for some reason. Try running
sudo nova-compute --config-file=/etc/nova/nova.conf

that should start it in the foreground so you can see any error messages that 
might pop up.

Vish

On Nov 16, 2012, at 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,
 
 The two servers time clock is off by 2 seconds, so obvious not time
 synced.  I will work on getting that fixed.  The compute node is ahead by
 about 2 seconds.  Would that cause such a problem?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 If I understand the email correctly from Gong Yong Sheng, he is asking
 you to check the status of ntp server on control and compute nodes.
 
 Thanks
 Krishnaprasad Narayanan
 
 -Original Message-
 From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
 Sent: Freitag, 16. November 2012 13:56
 To: Ahmed Al-Mehdi
 Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Command to find out list of compute nodes
 
 Can u check if the time is synchronized? Times on compute node and
 control node should be synchronized.
 On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,
 
 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.
 
 root@bodega:~/ahmed/new_guide# nova-manage  service list
 
 Binary  HostZone Status State   
 Updated_At
 nova-networkbodega  nova enabled:-) 
 2012-11-15 23:49:28
 nova-scheduler  bodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-computesonoma  nova enabledXXX 
 2012-11-15 23:46:46
 = compute-node
 
 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.
 
 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#
 
 There are no log entries in the log files on compute-node or
 control-node.
  Any ideas please?
 
 
 Thank you,
 Ahmed.
 
 
 
 
 
 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 You can use the command nova-manage service list from the command
 line of control node to get the list of compute nodes along with the
 nova-compute service status.
 
 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on
 behalf of Ahmed Al-Mehdi [ah...@coraid.com]
 Sent: Friday, November 16, 2012 12:19 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Command to find out list of compute nodes
 
 Hello,
 
 Is there a command I can issue on the control node to find out the
 list of compute node(s) (nodes running nova-compute), and potentially
 any additional info about the compute node(s)?
 
 Thank you,
 Ahmed.
 
 
 ___
 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] Looking for a good Folsom + Quantum guide

[Samuel Winchenbach]

I was attempting to use VLAN/2NICs because that is that I am most familiar
with and I do not currently have 3 network cards (I have Infiniband, but it
is not currently hooked up).  I am a little unclear why GRE requires 3
network cards, probably because I am very unfamiliar with openvswitch.
Thanks for the documents and suggestions so far.  I will keep hammering
away at it.

Sam

On Thu, Nov 15, 2012 at 8:06 PM, Dan Wendlandt d...@nicira.com wrote:



 On Thu, Nov 15, 2012 at 4:11 PM, Dan Wendlandt d...@nicira.com wrote:

 Thanks for your comments. This is all good feedback.  A couple of things
 to mention:

 1) The l3-agent rootwrap error mentioned earlier in the thread is in
 stable/folsom and according to launchpad was added to the Ubuntu stable
 release archive about a week ago.  see:
 https://bugs.launchpad.net/quantum/+bug/1069966


 I take that back, it was committed to the Ubuntu quantum repo a week ago,
 but it looks like it has not yet been pulled into Precise.

 dan



 2) The Horizon dashboard only knows how to talk to Nova about floating
 IPs in Folsom.  However, early in grizzly there was a change to be able to
 proxy nova floating IP calls to Quantum, and it appears that this change is
 in the process of being backported to folsom/stable by Chuck Short,
 presumably to be included as an update in the Ubuntu stable release, see:
 https://bugs.launchpad.net/nova/+bug/1023169

 Dan


 On Thu, Nov 15, 2012 at 7:42 AM, Gary Kotton gkot...@redhat.com wrote:

  On 11/15/2012 05:17 PM, Skible OpenStack wrote:

 I believe that the biggest problem is not bug fixes, we are able to fix
 them out by our selves.
 Instead, we do need *that Dashboard able to communicate with the
 quantum to allocate floating IP *

 Does anyone have  an idea about the date ?


 I am not sure if anyone is working on this. You are welome to add the
 support. It would be great.


 Le 15/11/2012 16:14, Gary Kotton a écrit :

 Hi,
 A considerable effort has been made to close a number of problems in the
 Folsom release.
 The list of issues addressed can be seen at
 https://review.openstack.org/#/q/status:merged+project:openstack/quantum+branch:stable/folsom,n,z
 There are still a few bug fixes in review. If I understand correctly
 around the 22nd of November there will be a stable release (maybe give or
 take a day).
 My two cents is to wait a couple of days for the reviews to go through
 and the various distributions to build the packages.
 If there is a painful issue that you have then please let us know.
 Thanks
 Gary

 On 11/15/2012 05:10 PM, Skible OpenStack wrote:

 Are you talking about this l3 bug ?


 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/Tricks%26Ideas/modify_iptables_manager.rst

 Le 15/11/2012 16:06, Razique Mahroua a écrit :

 Hi Sam,
 here is an official guide to start with

 http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ap_installingfolsomubuntuprecise.html
 Note that at the moment, the official quantum packages contain bugs -
 I'm thinking about  the l3 agent for instance.
 Let us know how it's going
 Best regards,
 Razique

  *Nuage  Co - Razique Mahroua** *
 razique.mahr...@gmail.com


  Le 15 nov. 2012 à 15:30, Samuel Winchenbach swinc...@gmail.com a
 écrit :

 Hi All,


 I am looking for a good guide to help me get started with Folsom and
 Quantum for either 12.04 or 12.10.

 I have been attempting to use: goo.gl/vIdcr but when I get to section
 5 (openvswitch) I get an error (SIOCADDRT: no such process) when
 trying to set the interface for the default gateway to the bridge
 created in the previous step.  I have tried a number of different
 things, including installing 12.10 on a virtual machine and trying it
 there instead of bare metal.  Same outcome.

 Doe anyone have any recommendations for a good guide to follow?   Or
 if you have any suggestions on fixing the above error, that would be
 great too!

 Thanks,
 Sam

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




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




 ___
 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: 

Re: [Openstack] Looking for a good Folsom + Quantum guide

[Dan Wendlandt]

Note: use network definitions describe here:
http://docs.openstack.org/trunk/openstack-network/admin/content/connectivity.html

With an overlay type deployment using NVP or OVS plugins you can choose to
consolidate the data network and management network and use the same IP
adress for both types of connectivity if you like.

You definitely want the external network (used for floating ips, etc.) to
be a different IP network, as you wouldn't want VMs having direct access to
your management network or the network you use for tunneling.

Dan


On Fri, Nov 16, 2012 at 11:39 AM, Samuel Winchenbach swinc...@gmail.comwrote:

 I was attempting to use VLAN/2NICs because that is that I am most familiar
 with and I do not currently have 3 network cards (I have Infiniband, but it
 is not currently hooked up).  I am a little unclear why GRE requires 3
 network cards, probably because I am very unfamiliar with openvswitch.
 Thanks for the documents and suggestions so far.  I will keep hammering
 away at it.

 Sam


 On Thu, Nov 15, 2012 at 8:06 PM, Dan Wendlandt d...@nicira.com wrote:



 On Thu, Nov 15, 2012 at 4:11 PM, Dan Wendlandt d...@nicira.com wrote:

 Thanks for your comments. This is all good feedback.  A couple of things
 to mention:

 1) The l3-agent rootwrap error mentioned earlier in the thread is in
 stable/folsom and according to launchpad was added to the Ubuntu stable
 release archive about a week ago.  see:
 https://bugs.launchpad.net/quantum/+bug/1069966


 I take that back, it was committed to the Ubuntu quantum repo a week ago,
 but it looks like it has not yet been pulled into Precise.

 dan



 2) The Horizon dashboard only knows how to talk to Nova about floating
 IPs in Folsom.  However, early in grizzly there was a change to be able to
 proxy nova floating IP calls to Quantum, and it appears that this change is
 in the process of being backported to folsom/stable by Chuck Short,
 presumably to be included as an update in the Ubuntu stable release, see:
 https://bugs.launchpad.net/nova/+bug/1023169

 Dan


 On Thu, Nov 15, 2012 at 7:42 AM, Gary Kotton gkot...@redhat.com wrote:

  On 11/15/2012 05:17 PM, Skible OpenStack wrote:

 I believe that the biggest problem is not bug fixes, we are able to fix
 them out by our selves.
 Instead, we do need *that Dashboard able to communicate with the
 quantum to allocate floating IP *

 Does anyone have  an idea about the date ?


 I am not sure if anyone is working on this. You are welome to add the
 support. It would be great.


 Le 15/11/2012 16:14, Gary Kotton a écrit :

 Hi,
 A considerable effort has been made to close a number of problems in
 the Folsom release.
 The list of issues addressed can be seen at
 https://review.openstack.org/#/q/status:merged+project:openstack/quantum+branch:stable/folsom,n,z
 There are still a few bug fixes in review. If I understand correctly
 around the 22nd of November there will be a stable release (maybe give or
 take a day).
 My two cents is to wait a couple of days for the reviews to go through
 and the various distributions to build the packages.
 If there is a painful issue that you have then please let us know.
 Thanks
 Gary

 On 11/15/2012 05:10 PM, Skible OpenStack wrote:

 Are you talking about this l3 bug ?


 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/Tricks%26Ideas/modify_iptables_manager.rst

 Le 15/11/2012 16:06, Razique Mahroua a écrit :

 Hi Sam,
 here is an official guide to start with

 http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ap_installingfolsomubuntuprecise.html
 Note that at the moment, the official quantum packages contain bugs -
 I'm thinking about  the l3 agent for instance.
 Let us know how it's going
 Best regards,
 Razique

  *Nuage  Co - Razique Mahroua** *
 razique.mahr...@gmail.com


  Le 15 nov. 2012 à 15:30, Samuel Winchenbach swinc...@gmail.com a
 écrit :

 Hi All,


 I am looking for a good guide to help me get started with Folsom and
 Quantum for either 12.04 or 12.10.

 I have been attempting to use: goo.gl/vIdcr but when I get to section
 5 (openvswitch) I get an error (SIOCADDRT: no such process) when
 trying to set the interface for the default gateway to the bridge
 created in the previous step.  I have tried a number of different
 things, including installing 12.10 on a virtual machine and trying it
 there instead of bare metal.  Same outcome.

 Doe anyone have any recommendations for a good guide to follow?   Or
 if you have any suggestions on fixing the above error, that would be
 great too!

 Thanks,
 Sam

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




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

Re: [Openstack] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

I ran nova-compute in the foreground, and I don't see any error messages,
only DEBUG/INFO/AUDIT messages.  I also don't see nova-compute exiting
when run in foreground.  I am currently sifting through the log messages
spit out by nova-compute.  I have also copied the log messages onto
pastebin - http://pastebin.com/8tdZr2mr

Thank you very much for helping out.

Regards,
Ahmed.


On 11/16/12 11:34 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:

nova-compute is crashing for some reason. Try running
sudo nova-compute --config-file=/etc/nova/nova.conf

that should start it in the foreground so you can see any error messages
that might pop up.

Vish

On Nov 16, 2012, at 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,
 
 The two servers time clock is off by 2 seconds, so obvious not time
 synced.  I will work on getting that fixed.  The compute node is ahead
by
 about 2 seconds.  Would that cause such a problem?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 If I understand the email correctly from Gong Yong Sheng, he is asking
 you to check the status of ntp server on control and compute nodes.
 
 Thanks
 Krishnaprasad Narayanan
 
 -Original Message-
 From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
 Sent: Freitag, 16. November 2012 13:56
 To: Ahmed Al-Mehdi
 Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Command to find out list of compute nodes
 
 Can u check if the time is synchronized? Times on compute node and
 control node should be synchronized.
 On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,
 
 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.
 
 root@bodega:~/ahmed/new_guide# nova-manage  service list
 
 Binary HostZone Status State   
 Updated_At
 nova-network   bodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-scheduler bodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-compute   sonoma  nova enabledXXX 
 2012-11-15
23:46:46
 = compute-node
 
 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.
 
 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#
 
 There are no log entries in the log files on compute-node or
 control-node.
  Any ideas please?
 
 
 Thank you,
 Ahmed.
 
 
 
 
 
 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 You can use the command nova-manage service list from the command
 line of control node to get the list of compute nodes along with the
 nova-compute service status.
 
 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on
 behalf of Ahmed Al-Mehdi [ah...@coraid.com]
 Sent: Friday, November 16, 2012 12:19 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Command to find out list of compute nodes
 
 Hello,
 
 Is there a command I can issue on the control node to find out the
 list of compute node(s) (nodes running nova-compute), and potentially
 any additional info about the compute node(s)?
 
 Thank you,
 Ahmed.
 
 
 ___
 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] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

Hello,

I resolved the issue, and I feel really silly about the root cause.
Thanks to a suggestion from a member of the community, running the exact
command from /etc/init/nova-compute.conf manually revealed the issue.

root@sonoma:~# date; exec su -s /bin/sh -c exec nova-compute
--config-file=/etc/nova/nova.conf
--config-file=/etc/nova/nova-compute.conf nova
Fri Nov 16 13:12:45 PST 2012
Traceback (most recent call last):
  File /usr/bin/nova-compute, line 43, in module
flags.parse_args(sys.argv)
  File /usr/lib/python2.7/dist-packages/nova/flags.py, line 43, in
parse_args
default_config_files=default_config_files)
  File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
line 1026, in __call__
self._parse_config_files()
  File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
line 1496, in _parse_config_files
raise ConfigFilesNotFoundError(not_read_ok)
nova.openstack.common.cfg.ConfigFilesNotFoundError: Failed to read some
===
config files: /etc/nova/nova.conf
Connection to sonoma closed.
Ahmeds-MacBook-Pro:~ ahmed$
Ahmeds-MacBook-Pro:~ ahmed$
Ahmeds-MacBook-Pro:~ ahmed$ ssh root@sonoma
root@sonoma's password:
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-23-generic x86_64)
root@sonoma:~#
root@sonoma:~# ls -l /etc/nova/nova.conf
-rw-r- 1 root root 2208 Nov 14 10:53 nova.conf  ==


Much thanks to everyone for helping out.  I am a step closer to getting my
setup working.



Regards,

Ahmed.


On 11/16/12 11:34 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:

nova-compute is crashing for some reason. Try running
sudo nova-compute --config-file=/etc/nova/nova.conf

that should start it in the foreground so you can see any error messages
that might pop up.

Vish

On Nov 16, 2012, at 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,
 
 The two servers time clock is off by 2 seconds, so obvious not time
 synced.  I will work on getting that fixed.  The compute node is ahead
by
 about 2 seconds.  Would that cause such a problem?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 If I understand the email correctly from Gong Yong Sheng, he is asking
 you to check the status of ntp server on control and compute nodes.
 
 Thanks
 Krishnaprasad Narayanan
 
 -Original Message-
 From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
 Sent: Freitag, 16. November 2012 13:56
 To: Ahmed Al-Mehdi
 Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Command to find out list of compute nodes
 
 Can u check if the time is synchronized? Times on compute node and
 control node should be synchronized.
 On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,
 
 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.
 
 root@bodega:~/ahmed/new_guide# nova-manage  service list
 
 Binary HostZone Status State   
 Updated_At
 nova-network   bodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-scheduler bodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-compute   sonoma  nova enabledXXX 
 2012-11-15
23:46:46
 = compute-node
 
 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.
 
 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#
 
 There are no log entries in the log files on compute-node or
 control-node.
  Any ideas please?
 
 
 Thank you,
 Ahmed.
 
 
 
 
 
 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 You can use the command nova-manage service list from the command
 line of control node to get the list of compute nodes along with the
 nova-compute service status.
 
 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on
 behalf of Ahmed Al-Mehdi [ah...@coraid.com]
 Sent: Friday, November 16, 2012 12:19 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Command to find out list of compute nodes
 
 Hello,
 
 Is there a command I can issue on the control node to find out the
 list of compute node(s) (nodes running 

Re: [Openstack] Command to find out list of compute nodes

[Ahmed Al-Mehdi]

Hello,

I would like to add, it would have been really helpful if nova-compute put
some error log message in /var/log/nova/nova-compute.log or
/var/log/syslog.  Is that an enhancement worth filing against nova-compute?

Regards,
Ahmed.


On 11/16/12 1:40 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:

Hello,

I resolved the issue, and I feel really silly about the root cause.
Thanks to a suggestion from a member of the community, running the exact
command from /etc/init/nova-compute.conf manually revealed the issue.

root@sonoma:~# date; exec su -s /bin/sh -c exec nova-compute
--config-file=/etc/nova/nova.conf
--config-file=/etc/nova/nova-compute.conf nova
Fri Nov 16 13:12:45 PST 2012
Traceback (most recent call last):
  File /usr/bin/nova-compute, line 43, in module
flags.parse_args(sys.argv)
  File /usr/lib/python2.7/dist-packages/nova/flags.py, line 43, in
parse_args
default_config_files=default_config_files)
  File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
line 1026, in __call__
self._parse_config_files()
  File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
line 1496, in _parse_config_files
raise ConfigFilesNotFoundError(not_read_ok)
nova.openstack.common.cfg.ConfigFilesNotFoundError: Failed to read some
===
config files: /etc/nova/nova.conf
Connection to sonoma closed.
Ahmeds-MacBook-Pro:~ ahmed$
Ahmeds-MacBook-Pro:~ ahmed$
Ahmeds-MacBook-Pro:~ ahmed$ ssh root@sonoma
root@sonoma's password:
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-23-generic x86_64)
root@sonoma:~#
root@sonoma:~# ls -l /etc/nova/nova.conf
-rw-r- 1 root root 2208 Nov 14 10:53 nova.conf  ==


Much thanks to everyone for helping out.  I am a step closer to getting my
setup working.



Regards,

Ahmed.


On 11/16/12 11:34 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:

nova-compute is crashing for some reason. Try running
sudo nova-compute --config-file=/etc/nova/nova.conf

that should start it in the foreground so you can see any error messages
that might pop up.

Vish

On Nov 16, 2012, at 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,
 
 The two servers time clock is off by 2 seconds, so obvious not time
 synced.  I will work on getting that fixed.  The compute node is ahead
by
 about 2 seconds.  Would that cause such a problem?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 If I understand the email correctly from Gong Yong Sheng, he is asking
 you to check the status of ntp server on control and compute nodes.
 
 Thanks
 Krishnaprasad Narayanan
 
 -Original Message-
 From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
 Sent: Freitag, 16. November 2012 13:56
 To: Ahmed Al-Mehdi
 Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Command to find out list of compute nodes
 
 Can u check if the time is synchronized? Times on compute node and
 control node should be synchronized.
 On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,
 
 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.
 
 root@bodega:~/ahmed/new_guide# nova-manage  service list
 
 BinaryHostZone Status State   
 Updated_At
 nova-network  bodega  nova enabled:-) 
 2012-11-15
23:49:28
 nova-schedulerbodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-compute  sonoma  nova enabledXXX 
 2012-11-15
23:46:46
 = compute-node
 
 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.
 
 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#
 
 There are no log entries in the log files on compute-node or
 control-node.
  Any ideas please?
 
 
 Thank you,
 Ahmed.
 
 
 
 
 
 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 You can use the command nova-manage service list from the command
 line of control node to get the list of compute nodes along with the
 nova-compute service status.
 
 Thanks
 Krishnaprasad Narayanan
 
 From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net
 [openstack-bounces+narayana=uni-mainz...@lists.launchpad.net] on
 behalf of Ahmed 

Re: [Openstack] cannot launch the cirros-0.3.0-i386-uec cloud instance

[alan yang]

 image=/home/alan/devstack/files/images/cirros-0.3.0.i386-uec/cirros-0.3.0-i386-blank.img

cirros-0.3.0-i386-disk.img allows the VM instance to be launched successfully.

I have devstack installed on my laptop vmware workstation 7 with
ubuntu 12.04 virtual machine.
The openstack launched cirros instance, does not seem to have
networking connection.  I wonder
any notes/docs that describe how to configure the network connection
in VM instance launched
and/or vmware workstation + ubuntu VM?

Thanks in advance!

___
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] Command to find out list of compute nodes

[Vishvananda Ishaya]

This is before nova has parsed the log config options, but you would think
upstart would log the error message somewhere. Perhaps a bug against the ubuntu
package?

Vish

On Nov 16, 2012, at 1:43 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,
 
 I would like to add, it would have been really helpful if nova-compute put
 some error log message in /var/log/nova/nova-compute.log or
 /var/log/syslog.  Is that an enhancement worth filing against nova-compute?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 1:40 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:
 
 Hello,
 
 I resolved the issue, and I feel really silly about the root cause.
 Thanks to a suggestion from a member of the community, running the exact
 command from /etc/init/nova-compute.conf manually revealed the issue.
 
 root@sonoma:~# date; exec su -s /bin/sh -c exec nova-compute
 --config-file=/etc/nova/nova.conf
 --config-file=/etc/nova/nova-compute.conf nova
 Fri Nov 16 13:12:45 PST 2012
 Traceback (most recent call last):
 File /usr/bin/nova-compute, line 43, in module
   flags.parse_args(sys.argv)
 File /usr/lib/python2.7/dist-packages/nova/flags.py, line 43, in
 parse_args
   default_config_files=default_config_files)
 File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
 line 1026, in __call__
   self._parse_config_files()
 File /usr/lib/python2.7/dist-packages/nova/openstack/common/cfg.py,
 line 1496, in _parse_config_files
   raise ConfigFilesNotFoundError(not_read_ok)
 nova.openstack.common.cfg.ConfigFilesNotFoundError: Failed to read some
 ===
 config files: /etc/nova/nova.conf
 Connection to sonoma closed.
 Ahmeds-MacBook-Pro:~ ahmed$
 Ahmeds-MacBook-Pro:~ ahmed$
 Ahmeds-MacBook-Pro:~ ahmed$ ssh root@sonoma
 root@sonoma's password:
 Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-23-generic x86_64)
 root@sonoma:~#
 root@sonoma:~# ls -l /etc/nova/nova.conf
 -rw-r- 1 root root 2208 Nov 14 10:53 nova.conf  ==
 
 
 Much thanks to everyone for helping out.  I am a step closer to getting my
 setup working.
 
 
 
 Regards,
 
 Ahmed.
 
 
 On 11/16/12 11:34 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:
 
 nova-compute is crashing for some reason. Try running
 sudo nova-compute --config-file=/etc/nova/nova.conf
 
 that should start it in the foreground so you can see any error messages
 that might pop up.
 
 Vish
 
 On Nov 16, 2012, at 9:28 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:
 
 Hello,
 
 The two servers time clock is off by 2 seconds, so obvious not time
 synced.  I will work on getting that fixed.  The compute node is ahead
 by
 about 2 seconds.  Would that cause such a problem?
 
 Regards,
 Ahmed.
 
 
 On 11/16/12 8:56 AM, Narayanan, Krishnaprasad naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 If I understand the email correctly from Gong Yong Sheng, he is asking
 you to check the status of ntp server on control and compute nodes.
 
 Thanks
 Krishnaprasad Narayanan
 
 -Original Message-
 From: gong yong sheng [mailto:gong...@linux.vnet.ibm.com]
 Sent: Freitag, 16. November 2012 13:56
 To: Ahmed Al-Mehdi
 Cc: Narayanan, Krishnaprasad; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Command to find out list of compute nodes
 
 Can u check if the time is synchronized? Times on compute node and
 control node should be synchronized.
 On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
 Hi Narayanan,
 
 Awesome, thank you.  There reason I was not seeing the nova-compute
 listed is because it did not launch on the compute node.  I did a
 manual start of nova-compute on the compute node, and I do see it
 listed on the control-node but with XXX State.
 
 root@bodega:~/ahmed/new_guide# nova-manage  service list
 
 Binary   HostZone Status State   
 Updated_At
 nova-network bodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-scheduler   bodega  nova enabled:-) 
 2012-11-15
 23:49:28
 nova-compute sonoma  nova enabledXXX 
 2012-11-15
 23:46:46
 = compute-node
 
 What I don't understand is even though nova-compute is listed on the
 control-node, the service is not running on the compute node.  That
 does not seem right.
 
 root@sonoma:~# service nova-compute status nova-compute stop/waiting
 root@sonoma:~# date;  service nova-compute start Thu Nov 15 15:48:08
 PST 2012 nova-compute start/running, process 2785 root@sonoma:~#
 service nova-compute status nova-compute stop/waiting root@sonoma:~#
 ps aux | grep nova
 root  2810  0.0  0.0   9384   924 pts/0S+   15:49   0:00 grep
 --color=auto nova
 root@sonoma:~# service  nova-compute status nova-compute stop/waiting
 root@sonoma:~#
 
 There are no log entries in the log files on compute-node or
 control-node.
 Any ideas please?
 
 
 Thank you,
 Ahmed.
 
 
 
 
 
 On 11/15/12 3:29 PM, Narayanan, Krishnaprasad
 naray...@uni-mainz.de
 wrote:
 
 Hi Ahmed,
 
 You can use the command nova-manage service list from the command
 line of control node to get the 

[Openstack] OpenStack Community Weekly Newsletter (Nov 9-16)

[Stefano Maffulli]

   Highlights of the week


 OpenStack Outreach Program for Women Accepting Candidates
 
http://www.openstack.org/blog/2012/11/openstack-outreach-program-for-women-accepting-candidates/

OpenStack provides open source software for building public and private 
clouds. We are constantly moving and growing and very excited to invite 
newcomers to our community. To this end, the OpenStack Foundation has 
joined the GNOME Outreach Program for Women 
https://live.gnome.org/OutreachProgramForWomen. Join the list of 
mentors, contribute ideas 
http://wiki.openstack.org/OutreachProgramForWomen/Ideas, apply as intern.



 What's new in libvirt for the OpenStack Nova Folsom release
 
http://berrange.com/posts/2012/11/16/what-was-new-in-libvirt-for-the-openstack-nova-folsom-release/

Even if Folsom has been out for a while now, Daniel P. Berrangé 
http://berrange.com/ provided a little more detail on some of the 
changes he was involved with making to the libvirt driver and what 
motivated them.



 Why to refactor the virt disk API in Nova
 http://berrange.com/posts/2012/11/15/692/

When launching a virtual machine, Nova http://openstack.org/ has the 
ability to inject various files into the disk image immediately prior to 
boot up. Nova runs as an unprivileged user, and the guest files to be 
changed are typically owned as root. This means all the file injection 
commands need to run via Nova's rootwrap utility to gain root 
privileges. It should come as little surprise that this has already 
resulted in a security vulnerability / CVE 
https://lists.launchpad.net/openstack/msg14089.html against Nova. The 
solution to this class of security problems is to decouple the file 
injection code from the host filesystem. Read more on Daniel's blog post 
http://berrange.com/posts/2012/11/15/692/.



 Swift 1.7.5 Released
 http://swiftstack.com/blog/2012/11/14/swift-1.7.5-release/

Swift 1.7.5 has been released. This release is the work of twenty-seven 
contributors and includes several important new features and bug fixes.



 Making keystoneclient python library a little easier to work with
 
http://www.rhonabwy.com/wp/2012/11/11/making-keystoneclient-python-library-a-little-easier-to-work-with/

A quick guide to using the python keystoneclient library and some of its 
new features, with v2 API examples throughout.



 Installing OpenStack Nova Compute on Hyper-V
 http://www.cloudbase.it/installing-openstack-nova-compute-on-hyper-v/

A lot of work went on OpenStack and Hyper-V integration, with the result 
of bringing back Hyper-V in the Nova sources 
https://github.com/openstack/nova in time for the Folsom release. Get 
started with OpenStack and Hyper-V using the installer developed by 
Cloudbase Solutions.



   Security Advisories

 * CVE-2012-4573, CVE-2012-5482 -- Authentication bypass for image
   deletion
   
http://secstack.org/2012/11/cve-2012-4573-cve-2012-5482-authentication-bypass-for-image-deletion/


   Tips and tricks

 * By Hui Cheng http://freedomhui.com/: How to Deploy Hadoop Cluster
   In Openstack Intances Using Apache Ambari
   
http://freedomhui.com/2012/11/how-to-deploy-hadoop-cluster-using-apache-ambari/
 * By Sébastien Han http://sebastien-han.fr/: OpenStack Retrieve
   usage statictics
   
http://sebastien-han.fr/blog/2012/11/09/tip-openstack-retrieve-usage-statictic/


   Upcoming Events

 * OpenStack Delhi NCR Meetup
   http://www.meetup.com/Indian-OpenStack-User-Group/events/90700582/
   Nov 17, 2012 -- Delhi, India Details
   http://www.meetup.com/Indian-OpenStack-User-Group/events/90700582/
 * Australian OpenStack User Group -- Brisbane Technical Meetup
   http://aosug.openstack.org.au/ Nov 20, 2012 -- Brisbane and other
   cities Details http://aosug.openstack.org.au/
 * OpenStack China Tour: Nanjing
   http://hui.csdn.net/MeetingInfo.aspx?mid=155 Nov 24, 2012 --
   Nanjing, China Details http://hui.csdn.net/MeetingInfo.aspx?mid=155
 * OpenStack Users November meetup
   http://www.meetup.com/Indian-OpenStack-User-Group/events/90021782/
   Nov 25, 2012 -- Bangalore, India Details
   http://www.meetup.com/Indian-OpenStack-User-Group/events/90021782/
 * OpenStack Israel http://www.meetup.com/IGTCloud/events/87103152/
   Nov 27, 2012 -- Tel Aviv, Israel Register
   http://www.meetup.com/IGTCloud/events/87103152/
 * OpenStack in action!
   http://openstackinaction3theopenrevolution.eventbrite.com/ Nov 29,
   2012 -- Paris, France Register
   http://openstackinaction3theopenrevolution.eventbrite.com/
 * Pune OpenStack Meetup
   http://www.meetup.com/Indian-OpenStack-User-Group/events/89610092/
   Dec 02, 2012 -- Pune, India Details
   http://www.meetup.com/Indian-OpenStack-User-Group/events/89610092/
 * EMEA OpenStack Day http://emeaopenstackday2.eventbrite.com/ Dec
   05, 2012 -- London Details http://emeaopenstackday2.eventbrite.com/


   Other news

 * MediaGoblin adding support to OpenStack Swift
   

[Openstack] Networking issues for openstack on XCP

[Yan Zhai]

Hi,

   I am trying a proof of concept install of openstack on xen cloud
platform. However, I am a little confused about the network part in Folsom.
   My architecture:
 1 Controller node: no Xen, only Ubuntu 12.04, everything for openstack
service except for nova-compute
 2 Compute node: XCP 1.6 beta, with nova-compute in special domU
(Ubuntu 12.04), xenapi plugin installed in dom0 already
 each node has two NIC, one with public IP (Only limited floating IP),
and another in private network (Any IP is OK)

   My goal for network:
 flat network or flat dhcp network. I want to use eth0 for public
traffic and service request, and eth1 for inter-vm traffic.

   My questions:
 1.) does each domU need nova-network running? My understanding is it's
OK to run nova-network individually, but then how to mange the floating IP
globally?
 2.) in document for flatdhcp network, I saw four interfaces for each
management domU. Is it OK to have only two interfaces? Say,
  eth0-xenbr0 for public IP and services, and eth1-xenbr1 for VM
network?
 3.) Is the network isolation rules a must for test install? I found
the patch to vif is still for xenserver 5.6_p2, and can not be applied to
vif of xcp 1.6 or xenserver 6.1, which might be a trouble.

   If anyone could help me kindly, it will be quite appreciated, I have
been stuck with install document for several days.

thanks a lot!
- Yan
___
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] Networking issues for openstack on XCP

[Robert Garron]

Yan,

In my opinion, if you are going to spend all the time learning a new 
product -- i.e. nova network vs quantum.  And if you are only testing a 
concept, I would spend it upon Folsom and move from Essex and/or nova 
network and nova storage.  Quantum eases many of the issues Nova network 
has  or had, but quantum is the system for support and deployment going 
forward just my 2 cents...


Robert



On 11/17/12 12:33 AM, Yan Zhai wrote:

Hi,

 I am trying a proof of concept install of openstack on xen cloud 
platform. However, I am a little confused about the network part in 
Folsom.

 My architecture:
   1 Controller node: no Xen, only Ubuntu 12.04, everything for 
openstack service except for nova-compute
   2 Compute node: XCP 1.6 beta, with nova-compute in special domU 
(Ubuntu 12.04), xenapi plugin installed in dom0 already
   each node has two NIC, one with public IP (Only limited floating 
IP), and another in private network (Any IP is OK)


   My goal for network:
 flat network or flat dhcp network. I want to use eth0 for public 
traffic and service request, and eth1 for inter-vm traffic.


   My questions:
   1.) does each domU need nova-network running? My understanding is 
it's OK to run nova-network individually, but then how to mange the 
floating IP globally?
 2.) in document for flatdhcp network, I saw four interfaces for 
each management domU. Is it OK to have only two interfaces? Say,
  eth0-xenbr0 for public IP and services, and eth1-xenbr1 for 
VM network?
 3.) Is the network isolation rules a must for test install? I 
found the patch to vif is still for xenserver 5.6_p2, and can not be 
applied to vif of xcp 1.6 or xenserver 6.1, which might be a trouble.


   If anyone could help me kindly, it will be quite appreciated, I 
have been stuck with install document for several days.


thanks a lot!
- Yan



___
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] Networking issues for openstack on XCP

[Yan Zhai]

Hi Robert,

 thanks for reply. Currently I am just looking for a way to bring it up for
internal trial, so if Quantum is better I will move to that. The only
reason that I am still asking for questions about nova-network is because
of the document order: I am setting things following the install document,
but when it comes to the network part I encountered above confusions. I
will check the quantum document to see if anything can be simplified.
Thanks again!

best
Yan

On Fri, Nov 16, 2012 at 11:54 PM, Robert Garron 
robert.gar...@access3000.net wrote:

  Yan,

 In my opinion, if you are going to spend all the time learning a new
 product -- i.e. nova network vs quantum.  And if you are only testing a
 concept, I would spend it upon Folsom and move from Essex and/or nova
 network and nova storage.  Quantum eases many of the issues Nova network
 has  or had, but quantum is the system for support and deployment going
 forward just my 2 cents...

 Robert




 On 11/17/12 12:33 AM, Yan Zhai wrote:

 Hi,

 I am trying a proof of concept install of openstack on xen cloud
 platform. However, I am a little confused about the network part in Folsom.
My architecture:
  1 Controller node: no Xen, only Ubuntu 12.04, everything for
 openstack service except for nova-compute
  2 Compute node: XCP 1.6 beta, with nova-compute in special domU
 (Ubuntu 12.04), xenapi plugin installed in dom0 already
  each node has two NIC, one with public IP (Only limited floating IP),
 and another in private network (Any IP is OK)

 My goal for network:
  flat network or flat dhcp network. I want to use eth0 for public
 traffic and service request, and eth1 for inter-vm traffic.

 My questions:
  1.) does each domU need nova-network running? My understanding is
 it's OK to run nova-network individually, but then how to mange the
 floating IP globally?
  2.) in document for flatdhcp network, I saw four interfaces for each
 management domU. Is it OK to have only two interfaces? Say,
   eth0-xenbr0 for public IP and services, and eth1-xenbr1 for VM
 network?
  3.) Is the network isolation rules a must for test install? I found
 the patch to vif is still for xenserver 5.6_p2, and can not be applied to
 vif of xcp 1.6 or xenserver 6.1, which might be a trouble.

 If anyone could help me kindly, it will be quite appreciated, I have
 been stuck with install document for several days.

  thanks a lot!
 - Yan



 ___
 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




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

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_quantum_trunk #47

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/47/Project:precise_grizzly_quantum_trunkDate of build:Fri, 16 Nov 2012 06:01:22 -0500Build duration:1 min 37 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove qpid configuration variables no longer supportedby gkottoneditetc/quantum.confConsole Output[...truncated 2518 lines...]Hunk #1 succeeded at 38 (offset 19 lines).patching file etc/quantum/plugins/linuxbridge/linuxbridge_conf.iniHunk #2 FAILED at 50.1 out of 2 hunks FAILED -- rejects in file etc/quantum/plugins/linuxbridge/linuxbridge_conf.inipatching file etc/quantum/plugins/metaplugin/metaplugin.inipatching file etc/quantum/plugins/nec/nec.inipatching file etc/quantum/plugins/nicira/nvp.inipatching file etc/quantum/plugins/openvswitch/ovs_quantum_plugin.inipatching file etc/quantum/plugins/ryu/ryu.iniHunk #2 succeeded at 43 (offset 27 lines).Patch fix-quantum-configuration.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5cdf2f3e-91de-4a9a-b01a-7a5ff6bae117', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5cdf2f3e-91de-4a9a-b01a-7a5ff6bae117', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/precise-grizzly-proposed /tmp/tmpfeblM_/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpfeblM_/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211160601~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [df54e34] plugin/ryu, linux/interface: remove ryu specific interface driverdch -a [7a07690] Allow NVP plugin to use per-tenant quota extensiondch -a [b4a0f65] Revert "Put gw_port into router dict result."dch -a [c8375cf] Ensure that fixed port IP address is in valid allocation range.dch -a [4f824cf] RESTProxy Plugin for Floodlight and BigSwitchdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5cdf2f3e-91de-4a9a-b01a-7a5ff6bae117', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-5cdf2f3e-91de-4a9a-b01a-7a5ff6bae117', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_python-quantumclient_trunk #5

[openstack-testing-bot]

Title: precise_grizzly_python-quantumclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-quantumclient_trunk/5/Project:precise_grizzly_python-quantumclient_trunkDate of build:Fri, 16 Nov 2012 10:01:21 -0500Build duration:3 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesConvenience cmds for l3by bozhueditquantumclient/shell.pyeditquantumclient/quantum/v2_0/network.pyeditquantumclient/tests/unit/test_cli20_port.pyeditquantumclient/quantum/v2_0/port.pyeditquantumclient/tests/unit/test_cli20_network.pyConsole Output[...truncated 2145 lines...]INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changes']File "pool/main/p/python-quantumclient/python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_all.deb" is already registered with different checksums!md5 expected: eb26c4f78225987876214cef3a9f1fd9, got: 5ff62f91d5179bf423145ec6bf589d3bsha1 expected: d1730bcd608c17fd19925ee2b675ae3b825b1cf3, got: c32fd7d8e856e225b8679001e3199a6547b06197sha256 expected: efe8e2229b4b55045c5d0a93fbec38d2f88e21072b7786241bc114665c584283, got: 3935a4e83a85dfadbd5161b1908104364cf4c317594b8fa695f17697ae1a45d5size expected: 42368, got: 42388There have been errors!ERROR:root:Error occurred during package creation/build: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254ERROR:root:Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/precise-grizzly-proposed /tmp/tmpsli8l4/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmpsli8l4/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/python-quantumclient --forcedch -b -D precise --newversion 1:2.1.9.g041a510+git201211161001~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [eb7a744] Convenience cmds for l3dch -a [57f0e91] Fix curl command for PUT and DELETE.dch -a [6857c2a] Fixes setup compatibility issue on Windowsdch -a [4ca0365] Adds securitygroup implementationdch -a [855c4a1] Add OpenStack trove classifier for PyPIdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changesTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.9.g041a510+git201211161001~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_python-quantumclient_trunk #5

[openstack-testing-bot]

Title: raring_grizzly_python-quantumclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-quantumclient_trunk/5/Project:raring_grizzly_python-quantumclient_trunkDate of build:Fri, 16 Nov 2012 10:01:22 -0500Build duration:4 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesConvenience cmds for l3by bozhueditquantumclient/tests/unit/test_cli20_port.pyeditquantumclient/shell.pyeditquantumclient/tests/unit/test_cli20_network.pyeditquantumclient/quantum/v2_0/network.pyeditquantumclient/quantum/v2_0/port.pyConsole Output[...truncated 2547 lines...]Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-quantumclient/python-quantumclient_2.1.7.g57f0e91+git20120201~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/python-quantumclient']bzr: ERROR: These branches have diverged.  See "bzr help diverged-branches" for more information.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/python-quantumclient']' returned non-zero exit status 3ERROR:root:Command '['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/python-quantumclient']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/raring-grizzly-proposed /tmp/tmpHOYl6I/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmpHOYl6I/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 855c4a1209d03c9aeeb5fa04310cb78b576ff404..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/python-quantumclient --forcedch -b -D raring --newversion 1:2.1.9.g041a510+git201211161001~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [eb7a744] Convenience cmds for l3dch -a [57f0e91] Fix curl command for PUT and DELETE.dch -a [6857c2a] Fixes setup compatibility issue on Windowsdch -a [4ca0365] Adds securitygroup implementationdch -a [c8e7ed2] Generate bash_completion string so that we can use bash completion.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.1.9.g041a510+git201211161001~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A python-quantumclient_2.1.9.g041a510+git201211161001~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-quantumclient_2.1.9.g041a510+git201211161001~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly python-quantumclient_2.1.9.g041a510+git201211161001~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/quantum/python-quantumclientTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/python-quantumclient']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/python-quantumclient']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #116

[openstack-testing-bot]

Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/116/Project:precise_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 11:01:26 -0500Build duration:2 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSync eventlet_backdoor from oslo.by treinisheditopenstack-common.confaddnova/openstack/common/eventlet_backdoor.pyConsole Output[...truncated 3957 lines...]git log beacd8b668fc5aaef5ee49677add1dde49582b92..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211161102~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-33c3c037-2a8f-468d-b882-a1ce03b9f6e3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-33c3c037-2a8f-468d-b882-a1ce03b9f6e3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #118

[openstack-testing-bot]

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/118/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 11:01:24 -0500Build duration:4 min 13 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSync eventlet_backdoor from oslo.by treinishaddnova/openstack/common/eventlet_backdoor.pyeditopenstack-common.confConsole Output[...truncated 5138 lines...]git log beacd8b668fc5aaef5ee49677add1dde49582b92..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211161102~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-75b8dd60-6ed5-4f74-9b0e-0b95a4c0979e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-75b8dd60-6ed5-4f74-9b0e-0b95a4c0979e', '-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_python-keystoneclient_trunk #77

[openstack-testing-bot]

Title: quantal_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-keystoneclient_trunk/77/Project:quantal_folsom_python-keystoneclient_trunkDate of build:Fri, 16 Nov 2012 12:33:55 -0500Build duration:1 min 8 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changescheck creds before token/endpoint (bug 1076233)by dolph.mathewseditkeystoneclient/shell.pyCheck for auth URL before password (bug 1076235)by dolph.mathewseditkeystoneclient/shell.pyConsole Output[...truncated 924 lines...]hard linking tools/pip-requires -> python-keystoneclient-0.1.3.80.g27f0c72/toolshard linking tools/test-requires -> python-keystoneclient-0.1.3.80.g27f0c72/toolshard linking tools/with_venv.sh -> python-keystoneclient-0.1.3.80.g27f0c72/toolscopying setup.cfg -> python-keystoneclient-0.1.3.80.g27f0c72Writing python-keystoneclient-0.1.3.80.g27f0c72/setup.cfgcreating distCreating tar archiveremoving 'python-keystoneclient-0.1.3.80.g27f0c72' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 0.1.3.80.g27f0c72INFO:root:Building package using /tmp/tmpxbazKv/python-keystoneclient_0.1.3.80.g27f0c72+git201211161233~quantal.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:10e16be489dc13ff44d1abad71fc7ad259838a10INFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '76b7d92dcc189908000f7d70d3f75c5c3aec3e73..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 0.1.3.66.gf617b09+git201211092231~quantal. M  debian/changelogText conflict in debian/changelog1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom-proposed /tmp/tmpxbazKv/python-keystoneclientmk-build-deps -i -r -t apt-get -y /tmp/tmpxbazKv/python-keystoneclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 76b7d92dcc189908000f7d70d3f75c5c3aec3e73..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/python-keystoneclient/quantal-folsom', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #119

[openstack-testing-bot]

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/119/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 12:31:24 -0500Build duration:4 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd support for resizes to resource tracker.by brian.elliotteditnova/compute/resource_tracker.pyeditnova/compute/api.pyeditnova/compute/stats.pyeditnova/tests/compute/test_claims.pyeditnova/compute/claims.pyeditnova/compute/manager.pyeditnova/tests/compute/test_resource_tracker.pyupdate api_samples add os-server-start-stopby sdagueadddoc/api_samples/os-server-start-stop/server-post-resp.jsonadddoc/api_samples/os-server-start-stop/server-post-req.jsoneditdoc/api_samples/os-server-start-stop/server_start_stop.xmladddoc/api_samples/os-server-start-stop/server-post-req.xmladddoc/api_samples/os-server-start-stop/server-post-resp.xmlConsole Output[...truncated 5148 lines...]dch -b -D raring --newversion 2013.1+git201211161232~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [b349340] update api_samples add os-server-start-stopdch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [5bc0ff6] Add support for resizes to resource tracker.dch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-73e5bf5b-e803-473f-9460-b27b160b105a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-73e5bf5b-e803-473f-9460-b27b160b105a', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #117

[openstack-testing-bot]

Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/117/Project:precise_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 12:33:39 -0500Build duration:3 min 10 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd support for resizes to resource tracker.by brian.elliotteditnova/tests/compute/test_claims.pyeditnova/compute/stats.pyeditnova/compute/claims.pyeditnova/tests/compute/test_resource_tracker.pyeditnova/compute/manager.pyeditnova/compute/api.pyeditnova/compute/resource_tracker.pyupdate api_samples add os-server-start-stopby sdagueadddoc/api_samples/os-server-start-stop/server-post-req.jsoneditdoc/api_samples/os-server-start-stop/server_start_stop.xmladddoc/api_samples/os-server-start-stop/server-post-resp.xmladddoc/api_samples/os-server-start-stop/server-post-resp.jsonadddoc/api_samples/os-server-start-stop/server-post-req.xmlConsole Output[...truncated 3967 lines...]dch -b -D precise --newversion 2013.1+git201211161234~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [b349340] update api_samples add os-server-start-stopdch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [5bc0ff6] Add support for resizes to resource tracker.dch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-e2180183-37e7-41b5-b6fa-27ed33885deb', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-e2180183-37e7-41b5-b6fa-27ed33885deb', '-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_swift_stable #110

[openstack-testing-bot]

-server.conf-sampleedittest/unit/common/middleware/test_proxy_logging.pystatsd timing refactorby darrelleditswift/obj/server.pyeditswift/container/server.pyeditswift/common/utils.pyeditswift/account/server.pyeditdoc/source/admin_guide.rstedittest/unit/common/test_utils.pyupdated for 1.7.5 releaseby meeditCHANGELOGeditAUTHORS1.7.6 version bumpby meeditswift/__init__.pyUse computed size on object PUT, not fstat.by sameditswift/obj/server.pyFixed bugs with internal client and object expirerby z-launchpadedittest/unit/common/test_internal_client.pyeditswift/obj/expirer.pyeditswift/common/internal_client.pyedittest/unit/obj/test_expirer.pyFixed swift-bench when using -b and a conf fileby joeeditbin/swift-bencheditswift/common/bench.pyuse Host: for location rewritesby mikeeditswift/common/swob.pyedittest/unit/common/test_swob.pycharset for default responsesby mikeeditswift/common/swob.pyedittest/unit/common/test_swob.pyMake DELETE requests to expired objects return 404.by sameditswift/obj/server.pyedittest/unit/obj/test_server.pygive swob default content-typeby mikeeditswift/proxy/controllers/base.pyedittest/functionalnosetests/test_container.pyeditswift/common/swob.pyedittest/functionalnosetests/test_object.pyMake swift-bench use less memory with large object sizes.by sameditswift/common/direct_client.pyeditswift/common/bench.pyfix error with setting max age and incorrect testsby meedittest/unit/proxy/test_server.pyeditswift/proxy/controllers/base.pyBetter TempAuth storage URL guessingby z-launchpadeditetc/proxy-server.conf-sampleeditdoc/source/deployment_guide.rstedittest/unit/common/middleware/test_tempauth.pyeditswift/common/swob.pyedittest/unit/common/test_swob.pyeditswift/common/middleware/tempauth.pyfix bug1039861, remove license header in doc/source/conf.py.by mail.zhang.yeeeditdoc/source/conf.pyFix 500 on GET of many-segment manifest.by sameditswift/common/middleware/proxy_logging.pyedittest/unit/common/middleware/test_proxy_logging.pypatch utils.HASH_PATH_SUFFIX in proxy unittestsby clay.gerrardedittest/unit/proxy/test_server.pyRemove outdated Debian packaging guide.by sameditdoc/source/index.rsteditdoc/source/getting_started.rstdeletedoc/source/debian_package_guide.rstfix bug in deleting account memcache.by alex890714editswift/proxy/controllers/account.pyRefactor db_replicators roundrobin_datadirsby z-launchpadedittest/unit/common/test_db_replicator.pyeditswift/common/db_replicator.pyUpdating doc reflecting the move of auth_token.by chmoueleditdoc/source/overview_auth.rstConsole Output[...truncated 2761 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 46Source-Version: 1.7.6+git201211161249~precise-0ubuntu1Space: 17648Status: attemptedVersion: 1.7.6+git201211161249~precise-0ubuntu1Finished at 20121116-1251Build needed 00:00:46, 17648k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161249~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161249~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpfDQMnC/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpfDQMnC/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.6+git201211161249~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [101f566] Updating doc reflecting the move of auth_token.dch -a [4e5889d] Refactor db_replicator's roundrobin_datadirsdch -a [1701b6b] fix bug in deleting account memcache.dch -a [bf90ba2] Remove outdated Debian packaging guide.dch -a [4236e63] patch utils.HASH_PATH_SUFFIX in proxy unittestsdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211161249~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.6+git201211161249~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_nova_stable #652

[openstack-testing-bot]

Title: precise_folsom_nova_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_stable/652/Project:precise_folsom_nova_stableDate of build:Fri, 16 Nov 2012 12:44:26 -0500Build duration:13 minBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changesread_deleted snapshot and volume id mappings.by adam.gandelmaneditnova/db/sqlalchemy/api.pyhandles empty dhcp_domain with hostname in metadataby melwitteditnova/api/metadata/base.pyAvoid leaking BDMs for deleted instances.by eglynneditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyFix issues deleting instances in RESIZED stateby chuck.shorteditnova/tests/compute/test_compute.pyeditnova/compute/api.pylibvirt: allows attach and detach from all domainsby chuck.shorteditnova/virt/libvirt/driver.pyeditnova/tests/fakelibvirt.pyxenapi: Refactor snapshots during resizeby chuck.shorteditnova/virt/xenapi/vm_utils.pyeditnova/virt/xenapi/driver.pyeditnova/tests/test_xenapi.pyeditnova/virt/xenapi/volumeops.pyeditnova/compute/manager.pyeditnova/virt/xenapi/vmops.pylibvirt: Fix _cleanup_resizeby chuck.shorteditnova/virt/libvirt/driver.pyeditnova/tests/test_libvirt.pyConsistent Rollback for instance creation failuresby andy.mccraeeditnova/compute/api.pyAdd call to trigger_instance[add/remove]_security_group_refresh quantumby aroseneditnova/network/quantumv2/api.pyDetect and fix issues caused by vol ID migrationby john.griffitheditnova/tests/api/ec2/test_cloud.pyeditnova/volume/driver.pyeditnova/volume/manager.pyeditnova/volume/iscsi.pyeditetc/nova/rootwrap.d/volume.filterspin sqlalchemy to the 0.7.x seriesby sdagueedittools/pip-requiresFix nova-network MAC collision logicby revieweditnova/db/sqlalchemy/api.pyeditnova/tests/network/test_manager.pyFix reserve_block_device_name while attach volumeby vishvanandaeditnova/compute/manager.pycreate_db_entry_for_new_instance did not call sgh for defaultby aroseneditnova/compute/api.pyFix VM deletion from down compute nodeby vishvanandaeditnova/compute/api.pyeditnova/tests/compute/test_compute.pyeditnova/network/manager.pyFixed instance deletion issue from Nova API.by vishvanandaeditnova/tests/compute/test_compute.pyeditnova/compute/api.py fix deletion of LVM backed instancesby heut2008editnova/virt/libvirt/utils.pyMake resource tracker uses faster DB queryby mikaleditnova/tests/compute/test_resource_tracker.pyeditnova/tests/compute/test_compute.pyeditnova/compute/resource_tracker.pyFix incorrect LOG.error usage in _compare_cpuby mikaleditnova/virt/libvirt/driver.pyConsole Output[...truncated 19007 lines...]deleting and forgetting pool/main/n/nova/nova-compute-qemu_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-uml_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xcp_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xen_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-novncproxy_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2012.2+git201210091907~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2012.2+git201210091907~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-folsom']Pushed up to revision 402.2 tags updated.INFO:root:Storing current commit for next build: 92eddd2d471269835ade19412a28539fa9246bfcINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpj6kcjh/novamk-build-deps -i -r -t apt-get -y /tmp/tmpj6kcjh/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges 

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_keystone_trunk #27

[openstack-testing-bot]

Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/27/Project:precise_grizzly_keystone_trunkDate of build:Fri, 16 Nov 2012 13:02:53 -0500Build duration:6 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMake the controller addresses configurable.by jhenneredittools/sample_data.shImported Translations from Transifexby ayoungaddkeystone/locale/ca/LC_MESSAGES/keystone.poeditkeystone/locale/keystone.potaddkeystone/locale/ja/LC_MESSAGES/keystone.poConsole Output[...truncated 14999 lines...]Machine Architecture: amd64Package: keystonePackage-Time: 187Source-Version: 2013.1+git201211161303~precise-0ubuntu1Space: 11272Status: attemptedVersion: 2013.1+git201211161303~precise-0ubuntu1Finished at 20121116-1308Build needed 00:03:07, 11272k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211161303~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211161303~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-grizzly-proposed /tmp/tmp70P_8Z/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmp70P_8Z/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211161303~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [a92b1da] Imported Translations from Transifexdch -a [90ebf9f] Make the controller addresses configurable.dch -a [be754ff] Refactor TokenController.authenticate() method.dch -a [2b83d4d] Fix error un fixtures.dch -a [9d68b40] Ensures User is member of tenant in ec2 validationdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201211161303~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201211161303~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211161303~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201211161303~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_python-keystoneclient_trunk #16

[openstack-testing-bot]

Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/16/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Fri, 16 Nov 2012 13:09:11 -0500Build duration:2 min 23 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesCheck for auth URL before password (bug 1076235)by dolph.mathewseditkeystoneclient/shell.pyConsole Output[...truncated 2105 lines...]Finished at 20121116-1311Build needed 00:00:59, 2176k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_source.changes']gpg: Signature made Fri Nov 16 13:10:27 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Fri Nov 16 13:10:27 2012 EST 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/tmpmjX6o4/python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpmjX6o4/python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1.dsc: done.  Uploading python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise.orig.tar.gz: done.  Uploading python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1.debian.tar.gz: done.  Uploading python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-keystoneclient/python-keystoneclient_0.1.3.72.gb111637+git201211152106~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly']Pushed up to revision 35.INFO:root:Storing current commit for next build: 10e16be489dc13ff44d1abad71fc7ad259838a10INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly-proposed /tmp/tmpmjX6o4/python-keystoneclientmk-build-deps -i -r -t apt-get -y /tmp/tmpmjX6o4/python-keystoneclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzly --forcedch -b -D precise --newversion 1:0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-keystoneclient_0.1.3.80.g27f0c72+git201211161309~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-keystoneclient/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #118

[openstack-testing-bot]

Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/118/Project:precise_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 14:31:23 -0500Build duration:3 min 1 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSwitch to using eventlet_backdoor from oslo.by treinishdeletenova/common/eventlet_backdoor.pyeditnova/service.pyAdd some sqlalchemy tweakablesby cbehrenseditnova/db/sqlalchemy/session.pyeditnova/config.pyEnsure cat process is terminatedby dimseditnova/tests/test_nova_rootwrap.pyConsole Output[...truncated 3975 lines...]dch -a [b349340] update api_samples add os-server-start-stopdch -a [73ea19a] Switch to using eventlet_backdoor from oslo.dch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [5bc0ff6] Add support for resizes to resource tracker.dch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-21306287-1cf3-484a-bb7a-56d4834a2917', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-21306287-1cf3-484a-bb7a-56d4834a2917', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #120

[openstack-testing-bot]

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/120/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 14:31:23 -0500Build duration:3 min 54 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSwitch to using eventlet_backdoor from oslo.by treinishdeletenova/common/eventlet_backdoor.pyeditnova/service.pyAdd some sqlalchemy tweakablesby cbehrenseditnova/db/sqlalchemy/session.pyeditnova/config.pyEnsure cat process is terminatedby dimseditnova/tests/test_nova_rootwrap.pyConsole Output[...truncated 5156 lines...]dch -a [b349340] update api_samples add os-server-start-stopdch -a [73ea19a] Switch to using eventlet_backdoor from oslo.dch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [5bc0ff6] Add support for resizes to resource tracker.dch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-8a537d8c-7407-493f-a492-d87b7984cf7e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-8a537d8c-7407-493f-a492-d87b7984cf7e', '-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_swift_stable #111

[openstack-testing-bot]

Title: precise_folsom_swift_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_stable/111/Project:precise_folsom_swift_stableDate of build:Fri, 16 Nov 2012 15:01:21 -0500Build duration:3 min 3 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changeschange catch_errors to use WSGIContextby meeditswift/common/middleware/catch_errors.pyedittest/unit/common/middleware/test_except.pyRefactor http_connect() to use http_connect_raw()by peter.portanteeditswift/common/bufferedhttp.pyConsole Output[...truncated 2761 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 67Source-Version: 1.7.6+git201211161501~precise-0ubuntu1Space: 17648Status: attemptedVersion: 1.7.6+git201211161501~precise-0ubuntu1Finished at 20121116-1504Build needed 00:01:07, 17648k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161501~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161501~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpWOzB23/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpWOzB23/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.6+git201211161501~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [259aafb] Refactor http_connect() to use http_connect_raw()dch -a [101f566] Updating doc reflecting the move of auth_token.dch -a [4e5889d] Refactor db_replicator's roundrobin_datadirsdch -a [20d4b00] change catch_errors to use WSGIContextdch -a [1701b6b] fix bug in deleting account memcache.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211161501~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.6+git201211161501~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161501~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161501~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #121

[openstack-testing-bot]

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/121/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 16:01:23 -0500Build duration:3 min 57 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesChange a toplevel function comment to a docstring.by driptoneditnova/db/sqlalchemy/api.pyConsole Output[...truncated 5159 lines...]dch -a [b349340] update api_samples add os-server-start-stopdch -a [73ea19a] Switch to using eventlet_backdoor from oslo.dch -a [0f57821] Sync eventlet_backdoor from oslo.dch -a [65686d7] Fix use of 'volume' variable namedch -a [fa26d7f] Ditch unused import and variabledch -a [fe27642] Adds documentation for Hyper-V testingdch -a [a071a90] Adds support for ConfigDriveV2 in Hyper-Vdch -a [3f95c7a] don't explode if a 413 didn't set Retry-Afterdch -a [531ebc0] Fix a couple uses of FLAGSdch -a [1cd7ba8] Remove nova.flags imports from scheduler codedch -a [c9575fd] Remove some unused imports from compute/*dch -a [f283bec] Remove importing of flags from compute/*dch -a [e374fb0] Remove nova.flags imports from bin/*dch -a [dd0a268] Move nova shared config options to nova.configdch -a [1b45592] Fix use_single_default_gatewaydch -a [425af5b] Update api_samples README.rst to use toxdch -a [3498d0d] Do not alias stdlib uuid module as uuidutils, since nova has uuidutils.dch -a [0c1fb6a] Allow group='foo' in self.flags() for tests.dch -a [123fa7b] updated api_samples with real hypervisor_hostnamedch -a [137e0d7] Issue a hard shutdown if clean fails on resize updch -a [543d22e] Fix network RPC API backwards compatdch -a [45402ff] create_db_entry_for_new_instance did not call sgh for defaultdch -a [f92c1dd] Add support for backdoor_port to be returned with a rpc call.dch -a [e85156e] Move all mount classes into a subdirectorydch -a [5bc0ff6] Add support for resizes to resource tracker.dch -a [a220aa1] API extension for fpinging instancesdch -a [e0921b8] Allow controller extensions to extend update/showdch -a [8d59c47] Enable Quantum linux bridge VIF driver to use "bridge" typedebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-83112ff9-8352-4f2c-9984-0694e946f63e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-83112ff9-8352-4f2c-9984-0694e946f63e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_glance_trunk #20

[openstack-testing-bot]

Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/20/Project:precise_grizzly_glance_trunkDate of build:Fri, 16 Nov 2012 18:01:22 -0500Build duration:2 min 25 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd note about urlencoding the sql_connection config optby bcwaldoneditdoc/source/configuring.rstConsole Output[...truncated 2237 lines...]Hunk #10 succeeded at 389 (offset 3 lines).Hunk #11 succeeded at 427 (offset 3 lines).Hunk #12 succeeded at 476 (offset 3 lines).Hunk #13 succeeded at 537 (offset 3 lines).Hunk #14 succeeded at 560 (offset 3 lines).Hunk #15 succeeded at 593 (offset 3 lines).patching file glance/tests/unit/v2/test_image_data_resource.pyHunk #1 succeeded at 16 with fuzz 1.Hunk #3 succeeded at 156 (offset 1 line).Hunk #4 succeeded at 228 (offset 1 line).Patch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1774014a-7e7b-48e6-bb65-67cb6218ecb8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1774014a-7e7b-48e6-bb65-67cb6218ecb8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-grizzly-proposed /tmp/tmpj_CyT8/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpj_CyT8/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211161801~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [5acfb0c] Add note about urlencoding the sql_connection config optdch -a [43ba08d] Add an image domain model and related helpers.dch -a [4c86cf4] Fix simple db image_get to look like sqlalchemydch -a [1758e86] Return 403 on images you can see but can't modifydch -a [d635c41] Fixes is_image_visible to not use deleted keydebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1774014a-7e7b-48e6-bb65-67cb6218ecb8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-1774014a-7e7b-48e6-bb65-67cb6218ecb8', '-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: precise_grizzly_python-novaclient_trunk #11

[openstack-testing-bot]

Title: precise_grizzly_python-novaclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-novaclient_trunk/11/Project:precise_grizzly_python-novaclient_trunkDate of build:Fri, 16 Nov 2012 18:03:47 -0500Build duration:3 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesAdding support to filter instances by tenant from the admin apiby paul.voccioeditnovaclient/v1_1/shell.pyConsole Output[...truncated 2447 lines...]gpg: Signature made Fri Nov 16 18:05:25 2012 EST using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpim9Kuk/python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpim9Kuk/python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1.dsc: done.  Uploading python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise.orig.tar.gz: done.  Uploading python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1.debian.tar.gz: done.  Uploading python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-novaclient/python-novaclient_2.9.0.30.ga84300f+git201211071804~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-novaclient/precise-grizzly']Pushed up to revision 45.INFO:root:Storing current commit for next build: aa8d44c551643bb97e039624d602bd4ad07cbe9cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-novaclient/precise-grizzly-proposed /tmp/tmpim9Kuk/python-novaclientmk-build-deps -i -r -t apt-get -y /tmp/tmpim9Kuk/python-novaclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e9c16ca33ad035fda38d42ec3f7e9e40e56cbf6b..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-novaclient/precise-grizzly --forcedch -b -D precise --newversion 1:2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [aa8d44c] Adding support to filter instances by tenant from the admin apidch -a [aa56221] discover extensions via entry pointsdch -a [4ad512b] show help when calling without argumentsdch -a [8be01b6] Fixes setup compatibility issue on Windowsdch -a [33b2830] Allows deletion of multiple servers through CLIdch -a [51faac4] Add ability of nova client to display availability zones when listing hostsdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-novaclient_2.9.0.33.gaa8d44c+git201211161803~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-novaclient/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_swift_stable #112

[openstack-testing-bot]

Title: precise_folsom_swift_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_stable/112/Project:precise_folsom_swift_stableDate of build:Fri, 16 Nov 2012 18:06:48 -0500Build duration:3 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changescheck response status in WSGIContext._app_callby mikeeditswift/common/wsgi.pyRefactor DiskFile to hide temp file names and extsby peter.portanteedittest/unit/obj/test_auditor.pyedittest/unit/obj/test_server.pyeditswift/obj/server.pyUse a delta timeout for memcache where possibleby peter.portanteeditswift/common/memcached.pyedittest/unit/common/test_memcached.pyConsole Output[...truncated 2761 lines...]Machine Architecture: amd64Package: swiftPackage-Time: 58Source-Version: 1.7.6+git201211161806~precise-0ubuntu1Space: 17664Status: attemptedVersion: 1.7.6+git201211161806~precise-0ubuntu1Finished at 20121116-1809Build needed 00:00:58, 17664k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161806~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161806~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpbE1B0n/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpbE1B0n/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.6+git201211161806~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [1ac7b88] Use a delta timeout for memcache where possibledch -a [259aafb] Refactor http_connect() to use http_connect_raw()dch -a [101f566] Updating doc reflecting the move of auth_token.dch -a [4e5889d] Refactor db_replicator's roundrobin_datadirsdch -a [20d4b00] change catch_errors to use WSGIContextdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.6+git201211161806~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.6+git201211161806~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161806~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.6+git201211161806~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_python-glanceclient_trunk #93

[openstack-testing-bot]

Title: quantal_folsom_python-glanceclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-glanceclient_trunk/93/Project:quantal_folsom_python-glanceclient_trunkDate of build:Fri, 16 Nov 2012 20:01:21 -0500Build duration:3 min 24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUnpin keystoneclient dependencyby bcwaldonedittools/pip-requiresConsole Output[...truncated 2039 lines...]Status: attemptedVersion: 1:0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1Finished at 20121116-2004Build needed 00:01:49, 888k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom-proposed /tmp/tmpBxMx2G/python-glanceclientmk-build-deps -i -r -t apt-get -y /tmp/tmpBxMx2G/python-glanceclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log cdc06d9fdb15cd19bd5d26304dfebf092c6c8df8..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom --forcedch -b -D quantal --newversion 1:0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [8d81623] Unpin keystoneclient dependencydch -a [6c201e6] Fixes bug on Windows related to a wrong API urldch -a [00eff28] Enhance --checksum help with algorithmdch -a [16aafa7] Fixes setup compatibility issue on Windowsdch -a [8b2c227] Allow deletion of multiple images through CLIdch -a [1e14e82] Fixes shell command for member-deletedch -a [c420fa1] Add OpenStack trove classifier for PyPIdch -a [556082c] Implement blueprint ssl-connect-reworkdch -a [727aadb] Handle create/update of images with unknown sizedch -a [b5d46e2] Display acceptable disk/container formats in help textdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-glanceclient_0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A python-glanceclient_0.5.1.24.g1899ac2+git201211162001~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~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.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~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_grizzly_python-glanceclient_trunk #5

[openstack-testing-bot]

Title: precise_grizzly_python-glanceclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-glanceclient_trunk/5/Project:precise_grizzly_python-glanceclient_trunkDate of build:Fri, 16 Nov 2012 20:01:21 -0500Build duration:3 min 41 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUnpin keystoneclient dependencyby bcwaldonedittools/pip-requiresConsole Output[...truncated 1820 lines...]Machine Architecture: amd64Package: python-glanceclientPackage-Time: 123Source-Version: 1:0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1Space: 884Status: attemptedVersion: 1:0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1Finished at 20121116-2005Build needed 00:02:03, 884k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-glanceclient/precise-grizzly-proposed /tmp/tmpfhcmK3/python-glanceclientmk-build-deps -i -r -t apt-get -y /tmp/tmpfhcmK3/python-glanceclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-glanceclient/precise-grizzly --forcedch -b -D precise --newversion 1:0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [8d81623] Unpin keystoneclient dependencydch -a [6c201e6] Fixes bug on Windows related to a wrong API urldch -a [00eff28] Enhance --checksum help with algorithmdch -a [16aafa7] Fixes setup compatibility issue on Windowsdch -a [8b2c227] Allow deletion of multiple images through CLIdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'python-glanceclient_0.5.1.24.g1899ac2+git201211162001~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp