openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #19483
Re: "nova boot" errors while attaching a volume to an instance
I'm running the same problem! And I would be grateful if someone could help
me!
root@oxala:/var/log/nova# iscsiadm -m node
200.131.6.250:3260,1
iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-i386-ephemeral-20120424
10.5.5.35:3260,1
iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-i386-ephemeral-20120424
200.131.6.250:3260,1
iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-amd64-ephemeral-20120424
10.5.5.35:3260,1
iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-amd64-ephemeral-20120424
200.131.6.250:3260,-1 iqn.2010-10.org.openstack:volume-00000006
150.164.3.236:3260,-1 iqn.2010-10.org.openstack:volume-00000002
200.131.6.250:3260,-1 iqn.2010-10.org.openstack:volume-00000005
When I'm running iscsadm -m node all my openstack-volumes got this strange
-1 (node.tpgt = -1). I've tried to create the iscsi target by hand, but I
couldnt.
If some could help me! Here is my fulll nova-compute.log:
http://paste.openstack.org/show/28109/
Thanks in advance
On Wed, Oct 31, 2012 at 6:14 PM, John Griffith
<john.griffith@xxxxxxxxxxxxx>wrote:
>
>
> On Wed, Oct 31, 2012 at 1:29 PM, Bontala, Vibhuvardhan <
> vibhuvardhan.bontala@xxxxxxx> wrote:
>
>> Hi,****
>>
>> ** **
>>
>> I am running GA bits of Folsom. I am running a two node setup where the
>> first node is the controller+compute node that has Cinder running as well.
>> The second node is merely a compute node. I am seeing an issue while
>> booting an instance from Cinder volume on both the nodes. The “nova boot”
>> operation fails while spawning the instance with the following error.****
>>
>> ** **
>>
>> [00mProcessExecutionError: Unexpected error while running command.****
>>
>> [00mCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node
>> -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
>> 192.168.150.96:3260 --rescan****
>>
>> [00mExit code: 255****
>>
>> [00mStdout: ''****
>>
>> [00mStderr: 'iscsiadm: No portal found.\n'****
>>
>> [00m****
>>
>> ** **
>>
>> I had successfully created a Cinder volume with a valid image on it.****
>>
>> ** **
>>
>>
>> +--------------------------------------+-----------+--------------+------+-------------+-------------+
>> ****
>>
>> | ID | Status | Display Name | Size
>> | Volume Type | Attached to |****
>>
>>
>> +--------------------------------------+-----------+--------------+------+-------------+-------------+
>> ****
>>
>> | 3ac4b027-905e-4318-a74e-2bdf94f5d887 | available | Volume1 | 2
>> | None | |****
>>
>>
>> +--------------------------------------+-----------+--------------+------+-------------+-------------+
>> ****
>>
>> ** **
>>
>> I even tried to discover the iSCSI targets. But it returns with “no
>> records found”.****
>>
>> ** **
>>
>> I then looked into to MySQL database for Cinder and looked at the
>> entries, specifically “provider_location” and it looked just fine.
>> 192.168.150.96 is the node where I have controller and cinder running.***
>> *
>>
>> ** **
>>
>>
>> +-----------------------------------------------------------------------------------------------+
>> ****
>>
>> |
>> provider_location
>> |****
>>
>>
>> +-----------------------------------------------------------------------------------------------+
>> ****
>>
>> |
>> NULL
>> |****
>>
>> | 192.168.150.96:3260,1
>> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 1 |
>> ****
>>
>> ** **
>>
>> I manually tried to discover the iSCSI targets and it couldn’t find any.*
>> ***
>>
>> ** **
>>
>> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m discovery -t
>> sendtargets -p 192.168.150.96:3260 192.168.150.96:3260,1
>> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887****
>>
>> iscsiadm: Connection to Discovery Address 192.168.150.96 closed****
>>
>> iscsiadm: Login I/O error, failed to receive a PDU****
>>
>> iscsiadm: retrying discovery login to 192.168.150.96****
>>
>> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T
>> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
>> 192.168.150.96:3260iscsiadm: no records found!****
>>
>> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T
>> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
>> 192.168.150.96:3260 --rescan****
>>
>> iscsiadm: No portal found.****
>>
>> stack@esg-dell-c4-s08:/etc/cinder$****
>>
>> ** **
>>
>> I am not sure what’s wrong with my setup. Any help is greatly appreciated.
>> ****
>>
>> ** **
>>
>> Thanks****
>>
>> Vibhu****
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>> Hi Vibnu,
>
> Strange, you're unable to see the target on either of the nodes? I'm
> assuming your using the default LVM storage back-end.
>
> Something to look at:
>
> "sudo tgtadm --lld iscsi --op show --mode target" - Make sure your target
> is present (on the cinder node)
>
>
> You shouldn't *need* to do this, but to trouble-shoot you could also try:
>
> "sudo iscsiadm -m discovery -p 192.168.150.96:3260 -t st"
>
> followed by trying to login.
>
> "sudo iscsiadm -m node
> -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -l"
>
> John
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
--
*guilherme* \n
\t *maluf*
Follow ups
References