date:20130311


Hi Rick, reply inline.

Le 08/03/2013 20:27, Rick Jones a écrit :

On 03/08/2013 09:55 AM, Aaron Rosen wrote:

Hi Sylvain,


This seems very odd to me. The reason this should happen is if your
client is sending packets with the DF (don't fragment) bit set in the
TCP header of the packets you are sending. I'd confirm that your
version of 'curl' is doing this (which it should definitely not do!).


Why shouldn't a TCP connection initiated by curl (or anything else) 
have Path MTU discovery enabled? (ie the DF bit set in the IP 
datagrams carrying the TCP segments)




[SBA] Thanks for the explanation of the DF flag

What should happen is the router should fragment the packets for you
and if a fragment is lost TCP will just re-transmit the full packet
again and things should eventually work


Here I thought all the IETF demigods considered IP Fragmentation 'To 
Be Avoided (tm)' - hence the creation of Path MTU discovery in the 
first place. :)


FWIW, in the IPv6 world, routers do not fragment.  That implies either 
functioning PathMTU discovery, or lowest common MTU...




Aaron


On Fri, Mar 8, 2013 at 9:08 AM, Sylvain Bauza
sylvain.ba...@digimind.com wrote:

Hi,

I recently observed a strange behaviour with L3 Quantum routing 
(Openvswitch

setup with Provider Router). A simple curl to an external website is
sometimes failing due to packet size  :

 192.168.10.3  X.X.X.X: ICMP 192.168.10.3 unreachable - need to 
frag

(mtu 1454), length 556
 IP (tos 0x0, ttl 48, id 25918, offset 0, flags [DF], proto TCP 
(6),

length 1500)


Why is the ICMP Destination Unreachable datagram being sent back so 
large?  I would have expected it to be rather smaller - an Ethernet, 
IP and ICMP header, and then the original IP header and something like 
8 bytes or so of the original IP datagram's payload.


I take it that ICMP is not getting back to the original sender? Or is 
being ignored?





[SBA] I take the point. That means that PathMTU is not working for my 
Quantum installation. I also had a Nova-network (FlatDHCP mode) and I 
didn't noticed the issue. So, I assume something is wrong with my config.





Only changing the VM MTU to 1454 does the trick ('ifconfig eth0 mtu 
1454').


For info, 192.168.10.3 is the floating IP bound to 10.0.0.4 (private 
IP).


I suppose if 10.0.0.4 doesn't explicitly know about 192.168.10.3 it 
might indeed ignore the ICMP message.  Assuming it isn't getting 
un-NATted on the way back.




[SBA] This *is* un-NAT'd on the way back. By tcpdump'ing with the '-i 
any' interface, I can see the DNAT mapping on the way back :



Do you have any idea on what I should fix (or at least workaround) to 
have PathMTU working ?
By the way, I did check and both client (10.0.0.4) and server (X.X.X.X) 
have MTU set to 1500. I can't understand why the server is asking for a 
fragment size of 1454.


Thanks,
-Sylvain


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

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

I also forgot to mention: I'm using a typical Openvswitch setup with GRE 
encapsulation.

I can't proof, but would GRE not able to work with PathMTU ?

-Sylvain

Le 11/03/2013 09:40, Sylvain Bauza a écrit :

Hi Rick, reply inline.

Le 08/03/2013 20:27, Rick Jones a écrit :

On 03/08/2013 09:55 AM, Aaron Rosen wrote:

Hi Sylvain,


This seems very odd to me. The reason this should happen is if your
client is sending packets with the DF (don't fragment) bit set in the
TCP header of the packets you are sending. I'd confirm that your
version of 'curl' is doing this (which it should definitely not do!).


Why shouldn't a TCP connection initiated by curl (or anything else) 
have Path MTU discovery enabled? (ie the DF bit set in the IP 
datagrams carrying the TCP segments)




[SBA] Thanks for the explanation of the DF flag

What should happen is the router should fragment the packets for you
and if a fragment is lost TCP will just re-transmit the full packet
again and things should eventually work


Here I thought all the IETF demigods considered IP Fragmentation 'To 
Be Avoided (tm)' - hence the creation of Path MTU discovery in the 
first place. :)


FWIW, in the IPv6 world, routers do not fragment.  That implies 
either functioning PathMTU discovery, or lowest common MTU...




Aaron


On Fri, Mar 8, 2013 at 9:08 AM, Sylvain Bauza
sylvain.ba...@digimind.com wrote:

Hi,

I recently observed a strange behaviour with L3 Quantum routing 
(Openvswitch

setup with Provider Router). A simple curl to an external website is
sometimes failing due to packet size  :

 192.168.10.3  X.X.X.X: ICMP 192.168.10.3 unreachable - need 
to frag

(mtu 1454), length 556
 IP (tos 0x0, ttl 48, id 25918, offset 0, flags [DF], proto TCP 
(6),

length 1500)


Why is the ICMP Destination Unreachable datagram being sent back so 
large?  I would have expected it to be rather smaller - an Ethernet, 
IP and ICMP header, and then the original IP header and something 
like 8 bytes or so of the original IP datagram's payload.


I take it that ICMP is not getting back to the original sender? Or is 
being ignored?





[SBA] I take the point. That means that PathMTU is not working for my 
Quantum installation. I also had a Nova-network (FlatDHCP mode) and I 
didn't noticed the issue. So, I assume something is wrong with my config.





Only changing the VM MTU to 1454 does the trick ('ifconfig eth0 mtu 
1454').


For info, 192.168.10.3 is the floating IP bound to 10.0.0.4 
(private IP).


I suppose if 10.0.0.4 doesn't explicitly know about 192.168.10.3 it 
might indeed ignore the ICMP message.  Assuming it isn't getting 
un-NATted on the way back.




[SBA] This *is* un-NAT'd on the way back. By tcpdump'ing with the '-i 
any' interface, I can see the DNAT mapping on the way back :



Do you have any idea on what I should fix (or at least workaround) to 
have PathMTU working ?
By the way, I did check and both client (10.0.0.4) and server 
(X.X.X.X) have MTU set to 1500. I can't understand why the server is 
asking for a fragment size of 1454.


Thanks,
-Sylvain




___
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] [Heat] Problem with visit 169.254.169.254 from VM

2013-03-11 Thread Steven Hardy

On Thu, Mar 07, 2013 at 09:09:57AM +0800, 蒋闻天 wrote:
 Hi everyone, I have a problem when i use devstack to test heat and quantum.
 This is my localrc
 
 DATABASE_PASSWORD=nova
 RABBIT_PASSWORD=nova
 SERVICE_TOKEN=nova
 SERVICE_PASSWORD=nova
 ADMIN_PASSWORD=nova
 SCREEN_LOGDIR=/var/log/devstack
 ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
 ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta
 ENABLED_SERVICES-=n-net

This last line looks like invalid bash syntax?

Try:

ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed 's/n-net//')

I suspect the problem is you have quantum and nova networking enabled due to
this bash error in the localrc

Steve

___
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] Network node needed?

No it's not needed, you just run quantum-server, the L3 agent, the DHCP
agent, and the plugin agent (probably open vSwitch) all on the controller.
You'll just need to plan out which NICs you'll use for what purpose and
setup accordingly.

As a side note, you'll also need to run the plugin agent on all your
compute nodes
On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote:

 Greetings all,

 Next week I'll be putting up a new folsom cluster (perhaps using these
 instructions:
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide).
 Presently, I don't have a box to devote to being a network node.  Is it
 necessary?  The clouds I've put up so far have just had controller and
 compute nodes? Is the network node required by quantum?

 Thanks much,
 JR

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

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

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

Okay. I think I got the reason why it's not working with OVS/GRE
contrary to FlatDHCP nova-network.
So, as per
http://www.cisco.com/en/US/tech/tk827/tk369/technologies_white_paper09186a00800d6979.shtml
,
GRE encapsulation protocol can add up to 34 bytes to the IP datagram
(meaning the TCP segment is only 1456 bytes if MTU set to 1500).
When the packet is about 1500 bytes, then it should fragment to keep the
1500-byte size of the reply (including GRE encap then).

Unfortunaly, due to security purpose, the ICMP packet type 3/code 4
(frag. needed) can't be reached to the X.X.X.X backend as this backend
is denying any ICMP request (firewall).
As a consequence, PathMTU is failing and packets still retransmited with
1500-byte size again and again...

As said on my first post, the only workaround I found is to modify *all*
my VMs with MTU set to 1454 (don't know why there is a 2-bytes overhead
compared to the 1456-byte I told above), including my Windows VMs which
is not a cool stuff (modifying a registry key and reboot the VM. Yes,
you aren't dreaming. This is the way for Windows-based machines to
modify MTUs...)

Do you know if any cool idea would prevent to modify VMs, and only do
things on the network node ?

My TCP/IP knowledge is quite at its limits, so any idea is great for me.

Thanks,
-Sylvain

(BTW, maybe my explanation is absolutely wrong, and GRE is not
responsible of the 36-byte overhead. If yes, please accept my apologies,
any other clarification would be great).

Le 11/03/2013 10:07, Sylvain Bauza a écrit :
I also forgot to mention: I'm using a typical Openvswitch setup with
GRE encapsulation.

I can't proof, but would GRE not able to work with PathMTU ?

-Sylvain

Le 11/03/2013 09:40, Sylvain Bauza a écrit :

Hi Rick, reply inline.

Le 08/03/2013 20:27, Rick Jones a écrit :

On 03/08/2013 09:55 AM, Aaron Rosen wrote:

Hi Sylvain,

This seems very odd to me. The reason this should happen is if your
client is sending packets with the DF (don't fragment) bit set in the
TCP header of the packets you are sending. I'd confirm that your
version of 'curl' is doing this (which it should definitely not do!).

Why shouldn't a TCP connection initiated by curl (or anything else)
have Path MTU discovery enabled? (ie the DF bit set in the IP
datagrams carrying the TCP segments)

[SBA] Thanks for the explanation of the DF flag

What should happen is the router should fragment the packets for you
and if a fragment is lost TCP will just re-transmit the full packet
again and things should eventually work

Here I thought all the IETF demigods considered IP Fragmentation 'To
Be Avoided (tm)' - hence the creation of Path MTU discovery in the
first place. :)

FWIW, in the IPv6 world, routers do not fragment. That implies
either functioning PathMTU discovery, or lowest common MTU...

Aaron

On Fri, Mar 8, 2013 at 9:08 AM, Sylvain Bauza
sylvain.ba...@digimind.com wrote:

Hi,

I recently observed a strange behaviour with L3 Quantum routing
(Openvswitch

setup with Provider Router). A simple curl to an external website is
sometimes failing due to packet size :

192.168.10.3 X.X.X.X: ICMP 192.168.10.3 unreachable - need
to frag

(mtu 1454), length 556
IP (tos 0x0, ttl 48, id 25918, offset 0, flags [DF], proto
TCP (6),

length 1500)

Why is the ICMP Destination Unreachable datagram being sent back so
large? I would have expected it to be rather smaller - an Ethernet,
IP and ICMP header, and then the original IP header and something
like 8 bytes or so of the original IP datagram's payload.

I take it that ICMP is not getting back to the original sender? Or
is being ignored?

[SBA] I take the point. That means that PathMTU is not working for my
Quantum installation. I also had a Nova-network (FlatDHCP mode) and I
didn't noticed the issue. So, I assume something is wrong with my
config.

Only changing the VM MTU to 1454 does the trick ('ifconfig eth0
mtu 1454').

For info, 192.168.10.3 is the floating IP bound to 10.0.0.4
(private IP).

I suppose if 10.0.0.4 doesn't explicitly know about 192.168.10.3 it
might indeed ignore the ICMP message. Assuming it isn't getting
un-NATted on the way back.

[SBA] This *is* un-NAT'd on the way back. By tcpdump'ing with the '-i
any' interface, I can see the DNAT mapping on the way back :

Do you have any idea on what I should fix (or at least workaround) to
have PathMTU working ?
By the way, I did check and both client (10.0.0.4) and server
(X.X.X.X) have MTU set to 1500. I can't understand why the server is
asking for a fragment size of 1454.

Thanks,
-Sylvain

___
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] Incredibly odd mysql permission error

Does anyone think this could be an openstack bug?  I just want to check
before submitting a bug report.

Sam


On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 Sorry, I really can't think of anything :(

 On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
  I dropped those users and no change.
 
  I also set up general logging in mysql but it really doesn't provide any
  additional information.  Any idea for a next step I could take?
 
  I am almost at the point of taking a tcpdump and trying to recreate the
  salted password.  :/
 
  Thanks for the help
 
  Sam
 
 
 
 
  On Fri, Mar 8, 2013 at 3:38 PM, Jay Pipes jaypi...@gmail.com
  mailto:jaypi...@gmail.com wrote:
 
  I'm stumped :( Looks like everything is set up correctly to me. What
 is
  interested is that your nova user access works from test2, but there
 is
  no nova@test2 user in the mysql.user table. What about doing a DROP
 USER
  nova@test1; FLUSH PRIVILEGES; and then see if that fixes things...
 since
  the nova@10.21.0.0/255.255.0.0 http://nova@10.21.0.0/255.255.0.0
  user is clearly working for the access
  from test2.
 
  Also, I'd recommend highly removing the nova@% user.
 
  Best,
  -jay
 
  On 03/08/2013 03:09 PM, Samuel Winchenbach wrote:
  
   http://paste2.org/p/3085807
  
  
   On Fri, Mar 8, 2013 at 2:46 PM, Jay Pipes jaypi...@gmail.com
  mailto:jaypi...@gmail.com
   mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
  
   Please paste the results of SELECT User, Host, Password FROM
  mysql.user
   when running as root...
  
   Thanks!
   -jay
  
   On 03/08/2013 02:25 PM, Samuel Winchenbach wrote:
