Ask Your Question
3

Why do I get "No portal found" error while attaching cinder volume to VM?

asked 2013-04-04 02:54:59 -0500

shanthakumar K gravatar image

updated 2013-04-30 17:55:14 -0500

smaffulli gravatar image

I have 2 node openstack - Grizzly running on ubuntu 12.04 64b

All the O~S components are running & cinder services are also running, while I'm trying to attach the ext volume to vm instance im getting error

2013-02-05 11:59:32.200 1380 TRACE nova.openstack.common.rpc.amqp Command: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node -T iqn.2010-10.org.openstack:volume-d01a5074-3952-4e57-a8dc-780dd6aeba4f -p 10.1.0.1:3260 --rescan
2013-02-05 11:59:32.200 1380 TRACE nova.openstack.common.rpc.amqp Exit code: 255
2013-02-05 11:59:32.200 1380 TRACE nova.openstack.common.rpc.amqp Stdout: ''
2013-02-05 11:59:32.200 1380 TRACE nova.openstack.common.rpc.amqp Stderr: 'iscsiadm: No portal found.\n'

O~S & cinder services

root@ubuntu:/home/user# nova-manage service list
Binary           Host                                 Zone             Status     State Updated_At
nova-consoleauth ubuntu                               internal         enabled    :-)   2013-02-05 07:08:34
nova-cert        ubuntu                               internal         enabled    :-)   2013-02-05 07:08:36
nova-conductor   ubuntu                               internal         enabled    :-)   2013-02-05 07:08:31
nova-scheduler   ubuntu                               internal         enabled    :-)   2013-02-05 07:08:32
nova-compute     ubuntu                               nova             enabled    :-)   2013-02-05 07:08:33
root@ubuntu:/home/user#

user@ubuntu:~$ cinder list
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
|                  ID                  |   Status  | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| d01a5074-3952-4e57-a8dc-780dd6aeba4f | attaching |     test     |  1   |     None    |  false   |             |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
edit retag flag offensive close merge delete

Comments

I i think i have a similar problem but it is in Folsom not in grizzly and Ubuntu 12.04.However, I can not start instances with attached Volumes of Cinder. The volumes can be created, When I start an instance with no volume then it will be created and then still can not attach volume

OMaller gravatar imageOMaller ( 2013-04-04 07:01:26 -0500 )edit

hey, I've got the same problem here... both solutions with me cause no change.

r-muhl gravatar imager-muhl ( 2013-04-30 06:03:33 -0500 )edit
2

tgtadm is fine and actually preferred for your iscsi_helper, switching around can cause issues but if you started with that it should be fine. I would suggest you verify that you can ping the cinder node (192.168.128.129) from your compute node.

jgriffith gravatar imagejgriffith ( 2013-04-30 09:24:32 -0500 )edit
1

FYI, posting an answer with a "me too" doesn't help much and adds confusion for folks (like me :) ) when I confuse your config files with the original posters. :) You can add a comment stating that you're experiencing the problem as well and ask for help that way, but it's not an "answer"

jgriffith gravatar imagejgriffith ( 2013-04-30 09:28:45 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
9

answered 2013-05-03 11:05:01 -0500

briancline gravatar image

updated 2013-05-07 14:24:10 -0500

In addition to @obuisson's answer, here's a good checklist to run through to diagnose problems with attaching Cinder volumes:

  • Ensure the sysfsutils package is installed, which provides the systool command
  • Ensure the cinder-volumes LVM volume group is active if you're using LVM: vgchange -ay cinder-volumes
  • Determine whether you have both tgt and iscsitarget installed and running. If so, remove one, and use the --purge flag with apt-get to remove the other (i.e., apt-get remove --purge iscsitarget). Then, start or restart the one you wish to keep, if it's not already running.
  • Ensure iscsid is started with service open-iscsi status
  • Verify you get something back from iscsiadm -m discovery
  • If the iscsiadm discovery returned a result, take note of the IP address and and verify you don't get any errors from iscsiadm -m discovery -t sendtargets -p 127.0.0.1:3260 (assuming 127.0.0.1:3260 is what you got from iscsiadm's discovery)
  • Check your /etc/cinder/cinder.conf file to ensure:
    • iscsi_helper is set to tgtadm if you're using tgt, or ietadm if you're using iscsitarget
    • iscsi_ip_address is set to the management-network (private) IP where you are running Cinder and tgt/iscsitarget
    • volume_group and volume_name_template are set correctly if using LVM
  • Check your /etc/nova/nova.conf file to ensure:
    • volume_api_class is set to nova.volume.cinder.API
    • iscsi_helper is set the same as it is in cinder.conf
    • iscsi_ip_address is set the same as it is in cinder.conf
    • volume_group and volume_name_template are the same as they are in cinder.conf, if using LVM
  • Restart all Cinder services: for ii in /etc/init.d/cinder-*; do restart $(basename $ii); done
  • Restart all Nova services: for ii in /etc/init.d/nova-*; do restart $(basename $ii); done
  • Test again with a brand new Cinder volume, since some of the info attached to volumes from previous tests may be wrong (it gets set at create time; so if the config is bad when a volume is created, the info in Cinder's DB will be bad for that volume even after you correct the config files).

I was receiving precisely the same error on a dev environment deploy yesterday and this seemed to be the most exhaustive set of things I could think of to run through to diagnose the issue. Ultimately I was able to get it working.

As always, be sure to take note of any change in the log messages each time you test a change. Good luck!

edit flag offensive delete link more

Comments

Great write-up, Brian!

VMTrooper gravatar imageVMTrooper ( 2013-08-05 13:08:37 -0500 )edit
1

answered 2013-04-11 08:22:57 -0500

obuisson gravatar image

Ensure that the tgt daemon is not running. I already had this kind of trouble with it. Try to stop tgt, restart both iscsitarget and cinder-volume. After that, create a new volume and attach to an instance.

edit flag offensive delete link more

Comments

1

tgtadm is fine if that's what was used initially. I would ask if you could provide your cinder.conf and nova.conf. I'd make sure that you can ping your cinder node from your compute node.

jgriffith gravatar imagejgriffith ( 2013-04-30 09:27:08 -0500 )edit
0

answered 2013-05-09 14:04:58 -0500

shanthakumar K gravatar image

Thanks for your resposne.

Problem got resolved , by stopping the one target.

Thats an issue with documentation.

edit flag offensive delete link more

Comments

can you confirm which target

bgyako gravatar imagebgyako ( 2013-12-10 13:50:45 -0500 )edit

I have a problem with boot instance from volume ,I have single node havana setup with bootable volume in cinder.My system not returing anything on: iscsiadm -m discovery -t sendtargets -p 127.0.0.1:3260 What should be the output of this command? what is the problem in my case?

harishamrale gravatar imageharishamrale ( 2014-03-24 11:11:02 -0500 )edit

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

6 followers

Stats

Asked: 2013-04-04 02:54:59 -0500

Seen: 7,839 times

Last updated: May 09 '13