Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Chathura M. Sarathchandra Magurawalage
Hello guys,

The problem still exists. Any ideas?

Thanks

On 15 February 2013 14:37, Sylvain Bauza sylvain.ba...@digimind.com wrote:

 Metadata API allows to fetch SSH credentials when booting (pubkey I mean).
 If a VM is unable to reach metadata service, then it won't be able to get
 its public key, so you won't be able to connect, unless you specifically go
 thru a Password authentication (provided password auth is enabled in
 /etc/ssh/sshd_config, which is not the case with Ubuntu cloud archive).
 There is also a side effect, the boot process is longer as the instance is
 waiting for the curl timeout (60sec.) to finish booting up.

 Re: Quantum, the metadata API is actually DNAT'd from Network node to the
 Nova-api node (here 172.16.0.1 as internal management IP) :
 Chain quantum-l3-agent-PREROUTING (1 references)

 target prot opt source   destination
 DNAT   tcp  --  0.0.0.0/0169.254.169.254  tcp dpt:80
 to:172.16.0.1:8775


 Anyway, the first step is to :
 1. grab the console.log
 2. access thru VNC to the desired instance

 Troubleshooting will be easier once that done.

 -Sylvain



 Le 15/02/2013 14:24, Chathura M. Sarathchandra Magurawalage a écrit :

 Hello Guys,

 Not sure if this is the right port but these are the results:

 *Compute node:*


 root@computenode:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775  0.0.0.0:*
 LISTEN

 *Controller: *


 root@controller:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775  0.0.0.0:*
 LISTEN

 *Additionally I cant curl 169.254.169.254 from the compute node. I am not
 sure if this is related to not being able to PING the VM.*


 curl -v http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...

 Thanks for your help


 --**--**
 --**--**-
 Chathura Madhusanka Sarathchandra Magurawalage.
 1NW.2.1, Desk 2
 School of Computer Science and Electronic Engineering
 University Of Essex
 United Kingdom.

 Email: csar...@essex.ac.uk mailto:csar...@essex.ac.uk
   
 chathura.sarathchandra@gmail.**comchathura.sarathchan...@gmail.commailto:
 77.chath...@gmail.com
 77.chath...@gmail.com mailto:77.chath...@gmail.com



 On 15 February 2013 11:03, Anil Vishnoi vishnoia...@gmail.com mailto:
 vishnoia...@gmail.com** wrote:

 If you are using ubuntu cloud image then the only way to log-in is
 to do ssh with the public key. For that you have to create ssh key
 pair and download the ssh key. You can create this ssh pair using
 horizon/cli.


 On Fri, Feb 15, 2013 at 4:27 PM, Sylvain Bauza
 sylvain.ba...@digimind.com 
 mailto:sylvain.bauza@**digimind.comsylvain.ba...@digimind.com
 

 wrote:


 Le 15/02/2013 11:42, Chathura M. Sarathchandra Magurawalage a
 écrit :


 How can I log into the VM from VNC? What are the credentials?


 You have multiple ways to get VNC access. The easiest one is
 thru Horizon. Other can be looking at the KVM command-line for
 the desired instance (on the compute node) and check the vnc
 port in use (assuming KVM as hypervisor).
 This is basic knowledge of Nova.



 nova-api-metadata is running fine in the compute node.


 Make sure the metadata port is avaible thanks to telnet or
 netstat, nova-api can be running without listening on metadata
 port.




 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 
 https://launchpad.net/%**7Eopenstackhttps://launchpad.net/%7Eopenstack
 
 Post to : openstack@lists.launchpad.net
 
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 
 https://launchpad.net/%**7Eopenstackhttps://launchpad.net/%7Eopenstack
 

 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp




 -- Thanks  Regards
 --Anil Kumar Vishnoi




___
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] Cant ping private or floating IP

2013-02-16 Thread Jean-Baptiste RANSY
Hello Chathura,

Are you using Folsom with Network Namespaces ?

If yes, have a look here :
http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html


Regards,

Jean-Baptsite RANSY


On 02/16/2013 05:01 PM, Chathura M. Sarathchandra Magurawalage wrote:
 Hello guys,

 The problem still exists. Any ideas?

 Thanks 

 On 15 February 2013 14:37, Sylvain Bauza sylvain.ba...@digimind.com
 mailto:sylvain.ba...@digimind.com wrote:

 Metadata API allows to fetch SSH credentials when booting (pubkey
 I mean).
 If a VM is unable to reach metadata service, then it won't be able
 to get its public key, so you won't be able to connect, unless you
 specifically go thru a Password authentication (provided password
 auth is enabled in /etc/ssh/sshd_config, which is not the case
 with Ubuntu cloud archive).
 There is also a side effect, the boot process is longer as the
 instance is waiting for the curl timeout (60sec.) to finish
 booting up.

 Re: Quantum, the metadata API is actually DNAT'd from Network node
 to the Nova-api node (here 172.16.0.1 as internal management IP) :
 Chain quantum-l3-agent-PREROUTING (1 references)

 target prot opt source   destination
 DNAT   tcp  --  0.0.0.0/0 http://0.0.0.0/0  
  169.254.169.254  tcp dpt:80 to:172.16.0.1:8775
 http://172.16.0.1:8775


 Anyway, the first step is to :
 1. grab the console.log
 2. access thru VNC to the desired instance

 Troubleshooting will be easier once that done.

 -Sylvain



 Le 15/02/2013 14:24, Chathura M. Sarathchandra Magurawalage a écrit :

 Hello Guys,

 Not sure if this is the right port but these are the results:

 *Compute node:*


 root@computenode:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775
 http://0.0.0.0:8775  0.0.0.0:*   LISTEN

 *Controller: *


 root@controller:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775
 http://0.0.0.0:8775  0.0.0.0:*   LISTEN

 *Additionally I cant curl 169.254.169.254 from the compute
 node. I am not sure if this is related to not being able to
 PING the VM.*


 curl -v http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...

 Thanks for your help


 
 -
 Chathura Madhusanka Sarathchandra Magurawalage.
 1NW.2.1, Desk 2
 School of Computer Science and Electronic Engineering
 University Of Essex
 United Kingdom.

 Email: csar...@essex.ac.uk mailto:csar...@essex.ac.uk
 mailto:csar...@essex.ac.uk mailto:csar...@essex.ac.uk
   chathura.sarathchan...@gmail.com
 mailto:chathura.sarathchan...@gmail.com
 mailto:77.chath...@gmail.com mailto:77.chath...@gmail.com
 77.chath...@gmail.com mailto:77.chath...@gmail.com
 mailto:77.chath...@gmail.com mailto:77.chath...@gmail.com



 On 15 February 2013 11:03, Anil Vishnoi vishnoia...@gmail.com
 mailto:vishnoia...@gmail.com mailto:vishnoia...@gmail.com
 mailto:vishnoia...@gmail.com wrote:

 If you are using ubuntu cloud image then the only way to
 log-in is
 to do ssh with the public key. For that you have to create
 ssh key
 pair and download the ssh key. You can create this ssh
 pair using
 horizon/cli.


 On Fri, Feb 15, 2013 at 4:27 PM, Sylvain Bauza
 sylvain.ba...@digimind.com
 mailto:sylvain.ba...@digimind.com
 mailto:sylvain.ba...@digimind.com
 mailto:sylvain.ba...@digimind.com

 wrote:


 Le 15/02/2013 11:42, Chathura M. Sarathchandra
 Magurawalage a
 écrit :


 How can I log into the VM from VNC? What are the
 credentials?


 You have multiple ways to get VNC access. The easiest
 one is
 thru Horizon. Other can be looking at the KVM
 command-line for
 the desired instance (on the compute node) and check
 the vnc
 port in use (assuming KVM as hypervisor).
 This is basic knowledge of Nova.



 nova-api-metadata is running fine in the compute node.


 Make sure the metadata port is avaible thanks to telnet or
 netstat, nova-api can be running without listening on
 metadata
 port.




 ___
 Mailing list: https://launchpad.net/~openstack
 

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Chathura M. Sarathchandra Magurawalage
Hello Jean,

Thanks for your reply.

I followed the instructions in
http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html.
And my Controller and the Network-node is installed in the same physical
node.

I am using Folsom but without Network namespaces.

But in the website you have provided it states that If you run both L3 +
DHCP services on the same node, you should enable namespaces to avoid
conflicts with routes :

But currently quantum-dhcp-agent and quantum-l3-agent are running in the
same node?

