Re: [Openstack] PAM authentication for Folsom Keystone

[Alvaro Lopez]

On Tue 26 Feb 2013 (13:41), Joshua wrote:
 Matt at this point I am just trying to log into keystone using users I
 created on the Unix system.

You mean authenticate against keystone using your system users?

You should be able to do so by running keystone as a WSGI behind an
Apache http server that will make the authentication (PAM in this case,
but can be any auth method supported by apache) and then using the
external authentication method [1].

[1] 
http://docs.openstack.org/developer/keystone/external-auth.html#using-httpd-authentication

Regards,
-- 
Álvaro López García  al...@ifca.unican.es
Instituto de Física de Cantabria http://devel.ifca.es/~aloga/
Ed. Juan Jordá, Campus UC  tel: (+34) 942 200 969
Avda. de los Castros s/n
39005 Santander (SPAIN)
_
Premature optimization is the root of all evil (or at least most of it)
 in programming. -- Donald Knuth



___
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] [HeatQuantum] Quantum Template ROLLBACK_FAILED Error

[蒋闻天]

no attribute admin_state_up


2013/2/28 蒋闻天 jiangwt...@gmail.com

 I have heat and quantum in my devstack, just like:
 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

 Then I restart my compute, ./rejoin-stack.sh
 All Service OK.

 Then I run some thing like:
 heat stack-create -f /opt/stack/heat/templates/Quantum.template susu

 heat stack-list ROLLBACK_FAILED
 I See The Error Happened , Is there anyone can help me with this problem.
 Maybe some config i did not known.

___
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 configuration on compute node

[Javier Alvarez]

Hello Ajiva,

You are right, I was missing the option flat_interface in my nova.conf, 
now when OpenStack creates the bridge, it is attached to eth2:


 brctl show

bridge name bridge id   STP enabled interfaces
br100   8000.68b599c23b0e   no  eth2
   vnet0

However it is still not working... Also, br100 is created without IP 
address, but is not working either even if I assign it a random one. 
Here is my nova.conf in the compute node:


[DEFAULT]
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
root_helper=sudo nova-rootwrap
auth_strategy=keystone
iscsi_helper=tgtadm
sql_connection=mysql://nova-common:secret@172.16.8.1/nova
connection_type=libvirt
libvirt_type=kvm
my_ip=172.16.8.21
rabbit_host=172.16.8.1
glance_host=172.16.8.1
image_service=nova.image.glance.GlanceImageService
network_manager=nova.network.manager.FlatDHCPManager
network_host=172.16.8.1
fixed_range=192.168.100.0/24
flat_interface=eth2
flat_network_bridge=br100

Thank you,

Javi

On 28/02/13 02:57, Ajiva Fan wrote:

the output of `#brclt show` shows that your br100 is not bridged on any nic
and the output of `ifconfig` shows that your br100 get no ipv4 addr

br100 plays roles of:
1) gateway
2) dhcp server
3) dns server

so since your br100 is not created correctly, i think the vm will not
get an ip trough dhcp

please paste your nova.conf file, especially the network part. hope
someone will find the problem



--
Javier Álvarez Cid-Fuentes
Grid Computing and Clusters Group
Barcelona Supercomputing Center (BSC-CNS)
Tel. (+34) 93 413 72 46


WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.

http://www.bsc.es/disclaimer

___
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] [HeatQuantum] Quantum Template ROLLBACK_FAILED Error

[Angus Salkeld]

On 28/02/13 15:30 +0800, 蒋闻天 wrote:

I have heat and quantum in my devstack, just like:
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

Then I restart my compute, ./rejoin-stack.sh
All Service OK.

Then I run some thing like:
heat stack-create -f /opt/stack/heat/templates/Quantum.template susu

heat stack-list ROLLBACK_FAILED
I See The Error Happened , Is there anyone can help me with this problem.
Maybe some config i did not known.


did you get any errors out of heat-engine?

Are you sure your Quantum is working? I made a super quick attempt
with your config and Quantum didn't start. Then Heat had the error
as you reported (with an exception in the log about no endpoint)
since Quantum didn't start.

-Angus



___
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] keystone-manage db_sync errors

[Atul Jha]

Looks like database connection error.

From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of 
Ashutosh Narayan [aashutoshnara...@gmail.com]
Sent: Thursday, February 28, 2013 5:42 PM
To: OpenStack
Subject: [Openstack] keystone-manage db_sync errors

Hi folks,

I following the instructions to install OpenStack on CentOS 6.3
mentioned on this 
linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
 . I am getting following errors when I execute
keystone-manage db_sync command.

[root@RLD1OPST01 ~]# keystone-manage db_sync
Traceback (most recent call last):
  File /usr/bin/keystone-manage, line 28, in module
cli.main(argv=sys.argv, config_files=config_files)
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 164, in main
return run(cmd, (args[:1] + args[2:]))
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 147, in run
return CMDS[cmd](argv=args).run()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 35, in run
return self.main()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 56, in main
driver.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/identity/backends/sql.py, 
line 136, in db_sync
migration.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 49, in db_sync
current_version = db_version()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 63, in db_version
return db_version_control(0)
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 68, in db_version_control
versioning_api.version_control(CONF.sql.connection, repo_path, version)
  File string, line 2, in version_control
  File /usr/lib/python2.6/site-packages/migrate/versioning/util/__init__.py, 
line 160, in with_engine
return f(*a, **kw)
  File /usr/lib/python2.6/site-packages/migrate/versioning/api.py, line 248, 
in version_control
ControlledSchema.create(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
137, in create
table = cls._create_table_version(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
178, in _create_table_version
if not table.exists():
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/schema.py,
 line 579, in exists
self.namehttp://self.name, schema=self.schema)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2424, in run_callable
conn = self.contextual_connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2490, in contextual_connect
self.pool.connect(),
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 224, in connect
return _ConnectionFairy(self).checkout()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 387, in __init__
rec = self._connection_record = pool._do_get()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 741, in _do_get
con = self._create_connection()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 188, in _create_connection
return _ConnectionRecord(self)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 270, in __init__
self.connection = self.__connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 330, in __connect
connection = self.__pool._creator()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/strategies.py,
 line 80, in connect
return dialect.connect(*cargs, **cparams)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py,
 line 281, in connect
return self.dbapi.connect(*cargs, **cparams)
  File /usr/lib64/python2.6/site-packages/MySQLdb/__init__.py, line 81, in 
Connect
return Connection(*args, **kwargs)
  File /usr/lib64/python2.6/site-packages/MySQLdb/connections.py, line 187, 
in __init__
super(Connection, self).__init__(*args, **kwargs2)
sqlalchemy.exc.OperationalError: (OperationalError) (1045, Access denied for 
user 'keystone'@'RLD1OPST01' (using password: YES)) None None

Where am I going wrong ?
Please suggest.

Thank you,
--
Ashutosh Narayan

http://ashutoshn.wordpress.com/

http://www.csscorp.com/common/email-disclaimer.php
___
Mailing list: https://launchpad.net/~openstack
Post to : 

Re: [Openstack] keystone-manage db_sync errors

[Ashutosh Narayan]

Hi Atul,

There was an instruction
http://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.htmlmentioning
-- After installing, openstack-utils openstack-keystone
python-keystoneclient packages,
we need to delete the sqlite database it creates, then change the
configuration to point to a MySQL database.
How can I achieve this ?

On Thu, Feb 28, 2013 at 5:48 PM, Atul Jha atul@csscorp.com wrote:

  Looks like database connection error.
  --
 *From:* 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 *Sent:* Thursday, February 28, 2013 5:42 PM
 *To:* OpenStack
 *Subject:* [Openstack] keystone-manage db_sync errors

  Hi folks,

  I following the instructions to install OpenStack on CentOS 6.3
  mentioned on this 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
  .
 I am getting following errors when I execute
 keystone-manage db_sync command.

  [root@RLD1OPST01 ~]# keystone-manage db_sync
 Traceback (most recent call last):
   File /usr/bin/keystone-manage, line 28, in module
 cli.main(argv=sys.argv, config_files=config_files)
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 164, in
 main
 return run(cmd, (args[:1] + args[2:]))
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 147, in run
 return CMDS[cmd](argv=args).run()
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 35, in run
 return self.main()
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 56, in main
 driver.db_sync()
   File
 /usr/lib/python2.6/site-packages/keystone/identity/backends/sql.py, line
 136, in db_sync
 migration.db_sync()
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 49, in db_sync
 current_version = db_version()
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 63, in db_version
 return db_version_control(0)
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 68, in db_version_control
 versioning_api.version_control(CONF.sql.connection, repo_path, version)
   File string, line 2, in version_control
   File
 /usr/lib/python2.6/site-packages/migrate/versioning/util/__init__.py,
 line 160, in with_engine
 return f(*a, **kw)
   File /usr/lib/python2.6/site-packages/migrate/versioning/api.py, line
 248, in version_control
 ControlledSchema.create(engine, repository, version)
   File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py,
 line 137, in create
 table = cls._create_table_version(engine, repository, version)
   File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py,
 line 178, in _create_table_version
 if not table.exists():
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/schema.py,
 line 579, in exists
 self.name, schema=self.schema)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2424, in run_callable
 conn = self.contextual_connect()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2490, in contextual_connect
 self.pool.connect(),
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 224, in connect
 return _ConnectionFairy(self).checkout()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 387, in __init__
 rec = self._connection_record = pool._do_get()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 741, in _do_get
 con = self._create_connection()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 188, in _create_connection
 return _ConnectionRecord(self)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 270, in __init__
 self.connection = self.__connect()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 330, in __connect
 connection = self.__pool._creator()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/strategies.py,
 line 80, in connect
 return dialect.connect(*cargs, **cparams)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py,
 line 281, in connect
 return self.dbapi.connect(*cargs, **cparams)
   File /usr/lib64/python2.6/site-packages/MySQLdb/__init__.py, line 81,
 in Connect
 return Connection(*args, **kwargs)
   File 

Re: [Openstack] OpenStack Eseex, XP instances and DHCP service (vlan mode)

[Razique Mahroua]

Ok , 
actually the dnsmasq 2.61 did solved the issue, I didn't noticed openstack was 
using the old version.
After a ln -s /usr/local/sbin/dnsmasq /usr/sbin/dnsmasq it's all good now :)



Le 21 févr. 2013 à 18:03, Sylvain Bauza sylvain.ba...@digimind.com a écrit :

 I did had trouble with DHCP leasing with 2K3 R2 using Essex. At first boot, 
 the lease was taken from our corporate DHCP server instead of nova-network 
 dnsmasq.
 I also noticed in EventViewer that, as you mention, DHCP leases were 
 sometimes forgotten.
 
 After long time investigating, I had to answer, neither no fix. The only 
 workaround was to isolate physically our Essex setup to make sure DHCP 
 broadcast was not reaching our corp Win2k DHCP server.
 
 Sorry, I admit this is not a clear solution, only the move to Quantum with 
 ProviderRouter fixed my issue.
 
 -Sylvain
 
 Le 21/02/2013 17:47, Razique Mahroua a écrit :
 Hi Guys,
 I'm currently using OPS Essex - from the Canonical repos.
 I'm running an heterogenous set of instanes (Ubutu, Debian, CentOS, Server 
 2K3 R2, 2K8, etc..)
 I'm facing an issue with the XP instances, all are running the SP3 in 64bits 
 - What happens is that sometimes they are not able to renew their IP address 
 toward the DHCP server, thus dropping all network connectivity. I've 
 upgraded all my dnsmasq services by compiling the version 2-61 - according 
 to that thread (https://lists.launchpad.net/openstack/msg11696.html)
 and let the long lease times in case of, but that doesn't change - I still 
 see in the event viewer of XP a warning about the DHCP service complaining 
 about a timeout.
 
 Any help would be much appreciated - my options are now as short as a hobbit
 cheers
 
 *Razique Mahroua** - **Nuage  Co*
 razique.mahr...@gmail.com mailto:razique.mahr...@gmail.com
 Tel : +33 9 72 37 94 15
 
 
 
 
 
 ___
 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] keystone/horizon/dashboard

