Ask Your Question
0

Devstack stable/essex release issue

asked 2012-07-17 03:02:46 -0500

neelugaddam gravatar image

Hi,

We are trying to test the openstack with quantum stable/essex release using devstack. We are seeing the following issue at our setup:

=========================================================

  • /opt/stack/nova/bin/nova-manage network create private 10.0.0.0/24 1 4096 2012-07-16 21:47:37 WARNING nova.network.quantum.manager [req-17beca79-321c-4645-9614-8aad8a1548c9 None None] Ignoring unnecessary parameter 'network_size' 2012-07-16 21:47:37 WARNING nova.network.quantum.manager [req-17beca79-321c-4645-9614-8aad8a1548c9 None None] QuantumManager does not use 'bridge' parameter. 2012-07-16 21:47:37 WARNING nova.network.quantum.manager [req-17beca79-321c-4645-9614-8aad8a1548c9 None None] QuantumManager does not use 'bridge_interface' parameter. 2012-07-16 21:47:37 DEBUG nova.network.quantum.quantum_connection [req-17beca79-321c-4645-9614-8aad8a1548c9 None None] Quantum Client Request: POST /v1.1/tenants/default/networks.json from (pid=15691) do_request /opt/stack/nova/nova/network/quantum/client.py:182 2012-07-16 21:47:37 DEBUG nova.network.quantum.quantum_connection [req-17beca79-321c-4645-9614-8aad8a1548c9 None None] {"network": {"name": "private", "nova_id": "nova"}} from (pid=15691) do_request /opt/stack/nova/nova/network/quantum/client.py:184 Command failed, please check log for more info ++ failed ++ local r=1 ++ set +o xtrace stack.sh failed: full log in /home/stack/logs/stack.log.2012-07-16-214633

=========================================================

Our localrc file is as follows:

==============================================================

Hosts

HOST_IP=<ip of="" eth0="">

Services

ENABLED_SERVICES=g-api,g-reg,key,n-api,n-crt,n-obj,n-net,n-vol,n-sch,n-novnc,n-xvnc,n-cauth,horizon,mysql,rabbit,quantum,q-svc,q-agt,n-cpu

Networks

FIXED_NETWORK_SIZE=4096 FIXED_RANGE=10.0.0.0/24 FLAT_INTERFACE=eth1 FLOATING_RANGE=172.16.142.128/25 Q_INTERFACE=eth1

Misc

MULTI_HOST=0 SERVICE_TOKEN=xyzpdqlazydog SYSLOG=True Q_PLUGIN=openvswitch

SYSLOG=True UPLOAD_LEGACY_TTY=1 DEFAULT_IMAGE_NAME=tty-quantum

GLANCE_BRANCH=stable/essex HORIZON_BRANCH=stable/essex KEYSTONE_BRANCH=stable/essex NOVA_BRANCH=stable/essex QUANTUM_BRANCH=stable/essex SWIFT_BRANCH=1.4.8

===============================================================================

Quantum server logs :

cd /opt/stack/quantum && PYTHO ^MNPATH=.:/opt/stack/python-quantumclient: python /opt/stack/quantum/bin/quantum-s ^Merver /etc/quantum/quantum.conf Traceback (most recent call last): File "/opt/stack/quantum/bin/quantum-server", line 22, in <module> from quantum.server import main as server File "/opt/stack/quantum/quantum/server/__init__.py", line 36, in <module> from quantum import service File "/opt/stack/quantum/quantum/service.py", line 19, in <module> from quantum.common import config ImportError: No module named common

We are trying this test on ubuntu 12.04 64 bit version. Did we miss anything in our configuration ? Please help us solving this issue.

edit retag flag offensive close merge delete

11 answers

Sort by ยป oldest newest most voted
0

answered 2012-07-20 18:48:06 -0500

neelugaddam gravatar image

Thanks dan wendlandt, that solved my question.

edit flag offensive delete link more
0

answered 2012-07-17 05:06:27 -0500

danwent gravatar image

The quantum server logs point to the problem. Quantum is not running, as it cannot import quantum.common

Most likely, this is because you are running the stable/essex branch for the 'quantum' repo, but not for the 'python-quantumclient'. During essex, quantum-server imported quantum.common from the python-quantumclient, but in folsom this was removed. You likely have a folsom version of python-quantumclient, and hence, there is no quantum.common to import.

edit flag offensive delete link more
0

answered 2012-07-17 05:17:33 -0500

neelugaddam gravatar image

Hi Dan,

Thanks for your reply.

You are correct we are running stable/essex for quantum. But which branch of 'python-quantumclient' works for quantum stable/essex release. What is the working combination of branches for nova, python nova client and keystone, python keystone client. Please help me understanding the working combination of all openstack components. Is this information documented anywhere ?

edit flag offensive delete link more
0

answered 2012-07-17 05:34:19 -0500

Can you try the following config in your stackrc:

quantum client

QUANTUM_CLIENT_REPO=https://github.com/openstack/python-quantumclient QUANTUM_CLIENT_BRANCH=2012.1

edit flag offensive delete link more
0

answered 2012-07-17 15:06:30 -0500

neelugaddam gravatar image

Hi,

I have successfully installed openstack with the following changes on controller localrc file. I can launch and ping the VMs on this single node setup.

Changes in localrc file on controller :

