Ask Your Question
0

nova-volume startup issues

asked 2011-04-15 12:46:07 -0500

mandeep-singh gravatar image

Hi, I have setup nova-volume service on a node different than my controller & compute nodes (accessible vice-versa). I have also setup nova-volumes group. When I start the nova-volume service, it keeps on trying to start with the following message in the logs:-

2011-04-15 18:03:14,953 DEBUG nova [-] Serving nova-volume from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:283 2011-04-15 18:03:14,953 DEBUG nova [-] Full set of FLAGS: from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:284 2011-04-15 18:03:14,955 DEBUG nova [-] storage_availability_zone : nova from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,956 DEBUG nova [-] help : None from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,956 DEBUG nova [-] ec2_dmz_host : 192.168.10.37 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,956 DEBUG nova [-] compute_topic : compute from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,957 DEBUG nova [-] glance_port : 9292 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,957 DEBUG nova [-] rabbit_password : guest from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,957 DEBUG nova [-] s3_dmz : 192.168.10.37 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,957 DEBUG nova [-] aws_access_key_id : admin from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,957 DEBUG nova [-] enable_new_services : True from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,958 DEBUG nova [-] my_ip : 192.168.10.37 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,959 DEBUG nova [-] quota_max_injected_files : 5 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,959 DEBUG nova [-] zone_capabilities : ['hypervisor=xenserver;kvm', 'os=linux;windows'] from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,959 DEBUG nova [-] logdir : /var/log/nova from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,960 DEBUG nova [-] sqlite_db : nova.sqlite from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,960 DEBUG nova [-] iscsi_target_prefix : iqn.2010-10.org.openstack: from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,963 DEBUG nova [-] blades_per_shelf : 16 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,963 DEBUG nova [-] osapi_max_limit : 1000 from (pid=17524) serve /usr/lib/pymodules/python2.6/nova/service.py:287 2011-04-15 18:03:14,964 DEBUG nova [-] aoe_eth_dev : eth0 from (pid=17524) serve /usr/lib/pymodules/python2.6 ... (more)

edit retag flag offensive close merge delete
add a comment

4 answers

Sort by ยป oldest newest most voted
0

answered 2011-04-15 15:34:36 -0500

itoumsn gravatar image

Hi Mandeep,

Do you have this issue if you run nova-volume on the same node with nova-api etc. ? In other word, running a single node installation successful?

I'm suspecting that there could be sqlalchemy version mismatch among nodes. For example, the node on which nova-volume runs has a bit (but critically) older version sqlalchemy or related python lpackages.

Thanks, Masanori

edit flag offensive delete link more
add a comment
0

answered 2011-04-18 05:21:20 -0500

mandeep-singh gravatar image

Thanks Masanori. I updated the packages on all the nodes and recreated the DB. This solved the above mentioned issue an I was able to successfully create a volume but now I am getting another issue, when I do euca-attach-volume -i i-00000001 -d /dev/sdb vol-00000001:

ERROR nova [-] Exception during message handling (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/rpc.py", line 188, in _receive (nova): TRACE: rval = node_func(context=ctxt, *node_args) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 105, in decorated_function (nova): TRACE: function(self, context, instance_id, *args, *kwargs) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 743, in attach_volume (nova): TRACE: volume_id) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/manager.py", line 164, in setup_compute_volume (nova): TRACE: path = self.driver.discover_volume(context, volume_ref) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/driver.py", line 446, in discover_volume (nova): TRACE: iscsi_properties = self._get_iscsi_properties(volume) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/driver.py", line 407, in _get_iscsi_properties (nova): TRACE: (volume['name'])) (nova): TRACE: Error: Could not find iSCSI export for volume volume-00000001 (nova): TRACE:

edit flag offensive delete link more
add a comment
0

answered 2011-04-18 06:45:31 -0500

vishvananda gravatar image

did you set --iscsi_ip_prefix to a useful value? The discovery code needs to know which ip to try to connect on and it currently uses that flag. If your local network is 192.168.1.0/24 for example, try setting the prefix to 192.168.1

Vish

On Apr 17, 2011, at 10:21 PM, Mandeep Singh wrote:

Question #152930 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+q...

Mandeep Singh gave more information on the question: Thanks Masanori. I updated the packages on all the nodes and recreated the DB. This solved the above mentioned issue an I was able to successfully create a volume but now I am getting another issue, when I do euca-attach-volume -i i-00000001 -d /dev/sdb vol-00000001:

ERROR nova [-] Exception during message handling (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/rpc.py", line 188, in _receive (nova): TRACE: rval = node_func(context=ctxt, *node_args) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 105, in decorated_function (nova): TRACE: function(self, context, instance_id, *args, *kwargs) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 743, in attach_volume (nova): TRACE: volume_id) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/manager.py", line 164, in setup_compute_volume (nova): TRACE: path = self.driver.discover_volume(context, volume_ref) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/driver.py", line 446, in discover_volume (nova): TRACE: iscsi_properties = self._get_iscsi_properties(volume) (nova): TRACE: File "/usr/lib/pymodules/python2.6/nova/volume/driver.py", line 407, in _get_iscsi_properties (nova): TRACE: (volume['name'])) (nova): TRACE: Error: Could not find iSCSI export for volume volume-00000001 (nova): TRACE:

You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).

edit flag offensive delete link more
add a comment
0

answered 2011-04-18 07:07:40 -0500

mandeep-singh gravatar image

Thanks Vish Ishaya, that solved my question.

edit flag offensive delete link more
add a comment

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

subscribe to rss feed

Stats

Asked: 2011-04-15 12:46:07 -0500

Seen: 42 times

Last updated: Apr 18 '11

Related questions

Security group no effect in r1215

STEP4:Can't create a Nova administrator on CentOS(2)

libvirrt error: Connection reset by peer

Validation on flavor name

admin context in host_filter.py

Unable to see the attached volume in instance

Used Quotas are Incorrect

Anyway to terminate instances stuck in REBUILD or RESIZE state?

optimistic concurrency support [closed]

Ensure the NAT rules have been added to iptables.?