[Mballo Cherif]

Hello everybody !

I need help,
when i try to authenticate with the dashboard I have this An error occurred 
authenticating. Please try again later. What is wrong with keystone or horizon?
How can I fix this issue?

Thanks you for your help!

Sherif.
___
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] keystone/horizon/dashboard

[Robert van Leeuwen]

 when i try to authenticate with the dashboard I have this “An error occurred 
 authenticating. Please try 
 again later.” What is wrong with keystone or horizon?

Just a couple things to check:
* apache error log 
* keystone log might be helpfull

Set the dashboard and keystone to debug in the config file to get more info.

Cheers,
Robert van Leeuwen



___
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] keystone/horizon/dashboard

[Atul Jha]

Mballo,

Please check if these are correct

1. configuration file of dashbaord
2. keystone endpoint configuration


Also check the apache error logfile and keystone log file as well.

From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of 
Mballo Cherif [cherif.mba...@gemalto.com]
Sent: Thursday, February 28, 2013 6:01 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] keystone/horizon/dashboard

Hello everybody !

I need help,
when i try to authenticate with the dashboard I have this “An error occurred 
authenticating. Please try again later.” What is wrong with keystone or horizon?
How can I fix this issue?

Thanks you for your help!

Sherif.
http://www.csscorp.com/common/email-disclaimer.php

___
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] keystone-manage db_sync errors

[Ashutosh Narayan]

I was able to resolve this issue.

Thank you,

On Thu, Feb 28, 2013 at 5:53 PM, Ashutosh Narayan 
aashutoshnara...@gmail.com wrote:

 Hi Atul,

 There was an instruction
 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.htmlmentioning
 -- After installing, openstack-utils openstack-keystone
 python-keystoneclient packages,
 we need to delete the sqlite database it creates, then change the
 configuration to point to a MySQL database.
 How can I achieve this ?


 On Thu, Feb 28, 2013 at 5:48 PM, Atul Jha atul@csscorp.com wrote:

  Looks like database connection error.
  --
 *From:* 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 *Sent:* Thursday, February 28, 2013 5:42 PM
 *To:* OpenStack
 *Subject:* [Openstack] keystone-manage db_sync errors

  Hi folks,

  I following the instructions to install OpenStack on CentOS 6.3
  mentioned on this 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
  .
 I am getting following errors when I execute
 keystone-manage db_sync command.

  [root@RLD1OPST01 ~]# keystone-manage db_sync
 Traceback (most recent call last):
   File /usr/bin/keystone-manage, line 28, in module
 cli.main(argv=sys.argv, config_files=config_files)
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 164, in
 main
 return run(cmd, (args[:1] + args[2:]))
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 147, in
 run
 return CMDS[cmd](argv=args).run()
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 35, in run
 return self.main()
   File /usr/lib/python2.6/site-packages/keystone/cli.py, line 56, in
 main
 driver.db_sync()
   File
 /usr/lib/python2.6/site-packages/keystone/identity/backends/sql.py, line
 136, in db_sync
 migration.db_sync()
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 49, in db_sync
 current_version = db_version()
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 63, in db_version
 return db_version_control(0)
   File
 /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, line
 68, in db_version_control
 versioning_api.version_control(CONF.sql.connection, repo_path,
 version)
   File string, line 2, in version_control
   File
 /usr/lib/python2.6/site-packages/migrate/versioning/util/__init__.py,
 line 160, in with_engine
 return f(*a, **kw)
   File /usr/lib/python2.6/site-packages/migrate/versioning/api.py, line
 248, in version_control
 ControlledSchema.create(engine, repository, version)
   File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py,
 line 137, in create
 table = cls._create_table_version(engine, repository, version)
   File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py,
 line 178, in _create_table_version
 if not table.exists():
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/schema.py,
 line 579, in exists
 self.name, schema=self.schema)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2424, in run_callable
 conn = self.contextual_connect()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2490, in contextual_connect
 self.pool.connect(),
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 224, in connect
 return _ConnectionFairy(self).checkout()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 387, in __init__
 rec = self._connection_record = pool._do_get()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 741, in _do_get
 con = self._create_connection()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 188, in _create_connection
 return _ConnectionRecord(self)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 270, in __init__
 self.connection = self.__connect()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 330, in __connect
 connection = self.__pool._creator()
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/strategies.py,
 line 80, in connect
 return dialect.connect(*cargs, **cparams)
   File
 /usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py,
 line 281, in connect
 return self.dbapi.connect(*cargs, **cparams)
   File 

Re: [Openstack] keystone-manage db_sync errors

[Atul Jha]

Ashutosh,

1. Install the packages
2. create the database manually, the guide says how.
3. change the keystone configuration file to match
4. restart the services
5. run the keysone sync command