GLANCE_BRANCH=stable/essex HORIZON_BRANCH=stable/essex KEYSTONE_BRANCH=stable/essex NOVA_BRANCH=stable/essex QUANTUM_BRANCH=stable/essex SWIFT_BRANCH=1.4.8

KEYSTONECLIENT_BRANCH=milestone-proposed NOVACLIENT_BRANCH=2012.1 QUANTUM_CLIENT_BRANCH=2012.1

Changes /etc/libvirt/qemu.conf of controller node.

Add the floowing to the file : /etc/libvirt/qemu.conf

cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc", "/dev/hpet", "/dev/net/tun", ]

When I try add the compute node with following configuration, VMs not getting launched on compute node. From the logs, there seems to be a database syncing issue. But I verified the versions of mysql and nova on controller and compute nodes and they are same.

localrc on compute node:

ENABLED_SERVICES=n-cpu,n-api,quantum,q-agt Q_PLUGIN=openvswitch LIBVIRT_TYPE=qemu

HOST_IP=<etho ip="">

Q_INTERFACE=eth1

GLANCE_HOSTPORT=<controller ip="">:9292 KEYSTONE_HOST=<controller ip=""> MYSQL_HOST=<controller ip=""> Q_HOST=<controller ip=""> RABBIT_HOST=<controller ip=""> SYSLOG_HOST=<controller ip="">

NOVA_BRANCH=stable/essex NOVACLIENT_BRANCH=2012.1 QUANTUM_BRANCH=stable/essex QUANTUM_CLIENT_BRANCH=2012.1 KEYSTONECLIENT_BRANCH=milestone-proposed

QUANTUM_CONF_DIR=/etc/quantum # This is needed because QUANTUM_CONF_DIR is not initialized.

nova compute logs on compute node:

2012-07-17 19:40:54 TRACE nova.manager Traceback (most recent call last): 2012-07-17 19:40:54 TRACE nova.manager File "/opt/stack/nova/nova/manager.py", line 167, in periodic_tasks 2012-07-17 19:40:54 TRACE nova.manager task(self, context) 2012-07-17 19:40:54 TRACE nova.manager File "/opt/stack/nova/nova/compute/manager.py", line 2293, in _heal_instance_info_cache 2012-07-17 19:40:54 TRACE nova.manager context, self.host) 2012-07-17 19:40:54 TRACE nova.manager File "/opt/stack/nova/nova/db/api.py", line 617, in instance_get_all_by_host 2012-07-17 19:40:54 TRACE nova.manager return IMPL.instance_get_all_by_host(context, host) 2012-07-17 19:40:54 TRACE nova.manager File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 114, in wrapper 2012-07-17 19:40:54 TRACE nova.manager return f(args, *kwargs) 2012-07-17 19:40:54 TRACE nova.manager File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1619, in instance_get_all_by_host 2012-07-17 19:40:54 TRACE nova.manager return _instance_get_all_query(context).filter_by(host=host).all() 2012-07-17 19:40:54 TRACE nova.manager File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 1947, in all 2012-07-17 19:40:54 TRACE nova.manager return list(self) 2012-07-17 19:40:54 TRACE nova.manager File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2057, in __iter__ 2012-07-17 19:40:54 TRACE nova.manager return self._execute_and_instances(context) 2012-07-17 19:40:54 TRACE nova.manager File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2072, in _execute_and_instances 2012-07-17 19:40:54 TRACE nova.manager result = conn.execute(querycontext.statement, self._params) 2012-07-17 19:40:54 TRACE nova.manager File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1405, in execute 2012-07-17 ... (more)

edit flag offensive delete link more
0

answered 2012-07-20 06:49:50 -0500

danwent gravatar image

this may be a database schema mismatch between what you have in mysql and what the code is expecting. Are you seeing this even if you unstack and restack? I've seen a related issue where stale pyc file in /opt/stack/nova caused problems as well, so I would suggest making sure you pull down a clean directory with the stable essex code, rather than re-using an /opt/stack/nova directory that had previously contained folsom code.

edit flag offensive delete link more
0

answered 2012-07-20 15:21:49 -0500

neelugaddam gravatar image

Hi Dan,

Yes, I am seeing the same issue when I did unstack and restack also. I did a fresh checkout of nova from stable/essex after deleting /opt/stack directory and observed the same issue. Also observed the same issue when I use the default branches of devstack of stable/essex (without changing the branch in localrc). Is there any work around to solve this isse ? Please help me .

edit flag offensive delete link more
0

answered 2012-07-20 16:30:13 -0500

danwent gravatar image

at this point, this is not a quantum issue, its a nova issue, and since its beyond my shallow knowledge of nova, I'd suggest switching it from the quantum project to the nova project above and trying to get help there.

edit flag offensive delete link more
0

answered 2012-08-06 21:47:59 -0500

What solved your question? How was this fixed? What solution/changes were made for stable/essex to work? Thanks

edit flag offensive delete link more
0

answered 2012-08-07 03:18:36 -0500

neelugaddam gravatar image

I removed /opt/stack/nova/ directory and ran the stack.sh again to reclone the nova code. With this, I did not see the issue again.

As Dan said, I too observed some stale .pyc files in the/opt/stack/nova/ in the code that was not working. Due to slow internet connection, nova is not cloning properly in my setup. So I did a manual clone of nova and copied to /opt/stack. This produced the issue for me.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-07-17 03:02:46 -0500

Seen: 73 times

Last updated: Aug 07 '12