Additionally the control node serves as a DHCP server for the local network
( Don't know if that would make and difference)

Any idea what the problem could be?


On 16 February 2013 16:21, Jean-Baptiste RANSY 
jean-baptiste.ra...@alyseo.com wrote:

  Hello Chathura,

 Are you using Folsom with Network Namespaces ?

 If yes, have a look here :
 http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html


 Regards,

 Jean-Baptsite RANSY



 On 02/16/2013 05:01 PM, Chathura M. Sarathchandra Magurawalage wrote:

 Hello guys,

  The problem still exists. Any ideas?

  Thanks

   On 15 February 2013 14:37, Sylvain Bauza sylvain.ba...@digimind.comwrote:

 Metadata API allows to fetch SSH credentials when booting (pubkey I mean).
 If a VM is unable to reach metadata service, then it won't be able to get
 its public key, so you won't be able to connect, unless you specifically go
 thru a Password authentication (provided password auth is enabled in
 /etc/ssh/sshd_config, which is not the case with Ubuntu cloud archive).
 There is also a side effect, the boot process is longer as the instance
 is waiting for the curl timeout (60sec.) to finish booting up.

 Re: Quantum, the metadata API is actually DNAT'd from Network node to the
 Nova-api node (here 172.16.0.1 as internal management IP) :
 Chain quantum-l3-agent-PREROUTING (1 references)

 target prot opt source   destination
  DNAT   tcp  --  0.0.0.0/0169.254.169.254  tcp
 dpt:80 to:172.16.0.1:8775


 Anyway, the first step is to :
 1. grab the console.log
 2. access thru VNC to the desired instance

 Troubleshooting will be easier once that done.

 -Sylvain



 Le 15/02/2013 14:24, Chathura M. Sarathchandra Magurawalage a écrit :

  Hello Guys,

 Not sure if this is the right port but these are the results:

  *Compute node:*


 root@computenode:~# netstat -an | grep 8775
  tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775  0.0.0.0:*
   LISTEN

 *Controller: *


 root@controller:~# netstat -an | grep 8775
  tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775  0.0.0.0:*
   LISTEN

 *Additionally I cant curl 169.254.169.254 from the compute node. I am
 not sure if this is related to not being able to PING the VM.*


 curl -v http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...

 Thanks for your help



 -
 Chathura Madhusanka Sarathchandra Magurawalage.
 1NW.2.1, Desk 2
 School of Computer Science and Electronic Engineering
 University Of Essex
 United Kingdom.

  Email: csar...@essex.ac.uk mailto:csar...@essex.ac.uk
   chathura.sarathchan...@gmail.com mailto:77.chath...@gmail.com
 
 77.chath...@gmail.com mailto:77.chath...@gmail.com



 On 15 February 2013 11:03, Anil Vishnoi vishnoia...@gmail.com mailto:
 vishnoia...@gmail.com wrote:

 If you are using ubuntu cloud image then the only way to log-in is
 to do ssh with the public key. For that you have to create ssh key
 pair and download the ssh key. You can create this ssh pair using
 horizon/cli.


 On Fri, Feb 15, 2013 at 4:27 PM, Sylvain Bauza
  sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com

 wrote:


 Le 15/02/2013 11:42, Chathura M. Sarathchandra Magurawalage a
 écrit :


 How can I log into the VM from VNC? What are the credentials?


 You have multiple ways to get VNC access. The easiest one is
 thru Horizon. Other can be looking at the KVM command-line for
 the desired instance (on the compute node) and check the vnc
 port in use (assuming KVM as hypervisor).
 This is basic knowledge of Nova.



 nova-api-metadata is running fine in the compute node.


 Make sure the metadata port is avaible thanks to telnet or
 netstat, nova-api can be running without listening on metadata
 port.




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

 More help   : 

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Jean-Baptiste RANSY
Please provide files listed bellow :

Controller Node :
/etc/nova/nova.conf
/etc/nova/api-paste.ini
/etc/quantum/l3_agent.ini
/etc/quantum/quantum.conf
/etc/quantum/dhcp_agent.ini
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
/etc/quantum/api-paste.ini
/var/log/nova/*.log
/var/log/quantum/*.log

Compute Node :
/etc/nova/nova.conf
/etc/nova/nova-compute.conf
/etc/nova/api-paste.ini
/etc/quantum/quantum.conf
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
/var/log/nova/*.log
/var/log/quantum/*.log

Plus, complete output of the following commands :

Controller Node :
$ keystone endpoint-list
$ ip link show
$ ip route show
$ ip netns show
$ ovs-vsctl show

Compute Node :
$ ip link show
$ ip route show
$ ovs-vsctl show

Regards,

Jean-Baptiste RANSY


On 02/16/2013 05:32 PM, Chathura M. Sarathchandra Magurawalage wrote:
 Hello Jean,

 Thanks for your reply.

 I followed the instructions
 in 
 http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html.
 And my Controller and the Network-node is installed in the same
 physical node.

 I am using Folsom but without Network namespaces. 

 But in the website you have provided it states that If you run both
 L3 + DHCP services on the same node, you should enable namespaces to
 avoid conflicts with routes :

 But currently quantum-dhcp-agent and quantum-l3-agent are running in
 the same node? 

 Additionally the control node serves as a DHCP server for the local
 network ( Don't know if that would make and difference)

 Any idea what the problem could be?


 On 16 February 2013 16:21, Jean-Baptiste RANSY
 jean-baptiste.ra...@alyseo.com
 mailto:jean-baptiste.ra...@alyseo.com wrote:

 Hello Chathura,

 Are you using Folsom with Network Namespaces ?

 If yes, have a look here :
 
 http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html


 Regards,

 Jean-Baptsite RANSY



 On 02/16/2013 05:01 PM, Chathura M. Sarathchandra Magurawalage wrote:
 Hello guys,

 The problem still exists. Any ideas?

 Thanks 

 On 15 February 2013 14:37, Sylvain Bauza
 sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com
 wrote:

 Metadata API allows to fetch SSH credentials when booting
 (pubkey I mean).
 If a VM is unable to reach metadata service, then it won't be
 able to get its public key, so you won't be able to connect,
 unless you specifically go thru a Password authentication
 (provided password auth is enabled in /etc/ssh/sshd_config,
 which is not the case with Ubuntu cloud archive).
 There is also a side effect, the boot process is longer as
 the instance is waiting for the curl timeout (60sec.) to
 finish booting up.

 Re: Quantum, the metadata API is actually DNAT'd from Network
 node to the Nova-api node (here 172.16.0.1 as internal
 management IP) :
 Chain quantum-l3-agent-PREROUTING (1 references)

 target prot opt source   destination
 DNAT   tcp  --  0.0.0.0/0 http://0.0.0.0/0  
  169.254.169.254  tcp dpt:80 to:172.16.0.1:8775
 http://172.16.0.1:8775


 Anyway, the first step is to :
 1. grab the console.log
 2. access thru VNC to the desired instance

 Troubleshooting will be easier once that done.

 -Sylvain



 Le 15/02/2013 14:24, Chathura M. Sarathchandra Magurawalage a
 écrit :

 Hello Guys,

 Not sure if this is the right port but these are the results:

 *Compute node:*


 root@computenode:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775
 http://0.0.0.0:8775  0.0.0.0:*   LISTEN

 *Controller: *


 root@controller:~# netstat -an | grep 8775
 tcp0  0 0.0.0.0:8775 http://0.0.0.0:8775
 http://0.0.0.0:8775  0.0.0.0:*   LISTEN

 *Additionally I cant curl 169.254.169.254 from the
 compute node. I am not sure if this is related to not
 being able to PING the VM.*


 curl -v http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...

 Thanks for your help


 
 -
 Chathura Madhusanka Sarathchandra Magurawalage.
 1NW.2.1, Desk 2
 School of Computer Science and Electronic Engineering
 University Of Essex
 United Kingdom.

 Email: csar...@essex.ac.uk mailto:csar...@essex.ac.uk
 mailto:csar...@essex.ac.uk mailto:csar...@essex.ac.uk
   chathura.sarathchan...@gmail.com

[Openstack] Install devstack problem

2013-02-16 Thread harryxiyou
Hi all,

When i installed Openstack by devstack, i was stucking in following
condition.

[...]
Downloading/unpacking prettytable (from -r
python_keystoneclient.egg-info/requires.txt (line 2))


It just got stuck here... and not moving forward.

Has anyone ever got the same problem? How did you solve this problem?
Please give me some suggestions. Thanks a lot in advance ;-)

-- 
Thanks
Harry Wei

___
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] Cant ping private or floating IP

2013-02-16 Thread Chathura M. Sarathchandra Magurawalage
Thanks Ransy,

I have created a tar file with the configuration and log files in it.
Please download it using the following URL. I have pasted the output of the
commands below.

https://www.dropbox.com/s/qyfcsn50060y304/confilesnlogs.tar

*Controller node:*
*root@controller:~# keystone endpoint-list*
+--+---+-+-++Controller
node
|id|   region  |
 publicurl|   internalurl
|  adminurl  |
+--+---+-+-++
| 2c9a1cb0fe8247d9b7716432cf459fe5 | RegionOne |
http://192.168.2.225:8774/v2/$(tenant_id)s   |
http://192.168.2.225:8774/v2/$(tenant_id)s   |
http://192.168.2.225:8774/v2/$(tenant_id)s |
| 2d306903ed3342a8c7c5680c116f | RegionOne |
http://192.168.2.225:9696/   |
http://192.168.2.225:9696/  |
http://192.168.2.225:9696/ |
| 3848114f120f42bf819bc2443b28ac9e | RegionOne |
http://192.168.2.225:8080/v1/AUTH_$(tenant_id)s |
http://192.168.2.225:8080/v1/AUTH_$(tenant_id)s |
http://192.168.2.225:8080/v1|
| 4955173b8d9e4d33ae4a5b29dc12c74d | RegionOne |
http://192.168.2.225:8776/v1/$(tenant_id)s   |
http://192.168.2.225:8776/v1/$(tenant_id)s   |
http://192.168.2.225:8776/v1/$(tenant_id)s |
| d313aa76bf854dde94f33a49a9f0c8ac | RegionOne |
http://192.168.2.225:9292/v2  |
http://192.168.2.225:9292/v2  |
http://192.168.2.225:9292/v2   |
| e5aa4ecf3cbe4dd5aba9b204c74fee6a | RegionOne |
http://192.168.2.225:5000/v2.0 |
http://192.168.2.225:5000/v2.0 |
http://192.168.2.225:35357/v2.0   |
| fba6f790e3b444c890d114f13cd32b37 | RegionOne |
http://192.168.2.225:8773/services/Cloud|
http://192.168.2.225:8773/services/Cloud|
http://192.168.2.225:8773/services/Admin  |
+--+---+-+-++

*root@controller:~# ip link show*
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen
1000
link/ether d4:ae:52:bb:aa:20 brd ff:ff:ff:ff:ff:ff
3: eth1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d4:ae:52:bb:aa:21 brd ff:ff:ff:ff:ff:ff
4: eth0.2@eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
state UP
link/ether d4:ae:52:bb:aa:20 brd ff:ff:ff:ff:ff:ff
5: br-int: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state
UNKNOWN
link/ether ba:7a:e9:dc:2b:41 brd ff:ff:ff:ff:ff:ff
7: br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 9a:41:c8:8a:9e:49 brd ff:ff:ff:ff:ff:ff
8: tapf71b5b86-5c: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
state UNKNOWN
link/ether 2a:44:a3:d1:7d:f3 brd ff:ff:ff:ff:ff:ff
9: qr-4d088f3a-78: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
state UNKNOWN
link/ether ca:5b:8d:4d:6d:fb brd ff:ff:ff:ff:ff:ff
10: qg-6f8374cb-cb: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
noqueue state UNKNOWN
link/ether 0e:7f:dd:3a:80:bc brd ff:ff:ff:ff:ff:ff
27: br-tun: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
link/ether 8a:cf:ec:7c:15:40 brd ff:ff:ff:ff:ff:ff

*root@controller:~# ip route show*
default via 192.168.2.253 dev eth0.2
default via 192.168.2.253 dev eth0.2  metric 100
10.5.5.0/24 dev tapf71b5b86-5c  proto kernel  scope link  src 10.5.5.2
10.5.5.0/24 dev qr-4d088f3a-78  proto kernel  scope link  src 10.5.5.1
10.10.10.0/24 dev eth0  proto kernel  scope link  src 10.10.10.1
192.168.2.0/24 dev eth0.2  proto kernel  scope link  src 192.168.2.225
192.168.2.0/24 dev qg-6f8374cb-cb  proto kernel  scope link  src
192.168.2.151
192.168.2.0/24 dev br-ex  proto kernel  scope link  src 192.168.2.225

*$ ip netns show (Did not return anything)*

*root@controller:~# ovs-vsctl show*
a566afae-d7a8-42a9-aefe-8b0f2f7054a3
Bridge br-tun
Port gre-4
Interface gre-4
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=10.10.10.12}
Port gre-3
Interface gre-3
type: gre
options: {in_key=flow, out_key=flow, remote_ip=127.0.0.1}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow, 

Re: [Openstack] [Swift][Keystone] Authentication problems with Swift and Keystone by Grizzly release

2013-02-16 Thread Adam Young

On 02/14/2013 09:38 AM, Heiko Krämer wrote:

Heyho Guys,

i'm testing Swift and Keystone (Grizzly).

!NOTE!
I'm posting only the importent stuff (output, responses, configs)

I've upgraded and migrate the database, the migration are working not
correct (kyestone-manage db_sync) because in the role table will create
a new column but with NULL values and this will break the auth (first
issue).

The next command of keystone they you will need is
keystone-manage pki_setup = done without errors but you will need to
change the rights of the generated files.



#
## Output / Log ###

My request to keystone are correct if i try to get a token with curl. I
get a token with all endpoints and other stuff.

 token: {
 expires: 2013-02-15T14:29:59Z,
 id:
MIIL-wYJKoZIhvcNAQcCoIIL8DCCC+wCAQExCTAHBgUrDgMCGjCCCtgGCSqGSIb3DQEHAaCCCskEggrFeyJhY2Nlc3MiOiB7InRva2VuIjogeyJpc3N1ZWRfYXQiOiAiMjAxMy0wMi0xNFQxNDoyOTo1OS44NDI0MjQiLCAiZXhwaXJlcyI6ICIyMDEzLTAyLTE1VDE0OjI5OjU5WiIsICJpZCI6ICJwbGFjZWhvbGRlciIsICJ0ZW5hbnQiOiB7ImVuYWJsZWQiOiB0cnVlLCAiaWQiOiAiNTY5NzdiYjVhMDU1NDc2MWJmMGViOWQ2Y2E3NzBkNzUiLCAibmFtZSI6ICJ0ZXN0aW5nIn19LCAic2VydmljZUNhdGFsb2ciOiBbeyJlbmRwb2ludHMiOiBbeyJhZG1pblVSTCI6ICJodHRwOi8vMTAuMC4wLjE6ODc3NC92Mi81Njk3N2JiNWEwNTU0NzYxYmYwZWI5ZDZjYTc3MGQ3NSIsICJyZWdpb24iOiAidGVzdGluZyIsICJpbnRlcm5hbFVSTCI6ICJodHRwOi8vMTAuMC4wLjE6ODc3NC92Mi81Njk3N2JiNWEwNTU0NzYxYmYwZWI5ZDZjYTc3MGQ3NSIsICJpZCI6ICJiOGQ3YTQzMWZjY2M0MWY2YTYzMzFjZTY3NjBlYjI1ZSIsICJwdWJsaWNVUkwiOiAiaHR0cDovLzg4LjE5OC42LjE1Mjo4Nzc0L3YyLzU2OTc3YmI1YTA1NTQ3NjFiZjBlYjlkNmNhNzcwZDc1In1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogImNvbXB1dGUiLCAibmFtZSI6ICJub3ZhIn0sIHsiZW5kcG9pbnRzIjogW3siYWRtaW5VUkwiOiAiaHR0cDovLzEwLjAuMC4xOjk2OTYiLCAicmVnaW9uIjogInRlc3RpbmciLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzEwLjAuMC4xOjk2OTYiLCAiaWQiOiAiM2ZjNTcxNzUyMDA3NDY3OWI3MTlkM2VmNTlmZGViYzMiLCAicHVibGljVVJMIjogImh0dHA6Ly8xMC4wLjAuMTo5Njk2In1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogIm5ldHdvcmsiLCAibmFtZSI6ICJxdWFudHVtIn0sIHsiZW5kcG9pbnRzIjogW3siYWRtaW5VUkwiOiAiaHR0cDovLzEwLjAuMC4xOjkyOTIvdjIiLCAicmVnaW9uIjogInRlc3RpbmciLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzEwLjAuMC4xOjkyOTIvdjIiLCAiaWQiOiAiMWZlZTllNDQ1NjNjNDcwYzhkNjFmNjE5NDNjYmIxM2YiLCAicHVibGljVVJMIjogImh0dHA6Ly84OC4xOTguNi4xNTI6OTI5Mi92MiJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJpbWFnZSIsICJuYW1lIjogImdsYW5jZSJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xMC4wLjAuMTo4Nzc2L3YxLzU2OTc3YmI1YTA1NTQ3NjFiZjBlYjlkNmNhNzcwZDc1IiwgInJlZ2lvbiI6ICJ0ZXN0aW5nIiwgImludGVybmFsVVJMIjogImh0dHA6Ly8xMC4wLjAuMTo4Nzc2L3YxLzU2OTc3YmI1YTA1NTQ3NjFiZjBlYjlkNmNhNzcwZDc1IiwgImlkIjogIjFmMjVlMDUwMjdmMTRmNGI5MDFmMWFmNjJiZTZhMzAwIiwgInB1YmxpY1VSTCI6ICJodHRwOi8vODguMTk4LjYuMTUyOjg3NzYvdjEvNTY5NzdiYjVhMDU1NDc2MWJmMGViOWQ2Y2E3NzBkNzUifV0sICJlbmRwb2ludHNfbGlua3MiOiBbXSwgInR5cGUiOiAidm9sdW1lIiwgIm5hbWUiOiAiY2luZGVyIn0sIHsiZW5kcG9pbnRzIjogW3siYWRtaW5VUkwiOiAiaHR0cDovLzEwLjAuMC4xOjg3NzMvc2VydmljZXMvQWRtaW4iLCAicmVnaW9uIjogInRlc3RpbmciLCAiaW50ZXJuYWxVUkwiOiAiaHR0cDovLzEwLjAuMC4xOjg3NzMvc2VydmljZXMvQ2xvdWQiLCAiaWQiOiAiMWIyZTViZjkzNTI2NGI2ODljZmZkZWViMTk1ZDRjMWQiLCAicHVibGljVVJMIjogImh0dHA6Ly84OC4xOTguNi4xNTI6ODc3My9zZXJ2aWNlcy9DbG91ZCJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJlYzIiLCAibmFtZSI6ICJlYzIifSwgeyJlbmRwb2ludHMiOiBbeyJhZG1pblVSTCI6ICJodHRwOi8vMTAuMC4wLjE6ODA4MC92MSIsICJyZWdpb24iOiAidGVzdGluZyIsICJpbnRlcm5hbFVSTCI6ICJodHRwOi8vMTAuMC4wLjE6ODA4MC92MS9BVVRIXzU2OTc3YmI1YTA1NTQ3NjFiZjBlYjlkNmNhNzcwZDc1IiwgImlkIjogIjI3YTEyYTBkMGI2ODQ2YjJhMDQzNjMwZmJlYzUwNmJhIiwgInB1YmxpY1VSTCI6ICJodHRwOi8vODguMTk4LjYuMTUyOjgwODAvdjEvQVVUSF81Njk3N2JiNWEwNTU0NzYxYmYwZWI5ZDZjYTc3MGQ3NSJ9XSwgImVuZHBvaW50c19saW5rcyI6IFtdLCAidHlwZSI6ICJvYmplY3Qtc3RvcmUiLCAibmFtZSI6ICJzd2lmdCJ9LCB7ImVuZHBvaW50cyI6IFt7ImFkbWluVVJMIjogImh0dHA6Ly8xMC4wLjAuMTozNTM1Ny92Mi4wIiwgInJlZ2lvbiI6ICJ0ZXN0aW5nIiwgImludGVybmFsVVJMIjogImh0dHA6Ly8xMC4wLjAuMTo1MDAwL3YyLjAiLCAiaWQiOiAiMDI2NWNmOTUyZDRmNGZhYWEyZjdlZGIzNGZlMGQxYTUiLCAicHVibGljVVJMIjogImh0dHA6Ly84OC4xOTguNi4xNTI6NTAwMC92Mi4wIn1dLCAiZW5kcG9pbnRzX2xpbmtzIjogW10sICJ0eXBlIjogImlkZW50aXR5IiwgIm5hbWUiOiAia2V5c3RvbmUifV0sICJ1c2VyIjogeyJ1c2VybmFtZSI6ICJkbGVpZGlzY2giLCAicm9sZXNfbGlua3MiOiBbXSwgImlkIjogIjRjZDRhNzRlMTVlMTQ4MmY5ZmExNmY1MjRhZmQ4ZWJlIiwgInJvbGVzIjogW3sibmFtZSI6ICJhZG1pbiJ9LCB7Im5hbWUiOiAiS2V5c3RvbmVTZXJ2aWNlQWRtaW4ifSwgeyJuYW1lIjogIktleXN0b25lQWRtaW4ifV0sICJuYW1lIjogImRsZWlkaXNjaCJ9LCAibWV0YWRhdGEiOiB7ImlzX2FkbWluIjogMCwgInJvbGVzIjogWyI0NzA3YzJmNDg3ODg0MmM1ODUzMWJkN2U4MGU0ZDkzMCIsICI4ZjRmNGNhNmJmZGM0NWUwOTdjMTc1YmViNzUwNjU0ZCIsICI0Y2Y5OWU0ZGQ1YTg0NjZiOTlmZTRmZTIyNTAxYjg5NyJdfX19MYH-MIH8AgEBMFwwVzELMAkGA1UEBhMCVVMxDjAMBgNVBAgTBVVuc2V0MQ4wDAYDVQQHEwVVbnNldDEOMAwGA1UEChMFVW5zZXQxGDAWBgNVBAMTD3d3dy5leGFtcGxlLmNvbQIBATAHBgUrDgMCGjANBgkqhkiG9w0BAQEFAASBgD0cne0M65sCpOWFFSBqmA9rm14ecxkLtI9+fYJapMFIY3URuFxp8dWD2YPNeR7Jxw0lBcGLX418nG15G559pAqtk7-vKVV+X4tvJYRuHOt33fw37-b4hsX3ZEbdeif24j4eQEJKqDe2r7cLy8Iox2rCMjC2yKfZwjhIZdmNf7ZS,

 issued_at: 2013-02-14T14:29:59.842424,
 tenant: {
 

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Jean-Baptiste RANSY
Controller node :
# iptables -L -n -v
# iptables -L -n -v -t nat


On 02/17/2013 03:18 AM, Chathura M. Sarathchandra Magurawalage wrote:
 You should be able to curl 169.254.169.254 from compute node, which I
 cant at the moment.

 I have got the bridge set up in the l3_agent.ini

___
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] Cant ping private or floating IP

2013-02-16 Thread Chathura M. Sarathchandra Magurawalage
root@computernode:~# curl -v  http://169.254.169.254
* About to connect() to 169.254.169.254 port 80 (#0)
*   Trying 169.254.169.254...

root@controller:~# curl -v  http://169.254.169.254
* About to connect() to 169.254.169.254 port 80 (#0)
*   Trying 169.254.169.254...


root@athena:~# iptables -L -n -v
Chain INPUT (policy ACCEPT 59009 packets, 22M bytes)
 pkts bytes target prot opt in out source
destination
59493   22M quantum-l3-agent-INPUT  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
59493   22M nova-api-INPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0
  484 73533 ACCEPT 47   --  *  *   0.0.0.0/0
0.0.0.0/0

Chain FORWARD (policy ACCEPT 707 packets, 47819 bytes)
 pkts bytes target prot opt in out source
destination
  707 47819 quantum-filter-top  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
  707 47819 quantum-l3-agent-FORWARD  all  --  *  *   0.0.0.0/0
   0.0.0.0/0
  707 47819 nova-filter-top  all  --  *  *   0.0.0.0/0
0.0.0.0/0
  707 47819 nova-api-FORWARD  all  --  *  *   0.0.0.0/0
0.0.0.0/0

Chain OUTPUT (policy ACCEPT 56022 packets, 22M bytes)
 pkts bytes target prot opt in out source
destination
56022   22M quantum-filter-top  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
56022   22M quantum-l3-agent-OUTPUT  all  --  *  *   0.0.0.0/0
   0.0.0.0/0
56022   22M nova-filter-top  all  --  *  *   0.0.0.0/0
0.0.0.0/0
56022   22M nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0

Chain nova-api-FORWARD (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-INPUT (1 references)
 pkts bytes target prot opt in out source
destination
0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
 192.168.2.225tcp dpt:8775

Chain nova-api-OUTPUT (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-local (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-filter-top (2 references)
 pkts bytes target prot opt in out source
destination
56729   22M nova-api-local  all  --  *  *   0.0.0.0/0
0.0.0.0/0

Chain quantum-filter-top (2 references)
 pkts bytes target prot opt in out source
destination
56729   22M quantum-l3-agent-local  all  --  *  *   0.0.0.0/0
 0.0.0.0/0

Chain quantum-l3-agent-FORWARD (1 references)
 pkts bytes target prot opt in out source
destination

Chain quantum-l3-agent-INPUT (1 references)
 pkts bytes target prot opt in out source
destination
0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
 192.168.2.225tcp dpt:8775

Chain quantum-l3-agent-OUTPUT (1 references)
 pkts bytes target prot opt in out source
destination

Chain quantum-l3-agent-local (1 references)
 pkts bytes target prot opt in out source
destination

root@athena:~# iptables -L -n -v -t nat
Chain PREROUTING (policy ACCEPT 3212 packets, 347K bytes)
 pkts bytes target prot opt in out source
destination
 3212  347K quantum-l3-agent-PREROUTING  all  --  *  *
0.0.0.0/0
0.0.0.0/0
 3212  347K nova-api-PREROUTING  all  --  *  *   0.0.0.0/0
   0.0.0.0/0

Chain INPUT (policy ACCEPT 639 packets, 84948 bytes)
 pkts bytes target prot opt in out source
destination

Chain OUTPUT (policy ACCEPT 3180 packets, 213K bytes)
 pkts bytes target prot opt in out source
destination
 3180  213K quantum-l3-agent-OUTPUT  all  --  *  *   0.0.0.0/0
   0.0.0.0/0
 3180  213K nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target prot opt in out source
destination
 3726  247K quantum-l3-agent-POSTROUTING  all  --  *  *
0.0.0.0/0
0.0.0.0/0
0 0 nova-api-POSTROUTING  all  --  *  *   0.0.0.0/0
   0.0.0.0/0
0 0 quantum-postrouting-bottom  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
0 0 nova-postrouting-bottom  all  --  *  *   0.0.0.0/0
   0.0.0.0/0

Chain nova-api-OUTPUT (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-POSTROUTING (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-PREROUTING (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-float-snat (1 references)
 pkts bytes target prot opt in out source
destination

Chain nova-api-snat (1 references)
 pkts bytes target prot opt in out source
destination
0 0 nova-api-float-snat  all  --  *  *   0.0.0.0/0
   0.0.0.0/0

Chain nova-postrouting-bottom (1 references)
 pkts bytes target prot opt in out source
destination
0 0 nova-api-snat  all  --  *  *   0.0.0.0/0
0.0.0.0/0

Chain quantum-l3-agent-OUTPUT (1 references)
 pkts bytes target prot opt in 

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Jean-Baptiste RANSY
For me, it's normal that you are not able to curl 169.254.169.254 from
your compute and controller nodes : Same thing on my side, but my VM get
their metadata.

Try to lunch an instance.

JB


On 02/17/2013 03:35 AM, Chathura M. Sarathchandra Magurawalage wrote:
 root@computernode:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254... 

 root@controller:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254... 


 root@athena:~# iptables -L -n -v
 Chain INPUT (policy ACCEPT 59009 packets, 22M bytes)
  pkts bytes target prot opt in out source  
 destination 
 59493   22M quantum-l3-agent-INPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 59493   22M nova-api-INPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   484 73533 ACCEPT 47   --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain FORWARD (policy ACCEPT 707 packets, 47819 bytes)
  pkts bytes target prot opt in out source  
 destination 
   707 47819 quantum-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   707 47819 quantum-l3-agent-FORWARD  all  --  *  *  
 0.0.0.0/0 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0  
 
   707 47819 nova-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   707 47819 nova-api-FORWARD  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain OUTPUT (policy ACCEPT 56022 packets, 22M bytes)
  pkts bytes target prot opt in out source  
 destination 
 56022   22M quantum-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 56022   22M quantum-l3-agent-OUTPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 56022   22M nova-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 56022   22M nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain nova-api-FORWARD (1 references)
  pkts bytes target prot opt in out source  
 destination 

 Chain nova-api-INPUT (1 references)
  pkts bytes target prot opt in out source  
 destination 
 0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
 http://0.0.0.0/0192.168.2.225tcp dpt:8775

 Chain nova-api-OUTPUT (1 references)
  pkts bytes target prot opt in out source  
 destination 

 Chain nova-api-local (1 references)
  pkts bytes target prot opt in out source  
 destination 

 Chain nova-filter-top (2 references)
  pkts bytes target prot opt in out source  
 destination 
 56729   22M nova-api-local  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain quantum-filter-top (2 references)
  pkts bytes target prot opt in out source  
 destination 
 56729   22M quantum-l3-agent-local  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain quantum-l3-agent-FORWARD (1 references)
  pkts bytes target prot opt in out source  
 destination 

 Chain quantum-l3-agent-INPUT (1 references)
  pkts bytes target prot opt in out source  
 destination 
 0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
 http://0.0.0.0/0192.168.2.225tcp dpt:8775

 Chain quantum-l3-agent-OUTPUT (1 references)
  pkts bytes target prot opt in out source  
 destination 

 Chain quantum-l3-agent-local (1 references)
  pkts bytes target prot opt in out source  
 destination

 root@athena:~# iptables -L -n -v -t nat
 Chain PREROUTING (policy ACCEPT 3212 packets, 347K bytes)
  pkts bytes target prot opt in out source  
 destination 
  3212  347K quantum-l3-agent-PREROUTING  all  --  *  *  
 0.0.0.0/0 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0  
 
  3212  347K nova-api-PREROUTING  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain INPUT (policy ACCEPT 639 packets, 84948 bytes)
  pkts bytes target prot opt in out source  
 destination 

 Chain OUTPUT (policy ACCEPT 3180 packets, 213K bytes)
  pkts 

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Chathura M. Sarathchandra Magurawalage
oh that's weird.

I still get this error. couldnt this be because I cannot ping the VM in the
first place?. Because as far as I know metadata takes care of ssh keys. But
what if you cant reach the VM in the first place?

no instance data found in start-local

ci-info: lo: 1 127.0.0.1   255.0.0.0   .

ci-info: eth0  : 1 10.5.5.3255.255.255.0   fa:16:3e:a7:28:25

ci-info: route-0: 0.0.0.0 10.5.5.10.0.0.0 eth0   UG

ci-info: route-1: 10.5.5.00.0.0.0 255.255.255.0   eth0   U

cloud-init start running: Sun, 17 Feb 2013 02:45:35 +. up 3.51 seconds

2013-02-17 02:48:25,840 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[50/120s]: url error [timed out]

2013-02-17 02:49:16,893 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[101/120s]: url error [timed out]

2013-02-17 02:49:34,912 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[119/120s]: url error [timed out]

2013-02-17 02:49:35,913 - DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds



no instance data found in start

Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

 * Starting AppArmor profiles   [80G
[74G[ OK ]



On 17 February 2013 02:41, Jean-Baptiste RANSY 
jean-baptiste.ra...@alyseo.com wrote:

  For me, it's normal that you are not able to curl 169.254.169.254 from
 your compute and controller nodes : Same thing on my side, but my VM get
 their metadata.

 Try to lunch an instance.

 JB



 On 02/17/2013 03:35 AM, Chathura M. Sarathchandra Magurawalage wrote:

  root@computernode:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...

  root@controller:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254...


  root@athena:~# iptables -L -n -v
 Chain INPUT (policy ACCEPT 59009 packets, 22M bytes)
  pkts bytes target prot opt in out source
 destination
 59493   22M quantum-l3-agent-INPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0
 59493   22M nova-api-INPUT  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
   484 73533 ACCEPT 47   --  *  *   0.0.0.0/0
 0.0.0.0/0

  Chain FORWARD (policy ACCEPT 707 packets, 47819 bytes)
  pkts bytes target prot opt in out source
 destination
   707 47819 quantum-filter-top  all  --  *  *   0.0.0.0/0
0.0.0.0/0
   707 47819 quantum-l3-agent-FORWARD  all  --  *  *   0.0.0.0/0
  0.0.0.0/0
   707 47819 nova-filter-top  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
   707 47819 nova-api-FORWARD  all  --  *  *   0.0.0.0/0
  0.0.0.0/0

  Chain OUTPUT (policy ACCEPT 56022 packets, 22M bytes)
  pkts bytes target prot opt in out source
 destination
 56022   22M quantum-filter-top  all  --  *  *   0.0.0.0/0
0.0.0.0/0
 56022   22M quantum-l3-agent-OUTPUT  all  --  *  *   0.0.0.0/0
  0.0.0.0/0
 56022   22M nova-filter-top  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
 56022   22M nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
 0.0.0.0/0

  Chain nova-api-FORWARD (1 references)
  pkts bytes target prot opt in out source
 destination

  Chain nova-api-INPUT (1 references)
  pkts bytes target prot opt in out source
 destination
 0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
  192.168.2.225tcp dpt:8775

  Chain nova-api-OUTPUT (1 references)
  pkts bytes target prot opt in out source
 destination

  Chain nova-api-local (1 references)
  pkts bytes target prot opt in out source
 destination

  Chain nova-filter-top (2 references)
  pkts bytes target prot opt in out source
 destination
 56729   22M nova-api-local  all  --  *  *   0.0.0.0/0
 0.0.0.0/0

  Chain quantum-filter-top (2 references)
  pkts bytes target prot opt in out source
 destination
 56729   22M quantum-l3-agent-local  all  --  *  *   0.0.0.0/0
0.0.0.0/0

  Chain quantum-l3-agent-FORWARD (1 references)
  pkts bytes target prot opt in out source
 destination

  Chain quantum-l3-agent-INPUT (1 references)
  pkts bytes target prot opt in out source
 destination
 0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
  192.168.2.225tcp dpt:8775

  Chain quantum-l3-agent-OUTPUT (1 references)
  pkts bytes target prot opt in out source
 destination

  Chain quantum-l3-agent-local (1 references)
  pkts bytes target prot opt in out source
 destination

  root@athena:~# iptables -L -n -v -t nat
 Chain PREROUTING (policy ACCEPT 3212 packets, 347K bytes)
  pkts bytes target prot opt in out source
 destination
  3212  347K quantum-l3-agent-PREROUTING  all  --  *  *   0.0.0.0/0
 0.0.0.0/0
  3212  347K nova-api-PREROUTING  all  --  *  *   

Re: [Openstack] Cant ping private or floating IP

2013-02-16 Thread Jean-Baptiste RANSY
Add Cirros Image to Glance :)

Username: cirros
Password: cubswin:)

http://docs.openstack.org/trunk/openstack-compute/install/apt/content/uploading-to-glance.html

to join your VM, it's a bit dirty but you can :
- put your computer in the same subnet as your controller (192.168.2.0/24)
- then adds a static route to the subnet of your VM. (ip route add
10.5.5.0/24 gw 192.168.2.151)
(192.168.2.151 is the quantum gateway)

I'm going to sleep, we will continue tomorrow.

JB

PS : You also should get some sleep :)


On 02/17/2013 03:53 AM, Chathura M. Sarathchandra Magurawalage wrote:
 oh that's weird.

 I still get this error. couldnt this be because I cannot ping the VM
 in the first place?. Because as far as I know metadata takes care of
 ssh keys. But what if you cant reach the VM in the first place?

 no instance data found in start-local

 ci-info: lo: 1 127.0.0.1   255.0.0.0   .

 ci-info: eth0  : 1 10.5.5.3255.255.255.0   fa:16:3e:a7:28:25

 ci-info: route-0: 0.0.0.0 10.5.5.10.0.0.0 eth0   UG

 ci-info: route-1: 10.5.5.00.0.0.0 255.255.255.0   eth0   U

 cloud-init start running: Sun, 17 Feb 2013 02:45:35 +. up 3.51 seconds

 2013-02-17 02:48:25,840 - util.py[WARNING]: 
 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: 
 url error [timed out]

 2013-02-17 02:49:16,893 - util.py[WARNING]: 
 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: 
 url error [timed out]

 2013-02-17 02:49:34,912 - util.py[WARNING]: 
 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: 
 url error [timed out]

 2013-02-17 02:49:35,913 - DataSourceEc2.py[CRITICAL]: giving up on md after 
 120 seconds



 no instance data found in start

 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

  * Starting AppArmor profiles   [80G 
 [74G[ OK ]


 On 17 February 2013 02:41, Jean-Baptiste RANSY
 jean-baptiste.ra...@alyseo.com
 mailto:jean-baptiste.ra...@alyseo.com wrote:

 For me, it's normal that you are not able to curl 169.254.169.254
 from your compute and controller nodes : Same thing on my side,
 but my VM get their metadata.

 Try to lunch an instance.

 JB



 On 02/17/2013 03:35 AM, Chathura M. Sarathchandra Magurawalage wrote:
 root@computernode:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254... 

 root@controller:~# curl -v  http://169.254.169.254
 * About to connect() to 169.254.169.254 port 80 (#0)
 *   Trying 169.254.169.254... 


 root@athena:~# iptables -L -n -v
 Chain INPUT (policy ACCEPT 59009 packets, 22M bytes)
  pkts bytes target prot opt in out source
   destination 
 59493   22M quantum-l3-agent-INPUT  all  --  *  *  
 0.0.0.0/0 http://0.0.0.0/00.0.0.0/0
 http://0.0.0.0/0   
 59493   22M nova-api-INPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   484 73533 ACCEPT 47   --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain FORWARD (policy ACCEPT 707 packets, 47819 bytes)
  pkts bytes target prot opt in out source
   destination 
   707 47819 quantum-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   707 47819 quantum-l3-agent-FORWARD  all  --  *  *  
 0.0.0.0/0 http://0.0.0.0/00.0.0.0/0
 http://0.0.0.0/0   
   707 47819 nova-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
   707 47819 nova-api-FORWARD  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain OUTPUT (policy ACCEPT 56022 packets, 22M bytes)
  pkts bytes target prot opt in out source
   destination 
 56022   22M quantum-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 56022   22M quantum-l3-agent-OUTPUT  all  --  *  *  
 0.0.0.0/0 http://0.0.0.0/00.0.0.0/0
 http://0.0.0.0/0   
 56022   22M nova-filter-top  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   
 56022   22M nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
 http://0.0.0.0/00.0.0.0/0 http://0.0.0.0/0   

 Chain nova-api-FORWARD (1 references)
  pkts bytes target prot opt in out source
   destination 

 Chain nova-api-INPUT (1 references)
  pkts bytes target prot opt in out source
   destination 

[Openstack] Horizon Keystone Nova miscommunication

2013-02-16 Thread Greg Chavez
It seems that nova and horizon are not communicating on my controller node.
 Acces and security objects created with nova are not seen by Horizon and
vice versa.  This includes key pairs and secgroup rules.  For example, if I
create a keypair with the nova client, it isn't visible in horizon, and if
I create one in horizon it is not visible via the nova client.

Possibly related: VMs that I create, whether via the nova client or
Horizon, are not shown with I run nova list.  The nova-api.log shows a
successful servers-detail query, but it comes back empty.

Also possibly related: Although I have all my services and endpoints
configured correctly, I can't get individual endpoint detail with
endpoint-get.  What's more, I see this error in Horizon's error log:

[Sun Feb 17 07:02:50 2013] [error] EndpointNotFound: Endpoint not found.
[Sun Feb 17 07:06:55 2013] [error] unable to retrieve service catalog with
token

This matches what I get when I run:

$ keystone endpoint-get --service nova
Endpoint not found.

But that can't be because endpoint-list shows all six endpoints I created
and all the information seems correct in the database:


mysql select * from endpoint where service_id
='9e40d355b49342f8ac6947c497df76d2'\G
*** 1. row ***
id: 922baafde75f4cffa7dbe7f57cddb951
region: RegionOne
service_id: 9e40d355b49342f8ac6947c497df76d2
 extra: {adminurl: http://192.168.241.100:35357/v2.0;,
internalurl: http://192.168.241.100:5000/v2.0;, publicurl: 
http://10.21.164.75:5000/v2.0}
1 row in set (0.00 sec)

mysql select * from service where id ='9e40d355b49342f8ac6947c497df76d2'\G
*** 1. row ***
   id: 9e40d355b49342f8ac6947c497df76d2
 type: identity
extra: {description: OpenStack Identity, name: keystone}
1 row in set (0.00 sec)

Please please please help me.  My boss is giving my project the ax on
Monday if I can't get this to work.

-- 
\*..+.-
--Greg Chavez
+//..;};
___
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: raring_grizzly_deploy #11

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/11/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 02:21:11 -0500Build duration:56 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesConsole Output[...truncated 13518 lines...]ERROR:root:Could not setup SSH connection to test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonWARNING:paramiko.transport:Oops, unhandled type 3ERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-08.os.magners.qa.lexingtonINFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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 Failure: precise_grizzly_deploy #147

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/147/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 03:18:19 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 13464 lines...]INFO:root:Setting up connection to test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-12.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #12

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/12/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 04:05:11 -0500Build duration:20 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 5410 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-12.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-12.os.magners.qa.lexingtonINFO:root:Setting up connection to test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_deploy #148

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/148/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 04:25:23 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 13462 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #13

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/13/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 05:12:22 -0500Build duration:20 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5540 lines...]INFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_cinder_trunk #150

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/150/Project:raring_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 06:02:10 -0500Build duration:6 min 50 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20Changesrbd: update volume->image copyingby josh.durgineditcinder/tests/test_rbd.pyeditcinder/volume/drivers/rbd.pyUpdate EMC SMI-S Driverby xing.yangeditcinder/volume/driver.pyeditcinder/tests/test_emc.pyeditcinder/volume/drivers/emc/emc_smis_iscsi.pyeditcinder/volume/drivers/emc/emc_smis_common.pyConsole Output[...truncated 6266 lines...]Package: cinderPackage-Time: 170Source-Version: 2013.1.a138.ge708025+git201302160602~raring-0ubuntu1Space: 24108Status: attemptedVersion: 2013.1.a138.ge708025+git201302160602~raring-0ubuntu1Finished at 20130216-0608Build needed 00:02:50, 24108k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpYnuwck/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpYnuwck/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a138.ge708025+git201302160602~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160602~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_cinder_trunk #148

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/148/Project:precise_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 06:09:01 -0500Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20Changesrbd: update volume->image copyingby josh.durgineditcinder/volume/drivers/rbd.pyeditcinder/tests/test_rbd.pyUpdate EMC SMI-S Driverby xing.yangeditcinder/volume/drivers/emc/emc_smis_common.pyeditcinder/tests/test_emc.pyeditcinder/volume/drivers/emc/emc_smis_iscsi.pyeditcinder/volume/driver.pyConsole Output[...truncated 3156 lines...]Package-Time: 0Source-Version: 2013.1.a138.ge708025+git201302160609~precise-0ubuntu1Space: 0Status: failedVersion: 2013.1.a138.ge708025+git201302160609~precise-0ubuntu1Finished at 20130216-0610Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160609~precise-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160609~precise-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmp3FAEag/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp3FAEag/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a138.ge708025+git201302160609~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a138.ge708025+git201302160609~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A cinder_2013.1.a138.ge708025+git201302160609~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', 'cinder_2013.1.a138.ge708025+git201302160609~precise-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a138.ge708025+git201302160609~precise-0ubuntu1.dsc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_keystone_trunk #137

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/137/Project:precise_grizzly_keystone_trunkDate of build:Sat, 16 Feb 2013 10:01:08 -0500Build duration:3 min 1 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changesadd missing kvs functionality (bug1119770)by chunggeditkeystone/identity/core.pyeditkeystone/identity/backends/kvs.pyedittests/test_content_types.pyedittests/test_backend_kvs.pyeditkeystone/identity/backends/ldap/core.pyedittests/test_backend_ldap.pyeditkeystone/identity/backends/pam.pyeditkeystone/identity/backends/sql.pyedittests/test_backend.pyeditkeystone/identity/controllers.pyConsole Output[...truncated 2527 lines...]Fail-Stage: install-depsHost Architecture: amd64Install-Time: 0Job: keystone_2013.1+git201302161001~precise-0ubuntu1.dscMachine Architecture: amd64Package: keystonePackage-Time: 0Source-Version: 2013.1+git201302161001~precise-0ubuntu1Space: 0Status: failedVersion: 2013.1+git201302161001~precise-0ubuntu1Finished at 20130216-1003Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201302161001~precise-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201302161001~precise-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmprNwbt9/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmprNwbt9/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201302161001~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201302161001~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201302161001~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+git201302161001~precise-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201302161001~precise-0ubuntu1.dsc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_cinder_trunk #149

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/149/Project:precise_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 10:02:17 -0500Build duration:4 min 19 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd LIO iSCSI backend support using python-rtslibby eharneyedittools/test-requireseditsetup.pyeditetc/cinder/rootwrap.d/volume.filterseditcinder/volume/drivers/lvm.pyeditcinder/tests/test_iscsi.pyaddbin/cinder-rtstooleditcinder/volume/iscsi.pyConsole Output[...truncated 5355 lines...]Package-Time: 133Source-Version: 2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1Space: 24168Status: attemptedVersion: 2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1Finished at 20130216-1006Build needed 00:02:13, 24168k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpCItj3m/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpCItj3m/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [1fc5575] Add LIO iSCSI backend support using python-rtslibdch -a [abd3475] Create a RemoteFsDriver classdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a140.gf623cdc+git201302161002~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A cinder_2013.1.a140.gf623cdc+git201302161002~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', 'cinder_2013.1.a140.gf623cdc+git201302161002~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', 'cinder_2013.1.a140.gf623cdc+git201302161002~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_cinder_trunk #151

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/151/Project:raring_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 10:04:10 -0500Build duration:2 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd LIO iSCSI backend support using python-rtslibby eharneyedittools/test-requireseditcinder/tests/test_iscsi.pyaddbin/cinder-rtstooleditsetup.pyeditcinder/volume/drivers/lvm.pyeditetc/cinder/rootwrap.d/volume.filterseditcinder/volume/iscsi.pyConsole Output[...truncated 1198 lines...]Get:56 http://archive.ubuntu.com/ubuntu/ raring/main libmysqlclient18 amd64 5.5.29-0ubuntu1 [921 kB]Get:57 http://archive.ubuntu.com/ubuntu/ raring/main python-mysqldb amd64 1.2.3-1build2 [63.2 kB]Get:58 http://archive.ubuntu.com/ubuntu/ raring/main python-setuptools-git all 1.0b1-0ubuntu2 [11.1 kB]Get:59 http://archive.ubuntu.com/ubuntu/ raring/main pep8 all 1.3.3-0ubuntu1 [32.0 kB]Get:60 http://archive.ubuntu.com/ubuntu/ raring/main python-stevedore all 0.8-2 [9736 B]Get:61 http://archive.ubuntu.com/ubuntu/ raring/universe python-hp3parclient all 1.0.0-0ubuntu2 [11.5 kB]Get:62 http://archive.ubuntu.com/ubuntu/ raring/main libfreetype6 amd64 2.4.11-0ubuntu1 [346 kB]Get:63 http://archive.ubuntu.com/ubuntu/ raring/main libjpeg-turbo8 amd64 1.2.1-0ubuntu2 [114 kB]Get:64 http://archive.ubuntu.com/ubuntu/ raring/main liblcms1 amd64 1.19.dfsg-1.2ubuntu2 [106 kB]Get:65 http://archive.ubuntu.com/ubuntu/ raring/main libpaper1 amd64 1.1.24+nmu2ubuntu2 [14.6 kB]Get:66 http://archive.ubuntu.com/ubuntu/ raring/main libyaml-0-2 amd64 0.1.4-2build1 [57.3 kB]Get:67 http://archive.ubuntu.com/ubuntu/ raring/main docutils-doc all 0.10-0ubuntu1 [1307 kB]Get:68 http://archive.ubuntu.com/ubuntu/ raring/main libjpeg8 amd64 8c-2ubuntu7 [2112 B]Get:69 http://archive.ubuntu.com/ubuntu/ raring/main libpaper-utils amd64 1.1.24+nmu2ubuntu2 [9164 B]Get:70 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging-compat all 1.1.7+1.7.8-1ubuntu2 [5628 B]Get:71 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging amd64 1.1.7+1.7.8-1ubuntu2 [304 kB]Get:72 http://archive.ubuntu.com/ubuntu/ raring/main python-openid all 2.2.5-3ubuntu1 [118 kB]Get:73 http://archive.ubuntu.com/ubuntu/ raring/main python-pastescript all 1.7.5-2 [118 kB]Get:74 http://archive.ubuntu.com/ubuntu/ raring/main python-scgi amd64 1.13-1ubuntu2 [20.4 kB]Get:75 http://archive.ubuntu.com/ubuntu/ raring/main python-yaml amd64 3.10-4build2 [113 kB]Get:76 http://archive.ubuntu.com/ubuntu/ raring/main sphinx-doc all 1.1.3+dfsg-5ubuntu1 [855 kB]Failed to fetch http://localhost/ubuntu/pool/main/p/python-keystoneclient/python-keystoneclient_0.2.2.40.g8e395e0+git201302160601~raring-0ubuntu1_all.deb  404  Not FoundFetched 13.0 MB in 14s (875 kB/s)E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?install call failedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-4179c30b-1751-4bf3-9502-b2911d9c0387', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpwtuf5Y/cinder/debian/control']' returned non-zero exit status 100ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-4179c30b-1751-4bf3-9502-b2911d9c0387', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpwtuf5Y/cinder/debian/control']' returned non-zero exit status 100INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpwtuf5Y/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpwtuf5Y/cinder/debian/controlTraceback (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-4179c30b-1751-4bf3-9502-b2911d9c0387', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpwtuf5Y/cinder/debian/control']' returned non-zero exit status 100Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or 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-4179c30b-1751-4bf3-9502-b2911d9c0387', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpwtuf5Y/cinder/debian/control']' returned non-zero exit status 100Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: 

[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_keystone_trunk #146

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/146/Project:raring_grizzly_keystone_trunkDate of build:Sat, 16 Feb 2013 10:04:05 -0500Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changesadd missing kvs functionality (bug1119770)by chunggeditkeystone/identity/backends/ldap/core.pyedittests/test_backend.pyeditkeystone/identity/backends/pam.pyeditkeystone/identity/core.pyeditkeystone/identity/backends/sql.pyedittests/test_backend_kvs.pyedittests/test_backend_ldap.pyeditkeystone/identity/backends/kvs.pyedittests/test_content_types.pyeditkeystone/identity/controllers.pyConsole Output[...truncated 1252 lines...]Get:95 http://archive.ubuntu.com/ubuntu/ raring/main libtxc-dxtn-s2tc0 amd64 0~git20121227-1 [61.7 kB]Get:96 http://archive.ubuntu.com/ubuntu/ raring/main tcl8.5 amd64 8.5.13-1ubuntu1 [1097 kB]Get:97 http://archive.ubuntu.com/ubuntu/ raring/main tk8.5 amd64 8.5.11-2ubuntu1 [1009 kB]Get:98 http://archive.ubuntu.com/ubuntu/ raring/main blt amd64 2.4z-5 [1700 kB]Get:99 http://archive.ubuntu.com/ubuntu/ raring/main docutils-doc all 0.10-0ubuntu1 [1307 kB]Get:100 http://archive.ubuntu.com/ubuntu/ raring/main libjpeg8 amd64 8c-2ubuntu7 [2112 B]Get:101 http://archive.ubuntu.com/ubuntu/ raring/main libpaper-utils amd64 1.1.24+nmu2ubuntu2 [9164 B]Get:102 http://archive.ubuntu.com/ubuntu/ raring/main libutempter0 amd64 1.1.5-4build1 [8366 B]Get:103 http://archive.ubuntu.com/ubuntu/ raring/main python-beautifulsoup all 3.2.1-1 [34.6 kB]Get:104 http://archive.ubuntu.com/ubuntu/ raring/main python-egenix-mxtools amd64 3.2.5-1 [89.3 kB]Get:105 http://archive.ubuntu.com/ubuntu/ raring/main python-egenix-mxdatetime amd64 3.2.5-1 [79.5 kB]Get:106 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging-compat all 1.1.7+1.7.8-1ubuntu2 [5628 B]Get:107 http://archive.ubuntu.com/ubuntu/ raring/main python-imaging amd64 1.1.7+1.7.8-1ubuntu2 [304 kB]Get:108 http://archive.ubuntu.com/ubuntu/ raring/main python-openid all 2.2.5-3ubuntu1 [118 kB]Get:109 http://archive.ubuntu.com/ubuntu/ raring/main python-scgi amd64 1.13-1ubuntu2 [20.4 kB]Get:110 http://archive.ubuntu.com/ubuntu/ raring/main python-sqlalchemy-ext amd64 0.7.9-1 [14.2 kB]Get:111 http://archive.ubuntu.com/ubuntu/ raring/main python-tk amd64 2.7.3-1ubuntu3 [28.3 kB]Get:112 http://archive.ubuntu.com/ubuntu/ raring/main sphinx-doc all 1.1.3+dfsg-5ubuntu1 [855 kB]Get:113 http://archive.ubuntu.com/ubuntu/ raring/main x11-utils amd64 7.7~1ubuntu1 [230 kB]Get:114 http://archive.ubuntu.com/ubuntu/ raring/main xbitmaps all 1.1.1-2 [28.1 kB]Get:115 http://archive.ubuntu.com/ubuntu/ raring/main xterm amd64 278-1ubuntu2 [584 kB]Failed to fetch http://localhost/ubuntu/pool/main/p/python-keystoneclient/python-keystoneclient_0.2.2.40.g8e395e0+git201302160601~raring-0ubuntu1_all.deb  404  Not FoundFetched 33.0 MB in 24s (1369 kB/s)E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?install call failedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-a6a026ce-9f39-45ce-9b18-5b970ecaf1ec', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpcX7znw/keystone/debian/control']' returned non-zero exit status 100ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'raring-amd64-a6a026ce-9f39-45ce-9b18-5b970ecaf1ec', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpcX7znw/keystone/debian/control']' returned non-zero exit status 100INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmpcX7znw/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpcX7znw/keystone/debian/controlTraceback (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-a6a026ce-9f39-45ce-9b18-5b970ecaf1ec', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpcX7znw/keystone/debian/control']' returned non-zero exit status 100Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or 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-a6a026ce-9f39-45ce-9b18-5b970ecaf1ec', '-u', 'root', '--', 'mk-build-deps', '-i', '-r', '-t', 'apt-get -y', '/tmp/tmpcX7znw/keystone/debian/control']' returned non-zero exit status 100Build step 

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_keystone_trunk #147

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/147/Project:raring_grizzly_keystone_trunkDate of build:Sat, 16 Feb 2013 10:17:21 -0500Build duration:6 min 1 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 9869 lines...]Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 32Job: keystone_2013.1+git201302161017~raring-0ubuntu1.dscMachine Architecture: amd64Package: keystonePackage-Time: 194Source-Version: 2013.1+git201302161017~raring-0ubuntu1Space: 13816Status: attemptedVersion: 2013.1+git201302161017~raring-0ubuntu1Finished at 20130216-1023Build needed 00:03:14, 13816k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161017~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161017~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmptXC1yL/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmptXC1yL/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201302161017~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201302161017~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201302161017~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161017~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161017~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_keystone_trunk #148

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/148/Project:raring_grizzly_keystone_trunkDate of build:Sat, 16 Feb 2013 11:01:09 -0500Build duration:4 min 29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40Changesremove unneeded config reloading (its already done during setUp)by iartarisiedittests/test_backend_ldap.pyConsole Output[...truncated 3611 lines...]Fail-Stage: install-depsHost Architecture: amd64Install-Time: 0Job: keystone_2013.1+git201302161101~raring-0ubuntu1.dscMachine Architecture: amd64Package: keystonePackage-Time: 0Source-Version: 2013.1+git201302161101~raring-0ubuntu1Space: 0Status: failedVersion: 2013.1+git201302161101~raring-0ubuntu1Finished at 20130216-1104Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161101~raring-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161101~raring-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmpQXx0Af/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpQXx0Af/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201302161101~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201302161101~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201302161101~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161101~raring-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'keystone_2013.1+git201302161101~raring-0ubuntu1.dsc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


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

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/138/Project:precise_grizzly_keystone_trunkDate of build:Sat, 16 Feb 2013 11:02:24 -0500Build duration:5 min 38 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60Changesremove unneeded config reloading (its already done during setUp)by iartarisiedittests/test_backend_ldap.pyConsole Output[...truncated 8706 lines...]Distribution: precise-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 46Job: keystone_2013.1+git201302161102~precise-0ubuntu1.dscMachine Architecture: amd64Package: keystonePackage-Time: 210Source-Version: 2013.1+git201302161102~precise-0ubuntu1Space: 13792Status: attemptedVersion: 2013.1+git201302161102~precise-0ubuntu1Finished at 20130216-1108Build needed 00:03:30, 13792k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201302161102~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'keystone_2013.1+git201302161102~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmpLka6Rs/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpLka6Rs/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201302161102~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201302161102~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201302161102~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+git201302161102~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+git201302161102~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_cinder_trunk #150

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/150/Project:precise_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 12:01:08 -0500Build duration:3 min 56 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd GlusterFS volume driverby eharneyeditcinder/exception.pyaddcinder/tests/test_glusterfs.pyaddcinder/volume/drivers/glusterfs.pyeditetc/cinder/cinder.conf.sampleConsole Output[...truncated 5394 lines...]Source-Version: 2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1Space: 24280Status: attemptedVersion: 2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1Finished at 20130216-1204Build needed 00:02:10, 24280k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpzXDMPS/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpzXDMPS/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [1fc5575] Add LIO iSCSI backend support using python-rtslibdch -a [06b26a8] Add GlusterFS volume driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a142.g1f0aad5+git201302161201~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A cinder_2013.1.a142.g1f0aad5+git201302161201~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', 'cinder_2013.1.a142.g1f0aad5+git201302161201~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', 'cinder_2013.1.a142.g1f0aad5+git201302161201~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_cinder_trunk #152

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/152/Project:raring_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 12:01:08 -0500Build duration:5 min 40 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd GlusterFS volume driverby eharneyaddcinder/tests/test_glusterfs.pyaddcinder/volume/drivers/glusterfs.pyeditetc/cinder/cinder.conf.sampleeditcinder/exception.pyConsole Output[...truncated 6309 lines...]Source-Version: 2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1Space: 24264Status: attemptedVersion: 2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1Finished at 20130216-1206Build needed 00:02:06, 24264k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmp8fJpx2/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp8fJpx2/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [1fc5575] Add LIO iSCSI backend support using python-rtslibdch -a [06b26a8] Add GlusterFS volume driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a142.g1f0aad5+git201302161201~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_deploy #149

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/149/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 13:46:21 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesConsole Output[...truncated 13414 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #14

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/14/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 14:33:19 -0500Build duration:19 minBuild cause:Started by command line by jenkinsStarted by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5325 lines...]INFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_cinder_trunk #151

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_cinder_trunk/151/Project:precise_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 15:31:10 -0500Build duration:4 min 45 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd an ID to temporary volume snapshot objectby john.griffitheditcinder/volume/drivers/lvm.pyConsole Output[...truncated 5397 lines...]Space: 24276Status: attemptedVersion: 2013.1.a144.ge835c9f+git201302161531~precise-0ubuntu1Finished at 20130216-1535Build needed 00:02:33, 24276k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpOHt2ra/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpOHt2ra/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a144.ge835c9f+git201302161531~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [1fc5575] Add LIO iSCSI backend support using python-rtslibdch -a [06b26a8] Add GlusterFS volume driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [9627e6d] Add an ID to temporary volume snapshot objectdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a144.ge835c9f+git201302161531~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A cinder_2013.1.a144.ge835c9f+git201302161531~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', 'cinder_2013.1.a144.ge835c9f+git201302161531~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', 'cinder_2013.1.a144.ge835c9f+git201302161531~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_cinder_trunk #153

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/153/Project:raring_grizzly_cinder_trunkDate of build:Sat, 16 Feb 2013 15:31:09 -0500Build duration:6 min 48 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd an ID to temporary volume snapshot objectby john.griffitheditcinder/volume/drivers/lvm.pyConsole Output[...truncated 6314 lines...]Space: 24268Status: attemptedVersion: 2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1Finished at 20130216-1537Build needed 00:02:39, 24268k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmpJmxxGD/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpJmxxGD/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 90971cd1026728d3061e13843d117e549c0be67c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [695e3a8] Adding support for Coraid AoE SANs Appliances.dch -a [f06f5e1] Add an update option to run_tests.shdch -a [edbfa6a] Update EMC SMI-S Driverdch -a [1fc5575] Add LIO iSCSI backend support using python-rtslibdch -a [06b26a8] Add GlusterFS volume driverdch -a [abd3475] Create a RemoteFsDriver classdch -a [9627e6d] Add an ID to temporary volume snapshot objectdch -a [d17cc23] Allow create_volume() to retry when exception happeneddch -a [029435c] rbd: update volume<->image copyingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'cinder_2013.1.a144.ge835c9f+git201302161531~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_deploy #150

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/150/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 14:53:06 -0500Build duration:47 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 13421 lines...]INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_glance_trunk #122

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/122/Project:precise_grizzly_glance_trunkDate of build:Sat, 16 Feb 2013 15:32:10 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesAdd status column to image_membersby iccha.sethieditglance/tests/unit/test_migrations.pyaddglance/db/sqlalchemy/migrate_repo/versions/016_add_status_image_member.pyeditglance/db/sqlalchemy/models.pyConsole Output[...truncated 5844 lines...]INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpJCzGXk/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpJCzGXk/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 86c73141a859c80265f3fbf835b15f7b6e964136..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 2013.1.a102.g2791d10+git201302161532~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [b4b126d] Add status column to image_membersdch -a [44ceb21] Adding image members in glance v2 apidch -a [31cae6a] Fix issues with migration 012dch -a [b584b83] Add migration.py based on the one in nova.dch -a [75dd3fb] Updated_at not being passed to db in image createdch -a [0756cf1] Clean dangling image fragments in filesystem storedch -a [3d4a77d] Sample config and doc for the show_image_direct_url option.dch -a [9f4fb2c] Avoid dangling partial image on size/checksum mismatchdch -a [6b706f1] Fix version issue during nosetests rundch -a [9518b9d] Adding database layer for image members domain modeldch -a [286dd79] Image Member Domain Modeldch -a [93cd456] Additional image member informationdch -a [c857149] Adding finer notifications.dch -a [a754aec] Add LazyPluggable utility from nova.dch -a [cb664f9] Update .coveragercdch -a [07e18c6] Replace nose plugin with testtools details.dch -a [68010c2] Convert some prints to addDetails calls.dch -a [68d71ea] Add _FATAL_EXCEPTION_FORMAT_ERRORS global.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a102.g2791d10+git201302161532~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1.a102.g2791d10+git201302161532~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', 'glance_2013.1.a102.g2791d10+git201302161532~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', 'glance_2013.1.a102.g2791d10+git201302161532~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: raring_grizzly_glance_trunk #136

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/136/Project:raring_grizzly_glance_trunkDate of build:Sat, 16 Feb 2013 15:31:10 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesAdd status column to image_membersby iccha.sethieditglance/db/sqlalchemy/models.pyeditglance/tests/unit/test_migrations.pyaddglance/db/sqlalchemy/migrate_repo/versions/016_add_status_image_member.pyConsole Output[...truncated 8449 lines...]Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1.a92.gdf01d01+git201302141801~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/raring-grizzly']Pushed up to revision 236.INFO:root:Storing current commit for next build: b4b126d41c4de71794ed3b601d511e15c9718af9INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpsqhcSs/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpsqhcSs/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 86c73141a859c80265f3fbf835b15f7b6e964136..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a102.g2791d10+git201302161531~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [b4b126d] Add status column to image_membersdch -a [44ceb21] Adding image members in glance v2 apidch -a [31cae6a] Fix issues with migration 012dch -a [b584b83] Add migration.py based on the one in nova.dch -a [75dd3fb] Updated_at not being passed to db in image createdch -a [0756cf1] Clean dangling image fragments in filesystem storedch -a [3d4a77d] Sample config and doc for the show_image_direct_url option.dch -a [9f4fb2c] Avoid dangling partial image on size/checksum mismatchdch -a [6b706f1] Fix version issue during nosetests rundch -a [9518b9d] Adding database layer for image members domain modeldch -a [286dd79] Image Member Domain Modeldch -a [93cd456] Additional image member informationdch -a [c857149] Adding finer notifications.dch -a [a754aec] Add LazyPluggable utility from nova.dch -a [cb664f9] Update .coveragercdch -a [07e18c6] Replace nose plugin with testtools details.dch -a [68010c2] Convert some prints to addDetails calls.dch -a [68d71ea] Add _FATAL_EXCEPTION_FORMAT_ERRORS global.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1.a102.g2791d10+git201302161531~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1.a102.g2791d10+git201302161531~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1.a102.g2791d10+git201302161531~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly glance_2013.1.a102.g2791d10+git201302161531~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/raring-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: raring_grizzly_deploy #15

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/15/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 15:40:06 -0500Build duration:19 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5210 lines...]INFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_deploy #151

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/151/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 15:59:30 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13865 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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: precise_grizzly_deploy #152

2013-02-16 Thread openstack-testing-bot
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/152/Project:precise_grizzly_deployDate of build:Sat, 16 Feb 2013 19:15:13 -0500Build duration:47 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13911 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-12.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-12.os.magners.qa.lexingtonINFO:root:Setting up connection to test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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_deploy #16

2013-02-16 Thread openstack-testing-bot
Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/16/Project:raring_grizzly_deployDate of build:Sat, 16 Feb 2013 20:02:16 -0500Build duration:19 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5680 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-12.os.magners.qa.lexingtonERROR:root:Could not setup SSH connection to test-12.os.magners.qa.lexingtonINFO:root:Setting up connection to test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.1p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-12.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-05.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-12.os.magners.qa.lexingtonERROR:root:Unable to get information from test-12.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.Traceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 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