Here are my grants.  I don't know if this helps, but I did
  verify that
the password was identical for each grant:
http://paste2.org/p/3085361
   
   
On Fri, Mar 8, 2013 at 2:17 PM, Samuel Winchenbach
   swinc...@gmail.com mailto:swinc...@gmail.com
  mailto:swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com
  mailto:swinc...@gmail.com mailto:swinc...@gmail.com wrote:
   
root@test1:/var/log# mysql -hmysql-ha -unova
-p -eSELECT User, Host,
  Password
FROM mysql.user;
ERROR 1142 (42000) at line 1: SELECT command denied to
 user
'nova'@'test1' for table 'user'
   
   
On Fri, Mar 8, 2013 at 2:06 PM, Jay Pipes
  jaypi...@gmail.com mailto:jaypi...@gmail.com
   mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
   
What does this show?
   
mysql -hmysql-ha -unova -pPASS -eSELECT User,
 Host,
   Password FROM
mysql.user
   
-jay
   
On 03/08/2013 01:46 PM, Samuel Winchenbach wrote:
 Sorry, that must have been a copy and paste error.
   Here
   is what I
 actually ran:

 http://paste2.org/p/3084996


 On Fri, Mar 8, 2013 at 12:40 PM, Jay Pipes
   jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com
 mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com
   mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:

 On 03/08/2013 12:19 PM, Samuel Winchenbach
 wrote:
  Hi All,
 
  I have two nodes (test1 and test2) that I am
  trying to
set up in a
  highly available configuration.
 
  During the setup process I tried running
  nova-manage
service list on
  both nodes.   It worked fine on test2, but
  fails on
test1 even
 though I
  can connect to the database with the mysql
  client from
test1.
 
  Here is a screen capture that shows the
 setup on
   the two
nodes are
  basically

[Openstack] Cinder volume as root in Grizzly?

Will Grizzly support specifying an empty Cinder volume as an instance's
root device?

Right now you need to setup the volume before hand and you can boot from
volume. But will there be support similar to AWS EBS-backed instances in
Grizzly?
___
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] Incredibly odd mysql permission error

So as to reproduce the nova-manage SQL command, I would recommand to 
tcpdump -A port 3306 on the host and get the SQL trace on what's failing.


Could you please explain further what is your HA config ? Are you using 
pacemaker/heartbeat or any VIP ?


-Sylvain

Le 11/03/2013 14:23, Samuel Winchenbach a écrit :
Does anyone think this could be an openstack bug?  I just want to 
check before submitting a bug report.


Sam


On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com 
mailto:jaypi...@gmail.com wrote:


Sorry, I really can't think of anything :(

On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
 I dropped those users and no change.

 I also set up general logging in mysql but it really doesn't
provide any
 additional information.  Any idea for a next step I could take?

 I am almost at the point of taking a tcpdump and trying to
recreate the
 salted password.  :/

 Thanks for the help

 Sam




 On Fri, Mar 8, 2013 at 3:38 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com
 mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:

 I'm stumped :( Looks like everything is set up correctly to
me. What is
 interested is that your nova user access works from test2,
but there is
 no nova@test2 user in the mysql.user table. What about doing
a DROP USER
 nova@test1; FLUSH PRIVILEGES; and then see if that fixes
things... since
 the nova@10.21.0.0/255.255.0.0
http://nova@10.21.0.0/255.255.0.0
http://nova@10.21.0.0/255.255.0.0
 user is clearly working for the access
 from test2.

 Also, I'd recommend highly removing the nova@% user.

 Best,
 -jay

 On 03/08/2013 03:09 PM, Samuel Winchenbach wrote:
 
  http://paste2.org/p/3085807
 
 
  On Fri, Mar 8, 2013 at 2:46 PM, Jay Pipes
jaypi...@gmail.com mailto:jaypi...@gmail.com
 mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
 
  Please paste the results of SELECT User, Host,
Password FROM
 mysql.user
  when running as root...
 
  Thanks!
  -jay
 
  On 03/08/2013 02:25 PM, Samuel Winchenbach wrote:
   Here are my grants.  I don't know if this helps, but
I did
 verify that
   the password was identical for each grant:
  http://paste2.org/p/3085361
  
  
   On Fri, Mar 8, 2013 at 2:17 PM, Samuel Winchenbach
  swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com
 mailto:swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com
   mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com
 mailto:swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com wrote:
  
   root@test1:/var/log# mysql -hmysql-ha -unova
   -p -eSELECT User, Host,
 Password
   FROM mysql.user;
   ERROR 1142 (42000) at line 1: SELECT command
denied to user
   'nova'@'test1' for table 'user'
  
  
   On Fri, Mar 8, 2013 at 2:06 PM, Jay Pipes
 jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
   mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com
 mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
  
   What does this show?
  
   mysql -hmysql-ha -unova -pPASS -eSELECT
User, Host,
  Password FROM
   mysql.user
  
   -jay
  
   On 03/08/2013 01:46 PM, Samuel Winchenbach
wrote:
Sorry, that must have been a copy and
paste error.
  Here
  is what I
actually ran:
   
http://paste2.org/p/3084996
   
   
On Fri, Mar 8, 2013 at 12:40 PM, Jay Pipes
  jaypi...@gmail.com mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com

Re: [Openstack] Incredibly odd mysql permission error

I
 enabled general_log in /etc/mysql/my.cnf  Here are the results of
connecting from test1, test2 and using the client:
http://paste2.org/p/3115525
I purposefully used the real password in case there is a problem with it.
  I changed before submitting post.


here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an
attempted nova-manage service list from test1:
https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

I looked at it with wireshark and couldn't see anything that jumped out at
me as incorrect.  I have not yet tried to recreate the salted password.


Here is my pacemaker configuration for mysql.  I stripped out openstack
services, rabbitmq and others for clarity.  All resources are currently
disabled (other than MySQL):
http://paste2.org/p/3115685


Please don't yell at me for having STONITH disabled :P  This is a testing
cluster and I am working on getting routed to the IPMI interface.

/etc/hosts:
http://paste2.org/p/3115713

/etc/nova/nova.conf:
http://paste2.org/p/3115739


If there is anything else I can provide you, please let me know!  I have
pulled out most of my hair at this point!

Sam




On Mon, Mar 11, 2013 at 10:11 AM, Sylvain Bauza
sylvain.ba...@digimind.comwrote:

  So as to reproduce the nova-manage SQL command, I would recommand to
 tcpdump -A port 3306 on the host and get the SQL trace on what's failing.

 Could you please explain further what is your HA config ? Are you using
 pacemaker/heartbeat or any VIP ?

 -Sylvain

 Le 11/03/2013 14:23, Samuel Winchenbach a écrit :

  Does anyone think this could be an openstack bug?  I just want to check
 before submitting a bug report.

  Sam


 On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 Sorry, I really can't think of anything :(

 On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
  I dropped those users and no change.
 
  I also set up general logging in mysql but it really doesn't provide any
  additional information.  Any idea for a next step I could take?
 
  I am almost at the point of taking a tcpdump and trying to recreate the
  salted password.  :/
 
  Thanks for the help
 
  Sam
 
 
 
 
  On Fri, Mar 8, 2013 at 3:38 PM, Jay Pipes jaypi...@gmail.com
   mailto:jaypi...@gmail.com wrote:
 
  I'm stumped :( Looks like everything is set up correctly to me.
 What is
  interested is that your nova user access works from test2, but
 there is
  no nova@test2 user in the mysql.user table. What about doing a
 DROP USER
  nova@test1; FLUSH PRIVILEGES; and then see if that fixes things...
 since
   the nova@10.21.0.0/255.255.0.0 http://nova@10.21.0.0/255.255.0.0
  user is clearly working for the access
  from test2.
 
  Also, I'd recommend highly removing the nova@% user.
 
  Best,
  -jay
 
  On 03/08/2013 03:09 PM, Samuel Winchenbach wrote:
  
   http://paste2.org/p/3085807
  
  
   On Fri, Mar 8, 2013 at 2:46 PM, Jay Pipes jaypi...@gmail.com
  mailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
  
Please paste the results of SELECT User, Host, Password FROM
  mysql.user
   when running as root...
  
   Thanks!
   -jay
  
   On 03/08/2013 02:25 PM, Samuel Winchenbach wrote:
Here are my grants.  I don't know if this helps, but I did
  verify that
the password was identical for each grant:
http://paste2.org/p/3085361
   
   
On Fri, Mar 8, 2013 at 2:17 PM, Samuel Winchenbach
   swinc...@gmail.com mailto:swinc...@gmail.com
  mailto:swinc...@gmail.com mailto:swinc...@gmail.com
mailto:swinc...@gmail.com mailto:swinc...@gmail.com
  mailto:swinc...@gmail.com mailto:swinc...@gmail.com wrote:
   
root@test1:/var/log# mysql -hmysql-ha -unova
-p -eSELECT User, Host,
  Password
FROM mysql.user;
ERROR 1142 (42000) at line 1: SELECT command denied to
 user
'nova'@'test1' for table 'user'
   
   
On Fri, Mar 8, 2013 at 2:06 PM, Jay Pipes
  jaypi...@gmail.com mailto:jaypi...@gmail.com
   mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com
 
  mailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote:
   
What does this show?
   
mysql -hmysql-ha -unova -pPASS -eSELECT User,
 Host,
   Password FROM
mysql.user
   
-jay
   
On 03/08/2013 01:46 PM, Samuel Winchenbach wrote:
 Sorry, that must have been a copy and paste error.
   Here
   is what I
 actually ran:

 http://paste2.org/p/3084996

Re: [Openstack] Network node needed?

2013-03-11 Thread Martinx - ジェームズ

Is it possible to deploy Quantum (Flat) with two servers (controller +
compute) that have only 1 ethernet on each?
Plus, the Instances gateway will not be the controller, but my office
firewall, external to the cloud, can be?

Tks!


On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com wrote:

 No it's not needed, you just run quantum-server, the L3 agent, the DHCP
 agent, and the plugin agent (probably open vSwitch) all on the controller.
 You'll just need to plan out which NICs you'll use for what purpose and
 setup accordingly.

 As a side note, you'll also need to run the plugin agent on all your
 compute nodes
 On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote:

 Greetings all,

 Next week I'll be putting up a new folsom cluster (perhaps using these
 instructions:
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide).
 Presently, I don't have a box to devote to being a network node.  Is it
 necessary?  The clouds I've put up so far have just had controller and
 compute nodes? Is the network node required by quantum?

 Thanks much,
 JR

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


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


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

Re: [Openstack] Network node needed?

2013-03-11 Thread JuanFra Rodriguez Cardoso

Hi:

You could find it in this link:
http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html


Regards,
JuanFra


2013/3/11 Martinx - ジェームズ thiagocmarti...@gmail.com

 Is it possible to deploy Quantum (Flat) with two servers (controller +
 compute) that have only 1 ethernet on each?
 Plus, the Instances gateway will not be the controller, but my office
 firewall, external to the cloud, can be?

 Tks!


 On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com wrote:

 No it's not needed, you just run quantum-server, the L3 agent, the DHCP
 agent, and the plugin agent (probably open vSwitch) all on the controller.
 You'll just need to plan out which NICs you'll use for what purpose and
 setup accordingly.

 As a side note, you'll also need to run the plugin agent on all your
 compute nodes
 On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote:

 Greetings all,

 Next week I'll be putting up a new folsom cluster (perhaps using these
 instructions:
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide).
 Presently, I don't have a box to devote to being a network node.  Is it
 necessary?  The clouds I've put up so far have just had controller and
 compute nodes? Is the network node required by quantum?

 Thanks much,
 JR

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


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



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


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

[Openstack] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Girija Sharan

Hi All,

I am trying to do Integration testing of Openstack environmment (Folsom)
using Tempest.

On controller node I am having my Tempest root directory and I have also
installed Coverage, Tissue
and Openstack-nose as it was mentioned in the setup.cfg file.

1. Do I have to use this release
https://github.com/openstack/tempest/tree/stable/folsom ?

2. I am not getting how to configure tempest.conf for Folsom set up. For
Essex we were having localrc file but here in Folsom we are not having any
such thing. Is there any way to know what values to pass to respective
fields in tempest.conf ?

Any help will be highly appreciated.


Thanks and Regards,
Girija Sharan Singh
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] quantum-agent-setup: command not found

2013-03-11 Thread Aru s

I belive the below command will work instead.
quantum-node-setup --plugin openvswitch

Regards,
Arumon

On Fri, Mar 8, 2013 at 9:54 PM, Aru s arumo...@gmail.com wrote:

 Hi,

 I have installed openstack-quantum-openvswitch on my compute host.
 When try to enable the agent i am getting the below error. Am i missing
 any packages to install? Please suggest.

 #quantum-agent-setup --plugin openvswitch
 -bash: quantum-agent-setup: command not found

 Regards,
 Arumon

___
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] Incredibly odd mysql permission error

#1 - No change
#2 - All of grants are in the ip/mask form such as: 'nova'@'
10.21.0.0/255.255.0.0'  I have also tried adding 'nova'@'test1' and
'nova'@'10.21.0.1'.
 No change.
