Re: [Openstack] Problem with attaching disks to an instance

[Vishvananda Ishaya]

FYI iscsi_ip_prefix doesn't exist in essex.  The ip is passed back to the compute node based on what it has stored in the database, so the compute node no longer finds it through discovery and matching to the prefix.  You should only need iscsi_ip_address on the volume node to make sure that the db entry is created properly. Vish On May 15, 2012, at 12:25 AM, Razique Mahroua wrote: In fact, it looks like the service is not able to retrieve the nova-volume' IP; as if there were some issue parsing the flag or something like that. Could you try by commenting that entry on all your servers : --iscsi_ip_address  and only keep the prefix ? Razique Shashank Sahni 14 mai 2012 18:22 Hi, Oh! They are same. I just masked the values before pasting the configuration files. Although, now that I think of it, its pretty harmless. Here are the originals. controller node - http://paste.openstack.org/show/17513/ compute node - http://paste.openstack.org/show/17514/ volume node - http://paste.openstack.org/show/17515/ As per my understanding, I just need to figure out how the volume node is identified. Thank you for replying. Regards, Shashank Sahni _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Nuage & Co - Razique Mahroua razique.mahr...@gmail.com <image.jpg>   _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to     : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp