openstack/openstack-manuals
Code Issues Proposed changes
Files
f779dece392924d976143fdf3d910f0ba6a6f8a5
openstack-manuals/doc/admin-guide-cloud/source/ts_non_existent_host.rst
yangyapeng f779dece39 Adding IQN to the glossary 
Abbreviation of IQN is not easy to understand,
add a description about it.Document containing
the glossary, for example:

doc/admin-guide-cloud/source/ts_non_existent_host.rst
doc/admin-guide-cloud/source/ts_cinder_config.rst
doc/admin-guide-cloud/source/ts-duplicate-3par-host.rst
doc/admin-guide-cloud/source/blockstorage-manage-volumes.rst

Change-Id: Ia9588d4f2e081f2b7d8f6a63286c9fdbf60f6a96
2015-10-14 16:50:30 -04:00

814 B
Raw Blame History

Non-existent host

Problem

This error could be caused by a volume being exported outside of OpenStack using a host name different from the system name that OpenStack expects. This error could be displayed with the IQN if the host was exported using iSCSI.

2013-04-19 04:02:02.336 2814 ERROR cinder.openstack.common.rpc.common [-] Returning exception Not found (HTTP 404)
NON_EXISTENT_HOST - HOST '10' was not found to caller.

Solution

Host names constructed by the driver use just the local hostname, not the fully qualified domain name (FQDN) of the Compute host. For example, if the FQDN was myhost.example.com, just myhost would be used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR storage server.