#3 - I changed the SQL connection string over to IP instead of hostname.
 No change.  I didn't restart nova-api because it isn't running.   If I
understand correctly nova-manage communicated directly with the db,
bypassing nova-api.   This would appear true seeing nova-manage service
list works correctly on test2.


:(

Thanks for the help!
Sam


On Mon, Mar 11, 2013 at 12:24 PM, Sylvain Bauza
sylvain.ba...@digimind.comwrote:

  When looking at MySQL 5.1 refman (
 http://dev.mysql.com/doc/refman/5.1/en/access-denied.html ), I would
 suggest to follow the procedure :
  1. 'mysqladmin flush-hosts'
  2. replace DNS entries in mysql.user table by IP addresses instead
  3. modify /etc/nova/nova.conf with IP address of HA Mysql instead (and
 restart nova-api !)

 I wouldn't bet on it, but I would say this is due to some name resolution
 which is incorrect.

 -Sylvain


 Le 11/03/2013 17:00, Sylvain Bauza a écrit :

 Ok, lemme try to summarize.
 You do have a DRBD setup for MySQL bound to a VIP 10.21.1.1 thanks to
 Pacemaker.
 This setup is relying on two hosts, test1 (10.21.0.1) and test2
 (10.21.0.2).
 Your nova.conf is pointing to mysql://10.21.1.1 which is the VIP.

 Are you sure your my.cnf is actually the same in between both DRBD nodes ?
 (I would recommend to symlink it to a physical file hosted on the DRBD
 device).

 One thing is hurting me : you told me that nova is also pacemake'd. If so,
 why can I still see my_ip=10.21.0.2 (test2) ? It should be pointing to
 nova-ha (assuming 10.21.2.4 as per /etc/hosts).

 Also, as per my understanding of Pacemaker, DRBD partition is setup by
 default on test2, correct ?


 Sorry, as per my first reading, I can't see anything obvious. That said,
 I'm not sure this is a Nova bug, as the tcpdump trace is seeing a correct
 MySQL connection attempt. But maybe I'm wrong ?

 Anyway, are you sure you only have *one* MySQL engine running (either on
 test1 or test2) and nova-manage trying to access this right one ?

 Perms look good to me. As it a test setup, you could try to unleash the
 grants by deleting them and allowing nova@'%' to see if it's a basic dns
 mapping issue.

 -Sylvain



 Le 11/03/2013 16:09, Samuel Winchenbach a écrit :

 I
 enabled general_log in /etc/mysql/my.cnf  Here are the results of
 connecting from test1, test2 and using the client:
  http://paste2.org/p/3115525
  I purposefully used the real password in case there is a problem with
 it.
  I changed before submitting post.

   here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an
 attempted nova-manage service list from test1:
  https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

  I looked at it with wireshark and couldn't see anything that jumped out
 at me as incorrect.  I have not yet tried to recreate the salted password.


   Here is my pacemaker configuration for mysql.  I stripped out openstack
 services, rabbitmq and others for clarity.  All resources are currently
 disabled (other than MySQL):
 http://paste2.org/p/3115685


   Please don't yell at me for having STONITH disabled :P  This is a
 testing cluster and I am working on getting routed to the IPMI interface.

   /etc/hosts:
 http://paste2.org/p/3115713
   /etc/nova/nova.conf:
 http://paste2.org/p/3115739


   If there is anything else I can provide you, please let me know!  I
 have pulled out most of my hair at this point!

   Sam




 On Mon, Mar 11, 2013 at 10:11 AM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

  So as to reproduce the nova-manage SQL command, I would recommand to
 tcpdump -A port 3306 on the host and get the SQL trace on what's failing.

 Could you please explain further what is your HA config ? Are you using
 pacemaker/heartbeat or any VIP ?

 -Sylvain

 Le 11/03/2013 14:23, Samuel Winchenbach a écrit :

  Does anyone think this could be an openstack bug?  I just want to check
 before submitting a bug report.

  Sam


 On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 Sorry, I really can't think of anything :(

 On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
  I dropped those users and no change.
 
  I also set up general logging in mysql but it really doesn't provide
 any
  additional information.  Any idea for a next step I could take?
 
  I am almost at the point of taking a tcpdump and trying to recreate the
  salted password.  :/
 
  Thanks for the help
 
  Sam
 
 
 
 
  On Fri, Mar 8, 2013 at 3:38 PM, Jay Pipes jaypi...@gmail.com
   mailto:jaypi...@gmail.com wrote:
 
  I'm stumped :( Looks like everything is set up correctly to me.
 What is
  interested is that your nova user access works from test2, but
 there is
  no nova@test2 user in the mysql.user table. What about doing a
 DROP USER
  nova@test1; FLUSH PRIVILEGES; and then see if that fixes
 things... since
   the

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

2013-03-11 Thread Rick Jones

On 03/11/2013 06:09 AM, Sylvain Bauza wrote:

That sounds like the reason.

Do you know if any cool idea would prevent to modify VMs, and only do
things on the network node ?

Yes. Let the ICMP Destination Unreachable, Datagram Too Big messages
through. So the network can function the way it was intended.

Otherwise you have no recourse but alter the MTU in the VMs. Or add the
insult of tweaking the code to ignore the DF bit to the injury of
blocking the ICMP messages. (Assuming that is even possible)

If you are Very Lucky (tm) all your network infrastructure in the
broadcast domain (everything on the same side of a router - device
forwarding based on Layer3 (eg IP) addressing or put another way,
everything reachable via just switches - in the proper sense of the term
wherein a switch is a device making forwarding decisions based on
layer2, eg Ethernet addresses) then you can try to increase the MTU of
your physical interfaces so the GRE encapsulation overhead can be
hidden from the VMs. But *everything* in the broadcast domain must
have the same maximum frame size (MTU) or life becomes even more
interesting.

My suggestion is let the ICMP Destination Unreachable, Datagram Too Big
messages through. It is perhaps my failing, but I fail to see how
blocking them improves security.

rick jones
adde parvum parvo magnus acervus erit - Ovid quoted in The Mythical Man
Month

___
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] Incredibly odd mysql permission error

For completeness here the routing table, and ip listing for both test1 and
test2.   Doubt this will help much:  http://paste2.org/p/3117125


On Mon, Mar 11, 2013 at 1:52 PM, Samuel Winchenbach swinc...@gmail.comwrote:

 #1 - No change
 #2 - All of grants are in the ip/mask form such as: 'nova'@'
 10.21.0.0/255.255.0.0'  I have also tried adding 'nova'@'test1' and
 'nova'@'10.21.0.1'.  No change.
 #3 - I changed the SQL connection string over to IP instead of hostname.
  No change.  I didn't restart nova-api because it isn't running.   If I
 understand correctly nova-manage communicated directly with the db,
 bypassing nova-api.   This would appear true seeing nova-manage service
 list works correctly on test2.


 :(

 Thanks for the help!
 Sam


 On Mon, Mar 11, 2013 at 12:24 PM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

  When looking at MySQL 5.1 refman (
 http://dev.mysql.com/doc/refman/5.1/en/access-denied.html ), I would
 suggest to follow the procedure :
  1. 'mysqladmin flush-hosts'
  2. replace DNS entries in mysql.user table by IP addresses instead
  3. modify /etc/nova/nova.conf with IP address of HA Mysql instead (and
 restart nova-api !)

 I wouldn't bet on it, but I would say this is due to some name resolution
 which is incorrect.

 -Sylvain


 Le 11/03/2013 17:00, Sylvain Bauza a écrit :

 Ok, lemme try to summarize.
 You do have a DRBD setup for MySQL bound to a VIP 10.21.1.1 thanks to
 Pacemaker.
 This setup is relying on two hosts, test1 (10.21.0.1) and test2
 (10.21.0.2).
 Your nova.conf is pointing to mysql://10.21.1.1 which is the VIP.

 Are you sure your my.cnf is actually the same in between both DRBD nodes
 ? (I would recommend to symlink it to a physical file hosted on the DRBD
 device).

 One thing is hurting me : you told me that nova is also pacemake'd. If
 so, why can I still see my_ip=10.21.0.2 (test2) ? It should be pointing to
 nova-ha (assuming 10.21.2.4 as per /etc/hosts).

 Also, as per my understanding of Pacemaker, DRBD partition is setup by
 default on test2, correct ?


 Sorry, as per my first reading, I can't see anything obvious. That said,
 I'm not sure this is a Nova bug, as the tcpdump trace is seeing a correct
 MySQL connection attempt. But maybe I'm wrong ?

 Anyway, are you sure you only have *one* MySQL engine running (either on
 test1 or test2) and nova-manage trying to access this right one ?

 Perms look good to me. As it a test setup, you could try to unleash the
 grants by deleting them and allowing nova@'%' to see if it's a basic dns
 mapping issue.

 -Sylvain



 Le 11/03/2013 16:09, Samuel Winchenbach a écrit :

 I
 enabled general_log in /etc/mysql/my.cnf  Here are the results of
 connecting from test1, test2 and using the client:
  http://paste2.org/p/3115525
  I purposefully used the real password in case there is a problem with
 it.
  I changed before submitting post.

   here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an
 attempted nova-manage service list from test1:
  https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

  I looked at it with wireshark and couldn't see anything that jumped out
 at me as incorrect.  I have not yet tried to recreate the salted password.


   Here is my pacemaker configuration for mysql.  I stripped out
 openstack services, rabbitmq and others for clarity.  All resources are
 currently disabled (other than MySQL):
 http://paste2.org/p/3115685


   Please don't yell at me for having STONITH disabled :P  This is a
 testing cluster and I am working on getting routed to the IPMI interface.

   /etc/hosts:
 http://paste2.org/p/3115713
   /etc/nova/nova.conf:
 http://paste2.org/p/3115739


   If there is anything else I can provide you, please let me know!  I
 have pulled out most of my hair at this point!

   Sam




 On Mon, Mar 11, 2013 at 10:11 AM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

  So as to reproduce the nova-manage SQL command, I would recommand to
 tcpdump -A port 3306 on the host and get the SQL trace on what's failing.

 Could you please explain further what is your HA config ? Are you using
 pacemaker/heartbeat or any VIP ?

 -Sylvain

 Le 11/03/2013 14:23, Samuel Winchenbach a écrit :

  Does anyone think this could be an openstack bug?  I just want to
 check before submitting a bug report.

  Sam


 On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 Sorry, I really can't think of anything :(

 On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
  I dropped those users and no change.
 
  I also set up general logging in mysql but it really doesn't provide
 any
  additional information.  Any idea for a next step I could take?
 
  I am almost at the point of taking a tcpdump and trying to recreate
 the
  salted password.  :/
 
  Thanks for the help
 
  Sam
 
 
 
 
  On Fri, Mar 8, 2013 at 3:38 PM, Jay Pipes jaypi...@gmail.com
   mailto:jaypi...@gmail.com wrote:
 
  I'm stumped :( Looks like everything is set up correctly to me.
 What is

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Miller, Mark M (EB SW Cloud - RD - Corvallis)

OK  Someone on the IRC channel got me closer, but we have no idea why
this would happen:

this works: root@test1:~# nova-manage --config-file=/etc/nova/nova.conf
service list

Why would I have to specify the config file though?  It is in the standard
place.

Thanks,
Sam




On Mon, Mar 11, 2013 at 2:01 PM, Samuel Winchenbach swinc...@gmail.comwrote:

 For completeness here the routing table, and ip listing for both test1 and
 test2.   Doubt this will help much:  http://paste2.org/p/3117125


 On Mon, Mar 11, 2013 at 1:52 PM, Samuel Winchenbach swinc...@gmail.comwrote:

 #1 - No change
 #2 - All of grants are in the ip/mask form such as: 'nova'@'
 10.21.0.0/255.255.0.0'  I have also tried adding 'nova'@'test1' and
 'nova'@'10.21.0.1'.  No change.
 #3 - I changed the SQL connection string over to IP instead of hostname.
  No change.  I didn't restart nova-api because it isn't running.   If I
 understand correctly nova-manage communicated directly with the db,
 bypassing nova-api.   This would appear true seeing nova-manage service
 list works correctly on test2.


 :(

 Thanks for the help!
 Sam


 On Mon, Mar 11, 2013 at 12:24 PM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

  When looking at MySQL 5.1 refman (
 http://dev.mysql.com/doc/refman/5.1/en/access-denied.html ), I would
 suggest to follow the procedure :
  1. 'mysqladmin flush-hosts'
  2. replace DNS entries in mysql.user table by IP addresses instead
  3. modify /etc/nova/nova.conf with IP address of HA Mysql instead (and
 restart nova-api !)

 I wouldn't bet on it, but I would say this is due to some name
 resolution which is incorrect.

 -Sylvain


 Le 11/03/2013 17:00, Sylvain Bauza a écrit :

 Ok, lemme try to summarize.
 You do have a DRBD setup for MySQL bound to a VIP 10.21.1.1 thanks to
 Pacemaker.
 This setup is relying on two hosts, test1 (10.21.0.1) and test2
 (10.21.0.2).
 Your nova.conf is pointing to mysql://10.21.1.1 which is the VIP.

 Are you sure your my.cnf is actually the same in between both DRBD nodes
 ? (I would recommend to symlink it to a physical file hosted on the DRBD
 device).

 One thing is hurting me : you told me that nova is also pacemake'd. If
 so, why can I still see my_ip=10.21.0.2 (test2) ? It should be pointing to
 nova-ha (assuming 10.21.2.4 as per /etc/hosts).

 Also, as per my understanding of Pacemaker, DRBD partition is setup by
 default on test2, correct ?


 Sorry, as per my first reading, I can't see anything obvious. That said,
 I'm not sure this is a Nova bug, as the tcpdump trace is seeing a correct
 MySQL connection attempt. But maybe I'm wrong ?

 Anyway, are you sure you only have *one* MySQL engine running (either on
 test1 or test2) and nova-manage trying to access this right one ?

 Perms look good to me. As it a test setup, you could try to unleash the
 grants by deleting them and allowing nova@'%' to see if it's a basic
 dns mapping issue.

 -Sylvain



 Le 11/03/2013 16:09, Samuel Winchenbach a écrit :

 I
 enabled general_log in /etc/mysql/my.cnf  Here are the results of
 connecting from test1, test2 and using the client:
  http://paste2.org/p/3115525
  I purposefully used the real password in case there is a problem with
 it.
  I changed before submitting post.

   here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an
 attempted nova-manage service list from test1:
  https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

  I looked at it with wireshark and couldn't see anything that jumped
 out at me as incorrect.  I have not yet tried to recreate the salted
 password.


   Here is my pacemaker configuration for mysql.  I stripped out
 openstack services, rabbitmq and others for clarity.  All resources are
 currently disabled (other than MySQL):
 http://paste2.org/p/3115685


   Please don't yell at me for having STONITH disabled :P  This is a
 testing cluster and I am working on getting routed to the IPMI interface.

   /etc/hosts:
 http://paste2.org/p/3115713
   /etc/nova/nova.conf:
 http://paste2.org/p/3115739


   If there is anything else I can provide you, please let me know!  I
 have pulled out most of my hair at this point!

   Sam




 On Mon, Mar 11, 2013 at 10:11 AM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

  So as to reproduce the nova-manage SQL command, I would recommand to
 tcpdump -A port 3306 on the host and get the SQL trace on what's failing.

 Could you please explain further what is your HA config ? Are you using
 pacemaker/heartbeat or any VIP ?

 -Sylvain

 Le 11/03/2013 14:23, Samuel Winchenbach a écrit :

  Does anyone think this could be an openstack bug?  I just want to
 check before submitting a bug report.

  Sam


 On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 Sorry, I really can't think of anything :(

 On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
  I dropped those users and no change.
 
  I also set up general logging in mysql but it really doesn't provide
 any
  additional information.  Any idea

Re: [Openstack] Network node needed?

2013-03-11 Thread Martinx - ジェームズ

Well, I've read that but, I'm still unable to run Quantum on
its simplest scenario... FlatDHCP single (multi=false, no-GRE, no L3
agents?)...?

I mean, I'm trying Quantum without the network-node too (i.e. controller
does that job)... So, not off-topic...  =)

Today, I have Folsom with Nova-Network FlatDHCP (1 ethernet
/ physical server), Cloud net 10.32.14.0/24, Instances net 10.33.14.0/24,
option multi = true = hypervisores are the gateways of its own Instances.

I followed this guide:
http://openstack-folsom-install-guide.readthedocs.org/en/latest/ - works
almost flawlessly.

So, how can I setup Quantum that works almost like Nova-Network-FlatDHCP
(but with like multi=false, gateway's instances is outside of the Cloud)?

I'm reading this:
http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html-
but, it doesn't help me to fix my Quantum PoC...

My Instances doesn't get an IP...

OpenvSwitch is working, I'm already using it with my previous Folsom +
Nova-Network (brcompat enabled). So, I'm trying OVSQuantumPluginV2...

Best,
Thiago

On 11 March 2013 12:59, JuanFra Rodriguez Cardoso 
juanfra.rodriguez.card...@gmail.com wrote:

 Hi:

 You could find it in this link:
 http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html


 Regards,
 JuanFra


 2013/3/11 Martinx - ジェームズ thiagocmarti...@gmail.com

 Is it possible to deploy Quantum (Flat) with two servers (controller +
 compute) that have only 1 ethernet on each?
 Plus, the Instances gateway will not be the controller, but my office
 firewall, external to the cloud, can be?

 Tks!


 On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com wrote:

 No it's not needed, you just run quantum-server, the L3 agent, the DHCP
 agent, and the plugin agent (probably open vSwitch) all on the controller.
 You'll just need to plan out which NICs you'll use for what purpose and
 setup accordingly.

 As a side note, you'll also need to run the plugin agent on all your
 compute nodes
 On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote:

 Greetings all,

 Next week I'll be putting up a new folsom cluster (perhaps using these
 instructions:
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide).
 Presently, I don't have a box to devote to being a network node.  Is it
 necessary?  The clouds I've put up so far have just had controller and
 compute nodes? Is the network node required by quantum?

 Thanks much,
 JR

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


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



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



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

Re: [Openstack] Keypair name - unsupported chars?

2013-03-11 Thread Scott Devoid

I can confirm this in Essex as well. I've posted a bug at:
https://bugs.launchpad.net/nova/+bug/1144839

~ Scott

On Wed, Mar 6, 2013 at 5:21 AM, Antonio Messina
antonio.s.mess...@gmail.com wrote:
 Hi all,

 I've just found that nova only accepts alphanumeric chars for keypair
 name, but it's giving an unclear message when you try to create a
 keypair using a non-alphanumeric char:

 (cloud)antonio@kenny:~$ nova keypair-add a/b --pub-key ~/.ssh/id_dsa.pub
 ERROR: Keypair data is invalid (HTTP 400) (Request-ID:
 req-5617dbb4-1c92-435b-ba88-7bcee5684f21)
 (cloud)antonio@kenny:~$ nova keypair-add a.b --pub-key ~/.ssh/id_dsa.pub
 ERROR: Keypair data is invalid (HTTP 400) (Request-ID:
 req-54078fcf-f8b1-4268-ba9e-3f20f79ce995)
 (cloud)antonio@kenny:~$ nova keypair-add a,b --pub-key ~/.ssh/id_dsa.pub
 ERROR: Keypair data is invalid (HTTP 400) (Request-ID:
 req-29bc9b76-83b3-42e4-8af2-ff9dd28c9149)
 (cloud)antonio@kenny:~$ nova keypair-add a:b --pub-key ~/.ssh/id_dsa.pub
 ERROR: Keypair data is invalid (HTTP 400) (Request-ID:
 req-87a32c9e-0f90-4fb9-b380-4d34c4f2df50)

 is this a knew feature or should I open a bug?

 This has been tested on folsom/ubuntu.

 .a.

 --
 antonio.s.mess...@gmail.com
 GC3: Grid Computing Competence Center
 http://www.gc3.uzh.ch/
 University of Zurich
 Winterthurerstrasse 190
 CH-8057 Zurich Switzerland

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

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

Re: [Openstack] Incredibly odd mysql permission error

I ran into a similar problem with the Grizzly-3 Keystone release. I had to 
specify keystone.conf as the config-file with keystone-manage/ db_sync command 
otherwise it would not use the mysql statement in the keystone.conf file.

Mark

From: openstack-bounces+mark.m.miller=hp@lists.launchpad.net 
[mailto:openstack-bounces+mark.m.miller=hp@lists.launchpad.net] On Behalf 
Of Samuel Winchenbach
Sent: Monday, March 11, 2013 11:18 AM
To: Sylvain Bauza
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Incredibly odd mysql permission error

OK  Someone on the IRC channel got me closer, but we have no idea why this 
would happen:

this works: root@test1:~# nova-manage --config-file=/etc/nova/nova.conf 
service list

Why would I have to specify the config file though?  It is in the standard 
place.

Thanks,
Sam



On Mon, Mar 11, 2013 at 2:01 PM, Samuel Winchenbach 
swinc...@gmail.commailto:swinc...@gmail.com wrote:
For completeness here the routing table, and ip listing for both test1 and 
test2.   Doubt this will help much:  http://paste2.org/p/3117125

On Mon, Mar 11, 2013 at 1:52 PM, Samuel Winchenbach 
swinc...@gmail.commailto:swinc...@gmail.com wrote:
#1 - No change
#2 - All of grants are in the ip/mask form such as: 
'nova'@'10.21.0.0/255.255.0.0http://10.21.0.0/255.255.0.0'  I have also tried 
adding 'nova'@'test1' and 'nova'@'10.21.0.1'.  No change.
#3 - I changed the SQL connection string over to IP instead of hostname.  No 
change.  I didn't restart nova-api because it isn't running.   If I understand 
correctly nova-manage communicated directly with the db, bypassing nova-api.   
This would appear true seeing nova-manage service list works correctly on 
test2.


:(

Thanks for the help!
Sam

On Mon, Mar 11, 2013 at 12:24 PM, Sylvain Bauza 
sylvain.ba...@digimind.commailto:sylvain.ba...@digimind.com wrote:
When looking at MySQL 5.1 refman 
(http://dev.mysql.com/doc/refman/5.1/en/access-denied.html ), I would suggest 
to follow the procedure :
 1. 'mysqladmin flush-hosts'
 2. replace DNS entries in mysql.user table by IP addresses instead
 3. modify /etc/nova/nova.conf with IP address of HA Mysql instead (and restart 
nova-api !)

I wouldn't bet on it, but I would say this is due to some name resolution which 
is incorrect.

-Sylvain


Le 11/03/2013 17:00, Sylvain Bauza a écrit :
Ok, lemme try to summarize.
You do have a DRBD setup for MySQL bound to a VIP 10.21.1.1 thanks to Pacemaker.
This setup is relying on two hosts, test1 (10.21.0.1) and test2 (10.21.0.2).
Your nova.conf is pointing to mysql://10.21.1.1http://10.21.1.1 which is the 
VIP.

Are you sure your my.cnf is actually the same in between both DRBD nodes ? (I 
would recommend to symlink it to a physical file hosted on the DRBD device).

One thing is hurting me : you told me that nova is also pacemake'd. If so, why 
can I still see my_ip=10.21.0.2 (test2) ? It should be pointing to nova-ha 
(assuming 10.21.2.4 as per /etc/hosts).

Also, as per my understanding of Pacemaker, DRBD partition is setup by default 
on test2, correct ?


Sorry, as per my first reading, I can't see anything obvious. That said, I'm 
not sure this is a Nova bug, as the tcpdump trace is seeing a correct MySQL 
connection attempt. But maybe I'm wrong ?

Anyway, are you sure you only have *one* MySQL engine running (either on test1 
or test2) and nova-manage trying to access this right one ?

Perms look good to me. As it a test setup, you could try to unleash the grants 
by deleting them and allowing nova@'%' to see if it's a basic dns mapping issue.

-Sylvain



Le 11/03/2013 16:09, Samuel Winchenbach a écrit :
I
enabled general_log in /etc/mysql/my.cnf  Here are the results of connecting 
from test1, test2 and using the client:
http://paste2.org/p/3115525
I purposefully used the real password in case there is a problem with it.
 I changed before submitting post.

here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an attempted 
nova-manage service list from test1:
https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

I looked at it with wireshark and couldn't see anything that jumped out at me 
as incorrect.  I have not yet tried to recreate the salted password.


Here is my pacemaker configuration for mysql.  I stripped out openstack 
services, rabbitmq and others for clarity.  All resources are currently 
disabled (other than MySQL):
http://paste2.org/p/3115685


Please don't yell at me for having STONITH disabled :P  This is a testing 
cluster and I am working on getting routed to the IPMI interface.

/etc/hosts:
http://paste2.org/p/3115713
/etc/nova/nova.conf:
http://paste2.org/p/3115739


If there is anything else I can provide you, please let me know!  I have pulled 
out most of my hair at this point!

Sam



On Mon, Mar 11, 2013 at 10:11 AM, Sylvain Bauza 
sylvain.ba...@digimind.commailto:sylvain.ba...@digimind.com wrote:
So as to reproduce the nova-manage SQL command, I would recommand to tcpdump -A 
port 3306 on the host and get

Re: [Openstack] Incredibly odd mysql permission error

ugh...  I had an example file called nova.conf in /root

Apparently nova-manage looks for that file first.  Case closed.  I wish I
could get the last week back.

Sam


On Mon, Mar 11, 2013 at 2:37 PM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:

  I ran into a similar problem with the Grizzly-3 Keystone release. I had
 to specify keystone.conf as the config-file with keystone-manage/ db_sync
 command otherwise it would not use the mysql statement in the keystone.conf
 file.

 ** **

 Mark

 ** **

 *From:* openstack-bounces+mark.m.miller=hp@lists.launchpad.net[mailto:
 openstack-bounces+mark.m.miller=hp@lists.launchpad.net] *On Behalf Of
 *Samuel Winchenbach
 *Sent:* Monday, March 11, 2013 11:18 AM
 *To:* Sylvain Bauza
 *Cc:* openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] Incredibly odd mysql permission error

 ** **

 OK  Someone on the IRC channel got me closer, but we have no idea why
 this would happen:

 ** **

 this works: root@test1:~# nova-manage --config-file=/etc/nova/nova.conf
 service list

 ** **

 Why would I have to specify the config file though?  It is in the standard
 place.

 ** **

 Thanks,

 Sam

 ** **

 ** **

 ** **

 On Mon, Mar 11, 2013 at 2:01 PM, Samuel Winchenbach swinc...@gmail.com
 wrote:

 For completeness here the routing table, and ip listing for both test1 and
 test2.   Doubt this will help much:  http://paste2.org/p/3117125

 ** **

 On Mon, Mar 11, 2013 at 1:52 PM, Samuel Winchenbach swinc...@gmail.com
 wrote:

 #1 - No change

 #2 - All of grants are in the ip/mask form such as: 'nova'@'
 10.21.0.0/255.255.0.0'  I have also tried adding 'nova'@'test1' and
 'nova'@'10.21.0.1'.  No change.

 #3 - I changed the SQL connection string over to IP instead of hostname.
  No change.  I didn't restart nova-api because it isn't running.   If I
 understand correctly nova-manage communicated directly with the db,
 bypassing nova-api.   This would appear true seeing nova-manage service
 list works correctly on test2.

 ** **

 ** **

 :(

 ** **

 Thanks for the help!

 Sam

 ** **

 On Mon, Mar 11, 2013 at 12:24 PM, Sylvain Bauza 
 sylvain.ba...@digimind.com wrote:

 When looking at MySQL 5.1 refman (
 http://dev.mysql.com/doc/refman/5.1/en/access-denied.html ), I would
 suggest to follow the procedure :
  1. 'mysqladmin flush-hosts'
  2. replace DNS entries in mysql.user table by IP addresses instead
  3. modify /etc/nova/nova.conf with IP address of HA Mysql instead (and
 restart nova-api !)

 I wouldn't bet on it, but I would say this is due to some name resolution
 which is incorrect.

 -Sylvain


 Le 11/03/2013 17:00, Sylvain Bauza a écrit :

  Ok, lemme try to summarize.
 You do have a DRBD setup for MySQL bound to a VIP 10.21.1.1 thanks to
 Pacemaker.
 This setup is relying on two hosts, test1 (10.21.0.1) and test2
 (10.21.0.2).
 Your nova.conf is pointing to mysql://10.21.1.1 which is the VIP.

 Are you sure your my.cnf is actually the same in between both DRBD nodes ?
 (I would recommend to symlink it to a physical file hosted on the DRBD
 device).

 One thing is hurting me : you told me that nova is also pacemake'd. If so,
 why can I still see my_ip=10.21.0.2 (test2) ? It should be pointing to
 nova-ha (assuming 10.21.2.4 as per /etc/hosts).

 Also, as per my understanding of Pacemaker, DRBD partition is setup by
 default on test2, correct ?


 Sorry, as per my first reading, I can't see anything obvious. That said,
 I'm not sure this is a Nova bug, as the tcpdump trace is seeing a correct
 MySQL connection attempt. But maybe I'm wrong ?

 Anyway, are you sure you only have *one* MySQL engine running (either on
 test1 or test2) and nova-manage trying to access this right one ?

 Perms look good to me. As it a test setup, you could try to unleash the
 grants by deleting them and allowing nova@'%' to see if it's a basic dns
 mapping issue.

 -Sylvain



 Le 11/03/2013 16:09, Samuel Winchenbach a écrit :

  I 

 enabled general_log in /etc/mysql/my.cnf  Here are the results of
 connecting from test1, test2 and using the client:

 http://paste2.org/p/3115525

 I purposefully used the real password in case there is a problem with it.
 

  I changed before submitting post.

 ** **

 here is a raw packet TCP dump (tcpdump -w rawdump port 3306) of an
 attempted nova-manage service list from test1:  

 https://www.dropbox.com/s/u4cjzxv6w6bwwe6/rawdump

  

 I looked at it with wireshark and couldn't see anything that jumped out at
 me as incorrect.  I have not yet tried to recreate the salted password.***
 *

 ** **

 ** **

 Here is my pacemaker configuration for mysql.  I stripped out openstack
 services, rabbitmq and others for clarity.  All resources are currently
 disabled (other than MySQL): 

 http://paste2.org/p/3115685 

  

 ** **

 Please don't yell at me for having STONITH disabled :P  This is

Re: [Openstack] Network node needed?

2013-03-11 Thread JR

Great, thanks Logan.

Also, for anyone on the list that aren't aware of it; last night I
discovered the Openstack Operations Guide at:
http://docs.openstack.org/ops/

It contains lots of answers to questions that I'd not found anywhere
else.  The only downside is that it doesn't cover quantum.

John

On 3/11/2013 8:55 AM, Logan McNaughton wrote:
 No it's not needed, you just run quantum-server, the L3 agent, the DHCP
 agent, and the plugin agent (probably open vSwitch) all on the
 controller. You'll just need to plan out which NICs you'll use for what
 purpose and setup accordingly.
 
 As a side note, you'll also need to run the plugin agent on all your
 compute nodes
 
 On Mar 9, 2013 4:57 PM, JR botem...@gmail.com
 mailto:botem...@gmail.com wrote:
 
 Greetings all,
 
 Next week I'll be putting up a new folsom cluster (perhaps using these
 instructions:
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide).
 Presently, I don't have a box to devote to being a network node.  Is it
 necessary?  The clouds I've put up so far have just had controller and
 compute nodes? Is the network node required by quantum?
 
 Thanks much,
 JR
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 

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

[Openstack] Agent out of sync with plugin!

2013-03-11 Thread Greg Chavez

So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom Install
Guide:

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

After following the steps to instantiate the network node, I'm left with 3
new but downed OVS bridges, and three error-filled logs for ovs-plugin,
dhcp-agent, and l3-agent.  I rectify it with this:

http://pastebin.com/L43d9q8a

When I restart the networking and then restart the plugin and agents,
everything seems to work, but I'm getting this strange INFO message in
/var/log/quantum/openvswitch-agent.log:

2013-03-11 17:48:02 INFO
[quantum.plugins.openvswitch.agent.ovs_quantum_agent] Agent out of sync
with plugin!

I traced it to this .py file:

https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py

Now I realize that this is and INFO message, not an error.  But I would
still like to know what this means.  Thanks!

-- 
\*..+.-
--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] Configuring More-than-One Cinder Node

2013-03-11 Thread Craig E. Ward

I have an installation that wants to deploy two or more cinder nodes within an 
OpenStack (Folsom) cluster. All of the hits I find on Google for configuring 
cinder only describe how to configure the software for a single node. Is it 
even possible to have more than one node running the cinder services in a cluster?


The setup I have has one of the cinder nodes identified as the cinder node to 
the compute and other node types. A second node was installed and the cinder 
services started.


On the nova controller node, however, while a new volume could be created that 
was listed in the MySQL database as on the second node, all attempts to attach 
that volume to an instance silently failed. The nova volume-attach command 
would come back with an id and mapping of instance to volume, but the very next 
nova volume-list command continued to show the volume in question as available.


If the second cinder node had the cinder-volume service running, volumes on 
that node could be deleted. If cinder-volume was not running, the delete 
would go on forever.


Everything works as expected with only the cinder node configured in nova.conf 
running, i.e. as a single cinder node installation. Volumes can be created, 
attached, used, detached, and deleted.


Are there some extra parameters that should be set in either nova.conf or 
cinder.conf to indicate that the cinder services are available on more-than-one 
node? Or is what we're trying to do something unexpected and not supported?


Thanks,

Craig

--
Craig E. Ward
USC Information Sciences Institute
cw...@isi.edu


___
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] Configuring More-than-One Cinder Node

2013-03-11 Thread Debashis Kundu (dkundu)

O

- Original Message -
From: Craig E. Ward [mailto:cw...@isi.edu]
Sent: Monday, March 11, 2013 05:23 PM
To: openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject: [Openstack] Configuring More-than-One Cinder Node

I have an installation that wants to deploy two or more cinder nodes within an 
OpenStack (Folsom) cluster. All of the hits I find on Google for configuring 
cinder only describe how to configure the software for a single node. Is it 
even possible to have more than one node running the cinder services in a 
cluster?

The setup I have has one of the cinder nodes identified as the cinder node to 
the compute and other node types. A second node was installed and the cinder 
services started.

On the nova controller node, however, while a new volume could be created that 
was listed in the MySQL database as on the second node, all attempts to attach 
that volume to an instance silently failed. The nova volume-attach command 
would come back with an id and mapping of instance to volume, but the very next 
nova volume-list command continued to show the volume in question as 
available.

If the second cinder node had the cinder-volume service running, volumes on 
that node could be deleted. If cinder-volume was not running, the delete 
would go on forever.

Everything works as expected with only the cinder node configured in nova.conf 
running, i.e. as a single cinder node installation. Volumes can be created, 
attached, used, detached, and deleted.

Are there some extra parameters that should be set in either nova.conf or 
cinder.conf to indicate that the cinder services are available on more-than-one 
node? Or is what we're trying to do something unexpected and not supported?

Thanks,

Craig

-- 
Craig E. Ward
USC Information Sciences Institute
cw...@isi.edu

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

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

Re: [Openstack] Cinder volume as root in Grizzly?

Oh great! I didn't realize you can create a cinder volume from an image. So
can I pass cinder a QCOW2 image, then boot from that volume?
On Mar 11, 2013 7:16 PM, Vishvananda Ishaya vishvana...@gmail.com wrote:

 Not exactly, although you can do something similar in both folsom and
 grizzly. If you have a volume snapshot you can pass it in the
 block_device_mapping when you boot an instance and nova will automatically
 create a volume from the snapshot and boot from it. If you also set
 delete_on_terminate true you have roughly the same experience as an EBS
 backed instance.

 nova boot --block-device-mapping vda=snap-id:snap:size:True


 You cannot currently pass an image id and get a volume backed instance. It
 requires two steps

 cinder create --image-id=image-id
 nova boot --block-device-mapping vda=vol-id

 Vish



 On Mar 11, 2013, at 6:24 AM, Logan McNaughton lo...@bacoosta.com wrote:

 Will Grizzly support specifying an empty Cinder volume as an instance's
 root device?

 Right now you need to setup the volume before hand and you can boot from
 volume. But will there be support similar to AWS EBS-backed instances in
 Grizzly?
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



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

Re: [Openstack] Configuring More-than-One Cinder Node

You'll want to look here:
http://docs.openstack.org/trunk/openstack-ha/content/s-cinder-api.html

You'll need to basically create a virtual IP and load balance between the
nodes running cinder-api and cinder-scheduler. If you want multiple nodes
running cinder-volume, you can add them regularly, like you would with a
nova-compute node.
On Mar 11, 2013 6:51 PM, Debashis Kundu (dkundu) dku...@cisco.com wrote:

 O

 - Original Message -
 From: Craig E. Ward [mailto:cw...@isi.edu]
 Sent: Monday, March 11, 2013 05:23 PM
 To: openstack@lists.launchpad.net openstack@lists.launchpad.net
 Subject: [Openstack] Configuring More-than-One Cinder Node

 I have an installation that wants to deploy two or more cinder nodes
 within an
 OpenStack (Folsom) cluster. All of the hits I find on Google for
 configuring
 cinder only describe how to configure the software for a single node. Is it
 even possible to have more than one node running the cinder services in a
 cluster?

 The setup I have has one of the cinder nodes identified as the cinder
 node to
 the compute and other node types. A second node was installed and the
 cinder
 services started.

 On the nova controller node, however, while a new volume could be created
 that
 was listed in the MySQL database as on the second node, all attempts to
 attach
 that volume to an instance silently failed. The nova volume-attach
 command
 would come back with an id and mapping of instance to volume, but the very
 next
 nova volume-list command continued to show the volume in question as
 available.

 If the second cinder node had the cinder-volume service running, volumes on
 that node could be deleted. If cinder-volume was not running, the delete
 would go on forever.

 Everything works as expected with only the cinder node configured in
 nova.conf
 running, i.e. as a single cinder node installation. Volumes can be created,
 attached, used, detached, and deleted.

 Are there some extra parameters that should be set in either nova.conf or
 cinder.conf to indicate that the cinder services are available on
 more-than-one
 node? Or is what we're trying to do something unexpected and not supported?

 Thanks,

 Craig

 --
 Craig E. Ward
 USC Information Sciences Institute
 cw...@isi.edu


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

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

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

Re: [Openstack] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Masayuki Igawa

Hi,

On Tue, Mar 12, 2013 at 1:14 AM, Girija Sharan
girijasharansi...@gmail.comwrote:

 Hi All,

 I am trying to do Integration testing of Openstack environmment (Folsom)
 using Tempest.

 On controller node I am having my Tempest root directory and I have also
 installed Coverage, Tissue
 and Openstack-nose as it was mentioned in the setup.cfg file.

 1. Do I have to use this release
 https://github.com/openstack/tempest/tree/stable/folsom ?


I think Yes, essex or master is not suitable for your environmment(Folsom).


2. I am not getting how to configure tempest.conf for Folsom set up. For
 Essex we were having localrc file but here in Folsom we are not having any
 such thing. Is there any way to know what values to pass to respective
 fields in tempest.conf ?


tempest.conf.sample has the explanation of the respective fields.


https://github.com/openstack/tempest/blob/stable/folsom/etc/tempest.conf.sample

Is this not good enough?

By the way, do you use devstack?(I think localrc is devstack's file.) If
so, localrc is present in your devstack's directory, and tempest.conf is
set up in your $TEMPEST_INSTALL_DIR/etc/tempest.conf automatically.


 Any help will be highly appreciated.


 Thanks and Regards,
 Girija Sharan Singh

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



Regards,
-- 
Masayuki Igawa
___
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] Agent out of sync with plugin!

It looks like it's a time sync error. Are you using NTP on all your nodes?
On Mar 11, 2013 6:14 PM, Greg Chavez greg.cha...@gmail.com wrote:


 So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom Install
 Guide:


 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst

 After following the steps to instantiate the network node, I'm left with 3
 new but downed OVS bridges, and three error-filled logs for ovs-plugin,
 dhcp-agent, and l3-agent.  I rectify it with this:

 http://pastebin.com/L43d9q8a

 When I restart the networking and then restart the plugin and agents,
 everything seems to work, but I'm getting this strange INFO message in
 /var/log/quantum/openvswitch-agent.log:

 2013-03-11 17:48:02 INFO
 [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Agent out of sync
 with plugin!

 I traced it to this .py file:


 https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py

 Now I realize that this is and INFO message, not an error.  But I would
 still like to know what this means.  Thanks!

 --
 \*..+.-
 --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


___
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] the ip_forward is enable when using vlan + multi_host on computer node

2013-03-11 Thread Lei Zhang

Hi all,

I am testing the nova-network + vlan + multi_host. But I found that the
ip_forward is enable automatically when launch new instances. You can check
the code
https://github.com/openstack/nova/blob/master/nova/network/linux_net.py#L770

I found there is some issue seriously when the ip_forward=1 on compute
node. Here my testing process

Controller:

[root@openstack-controller conf.d]# ip a
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
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: p3p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:b1:1c:0d:87:79 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.10/24 brd 192.168.3.255 scope global p3p1
inet6 fe80::92b1:1cff:fe0d:8779/64 scope link
   valid_lft forever preferred_lft forever
3: em1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000
link/ether 90:b1:1c:0d:87:7a brd ff:ff:ff:ff:ff:ff
inet 172.16.0.10/24 brd 172.16.0.255 scope global em1
inet6 fe80::92b1:1cff:fe0d:877a/64 scope link
   valid_lft forever preferred_lft forever

Computer Node:

[root@openstack-node2 vlan]# ip a
2: em1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000

link/ether 90:b1:1c:0d:73:ea brd ff:ff:ff:ff:ff:ff
inet 172.16.0.12/24 brd 172.16.0.255 scope global em1
inet6 fe80::92b1:1cff:fe0d:73ea/64 scope link
   valid_lft forever preferred_lft forever
4: p3p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:10:18:f7:4a:34 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.12/24 brd 192.168.3.255 scope global p3p1
inet 192.168.3.33/32 scope global p3p1
inet6 fe80::210:18ff:fef7:4a34/64 scope link
   valid_lft forever preferred_lft forever
9: vlan102@em1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
noqueue state UP
link/ether fa:16:3e:54:ea:11 brd ff:ff:ff:ff:ff:ff
inet6 fe80::f816:3eff:fe54:ea11/64 scope link
   valid_lft forever preferred_lft forever
10: br102: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
state UNKNOWN
link/ether fa:16:3e:54:ea:11 brd ff:ff:ff:ff:ff:ff
inet 10.0.102.4/24 brd 10.0.102.255 scope global br102
inet6 fe80::2816:24ff:feb5:5770/64 scope link
   valid_lft forever preferred_lft forever
11: vlan103@em1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
noqueue state UP
link/ether fa:16:3e:3a:a0:20 brd ff:ff:ff:ff:ff:ff
inet6 fe80::f816:3eff:fe3a:a020/64 scope link
   valid_lft forever preferred_lft forever
12: br103: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
state UNKNOWN
link/ether fa:16:3e:3a:a0:20 brd ff:ff:ff:ff:ff:ff
inet 10.0.103.4/24 brd 10.0.103.255 scope global br103
inet6 fe80::480c:f2ff:fe9b:a600/64 scope link
   valid_lft forever preferred_lft forever
13: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:16:3e:0c:65:73 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe0c:6573/64 scope link
   valid_lft forever preferred_lft forever
15: vnet1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:16:3e:7f:a2:d5 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe7f:a2d5/64 scope link
   valid_lft forever preferred_lft forever
16: vnet2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:16:3e:31:8f:7c brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe31:8f7c/64 scope link
   valid_lft forever preferred_lft forever
17: vnet3: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:16:3e:63:8c:e2 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe63:8ce2/64 scope link
   valid_lft forever preferred_lft forever
[root@openstack-node2 vlan]# brctl show
bridge namebridge idSTP enabledinterfaces
br1028000.fa163e54ea11novlan102
vnet0
vnet1
vnet2
br1038000.fa163e3aa020novlan103
vnet3
virbr08000.525400aaa1b5yesvirbr0-nic

if the ip_forward=1, then vm1(vnet1) can ping vm2(vnet4) and controller can
ping vm1(vnet1) and vm2(vnet4). this should be wrong.

Any body meet this error? and how to fix this except for changing the code.
-- 
Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l
___
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] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Girija Sharan

Hi Masayuki,

Thanks a lot for your early response.

I am using Openstack Folsom and not Devstack.

I am not getting how to integrate Tempest for Folsom. As you mentioned
there is tempest.conf.sample file but in that there is a field which
requires path to nova source directory (source_dir = /opt/stack/nova). What
path I have to give for Folsom setup?

Is this
https://github.com/openstack/tempest/blob/stable/folsom/etc/tempest.conf.sample
file
for Folsom ?

It will be very helpful for me if you can provide little more explanation
of the respective fields or if you can suggest any document for that.


Thanks and Regards,
Girija Sharan Singh



On Tue, Mar 12, 2013 at 7:05 AM, Masayuki Igawa masayuki.ig...@gmail.comwrote:

 Hi,

 On Tue, Mar 12, 2013 at 1:14 AM, Girija Sharan 
 girijasharansi...@gmail.com wrote:

 Hi All,

 I am trying to do Integration testing of Openstack environmment (Folsom)
 using Tempest.

 On controller node I am having my Tempest root directory and I have also
 installed Coverage, Tissue
 and Openstack-nose as it was mentioned in the setup.cfg file.

 1. Do I have to use this release
 https://github.com/openstack/tempest/tree/stable/folsom ?


 I think Yes, essex or master is not suitable for your environmment(Folsom).


 2. I am not getting how to configure tempest.conf for Folsom set up. For
 Essex we were having localrc file but here in Folsom we are not having any
 such thing. Is there any way to know what values to pass to respective
 fields in tempest.conf ?


 tempest.conf.sample has the explanation of the respective fields.


 https://github.com/openstack/tempest/blob/stable/folsom/etc/tempest.conf.sample

 Is this not good enough?

 By the way, do you use devstack?(I think localrc is devstack's file.) If
 so, localrc is present in your devstack's directory, and tempest.conf is
 set up in your $TEMPEST_INSTALL_DIR/etc/tempest.conf automatically.


 Any help will be highly appreciated.


 Thanks and Regards,
 Girija Sharan Singh

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



 Regards,
 --
 Masayuki Igawa


___
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 Failure: raring_grizzly_nova_trunk #867

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/867/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:09:34 -0400Build duration:35 secBuild cause:Started by user Adam GandelmanBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 28 lines...]DEBUG:root:Checking env for parameter: PARENT_BUILD_TAGDEBUG:root:Checking env for parameter: OPENSTACK_BRANCHDEBUG:root:Found: trunkDEBUG:root:Checking env for parameter: OPENSTACK_COMPONENTDEBUG:root:Found: novaDEBUG:root:Checking env for parameter: UBUNTU_RELEASEDEBUG:root:Found: raringDEBUG:root:Checking env for parameter: OPENSTACK_RELEASEDEBUG:root:Found: grizzlyDEBUG:root:Checking env for extra parameter: GIT_COMMITDEBUG:root:Checking env for extra parameter: AUTHORDEBUG:root:Checking env for extra parameter: BUILD_URLDEBUG:root:Checking env for extra parameter: DEPLOYMENTdebugTraceback (most recent call last):  File "/usr/bin/test-catalog", line 99, in pipeline.archive_job(build_info)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 229, in archive_jobtest_job = manager.create_test_job(job_dict)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 34, in create_test_jobtest_job.save(self.session)  File "/usr/lib/python2.7/dist-packages/test_catalog/db/models.py", line 17, in savesession.flush()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1583, in flushself._flush(objects)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1654, in _flushflush_context.execute()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 331, in executerec.execute(self)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 475, in executeuow  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 64, in save_objtable, insert)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 558, in _emit_insert_statementsexecute(statement, params)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1449, in executeparams)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1584, in _execute_clauseelementcompiled_sql, distilled_params  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1698, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1691, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 331, in do_executecursor.execute(statement, parameters)sqlalchemy.exc.OperationalError: (OperationalError) attempt to write a readonly database u'INSERT INTO test_job (build_tag, parent_build_tag, pipeline_id, status, extra, openstack_component, openstack_release, openstack_branch, ubuntu_release) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)' ('jenkins-raring_grizzly_nova_trunk-867', None, '5417b1b2-8a12-11e2-ac17-dbf4bd4af4f9', None, '{"build_url": "http://10.189.74.7:8080/job/raring_grizzly_nova_trunk/867/", "git_commit": "8c96d09ba3c12939d61e980474b75f9173ce6a63"}', 'nova', 'grizzly', 'trunk', 'raring')Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/868/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:10:36 -0400Build duration:34 secBuild cause:Started by user Adam GandelmanBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 28 lines...]DEBUG:root:Checking env for parameter: PARENT_BUILD_TAGDEBUG:root:Checking env for parameter: OPENSTACK_BRANCHDEBUG:root:Found: trunkDEBUG:root:Checking env for parameter: OPENSTACK_COMPONENTDEBUG:root:Found: novaDEBUG:root:Checking env for parameter: UBUNTU_RELEASEDEBUG:root:Found: raringDEBUG:root:Checking env for parameter: OPENSTACK_RELEASEDEBUG:root:Found: grizzlyDEBUG:root:Checking env for extra parameter: GIT_COMMITDEBUG:root:Checking env for extra parameter: AUTHORDEBUG:root:Checking env for extra parameter: BUILD_URLDEBUG:root:Checking env for extra parameter: DEPLOYMENTdebugTraceback (most recent call last):  File "/usr/bin/test-catalog", line 99, in pipeline.archive_job(build_info)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 229, in archive_jobtest_job = manager.create_test_job(job_dict)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 34, in create_test_jobtest_job.save(self.session)  File "/usr/lib/python2.7/dist-packages/test_catalog/db/models.py", line 17, in savesession.flush()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1583, in flushself._flush(objects)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1654, in _flushflush_context.execute()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 331, in executerec.execute(self)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 475, in executeuow  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 64, in save_objtable, insert)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 558, in _emit_insert_statementsexecute(statement, params)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1449, in executeparams)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1584, in _execute_clauseelementcompiled_sql, distilled_params  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1698, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1691, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 331, in do_executecursor.execute(statement, parameters)sqlalchemy.exc.OperationalError: (OperationalError) attempt to write a readonly database u'INSERT INTO test_job (build_tag, parent_build_tag, pipeline_id, status, extra, openstack_component, openstack_release, openstack_branch, ubuntu_release) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)' ('jenkins-raring_grizzly_nova_trunk-868', None, '7891d0f4-8a12-11e2-bee3-e775be5db875', None, '{"build_url": "http://10.189.74.7:8080/job/raring_grizzly_nova_trunk/868/", "git_commit": "8c96d09ba3c12939d61e980474b75f9173ce6a63"}', 'nova', 'grizzly', 'trunk', 'raring')Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/869/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:11:45 -0400Build duration:33 secBuild cause:Started by user Adam GandelmanBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesConsole Output[...truncated 28 lines...]DEBUG:root:Checking env for parameter: PARENT_BUILD_TAGDEBUG:root:Checking env for parameter: OPENSTACK_BRANCHDEBUG:root:Found: trunkDEBUG:root:Checking env for parameter: OPENSTACK_COMPONENTDEBUG:root:Found: novaDEBUG:root:Checking env for parameter: UBUNTU_RELEASEDEBUG:root:Found: raringDEBUG:root:Checking env for parameter: OPENSTACK_RELEASEDEBUG:root:Found: grizzlyDEBUG:root:Checking env for extra parameter: GIT_COMMITDEBUG:root:Checking env for extra parameter: AUTHORDEBUG:root:Checking env for extra parameter: BUILD_URLDEBUG:root:Checking env for extra parameter: DEPLOYMENTdebugTraceback (most recent call last):  File "/usr/bin/test-catalog", line 99, in pipeline.archive_job(build_info)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 229, in archive_jobtest_job = manager.create_test_job(job_dict)  File "/usr/lib/python2.7/dist-packages/test_catalog/pipeline/__init__.py", line 34, in create_test_jobtest_job.save(self.session)  File "/usr/lib/python2.7/dist-packages/test_catalog/db/models.py", line 17, in savesession.flush()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1583, in flushself._flush(objects)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1654, in _flushflush_context.execute()  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 331, in executerec.execute(self)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 475, in executeuow  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 64, in save_objtable, insert)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 558, in _emit_insert_statementsexecute(statement, params)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1449, in executeparams)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1584, in _execute_clauseelementcompiled_sql, distilled_params  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1698, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1691, in _execute_contextcontext)  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 331, in do_executecursor.execute(statement, parameters)sqlalchemy.exc.OperationalError: (OperationalError) attempt to write a readonly database u'INSERT INTO test_job (build_tag, parent_build_tag, pipeline_id, status, extra, openstack_component, openstack_release, openstack_branch, ubuntu_release) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)' ('jenkins-raring_grizzly_nova_trunk-869', None, 'a0a78c32-8a12-11e2-ae19-23f5127e9e04', None, '{"build_url": "http://10.189.74.7:8080/job/raring_grizzly_nova_trunk/869/", "git_commit": "8c96d09ba3c12939d61e980474b75f9173ce6a63"}', 'nova', 'grizzly', 'trunk', 'raring')Build 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: raring_grizzly_python-quantumclient_trunk #52

Title: raring_grizzly_python-quantumclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-quantumclient_trunk/52/Project:raring_grizzly_python-quantumclient_trunkDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:66 msBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_python-quantumclient_trunkFATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closedhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.call(Request.java:174)	at hudson.remoting.Channel.call(Channel.java:663)	at hudson.FilePath.act(FilePath.java:831)	at hudson.FilePath.act(FilePath.java:824)	at hudson.FilePath.mkdirs(FilePath.java:890)	at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)	at hudson.model.Run.execute(Run.java:1502)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.abort(Request.java:299)	at hudson.remoting.Channel.terminate(Channel.java:719)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Socket closed	at java.net.SocketInputStream.socketRead0(Native Method)	at java.net.SocketInputStream.read(SocketInputStream.java:150)	at java.net.SocketInputStream.read(SocketInputStream.java:121)	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2266)	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2559)	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2569)	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)	at hudson.remoting.Command.readFrom(Command.java:90)	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)-- 
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_python-cinderclient_trunk #41

Title: precise_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-cinderclient_trunk/41/Project:precise_grizzly_python-cinderclient_trunkDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:69 msBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_python-cinderclient_trunkFATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closedhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.call(Request.java:174)	at hudson.remoting.Channel.call(Channel.java:663)	at hudson.FilePath.act(FilePath.java:831)	at hudson.FilePath.act(FilePath.java:824)	at hudson.FilePath.mkdirs(FilePath.java:890)	at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)	at hudson.model.Run.execute(Run.java:1502)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.abort(Request.java:299)	at hudson.remoting.Channel.terminate(Channel.java:719)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Socket closed	at java.net.SocketInputStream.socketRead0(Native Method)	at java.net.SocketInputStream.read(SocketInputStream.java:150)	at java.net.SocketInputStream.read(SocketInputStream.java:121)	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2266)	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2559)	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2569)	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)	at hudson.remoting.Command.readFrom(Command.java:90)	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)-- 
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_essex_horizon_stable #34

Title: precise_essex_horizon_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/34/Project:precise_essex_horizon_stableDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:66 msBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_essex_horizon_stableFATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closedhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.call(Request.java:174)	at hudson.remoting.Channel.call(Channel.java:663)	at hudson.FilePath.act(FilePath.java:831)	at hudson.FilePath.act(FilePath.java:824)	at hudson.FilePath.mkdirs(FilePath.java:890)	at hudson.model.AbstractProject.checkout(AbstractProject.java:1254)	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)	at hudson.model.Run.execute(Run.java:1502)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed	at hudson.remoting.Request.abort(Request.java:299)	at hudson.remoting.Channel.terminate(Channel.java:719)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Socket closed	at java.net.SocketInputStream.socketRead0(Native Method)	at java.net.SocketInputStream.read(SocketInputStream.java:150)	at java.net.SocketInputStream.read(SocketInputStream.java:121)	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2266)	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2559)	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2569)	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)	at hudson.remoting.Command.readFrom(Command.java:90)	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_python-cinderclient_trunk #42

Title: precise_grizzly_python-cinderclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-cinderclient_trunk/42/Project:precise_grizzly_python-cinderclient_trunkDate of build:Mon, 11 Mar 2013 03:39:49 -0400Build duration:2 min 17 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 2122 lines...]Finished at 20130311-0341Build needed 00:00:45, 2224k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_source.changes']gpg: Signature made Mon Mar 11 03:41:14 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Mar 11 03:41:13 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmplwFnyY/python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmplwFnyY/python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1.dsc: done.  Uploading python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise.orig.tar.gz: done.  Uploading python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1.debian.tar.gz: done.  Uploading python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-cinderclient/python-cinderclient_1.0.2.26.g458ff24+git201302201301~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-cinderclient/precise-grizzly']Pushed up to revision 22.INFO:root:Storing current commit for next build: 458ff24513e39e9ebf669ea1155fc2d1c919f042INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-cinderclient/grizzly /tmp/tmplwFnyY/python-cinderclientmk-build-deps -i -r -t apt-get -y /tmp/tmplwFnyY/python-cinderclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-cinderclient/precise-grizzly --forcedch -b -D precise --newversion 1:1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-cinderclient_1.0.2.26.g458ff24+git201303110339~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-cinderclient/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_python-quantumclient_trunk #53