Let me know if it works. I don`t have a Centos/Yum machine to test it this 
side. :(

From: Ashutosh Narayan [aashutoshnara...@gmail.com]
Sent: Thursday, February 28, 2013 5:53 PM
To: Atul Jha; OpenStack
Subject: Re: [Openstack] keystone-manage db_sync errors

Hi Atul,

There was an instruction 
http://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
 mentioning -- After installing, openstack-utils openstack-keystone 
python-keystoneclient packages,
we need to delete the sqlite database it creates, then change the configuration 
to point to a MySQL database.
How can I achieve this ?

On Thu, Feb 28, 2013 at 5:48 PM, Atul Jha 
atul@csscorp.commailto:atul@csscorp.com wrote:
Looks like database connection error.

From: 
openstack-bounces+atul.jha=csscorp@lists.launchpad.netmailto:csscorp@lists.launchpad.net
 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.netmailto:csscorp@lists.launchpad.net]
 on behalf of Ashutosh Narayan 
[aashutoshnara...@gmail.commailto:aashutoshnara...@gmail.com]
Sent: Thursday, February 28, 2013 5:42 PM
To: OpenStack
Subject: [Openstack] keystone-manage db_sync errors

Hi folks,

I following the instructions to install OpenStack on CentOS 6.3
mentioned on this 
linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
 . I am getting following errors when I execute
keystone-manage db_sync command.

[root@RLD1OPST01 ~]# keystone-manage db_sync
Traceback (most recent call last):
  File /usr/bin/keystone-manage, line 28, in module
cli.main(argv=sys.argv, config_files=config_files)
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 164, in main
return run(cmd, (args[:1] + args[2:]))
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 147, in run
return CMDS[cmd](argv=args).run()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 35, in run
return self.main()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 56, in main
driver.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/identity/backends/sql.py, 
line 136, in db_sync
migration.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 49, in db_sync
current_version = db_version()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 63, in db_version
return db_version_control(0)
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 68, in db_version_control
versioning_api.version_control(CONF.sql.connection, repo_path, version)
  File string, line 2, in version_control
  File /usr/lib/python2.6/site-packages/migrate/versioning/util/__init__.py, 
line 160, in with_engine
return f(*a, **kw)
  File /usr/lib/python2.6/site-packages/migrate/versioning/api.py, line 248, 
in version_control
ControlledSchema.create(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
137, in create
table = cls._create_table_version(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
178, in _create_table_version
if not table.exists():
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/schema.py,
 line 579, in exists
self.namehttp://self.name, schema=self.schema)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2424, in run_callable
conn = self.contextual_connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2490, in contextual_connect
self.pool.connect(),
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 224, in connect
return _ConnectionFairy(self).checkout()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 387, in __init__
rec = self._connection_record = pool._do_get()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 741, in _do_get
con = self._create_connection()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 188, in _create_connection
return _ConnectionRecord(self)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 270, in __init__
self.connection = self.__connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 330, in __connect

[Openstack] Verifying Identity Service installation

[Ashutosh Narayan]

Hi folks,

I am unable to verify the Identity Service installation mentioned in this
linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/verifying-identity-install.html
 .
Its throws the following error:

[root@test ~]# keystone --os-username=admin --os-password=secretword
--os-auth-url=http://192.168.105.61:35357/v2.0 token-get
No handlers could be found for logger keystoneclient.v2_0.client
Authorization Failed: Unable to communicate with identity service: [Errno
111] Connection refused. (HTTP 400)

Why am I getting this error ? Http is not yet installed on the system. Is
it because of that ?

Help appreciated.
Thank you,
-- 
Ashutosh Narayan

http://ashutoshn.wordpress.com/
___
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] MySQL and Iptables

[Joe Warren-Meeks]

Hi all.

I run two compute nodes in one of my clusters and everything is generally
fine. All the management services (mysql dashboard etc) run on compute1 and
compute2 runs nova-network and nova-compute.

However, after a period of time something happens with (I presume) iptables
and then compute2 can't get to the MySQL database. It is fine if I reboot
it, but that is very much not optimal.

The errors I'm seeing are:
2013-02-28 13:33:16 WARNING nova.db.sqlalchemy.session
[req-028ed124-fb88-457b-9aed-222d4847adca None None] SQL connection failed.
7 attempts left.

If I try to telnet to the MySQL port I get:
root@compute2:/etc/nova# telnet 10.0.80.10 3306
Trying 10.0.80.10...
telnet: Unable to connect to remote host: Connection refused

But that RST isn't coming from the host with the database on, it looks to
be generated by IPtables on the localhost.

Anyone know what is causing this?

Kind regards

 -- joe.
___
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] Verifying Identity Service installation

[Ashutosh Narayan]

I get the following error after following this instruction :

Configuration error: Client configured to run without a service catalog.
Run the client using --os-auth-url or OS_AUTH_URL, instead of --os-endpoint
or OS_SERVICE_ENDPOINT, for example.

On Thu, Feb 28, 2013 at 7:09 PM, Atul Jha atul@csscorp.com wrote:

 This been discussed before as well

 https://lists.launchpad.net/openstack/msg15491.html

 A simple googling gave me that link.


 
 From: 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 Sent: Thursday, February 28, 2013 6:41 PM
 To: OpenStack
 Subject: [Openstack] Verifying Identity Service installation

 Hi folks,

 I am unable to verify the Identity Service installation mentioned in this
 link
 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verifying-identity-install.html
 .
 Its throws the following error:

 [root@test ~]# keystone --os-username=admin --os-password=secretword
 --os-auth-url=http://192.168.105.61:35357/v2.0 token-get
 No handlers could be found for logger keystoneclient.v2_0.client
 Authorization Failed: Unable to communicate with identity service: [Errno
 111] Connection refused. (HTTP 400)

 Why am I getting this error ? Http is not yet installed on the system. Is
 it because of that ?

 Help appreciated.
 Thank you,
 --
 Ashutosh Narayan

 http://ashutoshn.wordpress.com/
 http://www.csscorp.com/common/email-disclaimer.php




-- 
Ashutosh Narayan

http://ashutoshn.wordpress.com/
___
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] [HeatQuantum] Quantum Template ROLLBACK_FAILED Error

[蒋闻天]

Actually My Full Edition Of LocalRC is
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

And My Quantum Is Ok :) Without Celemeter

I Found The Problem:
h-eng
screen-h-eng.2013-02-28-154758.log:630:2013-02-28 16:30:59 DEBUG
[quantumclient.v2_0.client] Error message: {QuantumError: Unrecognized
attribute(s) 'admin_state_up'}
https://bugs.launchpad.net/heat/+bug/1135485

I fix the bug all the afternoon~~
https://review.openstack.org/#/c/23162/


Then It Just Works~~


2013/2/28 Angus Salkeld asalk...@redhat.com

 On 28/02/13 15:30 +0800, 蒋闻天 wrote:

 I have heat and quantum in my devstack, just like:
 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

 Then I restart my compute, ./rejoin-stack.sh
 All Service OK.

 Then I run some thing like:
 heat stack-create -f /opt/stack/heat/templates/**Quantum.template susu

 heat stack-list ROLLBACK_FAILED
 I See The Error Happened , Is there anyone can help me with this problem.
 Maybe some config i did not known.


 did you get any errors out of heat-engine?

 Are you sure your Quantum is working? I made a super quick attempt
 with your config and Quantum didn't start. Then Heat had the error
 as you reported (with an exception in the log about no endpoint)
 since Quantum didn't start.

 -Angus


  __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp



 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://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] Load Balancing Horizon

[Everett Toews]

Hi Gabriel,

I've read Deploying Horizon [1] and I had a few high-level questions for you 
about load balancing Horizon.

1. Do you have any suggestions or recommendations for load balancing Horizon?
2. Are there any gotchas?
3. Can you more or less just load balance it like any other web app?

Thanks,
Everett

[1] http://docs.openstack.org/developer/horizon/topics/deployment.html
___
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] Keystone and Swift Integration

[Julian Learmonth]

Hi,

I've built an OpenStack (Folsom) demo VM (Ubuntu 12.10) and manually
installed Swift. I am trying to get Swift to use Keystone for
authentication, but am having trouble finding what I need to do to the
/etc/swift/swift-proxy.conf file. The instructions I have been following
say I should Configure the paste file for swift-proxy
(`/etc/swift/swift-proxy.conf`), but I don't know what needs to be done.
The document I am following is here:
http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-swift-to-use-keystone.html

I've only been using OpenStack for about a week, so my apologies if this is
obvious, but I can't figure it out. I've tried googling the config file,
but I just get the document I am using (or the previous Wessex version) and
there's no sample file in the Swift distribution.

The second config file I need to edit is the /etc/swift/proxy-swift.conf
file. I have a couple of questions about this too. There's a section I need
to paste into it as follows:

===
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = 127.0.0.1
auth_port = 35357
auth_host = 127.0.0.1
auth_protocol = http
auth_uri = http://127.0.0.1:5000/
auth_token = 012345SECRET99TOKEN012345
admin_token = 012345SECRET99TOKEN012345
admin_tenant_name = service
admin_user = swift
admin_password = swift
===

Do I need to change the auth port? I can run the following command
successfully:

===
root@openstack02:/home/stack/bin# curl -v -H 'X-Storage-User: admin:admin'
-H 'X-Storage-Pass: admin' http://127.0.0.1:8080/auth/v1.0
* About to connect() to 127.0.0.1 port 8080 (#0)
*   Trying 127.0.0.1...
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
 GET /auth/v1.0 HTTP/1.1
 User-Agent: curl/7.27.0
 Host: 127.0.0.1:8080
 Accept: */*
 X-Storage-User: admin:admin
 X-Storage-Pass: admin

* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
 HTTP/1.1 200 OK
 X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_admin
 X-Auth-Token: AUTH_tk0022e539fae64647883b9fa529311982
 Content-Type: text/html; charset=UTF-8
 X-Storage-Token: AUTH_tk0022e539fae64647883b9fa529311982
 Content-Length: 0
 Date: Wed, 28 Feb 2013 15:00:02 GMT

* Connection #0 to host 127.0.0.1 left intact
* Closing connection #0
root@openstack02:/home/stack/bin#
===

So does that mean by auth_port is 8080? I assume that the X-Auth-Token is
both the admin_token and auth_token? Is the admin_user (given the example
above) going to be admin:admin?

Any assistance would very much be appreciated!

Regards,
Julian.
___
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] Load Balancing Horizon

[Robert van Leeuwen]

 I've read Deploying Horizon [1] and I had a few high-level questions for you 
 about load balancing Horizon.

 1. Do you have any suggestions or recommendations for load balancing Horizon?
 2. Are there any gotchas?
 3. Can you more or less just load balance it like any other web app?

Yes you can load balance it like any webpage.

Only gotcha is the vncproxy, it uses websockets that might be problematic for 
level 7 loadbalancers.
If you use tcp loadbalancing you should be fine though.

Cheers,
Robert van Leeuwen
___
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] keystone-manage db_sync errors

[Miller, Mark M (EB SW Cloud - RD - Corvallis)]

I had difficulty with the db_sync command and had to specify the keystone.conf 
file. I think it was trying to access a sqlite database even though I am using 
MySQL.


Ø  keystone-manage --config-file /etc/keystone/keystone.conf db_sync

Mark

From: openstack-bounces+mark.m.miller=hp@lists.launchpad.net 
[mailto:openstack-bounces+mark.m.miller=hp@lists.launchpad.net] On Behalf 
Of Atul Jha
Sent: Thursday, February 28, 2013 4:19 AM
To: Ashutosh Narayan; OpenStack
Subject: Re: [Openstack] keystone-manage db_sync errors

Looks like database connection error.

From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of 
Ashutosh Narayan [aashutoshnara...@gmail.com]
Sent: Thursday, February 28, 2013 5:42 PM
To: OpenStack
Subject: [Openstack] keystone-manage db_sync errors
Hi folks,

I following the instructions to install OpenStack on CentOS 6.3
mentioned on this 
linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
 . I am getting following errors when I execute
keystone-manage db_sync command.

[root@RLD1OPST01 ~]# keystone-manage db_sync
Traceback (most recent call last):
  File /usr/bin/keystone-manage, line 28, in module
cli.main(argv=sys.argv, config_files=config_files)
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 164, in main
return run(cmd, (args[:1] + args[2:]))
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 147, in run
return CMDS[cmd](argv=args).run()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 35, in run
return self.main()
  File /usr/lib/python2.6/site-packages/keystone/cli.py, line 56, in main
driver.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/identity/backends/sql.py, 
line 136, in db_sync
migration.db_sync()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 49, in db_sync
current_version = db_version()
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 63, in db_version
return db_version_control(0)
  File /usr/lib/python2.6/site-packages/keystone/common/sql/migration.py, 
line 68, in db_version_control
versioning_api.version_control(CONF.sql.connection, repo_path, version)
  File string, line 2, in version_control
  File /usr/lib/python2.6/site-packages/migrate/versioning/util/__init__.py, 
line 160, in with_engine
return f(*a, **kw)
  File /usr/lib/python2.6/site-packages/migrate/versioning/api.py, line 248, 
in version_control
ControlledSchema.create(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
137, in create
table = cls._create_table_version(engine, repository, version)
  File /usr/lib/python2.6/site-packages/migrate/versioning/schema.py, line 
178, in _create_table_version
if not table.exists():
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/schema.py,
 line 579, in exists
self.namehttp://self.name, schema=self.schema)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2424, in run_callable
conn = self.contextual_connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py,
 line 2490, in contextual_connect
self.pool.connect(),
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 224, in connect
return _ConnectionFairy(self).checkout()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 387, in __init__
rec = self._connection_record = pool._do_get()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 741, in _do_get
con = self._create_connection()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 188, in _create_connection
return _ConnectionRecord(self)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 270, in __init__
self.connection = self.__connect()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/pool.py,
 line 330, in __connect
connection = self.__pool._creator()
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/strategies.py,
 line 80, in connect
return dialect.connect(*cargs, **cparams)
  File 
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py,
 line 281, in connect
return self.dbapi.connect(*cargs, **cparams)
  File /usr/lib64/python2.6/site-packages/MySQLdb/__init__.py, line 81, in 
Connect
return Connection(*args, **kwargs)
  File 

[Openstack] Working with disk images

[Samuel Winchenbach]

Hi all,

I was recently tasked with creating a VM from an existing disk image.   I
was given a dd of what appears to be / and a tarball of the contents of
/home.


What do you think the best course of action is to get these into something
workable for openstack?  Everything I have done so far has been using
pre-made images.

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

Re: [Openstack] Load Balancing Horizon

[Everett Toews]

From:  Robert van Leeuwen robert.vanleeu...@spilgames.com
Date:  Thursday, February 28, 2013 9:33 AM
To:  openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject:  Re: [Openstack] Load Balancing Horizon


 I've read Deploying Horizon [1] and I had a few high-level questions for
you about load balancing Horizon.
 1. Do you have any suggestions or recommendations for load balancing
Horizon?
 2. Are there any gotchas?
 3. Can you more or less just load balance it like any other web app?

Yes you can load balance it like any webpage.

Only gotcha is the vncproxy, it uses websockets that might be problematic
for level 7 loadbalancers.
If you use tcp loadbalancing you should be fine though.

---

I'm having trouble getting Horizon (Folsom Stable) to point to Keystone at
another IP. All I should have to do is

vim openstack_dashboard/local/local_settings.py
  OPENSTACK_HOST = 123.123.123.123
sudo /etc/init.d/apache2 restart

Correct?

But the login page reads,

  An error occurred authenticating. Please try again later.

I dropped the Horizon DB and recreated it but that didn't help. Nothing
helpful in /var/log/apache2/horizon_error.log or
/var/log/apache2/horizon_access.log either.

Am I missing something obvious?

Thanks,
Everett


___
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] metadata server not responding

[Sylvain Bauza]

Metadata can be fetched from http://169.254.169.254:80/latest/metadata
Could you please tcpdump -nn -i your bridge intf. on your node running 
nova-network and check if you see request coming in ?


-Sylvain



Le 28/02/2013 17:29, mohammad kashif a écrit :


Hi

I have installed openstack on two node setup with rhel6.4. I am using 
nova-network with multi_host=True. Everything is running on controller 
node and second node is running nova-compute, nova-network and 
nova-api-metadata. I can create vm's and it is getting ip address but 
metadata server is not responding. I can see that it is running


lsof -i:8775
COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nova-api- 8009 nova4u  IPv4  28815  0t0  TCP *:8775 (LISTEN)

curl http://169.254.169.254:8775

html
 head
  title404 Not Found/title
 /head
 body
  h1404 Not Found/h1
  The resource could not be found.br /br /
 /body

in metadata log file

8009 ERROR nova.api.metadata.handler [-] Failed to get metadata for 
ip: 169.254.169.254


iptable looking ok to me (I dont have much experience with iptable)

DNAT   tcp  --  anywhere 169.254.169.254 tcp dpt:http 
to:192.168.9.3:8775 http://192.168.9.3:8775


192.168.9.3 is the address of compute node.

Can some one suggest something please.

Thanks

Kashif







___
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] Load Balancing Horizon

[Everett Toews]

On 2/28/13 10:26 AM, Everett Toews everett.to...@rackspace.com wrote:

I'm having trouble getting Horizon (Folsom Stable) to point to Keystone at
another IP. All I should have to do is

vim openstack_dashboard/local/local_settings.py
  OPENSTACK_HOST = 123.123.123.123
sudo /etc/init.d/apache2 restart

Correct?

But the login page reads,

  An error occurred authenticating. Please try again later.

I dropped the Horizon DB and recreated it but that didn't help. Nothing
helpful in /var/log/apache2/horizon_error.log or
/var/log/apache2/horizon_access.log either.

Am I missing something obvious?

Oops. I just needed to clear my browser cache (did a Command-Shift-r in
Chrome). The above setting works.

Thanks for listening,
Everett


___
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] Working with disk images

[Razique Mahroua]

Hey Samuel,What OS is it?
Regards,
Razique Mahroua-Nuage  Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15

Le 28 févr. 2013 à 17:19, Samuel Winchenbach swinc...@gmail.com a écrit :Hi all,
I was recently tasked with creating a VM from an existing disk image.  I was given a "dd" of what appears to be / and a tarball of the contents of /home.
What do you think the best course of action is to get these into something workable for openstack? Everything I have done so far has been using pre-made images.
Thanks,
Sam
___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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] Working with disk images

[Samuel Winchenbach]

*[swinchen@strongbad etc]$ cat debian_version *
*squeeze/sid*


On Thu, Feb 28, 2013 at 11:46 AM, Razique Mahroua razique.mahr...@gmail.com
 wrote:

 Hey Samuel,
 What OS is it?

 Regards,
 *Razique Mahroua** - **Nuage  Co*
 razique.mahr...@gmail.com
 Tel : +33 9 72 37 94 15


 Le 28 févr. 2013 à 17:19, Samuel Winchenbach swinc...@gmail.com a écrit
 :

 Hi all,

 I was recently tasked with creating a VM from an existing disk image.   I
 was given a dd of what appears to be / and a tarball of the contents of
 /home.


 What do you think the best course of action is to get these into something
 workable for openstack?  Everything I have done so far has been using
 pre-made images.

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



NUAGECO-LOGO-Fblan_petit.jpg___
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] keystone-manage db_sync errors

[Swapnil Kulkarni]

Hi Ashutosh,

Can you specify the way you have created database user and grants. Looks
like you have specified the hostname in the keystone.conf *(*Access denied
for user 'keystone'@'RLD1OPST01').

I think if you could create a user 'keystone'@'RLD1OPST01' and grant it
access to keystone database, it will solve your issue.

-- 
Best Regards,
Swapnil Kulkarni

On Thu, Feb 28, 2013 at 5:39 PM, Ashutosh Narayan 
aashutoshnara...@gmail.com wrote:

 Hi folks,

 I following the instructions to install OpenStack on CentOS 6.3
 mentioned on this 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
  .
 I

 --
 Ashutosh Narayan

 http://ashutoshn.wordpress.com/


 ___
 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] spice in devstack no working

[Daniel P. Berrange]

On Fri, Mar 01, 2013 at 02:33:32AM +0800, Shake Chen wrote:
 Hi
 
 I try to enable spice in devstack, but when I create vm, would report
 error. if not enable spice, it is work well.

If you want help, you're going to have to tell us much more than just
would report error.

What OS distro are you using ? What version of QEMU ? What version
of libvirt ? What is the full error (+ stack trace if any) you get ?
What tool did you see the error from ?

Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

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

[Openstack] swift multinode test

[Paras pradhan]

Hi,

I have a swift proxy node and a storage node. Also keystone resides in
another server. Swift is from ubuntu cloud archive i.e 1.7.4. I am
using private keys in swift proxy if it matters.The below command is
returning nothing and goes infinite.192.168.122.20 is my keystone
server.

--
root@controller:/var/log# swift -V 2 -A
http://192.168.122.20:35357/v2.0 -U service:swift -K service_pass stat
--

proxy-server.conf  is http://pastebin.com/B5hXqHns


How do start debugging? I am not seeing anything special on proxy node
syslog and keystone.log on keystone server.

Thanks,
Paras

___
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] [COMMUNITY] The path to Ask OpenStack

[Stefano Maffulli]

[please reply only to commun...@lists.openstack.org]

hello folks,

we all push to improve how we interact with the OpenStack users, help 
newcomers find answers to their questions and ease their path to 
adoption. That's why we kickstarted the project Ask OpenStack. We're 
installing an instance of Askbot under the openstack.org domain, with 
the help of Askbot developers. It will have a custom skin and 
authentication based on Launchpad like the rest of our services.


In the first phase it will support English and once we decide that we 
like it, we will start adding other languages so users will be able to 
ask questions and get answers in their own language.


While the technical part of Ask is being done, I'd like to start talking 
about the organization of the content of the site, the static pages, 
etc. We'll probably also need moderators and OpenStack experts that can 
help answer questions on the site. If you want to help with these tasks 
please join the Community mailing list

http://lists.openstack.org/cgi-bin/mailman/listinfo/community
where we can discuss the project further.

Thanks,
stef

___
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] Keystone Grizzly-3 Tokens not getting saved to database

[Miller, Mark M (EB SW Cloud - RD - Corvallis)]

Hello,

I have some tests that attempt to retrieve tenants/projects from Keystone using 
an admin user's token. The test gave the following error:

{error: {message: coercing to Unicode: need string or buffer, NoneType 
found, code: 400, title: Bad Request}}

The same code works fine if I use the X-Auth-Token from the keystone.conf file. 
I checked the database to look at the tokens and found that the token table 
is empty. Does anyone have any ideas as to why tokens are not getting stored on 
my system? I assume it is some keystone.conf parameter, but I really do not 
know.

Regards,

Mark
___
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] Keystone Grizzly-3 Tokens not getting saved to database

[KangEdda]

Please give us details on your keystone.conf parameter and it's handler. You 
know that unicode takes 2 bytes right? :D

Regards,

Edda Kang
The purpose of life is to live it, to taste experience to the utmost, to reach 
out eagerly and without fear for newer and richer experience. 


From: mark.m.mil...@hp.com
To: openstack@lists.launchpad.net
Date: Thu, 28 Feb 2013 23:23:46 +
Subject: [Openstack] Keystone Grizzly-3 Tokens not getting saved to database









Hello,
 
I have some tests that attempt to retrieve tenants/projects from Keystone using 
an admin user’s token. The test gave the following error:
 
{error: {message: coercing to Unicode: need string or buffer, NoneType 
found, code: 400, title: Bad Request}}
 
The same code works fine if I use the X-Auth-Token from the keystone.conf file. 
I checked the database to look at the tokens and found that the “token” table 
is empty. Does anyone have any ideas as to why tokens are not getting stored on
 my system? I assume it is some keystone.conf parameter, but I really do not 
know.
 
Regards,
 
Mark




___
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] [Nova] Right method to delete a tap interface

[Edgar Magana]

Hi,

I found a method to create a tap interface under:
nova/nova/network/linux_net.py
def create_tap_dev(dev, mac_address=None):

But I can't find the one for deleting a tap interface, can somebody tell me
the right way to do it?

Thanks,

Edgar


___
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] [Nova] Right method to delete a tap interface

[Chris Wright]

* Edgar Magana (emag...@plumgrid.com) wrote:
 I found a method to create a tap interface under:
 nova/nova/network/linux_net.py
 def create_tap_dev(dev, mac_address=None):
 
 But I can't find the one for deleting a tap interface, can somebody tell me
 the right way to do it?

I believe it's done w/ ip link delete which is hand coded in a couple
of spots.  One caller of create_tap_dev QuantumLinuxBridgeInterfaceDriver::plug 
does it in ::unplug (opencoded).  Other 
LibvirtGenericVIFDriver::plug_ovs_ethernet does it in unplug_ovs_ethernet via 
delete_ovs_vif_port

thanks,
-chris

___
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] spice in devstack no working

[Vishvananda Ishaya]

The default build of kvm-qemu does not have spice support on ubuntu-precise. If 
you are running on ubuntu you might have to do:

sudo apt-get install qemu-kvm-spice

Devstack should probably be modified to install that package if n-spice is 
enabled.

Vish

On Feb 28, 2013, at 10:33 AM, Shake Chen shake.c...@gmail.com wrote:

 Hi
 
 I try to enable spice in devstack, but when I create vm, would report error. 
 if not enable spice, it is work well.
 
 the below is my localrc
 
 HOST_IP=10.1.199.6
 ADMIN_PASSWORD=password
 MYSQL_PASSWORD=password
 RABBIT_PASSWORD=password
 SERVICE_PASSWORD=password
 SERVICE_TOKEN=password
 disable_service n-net
 disable_service n-novnc
 disable_service n-xvnc
 enable_service n-spice
 enable_service q-svc
 enable_service q-agt
 enable_service q-dhcp
 enable_service q-l3
 enable_service quantum
 enable_service g-api
 enable_service q-meta
 #enable_service tempest
 enable_service rabbit
 LOG=True
 SCHEDULER=nova.scheduler.simple.SimpleScheduler
 FIXED_RANGE=10.5.5.0/24
 NETWORK_GATEWAY=10.5.5.1
 FLOATING_RANGE=10.1.199.128/25
 EXT_GW_IP=10.1.199.1
 
 
 
 
 -- 
 Shake Chen
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
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] spice in devstack no working

[Shake Chen]

On Fri, Mar 1, 2013 at 11:18 AM, Vishvananda Ishaya
vishvana...@gmail.comwrote:

 The default build of kvm-qemu does not have spice support on
 ubuntu-precise. If you are running on ubuntu you might have to do:

 sudo apt-get install qemu-kvm-spice

 Devstack should probably be modified to install that package if n-spice is
 enabled.


Thanks, I solve the problem. Now I can create VM sccessful after install
qemu-kvm-spice

but when I access the console, is black. not show anything. the below show

1: Unknown message type 1!




 Vish

 On Feb 28, 2013, at 10:33 AM, Shake Chen shake.c...@gmail.com wrote:

 Hi

 I try to enable spice in devstack, but when I create vm, would report
 error. if not enable spice, it is work well.

 the below is my localrc

 HOST_IP=10.1.199.6
 ADMIN_PASSWORD=password
 MYSQL_PASSWORD=password
 RABBIT_PASSWORD=password
 SERVICE_PASSWORD=password
 SERVICE_TOKEN=password
 disable_service n-net
 disable_service n-novnc
 disable_service n-xvnc
 enable_service n-spice
 enable_service q-svc
 enable_service q-agt
 enable_service q-dhcp
 enable_service q-l3
 enable_service quantum
 enable_service g-api
 enable_service q-meta
 #enable_service tempest
 enable_service rabbit
 LOG=True
 SCHEDULER=nova.scheduler.simple.SimpleScheduler
 FIXED_RANGE=10.5.5.0/24
 NETWORK_GATEWAY=10.5.5.1
 FLOATING_RANGE=10.1.199.128/25
 EXT_GW_IP=10.1.199.1




 --
 Shake Chen

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





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

Re: [Openstack] Keystone and Swift Integration

[Gareth]

That 8080 is set in proxy conf
 X-Auth-Token is generated by keystone(actually keystoneclient) and sent by
swift. That't the token for admin:admin
admin_token is set in keystone conf

service_port = 5000
service_host = 127.0.0.1
auth_port = 35357
auth_host = 127.0.0.1
auth_protocol = http
auth_uri = http://127.0.0.1:5000/
auth_token = 012345SECRET99TOKEN012345
admin_token = 012345SECRET99TOKEN012345
admin_tenant_name = service
admin_user = swift
admin_password = swift

Such things depend on your env, which data you build in keystone. But some
details need to check documents. (checking source codes is better[?])

On Thu, Feb 28, 2013 at 11:07 PM, Julian Learmonth 
julian.learmo...@mobius.co.uk wrote:

 Hi,

 I've built an OpenStack (Folsom) demo VM (Ubuntu 12.10) and manually
 installed Swift. I am trying to get Swift to use Keystone for
 authentication, but am having trouble finding what I need to do to the
 /etc/swift/swift-proxy.conf file. The instructions I have been following
 say I should Configure the paste file for swift-proxy
 (`/etc/swift/swift-proxy.conf`), but I don't know what needs to be done.
 The document I am following is here:
 http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-swift-to-use-keystone.html

 I've only been using OpenStack for about a week, so my apologies if this
 is obvious, but I can't figure it out. I've tried googling the config file,
 but I just get the document I am using (or the previous Wessex version) and
 there's no sample file in the Swift distribution.

 The second config file I need to edit is the /etc/swift/proxy-swift.conf
 file. I have a couple of questions about this too. There's a section I need
 to paste into it as follows:

 ===
 [filter:authtoken]
 paste.filter_factory = keystone.middleware.auth_token:filter_factory
 # Delaying the auth decision is required to support token-less
 # usage for anonymous referrers ('.r:*').
 delay_auth_decision = 10
 service_port = 5000
 service_host = 127.0.0.1
 auth_port = 35357
 auth_host = 127.0.0.1
 auth_protocol = http
 auth_uri = http://127.0.0.1:5000/
 auth_token = 012345SECRET99TOKEN012345
 admin_token = 012345SECRET99TOKEN012345
 admin_tenant_name = service
 admin_user = swift
 admin_password = swift
 ===

 Do I need to change the auth port? I can run the following command
 successfully:

 ===
 root@openstack02:/home/stack/bin# curl -v -H 'X-Storage-User:
 admin:admin' -H 'X-Storage-Pass: admin' http://127.0.0.1:8080/auth/v1.0
 * About to connect() to 127.0.0.1 port 8080 (#0)
 *   Trying 127.0.0.1...
 * connected
 * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
  GET /auth/v1.0 HTTP/1.1
  User-Agent: curl/7.27.0
  Host: 127.0.0.1:8080
  Accept: */*
  X-Storage-User: admin:admin
  X-Storage-Pass: admin
 
 * additional stuff not fine transfer.c:1037: 0 0
 * HTTP 1.1 or later with persistent connection, pipelining supported
  HTTP/1.1 200 OK
  X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_admin
  X-Auth-Token: AUTH_tk0022e539fae64647883b9fa529311982
  Content-Type: text/html; charset=UTF-8
  X-Storage-Token: AUTH_tk0022e539fae64647883b9fa529311982
  Content-Length: 0
  Date: Wed, 28 Feb 2013 15:00:02 GMT
 
 * Connection #0 to host 127.0.0.1 left intact
 * Closing connection #0
 root@openstack02:/home/stack/bin#
 ===

 So does that mean by auth_port is 8080? I assume that the X-Auth-Token is
 both the admin_token and auth_token? Is the admin_user (given the example
 above) going to be admin:admin?

 Any assistance would very much be appreciated!

 Regards,
 Julian.


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




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to the organization specified by you.*
360.gif___
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] swift multinode test

[Gareth]

That goes infinite seems like waiting connection. You should check
connection first.

To use curl any_url is ok. Any response depends on successful connection.


On Fri, Mar 1, 2013 at 5:41 AM, Paras pradhan pradhanpa...@gmail.comwrote:

 Hi,

 I have a swift proxy node and a storage node. Also keystone resides in
 another server. Swift is from ubuntu cloud archive i.e 1.7.4. I am
 using private keys in swift proxy if it matters.The below command is
 returning nothing and goes infinite.192.168.122.20 is my keystone
 server.

 --
 root@controller:/var/log# swift -V 2 -A
 http://192.168.122.20:35357/v2.0 -U service:swift -K service_pass stat
 --

 proxy-server.conf  is http://pastebin.com/B5hXqHns


 How do start debugging? I am not seeing anything special on proxy node
 syslog and keystone.log on keystone server.

 Thanks,
 Paras

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




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to the organization specified by you.*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] keystone-manage db_sync errors

[Ashutosh Narayan]

On Thu, Feb 28, 2013 at 11:15 PM, Swapnil Kulkarni 
swapnilkulkarni2...@gmail.com wrote:

 Hi Ashutosh,

 Can you specify the way you have created database user and grants. Looks
 like you have specified the hostname in the keystone.conf *(*Accessdenied
 for user 'keystone'@'RLD1OPST01').

I followed the instruction mentioned on wiki.


 I think if you could create a user 'keystone'@'RLD1OPST01' and grant it
 access to keystone database, it will solve your issue.


Yes that's what I did to resolve the issue.


 --
 Best Regards,
 Swapnil Kulkarni

 On Thu, Feb 28, 2013 at 5:39 PM, Ashutosh Narayan 
 aashutoshnara...@gmail.com wrote:

 Hi folks,

 I following the instructions to install OpenStack on CentOS 6.3
 mentioned on this 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/install-keystone.html
  .
 I


 --
 Ashutosh Narayan

 http://ashutoshn.wordpress.com/


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








-- 
Ashutosh Narayan

http://ashutoshn.wordpress.com/
___
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] Error while executing sample_data.sh script

[Atul Jha]

Ashutosh,

my suggestion would be go through the documentation try to understand what each 
keystone command is doing. Just running a script and mailing to list for 
everything is not a good idea.

Spend sometime with document, understand key concepts. just a suggestion.


From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of 
Ashutosh Narayan [aashutoshnara...@gmail.com]
Sent: Friday, March 01, 2013 12:14 PM
To: OpenStack
Subject: [Openstack] Error while executing sample_data.sh script

Hi folks,

When I run the sample_data.sh script mentioned at the 
linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/scripted-keystone-setup.html
 I get the following errors :

Conflict occurred attempting to store user. (IntegrityError) (1062, Duplicate 
entry 'admin' for key 'name') (HTTP 409)
Conflict occurred attempting to store role. (IntegrityError) (1062, Duplicate 
entry 'admin' for key 'name') (HTTP 409)
usage: keystone user-role-add --user-id user-id --role-id role-id
  [--tenant-id tenant-id]
keystone user-role-add: error: argument --user-id/--user_id: expected one 
argument
Conflict occurred attempting to store tenant. (IntegrityError) (1062, 
Duplicate entry 'service' for key 'name') (HTTP 409)
Conflict occurred attempting to store user. (IntegrityError) (1062, Duplicate 
entry 'glance' for key 'name') (HTTP 409)
usage: keystone user-role-add --user-id user-id --role-id role-id
  [--tenant-id tenant-id]
keystone user-role-add: error: argument --user-id/--user_id: expected one 
argument
usage: keystone user-create --name user-name [--tenant-id tenant-id]
[--pass pass] [--email email]
[--enabled true|false]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id user-id --role-id role-id
  [--tenant-id tenant-id]
keystone user-role-add: error: argument --user-id/--user_id: expected one 
argument
usage: keystone user-create --name user-name [--tenant-id tenant-id]
[--pass pass] [--email email]
[--enabled true|false]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id user-id --role-id role-id
  [--tenant-id tenant-id]
keystone user-role-add: error: argument --user-id/--user_id: expected one 
argument
usage: keystone user-create --name user-name [--tenant-id tenant-id]
[--pass pass] [--email email]
[--enabled true|false]
keystone user-create: error: argument --tenant-id: expected one argument
usage: keystone user-role-add --user-id user-id --role-id role-id
  [--tenant-id tenant-id]
keystone user-role-add: error: argument --user-id/--user_id: expected one 
argument
+-+---+
|   Property  | Value |
+-+---+
|   adminurl  |  http://localhost:$(admin_port)s/v2.0 |
|  id |626ff3533c7e452e8850a94e4d30309f   |
| internalurl | http://localhost:$(public_port)s/v2.0 |
|  publicurl  | http://localhost:$(public_port)s/v2.0 |
|region   |   RegionOne   |
|  service_id |1fe65f54d1714d369f7b8975de89d41d   |
+-+---+
+-+--+
|   Property  |Value |
+-+--+
|   adminurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
|  id |   64206e8f1b6148a0b63870c5fd333887   |
| internalurl | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
|  publicurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
|region   |  RegionOne   |
|  service_id |   1c4096b5d6874d9cb9a51757ea86bbb0   |
+-+--+
+-++
|   Property  | Value  |
+-++
|   adminurl  | http://localhost:8776/v1/$(tenant_id)s |
|  id |8d2f5fb8fad341a19a88f1f092906425|
| internalurl | http://localhost:8776/v1/$(tenant_id)s |
|  publicurl  | http://localhost:8776/v1/$(tenant_id)s |
|region   |   RegionOne|
|  service_id |c50cce67fb7f44f888558112381240bf|
+-++
+-+--+
|   Property  |  Value

Re: [Openstack] Error while executing sample_data.sh script

[Ashutosh Narayan]

I will give value to your suggestion. Thanks

On Fri, Mar 1, 2013 at 12:21 PM, Atul Jha atul@csscorp.com wrote:

  Ashutosh,

 my suggestion would be go through the documentation try to understandwhat 
 each keystone command is doing. Just running a script and mailing to
 list for everything is not a good idea.

 Spend sometime with document, understand key concepts. just a suggestion.

  --
 *From:* 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 *Sent:* Friday, March 01, 2013 12:14 PM
 *To:* OpenStack
 *Subject:* [Openstack] Error while executing sample_data.sh script

   Hi folks,

  When I run the sample_data.sh script mentioned at the 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/scripted-keystone-setup.html
  I
 get the following errors :

  Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 Conflict occurred attempting to store role. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 Conflict occurred attempting to store tenant. (IntegrityError) (1062,
 Duplicate entry 'service' for key 'name') (HTTP 409)
 Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'glance' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 +-+---+
 |   Property  | Value |
 +-+---+
 |   adminurl  |  http://localhost:$(admin_port)s/v2.0 |
 |  id |626ff3533c7e452e8850a94e4d30309f   |
 | internalurl | http://localhost:$(public_port)s/v2.0 |
 |  publicurl  | http://localhost:$(public_port)s/v2.0 |
 |region   |   RegionOne   |
 |  service_id |1fe65f54d1714d369f7b8975de89d41d   |
 +-+---+
 +-+--+
 |   Property  |Value |
 +-+--+
 |   adminurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  id |   64206e8f1b6148a0b63870c5fd333887   |
 | internalurl | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  publicurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |region   |  RegionOne   |
 |  service_id |   1c4096b5d6874d9cb9a51757ea86bbb0   |
 +-+--+
 +-++
 |   Property  | Value  |
 +-++
 |   adminurl  | http://localhost:8776/v1/$(tenant_id)s |
 |  id |8d2f5fb8fad341a19a88f1f092906425|
 | internalurl | http://localhost:8776/v1/$(tenant_id)s |
 |  publicurl  | http://localhost:8776/v1/$(tenant_id)s |
 |region   |   RegionOne

Re: [Openstack] Error while executing sample_data.sh script

[Swapnil Kulkarni]

I agree with Atul, if you go through documentation you will find where to
change the passwords required by keystone commands.

Cheers :)
On Mar 1, 2013 12:22 PM, Atul Jha atul@csscorp.com wrote:

  Ashutosh,

 my suggestion would be go through the documentation try to understandwhat 
 each keystone command is doing. Just running a script and mailing to
 list for everything is not a good idea.

 Spend sometime with document, understand key concepts. just a suggestion.

  --
 *From:* 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 *Sent:* Friday, March 01, 2013 12:14 PM
 *To:* OpenStack
 *Subject:* [Openstack] Error while executing sample_data.sh script

   Hi folks,

  When I run the sample_data.sh script mentioned at the 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/scripted-keystone-setup.html
  I
 get the following errors :

  Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 Conflict occurred attempting to store role. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 Conflict occurred attempting to store tenant. (IntegrityError) (1062,
 Duplicate entry 'service' for key 'name') (HTTP 409)
 Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'glance' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 +-+---+
 |   Property  | Value |
 +-+---+
 |   adminurl  |  http://localhost:$(admin_port)s/v2.0 |
 |  id |626ff3533c7e452e8850a94e4d30309f   |
 | internalurl | http://localhost:$(public_port)s/v2.0 |
 |  publicurl  | http://localhost:$(public_port)s/v2.0 |
 |region   |   RegionOne   |
 |  service_id |1fe65f54d1714d369f7b8975de89d41d   |
 +-+---+
 +-+--+
 |   Property  |Value |
 +-+--+
 |   adminurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  id |   64206e8f1b6148a0b63870c5fd333887   |
 | internalurl | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  publicurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |region   |  RegionOne   |
 |  service_id |   1c4096b5d6874d9cb9a51757ea86bbb0   |
 +-+--+
 +-++
 |   Property  | Value  |
 +-++
 |   adminurl  | http://localhost:8776/v1/$(tenant_id)s |
 |  id |8d2f5fb8fad341a19a88f1f092906425|
 | internalurl | http://localhost:8776/v1/$(tenant_id)s |
 |  publicurl  | 

Re: [Openstack] keystone/horizon/dashboard

[Matthias Runge]

On 02/28/2013 01:31 PM, Mballo Cherif wrote:
 Hello everybody !
 
  
 
 I need help,
 
 when i try to authenticate with the dashboard I have this “An error
 occurred authenticating. Please try again later.” What is wrong with
 keystone or horizon?
 
 How can I fix this issue?
 
Verify, that
OPENSTACK_HOST (found in local_settings) points to your keystone and
also that keystone is reachable from your horizon host (verify
especially port 5000 on OPENSTACK_HOST is reachable, telnet my be your
friend.

If that works, you need to look at keystone: -verify database is
running, e.g.

Matthias

___
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] Error while executing sample_data.sh script

[Ashutosh Narayan]

Hi Swapnil, Atul

Reading document helps. I have done these steps manually before and
was again going ahead to run the script for the same. That's why I got
so many error messages. Looks like problem is solved. I get the
desired output.

On Fri, Mar 1, 2013 at 12:39 PM, Swapnil Kulkarni 
swapnilkulkarni2...@gmail.com wrote:

 I agree with Atul, if you go through documentation you will find where to
 change the passwords required by keystone commands.

 Cheers :)
 On Mar 1, 2013 12:22 PM, Atul Jha atul@csscorp.com wrote:

  Ashutosh,

 my suggestion would be go through the documentation try to understandwhat 
 each keystone command is doing. Just running a script and mailing to
 list for everything is not a good idea.

 Spend sometime with document, understand key concepts. just a suggestion.

  --
 *From:* 
 openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Ashutosh Narayan [
 aashutoshnara...@gmail.com]
 *Sent:* Friday, March 01, 2013 12:14 PM
 *To:* OpenStack
 *Subject:* [Openstack] Error while executing sample_data.sh script

   Hi folks,

  When I run the sample_data.sh script mentioned at the 
 linkhttp://docs.openstack.org/folsom/openstack-compute/install/yum/content/scripted-keystone-setup.html
  I
 get the following errors :

  Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 Conflict occurred attempting to store role. (IntegrityError) (1062,
 Duplicate entry 'admin' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 Conflict occurred attempting to store tenant. (IntegrityError) (1062,
 Duplicate entry 'service' for key 'name') (HTTP 409)
 Conflict occurred attempting to store user. (IntegrityError) (1062,
 Duplicate entry 'glance' for key 'name') (HTTP 409)
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 usage: keystone user-create --name user-name [--tenant-id tenant-id]
 [--pass pass] [--email email]
 [--enabled true|false]
 keystone user-create: error: argument --tenant-id: expected one argument
 usage: keystone user-role-add --user-id user-id --role-id role-id
   [--tenant-id tenant-id]
 keystone user-role-add: error: argument --user-id/--user_id: expected one
 argument
 +-+---+
 |   Property  | Value |
 +-+---+
 |   adminurl  |  http://localhost:$(admin_port)s/v2.0 |
 |  id |626ff3533c7e452e8850a94e4d30309f   |
 | internalurl | http://localhost:$(public_port)s/v2.0 |
 |  publicurl  | http://localhost:$(public_port)s/v2.0 |
 |region   |   RegionOne   |
 |  service_id |1fe65f54d1714d369f7b8975de89d41d   |
 +-+---+
 +-+--+
 |   Property  |Value |
 +-+--+
 |   adminurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  id |   64206e8f1b6148a0b63870c5fd333887   |
 | internalurl | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |  publicurl  | http://localhost:$(compute_port)s/v1.1/$(tenant_id)s |
 |region   |  RegionOne   |
 |  service_id |   1c4096b5d6874d9cb9a51757ea86bbb0   |
 +-+--+
 

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

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/372/Project:precise_grizzly_quantum_trunkDate of build:Thu, 28 Feb 2013 03:31:10 -0500Build duration:1 min 32 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove deprecated assertEquals alias.by motokieditquantum/tests/unit/test_extension_security_group.pyeditquantum/tests/unit/test_agent_config.pyeditquantum/tests/unit/test_attributes.pyeditquantum/tests/unit/midonet/test_midonet_lib.pyeditquantum/tests/unit/test_servicetype.pyeditquantum/tests/unit/nicira/test_nicira_plugin.pyeditquantum/tests/unit/test_security_groups_rpc.pyeditquantum/tests/unit/bigswitch/test_router_db.pyeditquantum/tests/unit/nicira/test_networkgw.pyeditquantum/tests/unit/test_extension_extraroute.pyeditquantum/tests/unit/midonet/test_midonet_plugin.pyeditquantum/tests/unit/test_extension_portsecurity.pyeditquantum/tests/unit/test_db_plugin.pyeditquantum/tests/unit/test_db.pyConsole Output[...truncated 1601 lines...]Writing quantum-2013.1.a67.gc507251/setup.cfgcreating distCreating tar archiveremoving 'quantum-2013.1.a67.gc507251' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 2013.1.a67.gc507251INFO:root:Building package using /tmp/tmpS4PESw/quantum_2013.1.a67.gc507251+git201302280331~precise.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:c5072518ca69e772836105f7c677dd62ca8150e6INFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '919976ab48c563c7e868acf9c6499386b79e88df..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 2013.1.a29.g919976a+git201302252001~precise.+N  debian/quantum-server.default M  debian/changelog M  debian/control-D  debian/quantum-server.default M  debian/rulesText conflict in debian/rules1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpS4PESw/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpS4PESw/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 919976ab48c563c7e868acf9c6499386b79e88df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
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 #790

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
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_nova_trunk #791

[openstack-testing-bot]

Title: raring_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/791/Project:raring_grizzly_nova_trunkDate of build:Thu, 28 Feb 2013 12:12:24 -0500Build duration:14 minBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 21722 lines...]deleting and forgetting pool/main/n/nova/nova-console_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-novncproxy_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-spiceproxy_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1.a4707.ge6b49c8+git201302271632~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 561.INFO:root:Storing current commit for next build: 40680d96302a266f2d56dcf3031ce7b27f260018INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpVuQ2lJ/novamk-build-deps -i -r -t apt-get -y /tmp/tmpVuQ2lJ/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e6b49c871660391da944e31aba66db3f80bc144a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1.a4727.g1767893+git201302281213~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [40680d9] Don't blindly skip first migration.dch -a [5fc5c6a] Imported Translations from Transifexdch -a [547a9d7] Fix `with_data` handling in test-migrations.dch -a [09a3566] BM Migration 004: Actually drop columndch -a [2c0065f] Actually run baremetal migration tests.dch -a [08a2c68] Bump python-quantumclient version to 2.1.2dch -a [3036eb4] Makes sure required powervm config options are setdch -a [0b23bdf] Migration 148: Fix drop table dependency orderdch -a [e62d0cb] Migration 147: Prevent duplicate aggregate_hostsdch -a [d10a2e1] Add API Sample tests for Snapshots extension.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1.a4727.g1767893+git201302281213~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1.a4727.g1767893+git201302281213~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1.a4727.g1767893+git201302281213~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1.a4727.g1767893+git201302281213~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_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: raring_grizzly_deploy #76

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/76/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 12:26:31 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13187 lines...]Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1045, in _inlineCallbacksresult = g.send(result)  File "/usr/lib/python2.7/dist-packages/juju/state/utils.py", line 257, in _get_node_valuereturnValue(node_data.get(key, default))  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1022, in returnValueraise _DefGen_Return(val)_DefGen_Return2013-02-28 13:13:07,235 ERROR Machine provider information missing: machine 48Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1045, in _inlineCallbacksresult = g.send(result)  File "/usr/lib/python2.7/dist-packages/juju/state/utils.py", line 257, in _get_node_valuereturnValue(node_data.get(key, default))  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1022, in returnValueraise _DefGen_Return(val)_DefGen_Return2013-02-28 13:13:07,237 ERROR Machine provider information missing: machine 49Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1045, in _inlineCallbacksresult = g.send(result)  File "/usr/lib/python2.7/dist-packages/juju/state/utils.py", line 257, in _get_node_valuereturnValue(node_data.get(key, default))  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1022, in returnValueraise _DefGen_Return(val)_DefGen_Return2013-02-28 13:13:07,238 ERROR Machine provider information missing: machine 50Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1045, in _inlineCallbacksresult = g.send(result)  File "/usr/lib/python2.7/dist-packages/juju/state/utils.py", line 257, in _get_node_valuereturnValue(node_data.get(key, default))  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1022, in returnValueraise _DefGen_Return(val)_DefGen_Return2013-02-28 13:13:07,240 ERROR Machine provider information missing: machine 51Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1045, in _inlineCallbacksresult = g.send(result)  File "/usr/lib/python2.7/dist-packages/juju/state/utils.py", line 257, in _get_node_valuereturnValue(node_data.get(key, default))  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1022, in returnValueraise _DefGen_Return(val)_DefGen_Return2013-02-28 13:13:07,245 INFO 'status' command finished successfully+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/373/Project:precise_grizzly_quantum_trunkDate of build:Thu, 28 Feb 2013 13:31:09 -0500Build duration:1 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesEnabled add gateway to refrain from checking exit codeby gkottoneditquantum/tests/unit/test_linux_ip_lib.pyeditquantum/agent/linux/ip_lib.pyConsole Output[...truncated 1601 lines...]Writing quantum-2013.1.a68.g063b7ee/setup.cfgcreating distCreating tar archiveremoving 'quantum-2013.1.a68.g063b7ee' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 2013.1.a68.g063b7eeINFO:root:Building package using /tmp/tmpwJGMvL/quantum_2013.1.a68.g063b7ee+git201302281331~precise.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:063b7ee3a35a266eaf6548c30c697e3d55748288INFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '919976ab48c563c7e868acf9c6499386b79e88df..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 2013.1.a29.g919976a+git201302252001~precise.+N  debian/quantum-server.default M  debian/changelog M  debian/control-D  debian/quantum-server.default M  debian/rulesText conflict in debian/rules1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpwJGMvL/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpwJGMvL/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 919976ab48c563c7e868acf9c6499386b79e88df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #77

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/77/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 13:13:12 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13158 lines...]ERROR:root:Could not setup SSH connection to test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/374/Project:precise_grizzly_quantum_trunkDate of build:Thu, 28 Feb 2013 14:01:09 -0500Build duration:1 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove compat cfg wrapperby motokiedittools/pip-requireseditquantum/tests/unit/ryu/test_ryu_agent.pyeditquantum/api/api_common.pyeditquantum/plugins/nicira/nicira_nvp_plugin/extensions/nvp_networkgw.pyeditquantum/plugins/ryu/ryu_quantum_plugin.pyeditquantum/tests/unit/test_routerserviceinsertion.pyeditquantum/db/agents_db.pydeletequantum/openstack/common/cfg.pyeditquantum/tests/unit/test_agent_ext_plugin.pyeditquantum/plugins/openvswitch/Makefileeditquantum/extensions/loadbalancer.pyeditquantum/tests/unit/nicira/test_networkgw.pyAdd session persistence support to LBaaS HAProxy driverby obondareveditquantum/plugins/services/agent_loadbalancer/drivers/haproxy/cfg.pyaddquantum/tests/unit/services/agent_loadbalancer/driver/haproxy/test_cfg.pyAdd stats reporting to HAProxy namespace driverby obondareveditquantum/plugins/services/agent_loadbalancer/constants.pyeditquantum/plugins/services/agent_loadbalancer/drivers/haproxy/cfg.pyeditquantum/tests/unit/services/agent_loadbalancer/driver/haproxy/test_namespace_driver.pyeditquantum/plugins/services/agent_loadbalancer/drivers/haproxy/namespace_driver.pyConsole Output[...truncated 1601 lines...]Writing quantum-2013.1.a74.g06e98c9/setup.cfgcreating distCreating tar archiveremoving 'quantum-2013.1.a74.g06e98c9' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 2013.1.a74.g06e98c9INFO:root:Building package using /tmp/tmp6_D0p2/quantum_2013.1.a74.g06e98c9+git201302281401~precise.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:063b7ee3a35a266eaf6548c30c697e3d55748288INFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '919976ab48c563c7e868acf9c6499386b79e88df..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 2013.1.a29.g919976a+git201302252001~precise.+N  debian/quantum-server.default M  debian/changelog M  debian/control-D  debian/quantum-server.default M  debian/rulesText conflict in debian/rules1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmp6_D0p2/quantummk-build-deps -i -r -t apt-get -y /tmp/tmp6_D0p2/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 919976ab48c563c7e868acf9c6499386b79e88df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #78

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/78/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 13:59:52 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13140 lines...]ERROR:root:Could not setup SSH connection to test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #79

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/79/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 14:46:32 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13036 lines...]ERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #80

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/80/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 15:45:06 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 13012 lines...]ERROR:root:Could not setup SSH connection to test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #81

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/81/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 17:15:25 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 12996 lines...]ERROR:root:Could not setup SSH connection to test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #82

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/82/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 21:15:02 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 12975 lines...]ERROR:root:Could not setup SSH connection to test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_deploy #83

[openstack-testing-bot]

Title: raring_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_deploy/83/Project:raring_grizzly_deployDate of build:Thu, 28 Feb 2013 23:15:07 -0500Build duration:46 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 12975 lines...]ERROR:root:Could not setup SSH connection to test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-07.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-07.os.magners.qa.lexingtonINFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-09.os.magners.qa.lexingtonINFO:root:Archiving logs on test-04.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-04.os.magners.qa.lexingtonINFO:root:Archiving logs on test-05.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-05.os.magners.qa.lexingtonINFO:root:Archiving logs on test-11.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-11.os.magners.qa.lexingtonINFO:root:Archiving logs on test-03.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-03.os.magners.qa.lexingtonINFO:root:Archiving logs on test-06.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-06.os.magners.qa.lexingtonINFO:root:Archiving logs on test-10.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-10.os.magners.qa.lexingtonINFO:root:Archiving logs on test-02.os.magners.qa.lexingtonERROR:root:Coult not create tarball of logs on test-02.os.magners.qa.lexingtonINFO:root:Grabbing information from test-07.os.magners.qa.lexingtonERROR:root:Unable to get information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonERROR:root:Unable to get information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonERROR:root:Unable to get information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonERROR:root:Unable to get information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-05.os.magners.qa.lexingtonERROR:root:Unable to get information from test-05.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonERROR:root:Unable to get information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonERROR:root:Unable to get information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonERROR:root:Unable to get information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonERROR:root:Unable to get information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonERROR:root:Unable to get information from test-02.os.magners.qa.lexingtonTraceback (most recent call last):  File "/var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py", line 88, in connections[host]["sftp"].close()KeyError: 'sftp'+ exit 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/375/Project:precise_grizzly_quantum_trunkDate of build:Fri, 01 Mar 2013 01:31:09 -0500Build duration:1 min 14 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImported Translations from Transifexby Jenkinseditquantum/locale/quantum.potConsole Output[...truncated 1601 lines...]Writing quantum-2013.1.a75.g642b7e2/setup.cfgcreating distCreating tar archiveremoving 'quantum-2013.1.a75.g642b7e2' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 2013.1.a75.g642b7e2INFO:root:Building package using /tmp/tmpJt4jvn/quantum_2013.1.a75.g642b7e2+git201303010131~precise.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:642b7e27464083850cba0db40adfbe6cc046810eINFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '919976ab48c563c7e868acf9c6499386b79e88df..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 2013.1.a29.g919976a+git201302252001~precise.+N  debian/quantum-server.default M  debian/changelog M  debian/control-D  debian/quantum-server.default M  debian/rulesText conflict in debian/rules1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpJt4jvn/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpJt4jvn/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 919976ab48c563c7e868acf9c6499386b79e88df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/376/Project:precise_grizzly_quantum_trunkDate of build:Fri, 01 Mar 2013 02:01:11 -0500Build duration:1 min 15 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUse db model hook to filter external networkby xuhjeditquantum/plugins/nec/nec_plugin.pyeditquantum/plugins/hyperv/hyperv_quantum_plugin.pyeditquantum/db/l3_db.pyeditquantum/plugins/ryu/ryu_quantum_plugin.pyeditquantum/plugins/nicira/nicira_nvp_plugin/QuantumPlugin.pyeditquantum/plugins/linuxbridge/lb_quantum_plugin.pyeditquantum/db/db_base_plugin_v2.pyeditquantum/plugins/midonet/plugin.pyeditquantum/tests/unit/test_l3_plugin.pyeditquantum/plugins/openvswitch/ovs_quantum_plugin.pyConsole Output[...truncated 1601 lines...]Writing quantum-2013.1.a77.gcf449dd/setup.cfgcreating distCreating tar archiveremoving 'quantum-2013.1.a77.gcf449dd' (and everything under it)DEBUG:root:Derived package version from sdist tarball: 2013.1.a77.gcf449ddINFO:root:Building package using /tmp/tmpiNaERc/quantum_2013.1.a77.gcf449dd+git201303010201~precise.orig.tar.gzINFO:root:Generating git changelog entries for this packageDEBUG:root:['git', 'log', '-n1', '--no-merges', '--pretty=format:%H']DEBUG:root:642b7e27464083850cba0db40adfbe6cc046810eINFO:root:Detected previous commit - readingDEBUG:root:['git', 'log', '919976ab48c563c7e868acf9c6499386b79e88df..HEAD', '--no-merges', '--pretty=format:[%h] %s']INFO:root:Merging testing branch from launchpadDEBUG:root:['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']Not attempting to fix packaging branch ancestry, missing pristine tar data for version 2013.1.a29.g919976a+git201302252001~precise.+N  debian/quantum-server.default M  debian/changelog M  debian/control-D  debian/quantum-server.default M  debian/rulesText conflict in debian/rules1 conflicts encountered.ERROR:root:Error occurred during package creation/build: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1ERROR:root:Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpiNaERc/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpiNaERc/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 919976ab48c563c7e868acf9c6499386b79e88df..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/precise-grizzly --forceTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['bzr', 'merge', 'lp:~openstack-ubuntu-testing/quantum/precise-grizzly', '--force']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp