469898a451
Move all blockstorage related section files into its own subdirectory like it is done for other section files. Follow conventions for service names/project names and capitalization. Change-Id: Ibaa14ca926975c37305f3a08fa1f4e7d50eea605
21 lines
1.4 KiB
XML
21 lines
1.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
||
<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink"
|
||
version="5.0" xml:id="section_ts_duplicate_3PAR_host">
|
||
<title>Duplicate 3PAR host</title>
|
||
<section xml:id="section_ts_duplicate_3PAR_host_problem">
|
||
<title>Problem</title>
|
||
<para>This error may 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.</para>
|
||
<programlisting>Duplicate3PARHost: 3PAR Host already exists: Host wwn 50014380242B9750 already used by host cld4b5ubuntuW(id = 68. The hostname must be called 'cld4b5ubuntu‘.</programlisting>
|
||
</section>
|
||
<section xml:id="section_ts_duplicate_3PAR_host_solution">
|
||
<title>Solution</title>
|
||
<para>Change the 3PAR host name to match the one that OpenStack expects. The 3PAR host
|
||
constructed by the driver uses just the local hostname, not the fully qualified domain
|
||
name (FQDN) of the compute host. For example, if the FQDN was
|
||
<emphasis>myhost.example.com</emphasis>, just <emphasis>myhost</emphasis> would be
|
||
used as the 3PAR hostname. IP addresses are not allowed as host names on the 3PAR
|
||
storage server.</para>
|
||
</section>
|
||
</section>
|