Title: raring_grizzly_python-quantumclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-quantumclient_trunk/53/Project:raring_grizzly_python-quantumclient_trunkDate of build:Mon, 11 Mar 2013 03:39:46 -0400Build duration:3 min 0 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 2319 lines...]Finished at 20130311-0342Build needed 00:00:42, 2908k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_source.changes']gpg: Signature made Mon Mar 11 03:41:55 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Mar 11 03:41:55 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmp5Rhjii/python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp5Rhjii/python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1.dsc: done.  Uploading python-quantumclient_2.2.0+git201303110339~raring.orig.tar.gz: done.  Uploading python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1.debian.tar.gz: done.  Uploading python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'raring-grizzly', 'python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-quantumclient/python-quantumclient_2.2.0+git201303072131~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-quantumclient/raring-grizzly']Pushed up to revision 23.INFO:root:Storing current commit for next build: f96219d67a56976e69a4b22d7efe7229d5e20345INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/grizzly /tmp/tmp5Rhjii/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmp5Rhjii/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-quantumclient/raring-grizzly --forcedch -b -D raring --newversion 2:2.2.0+git201303110339~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly python-quantumclient_2.2.0+git201303110339~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-quantumclient/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] Jenkins build is back to normal : cloud-archive_folsom_version-drift #10370

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10370/


-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_horizon_stable #35

Title: precise_essex_horizon_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/35/Project:precise_essex_horizon_stableDate of build:Mon, 11 Mar 2013 04:01:24 -0400Build duration:3 min 57 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 5272 lines...]Finished at 20130311-0405Build needed 00:01:32, 21328k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/essex-stable-testinggpg: Signature made Mon Mar 11 04:03:34 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Mar 11 04:03:34 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmpD8O8JY/horizon_2012.1.4+git201303110401~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpD8O8JY/horizon_2012.1.4+git201303110401~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading horizon_2012.1.4+git201303110401~precise-0ubuntu1.dsc: done.  Uploading horizon_2012.1.4+git201303110401~precise.orig.tar.gz: done.  Uploading horizon_2012.1.4+git201303110401~precise-0ubuntu1.debian.tar.gz: done.  Uploading horizon_2012.1.4+git201303110401~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptExporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/h/horizon/openstack-dashboard-ubuntu-theme_2012.1.4+git201212170840~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/openstack-dashboard_2012.1.4+git201212170840~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-horizon_2012.1.4+git201212170840~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-openstack_2012.1.4+git201212170840~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 108.INFO:root:Storing current commit for next build: 5ce394226a5333285d89cc8163bb4039a0c0e773INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/precise-essex-proposed /tmp/tmpD8O8JY/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpD8O8JY/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/horizon/precise-essex-stable --forcedch -b -D precise --newversion 2012.1.4+git201303110401~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC horizon_2012.1.4+git201303110401~precise-0ubuntu1_source.changessbuild -d precise-essex -n -A horizon_2012.1.4+git201303110401~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/essex-stable-testing horizon_2012.1.4+git201303110401~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-essex horizon_2012.1.4+git201303110401~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/horizon/precise-essex-stableEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_cinder_stable #147

Title: precise_folsom_cinder_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_stable/147/Project:precise_folsom_cinder_stableDate of build:Mon, 11 Mar 2013 04:01:24 -0400Build duration:4 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 5380 lines...]Build needed 00:02:10, 35584k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/folsom-stable-testinggpg: Signature made Mon Mar 11 04:03:15 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Mon Mar 11 04:03:15 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpZ8rxo8/cinder_2012.2.4+git201303110401~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpZ8rxo8/cinder_2012.2.4+git201303110401~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading cinder_2012.2.4+git201303110401~precise-0ubuntu1.dsc: done.  Uploading cinder_2012.2.4+git201303110401~precise.orig.tar.gz: done.  Uploading cinder_2012.2.4+git201303110401~precise-0ubuntu1.debian.tar.gz: done.  Uploading cinder_2012.2.4+git201303110401~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptExporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/cinder/cinder-api_2012.2.4+git201302221331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-common_2012.2.4+git201302221331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-scheduler_2012.2.4+git201302221331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-volume_2012.2.4+git201302221331~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/python-cinder_2012.2.4+git201302221331~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 67.INFO:root:Storing current commit for next build: fcf249d1f06938280d841cb13b61556971a58e0cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/folsom /tmp/tmpZ8rxo8/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpZ8rxo8/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2.4+git201303110401~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2.4+git201303110401~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2.4+git201303110401~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-stable-testing cinder_2012.2.4+git201303110401~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom cinder_2012.2.4+git201303110401~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/cinder/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_keystone_trunk #191

Title: precise_grizzly_keystone_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/191/Project:precise_grizzly_keystone_trunkDate of build:Mon, 11 Mar 2013 10:11:58 -0400Build duration:8 min 57 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesMake getting user-domain roles backend independantby henryneditkeystone/identity/backends/sql.pyeditkeystone/identity/backends/ldap/core.pyedittests/test_backend_ldap.pyeditkeystone/identity/core.pyedittests/test_backend.pyMake Keystone return v3 as part of the version apiby henryneditkeystone/routers.pyedittests/test_versions.pyeditkeystone/controllers.pyeditkeystone/service.pyConsole Output[...truncated 6754 lines...]deleting and forgetting pool/main/k/keystone/keystone_2013.1+git201303051733~precise-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/python-keystone_2013.1+git201303051733~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/keystone/precise-grizzly']Pushed up to revision 182.INFO:root:Storing current commit for next build: 2dd6481a2005df7de0fed1fd630b8d2fbe38b775INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmpH7Blgy/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpH7Blgy/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log a8992277cd7dcde27deb7d3863370fd6bc9fd5ae..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-grizzly --forcedch -b -D precise --newversion 1:2013.1+git201303111012~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [2dd6481] Make Keystone return v3 as part of the version apidch -a [a2c3636] Delete tokens for userdch -a [d8599dc] from tests importdch -a [31df378] v3 endpoints won't have legacy ID's (bug 1150930)dch -a [dd7d4fd] return 201 Created on POST request (bug1131119)dch -a [0297f6f] add missing attributes for group/project tables (bug1126021)dch -a [9789447] Remove unused methods from LDAP backed.dch -a [dea5eea] Move get_by_name to LdapBase.dch -a [38bf87b] fix typo in kvs backenddch -a [156f474] mark 2.0 API as stabledch -a [b1474da] unable to load certificate should abort requestdch -a [ddd2216] Move auth plugins to 'keystone.auth.plugins' (bug 1136967)dch -a [26ecdca] Change exception raised to Forbidden on trust_iddch -a [be23b79] remove unused importdch -a [7b2d5a4] ports should be ints in config (bug 1137696)dch -a [c0f017c] Expand v3 trust test coveragedch -a [601eeb5] Trustsdch -a [ab6e552] bug 1134802: fix inconsistent format for expires_at and issued_atdch -a [a14b67e] Straighten out NotFound raising in LDAP backend.dch -a [1e64378] Make getting user-domain roles backend independantdch -a [7f20fee] Unpin pam dependency versiondch -a [39f1260] keystone : Use Ec2Signer utility class from keystoneclientdch -a [eaab3c2] Remove obsolete *page[_marker] methods from LDAP backend.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201303111012~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A keystone_2013.1+git201303111012~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing keystone_2013.1+git201303111012~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly keystone_2013.1+git201303111012~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/keystone/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_keystone_trunk #204

Title: raring_grizzly_keystone_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/204/Project:raring_grizzly_keystone_trunkDate of build:Mon, 11 Mar 2013 10:12:03 -0400Build duration:9 min 51 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesMake getting user-domain roles backend independantby henrynedittests/test_backend_ldap.pyedittests/test_backend.pyeditkeystone/identity/backends/ldap/core.pyeditkeystone/identity/core.pyeditkeystone/identity/backends/sql.pyMake Keystone return v3 as part of the version apiby henryneditkeystone/routers.pyeditkeystone/controllers.pyedittests/test_versions.pyeditkeystone/service.pyConsole Output[...truncated 7728 lines...]deleting and forgetting pool/main/k/keystone/keystone_2013.1+git201303052236~raring-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/python-keystone_2013.1+git201303052236~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/keystone/raring-grizzly']Pushed up to revision 182.INFO:root:Storing current commit for next build: 2dd6481a2005df7de0fed1fd630b8d2fbe38b775INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmpnRw37B/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpnRw37B/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log a8992277cd7dcde27deb7d3863370fd6bc9fd5ae..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/raring-grizzly --forcedch -b -D raring --newversion 1:2013.1+git201303111012~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [2dd6481] Make Keystone return v3 as part of the version apidch -a [a2c3636] Delete tokens for userdch -a [d8599dc] from tests importdch -a [31df378] v3 endpoints won't have legacy ID's (bug 1150930)dch -a [dd7d4fd] return 201 Created on POST request (bug1131119)dch -a [0297f6f] add missing attributes for group/project tables (bug1126021)dch -a [9789447] Remove unused methods from LDAP backed.dch -a [dea5eea] Move get_by_name to LdapBase.dch -a [38bf87b] fix typo in kvs backenddch -a [156f474] mark 2.0 API as stabledch -a [b1474da] unable to load certificate should abort requestdch -a [ddd2216] Move auth plugins to 'keystone.auth.plugins' (bug 1136967)dch -a [26ecdca] Change exception raised to Forbidden on trust_iddch -a [be23b79] remove unused importdch -a [7b2d5a4] ports should be ints in config (bug 1137696)dch -a [c0f017c] Expand v3 trust test coveragedch -a [601eeb5] Trustsdch -a [ab6e552] bug 1134802: fix inconsistent format for expires_at and issued_atdch -a [a14b67e] Straighten out NotFound raising in LDAP backend.dch -a [1e64378] Make getting user-domain roles backend independantdch -a [7f20fee] Unpin pam dependency versiondch -a [39f1260] keystone : Use Ec2Signer utility class from keystoneclientdch -a [eaab3c2] Remove obsolete *page[_marker] methods from LDAP backend.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.1+git201303111012~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A keystone_2013.1+git201303111012~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing keystone_2013.1+git201303111012~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly keystone_2013.1+git201303111012~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/keystone/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 Fixed: precise_grizzly_ceilometer_trunk #131

