Why do I get "No portal found" error while attaching cinder volume to VM?
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 | |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
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
hey, I've got the same problem here... both solutions with me cause no change.
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.
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"