Title: precise_grizzly_ceilometer_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/131/Project:precise_grizzly_ceilometer_trunkDate of build:Mon, 11 Mar 2013 11:50:53 -0400Build duration:4 min 0 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 5336 lines...]DEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'ceilometer_2013.1+git20130350~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/ceilometer/ceilometer-agent-central_2013.1+git201303051101~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/ceilometer/ceilometer-agent-compute_2013.1+git201303051101~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/ceilometer/ceilometer-api_2013.1+git201303051101~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/ceilometer/ceilometer-collector_2013.1+git201303051101~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/ceilometer/ceilometer-common_2013.1+git201303051101~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/ceilometer/python-ceilometer_2013.1+git201303051101~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/ceilometer/precise-grizzly']Pushed up to revision 21.INFO:root:Storing current commit for next build: fa6bdc284ccd3af20839ea92f17caae465a63d82INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/ceilometer/grizzly /tmp/tmp07uT6m/ceilometermk-build-deps -i -r -t apt-get -y /tmp/tmp07uT6m/ceilometer/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log fba1ae00c324d9ad9ec0e6700ed317832e9e58e0..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/ceilometer/precise-grizzly --forcedch -b -D precise --newversion 1:2013.1+git20130350~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [fa6bdc2] Start both v1 and v2 api from one daemon.dch -a [43a9933] Handle missing units values in mongodb data.dch -a [cafec09] Imported Translations from Transifexdch -a [6a7633c] Make HACKING compliantdch -a [a909580] Update manual installation instructionsdch -a [df0a2ca] Fix oslo.config and unittest.dch -a [b7c30ca] Return something sane from the log impl.dch -a [bf0c01e] Fix an invalid test in the storage test suitedch -a [9aa2ec3] Add the etc directory to the sdist manifestdch -a [34e5932] api: run compute duration by resource on SQL backenddch -a [955ffa9] api: run list_projects tests against SQL backend toodch -a [75f4fff] api: run list users test against SQL backend toodch -a [fdadb09] api: run list meters tests against SQL backend toodch -a [b9d9539] Exclude tests directory from installation.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC ceilometer_2013.1+git20130350~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A ceilometer_2013.1+git20130350~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing ceilometer_2013.1+git20130350~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly ceilometer_2013.1+git20130350~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/ceilometer/precise-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_nova_trunk #789

Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/789/Project:precise_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 14:08:56 -0400Build duration:14 minBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changesdelete deleted image 500 bugby bknudsoneditnova/tests/glance/stubs.pyeditnova/api/openstack/compute/images.pyeditnova/tests/image/test_glance.pyeditnova/tests/api/openstack/fakes.pyeditnova/tests/api/openstack/compute/test_images.pyLibvirt driver create images even without metaby ndipanoveditnova/virt/libvirt/driver.pyeditnova/tests/test_libvirt.pyExtended server attributes can show wrong hypervisor_hostnameby hanlindeditnova/api/openstack/compute/contrib/extended_server_attributes.pyeditnova/db/sqlalchemy/api.pyeditnova/tests/api/openstack/compute/contrib/test_extended_server_attributes.pyeditnova/db/api.pyeditnova/tests/api/openstack/fakes.pyAdd ability to control max utilization of a cellby brian.elliotteditnova/cells/state.pyaddnova/tests/cells/test_cells_state_manager.pyeditnova/cells/opts.pyServer create will only process networks if os-networks is loaded.by philip.dayeditnova/api/openstack/compute/servers.pyeditnova/tests/api/openstack/compute/test_servers.pyRefactor db tests to ensure that notdb driver is used.by mikaleditnova/tests/test_db_api.pyConsole Output[...truncated 19220 lines...]deleting and forgetting pool/main/n/nova/nova-compute_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-conductor_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-novncproxy_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-spiceproxy_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201303111332~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201303111332~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 562.INFO:root:Storing current commit for next build: 28a6ef007e2faa47fd4ad0d855098945eacf2317INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpTfEw1K/novamk-build-deps -i -r -t apt-get -y /tmp/tmpTfEw1K/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e78528e113c3a8bb8900052f6db2c0ca2c05c9f9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 1:2013.1+git201303111409~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [28a6ef0] Refactor db tests to ensure that notdb driver is used.dch -a [e0fd027] Server create will only process "networks" if os-networks is loaded.dch -a [3d7d819] Correct exception args in vfs/guestfs.dch -a [aa1966d] Simple syntax fix up.dch -a [0b48884] Add ability to control max utilization of a celldch -a [0a22d9d] Extended server attributes can show wrong hypervisor_hostnamedch -a [3133096] Libvirt driver create images even without metadch -a [ccabf7a] delete deleted image 500 bugdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201303111409~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201303111409~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201303111409~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201303111409~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_glance_stable #208

Title: precise_folsom_glance_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_stable/208/Project:precise_folsom_glance_stableDate of build:Mon, 11 Mar 2013 20:31:25 -0400Build duration:2 min 18 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFixes deletion of invalid image memberby eglynneditglance/tests/unit/v1/test_api.pyeditglance/registry/api/v1/members.pyConsole Output[...truncated 2287 lines...]Applying patch disable-swift-tests.patchpatching file glance/tests/functional/test_bin_glance.pyHunk #2 FAILED at 309.Hunk #3 succeeded at 327 (offset 8 lines).1 out of 3 hunks FAILED -- rejects in file glance/tests/functional/test_bin_glance.pypatching file glance/tests/functional/v1/test_multiprocessing.pypatching file glance/tests/functional/v2/test_images.pypatching file glance/tests/unit/test_clients.pypatching file glance/tests/unit/test_swift_store.pypatching file glance/tests/unit/v2/test_image_data_resource.pyPatch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-0c2bdf11-4b56-4fe2-a000-25f9e9642a25', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-0c2bdf11-4b56-4fe2-a000-25f9e9642a25', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/folsom /tmp/tmpLzfm9z/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpLzfm9z/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log afe61664ac5f933622e349da1c0a92d134a81230..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-folsom --forcedch -b -D precise --newversion 2012.2.4+git201303112031~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [04f88c8] Fixes deletion of invalid image memberdch -a [5597697] Wait in TestBinGlance.test_update_copying_from until image is activedch -a [12d28c3] Swallow UserWarning from glance-cache-managedch -a [5183360] Clean dangling image fragments in filesystem storedch -a [03dc862] Avoid dangling partial image on size/checksum mismatchdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-0c2bdf11-4b56-4fe2-a000-25f9e9642a25', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-0c2bdf11-4b56-4fe2-a000-25f9e9642a25', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_glance_stable #206

Title: quantal_folsom_glance_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_glance_stable/206/Project:quantal_folsom_glance_stableDate of build:Mon, 11 Mar 2013 20:33:44 -0400Build duration:2 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesFixes deletion of invalid image memberby eglynneditglance/registry/api/v1/members.pyeditglance/tests/unit/v1/test_api.pyConsole Output[...truncated 2407 lines...]Applying patch disable-swift-tests.patchpatching file glance/tests/functional/test_bin_glance.pyHunk #2 FAILED at 309.Hunk #3 succeeded at 327 (offset 8 lines).1 out of 3 hunks FAILED -- rejects in file glance/tests/functional/test_bin_glance.pypatching file glance/tests/functional/v1/test_multiprocessing.pypatching file glance/tests/functional/v2/test_images.pypatching file glance/tests/unit/test_clients.pypatching file glance/tests/unit/test_swift_store.pypatching file glance/tests/unit/v2/test_image_data_resource.pyPatch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'quantal-amd64-74691229-52a7-42fa-b0b2-fe59fbe19b84', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'quantal-amd64-74691229-52a7-42fa-b0b2-fe59fbe19b84', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/folsom /tmp/tmpTBjumt/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpTBjumt/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log afe61664ac5f933622e349da1c0a92d134a81230..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/quantal-folsom --forcedch -b -D quantal --newversion 2012.2.4+git201303112033~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [04f88c8] Fixes deletion of invalid image memberdch -a [5597697] Wait in TestBinGlance.test_update_copying_from until image is activedch -a [12d28c3] Swallow UserWarning from glance-cache-managedch -a [5183360] Clean dangling image fragments in filesystem storedch -a [03dc862] Avoid dangling partial image on size/checksum mismatchdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'quantal-amd64-74691229-52a7-42fa-b0b2-fe59fbe19b84', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'quantal-amd64-74691229-52a7-42fa-b0b2-fe59fbe19b84', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_nova_stable #66

Title: precise_essex_nova_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_nova_stable/66/Project:precise_essex_nova_stableDate of build:Mon, 11 Mar 2013 22:02:45 -0400Build duration:14 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 3 builds failed.33ChangesNo ChangesConsole Output[...truncated 15212 lines...]deleting and forgetting pool/main/n/nova/nova-compute-kvm_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-lxc_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-qemu_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-uml_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xcp_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xen_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-vncproxy_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2012.1.4+git201301291205~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2012.1.4+git201301291205~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 402.INFO:root:Storing current commit for next build: b683ced5dfdcaa710f5e9405e73a98b9a09d55a2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-essex-proposed /tmp/tmpfr6DtB/novamk-build-deps -i -r -t apt-get -y /tmp/tmpfr6DtB/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 243d516cea9d3caa5a8267b12d2f577dcb24193b..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-essex-stable --forcedch -b -D precise --newversion 2012.1.4+git201303112203~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [b683ced] Add nosehtmloutput as a test dependency.dch -a [45274c8] Pin glance dependency to pre-grizzly versions.dch -a [e02b459] vnc unit-test fixesdch -a [e98928c] Flush tokens on instance deletedch -a [87361d3] Force earlier version of sqlalchemydch -a [c0a10db] Add a safe_minidom_parse_string function.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.1.4+git201303112203~precise-0ubuntu1_source.changessbuild -d precise-essex -n -A nova_2012.1.4+git201303112203~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/essex-stable-testing nova_2012.1.4+git201303112203~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-essex nova_2012.1.4+git201303112203~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-essex-stable+ [ ! 0 ]+ jenkins-cli build precise_essex_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_essex_deploy #18363

Title: precise_essex_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy/18363/Project:precise_essex_deployDate of build:Mon, 11 Mar 2013 22:17:40 -0400Build duration:14 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 2859 lines...]  -> Relation: nova-volume <-> mysql  -> Relation: nova-volume <-> rabbitmq  -> Relation: nova-volume <-> nova-cloud-controller  -> Relation: openstack-dashboard <-> keystone  -> Relation: nova-compute <-> mysql  -> Relation: nova-compute <-> rabbitmq  -> Relation: nova-compute <-> glance  -> Relation: nova-compute <-> nova-cloud-controller- Sleeping for 60 before ensuring relation state.- Deployment complete in 880 seconds.- Juju command log:juju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:nova-compute nova-compute -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:nova-volume nova-volume -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:nova-cloud-controller nova-cloud-controller -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:keystone keystone -e precisejuju deploy -n 1 --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:rabbitmq-server rabbitmq -e precisejuju deploy -n 1 --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:mysql mysql -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:openstack-dashboard openstack-dashboard -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:glance glance -e precisejuju deploy -n 1 --config=/tmp/tmpCdj1CP --repository=/var/lib/jenkins/jobs/precise_essex_deploy/workspace local:glance glance -e precisejuju add-relation keystone mysql -e precisejuju add-relation nova-cloud-controller mysql -e precisejuju add-relation nova-cloud-controller rabbitmq -e precisejuju add-relation nova-cloud-controller glance -e precisejuju add-relation nova-cloud-controller keystone -e precisejuju add-relation glance mysql -e precisejuju add-relation glance keystone -e precisejuju add-relation nova-volume mysql -e precisejuju add-relation nova-volume rabbitmq -e precisejuju add-relation nova-volume nova-cloud-controller -e precisejuju add-relation openstack-dashboard keystone -e precisejuju add-relation nova-compute mysql -e precisejuju add-relation nova-compute rabbitmq -e precisejuju add-relation nova-compute glance -e precisejuju add-relation nova-compute nova-cloud-controller -e precise+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build precise_essex_test+ exit 0Archiving artifactsERROR: No artifacts found that match the file pattern "logs/*". Configuration error?ERROR: 'logs/*' doesn't match anything, but '*' does. Perhaps that's what you mean?Build step 'Archive the artifacts' changed build result to FAILUREEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_test #600