Merge "Blockstorage TS files to RST"

doc/admin-guide-cloud-rst/source/blockstorage.rst

@@ -174,17 +174,17 @@ Storage installation.
    :maxdepth: 2
 
    ts_cinder_config.rst
+   ts_vol_attach_miss_sg_scan.rst
+   ts_non_existent_host.rst
+   ts_non_existent_vlun.rst
+
 
 .. TODO (MZ) Convert and include the following sections
-   include: blockstorage/section_ts_cinder_config.xml
    include: blockstorage/section_ts_multipath_warn.xml
    include: blockstorage/section_ts_eql_volume_size.xml
-   include: blockstorage/section_ts_vol_attach_miss_sg_scan.xml
    include: blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml
    include: blockstorage/section_ts_duplicate_3par_host.xml
    include: blockstorage/section_ts_failed_attach_vol_after_detach.xml
    include: blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml
    include: blockstorage/section_ts_failed_connect_vol_FC_SAN.xml
    include: blockstorage/section_ts_no_emulator_x86_64.xml
-   include: blockstorage/section_ts_non_existent_host.xml
-   include: blockstorage/section_ts_non_existent_vlun.xml

doc/admin-guide-cloud-rst/source/ts_cinder_config.rst

@@ -1,5 +1,5 @@
 .. highlight:: ini
-   :linenothreshold: 5
+   :linenothreshold: 1
 
 ============================================
 Troubleshoot the Block Storage configuration
@@ -117,7 +117,7 @@ these suggested solutions.
    restart of the ``tgt daemon``. By default, Block Storage uses a
    ``state_path`` variable, which if installing with Yum or APT should
    be set to :file:`/var/lib/cinder/`. The next part is the ``volumes_dir``
-   variable, by default this just simply appends a :file:`volumes\\`
+   variable, by default this just simply appends a :file:`volumes`
    directory to the ``state_path``. The result is a file-tree
    :file:`/var/lib/cinder/volumes/`.
 
@@ -127,44 +127,50 @@ these suggested solutions.
    ``volumes_dir`` does not exist, and it should provide information about
    which path it was looking for.
 
--  The persistent ``tgt include`` file.
+-  The persistent tgt include file.
 
    Along with the ``volumes_dir`` option, the iSCSI target driver also
-   needs to be configured to look in the correct place for the persist
+   needs to be configured to look in the correct place for the persistent
    files. This is a simple entry in the :file:`/etc/tgt/conf.d` file that you
    should have set when you installed OpenStack. If issues occur, verify
    that you have a :file:`/etc/tgt/conf.d/cinder.conf` file.
 
-   If the file is not present, create it with this command::
+   If the file is not present, create it with this command
 
-    # echo 'include /var/lib/cinder/volumes/ *' >> /etc/tgt/conf.d/cinder.conf
+   .. code-block:: console
+
+      # echo 'include /var/lib/cinder/volumes/ *' >> /etc/tgt/conf.d/cinder.conf
 
 -  No sign of attach call in the ``cinder-api log``.
 
    This is most likely going to be a minor adjustment to your :file:`nova.conf`
-   file. Make sure that your :file:`nova.conf` has this entry::
+   file. Make sure that your :file:`nova.conf` has this entry
 
-    volume\_api\_class=nova.volume.cinder.API
+   .. code:: ini
+
+      volume_api_class=nova.volume.cinder.API
 
 -  Failed to create iscsi target error in the :file:`cinder-volume.log` file.
 
-.. code:: bash
+   ::
 
-   2013-03-12 01:35:43 1248 TRACE cinder.openstack.common.rpc.amqp ISCSITargetCreateFailed:
+      2013-03-12 01:35:43 1248 TRACE cinder.openstack.common.rpc.amqp \
-   Failed to create iscsi target for volume volume-137641b2-af72-4a2f-b243-65fdccd38780.
+      ISCSITargetCreateFailed: \
+      Failed to create iscsi target for volume \
+      volume-137641b2-af72-4a2f-b243-65fdccd38780.
 
-You might see this error in :file:`cinder-volume.log` after trying to
+   You might see this error in :file:`cinder-volume.log` after trying to
-create a volume that is 1 GB. To fix this issue:
+   create a volume that is 1 GB. To fix this issue:
 
-Change contents of the :file:`/etc/tgt/targets.conf` from
+   Change contents of the :file:`/etc/tgt/targets.conf` from
-``include /etc/tgt/conf.d/*.conf`` to ``include /etc/tgt/conf.d/cinder_tgt.conf``,
+   ``include /etc/tgt/conf.d/*.conf`` to ``include /etc/tgt/conf.d/cinder_tgt.conf``,
-as follows:
+   as follows:
 
-.. code:: bash
+   ::
 
-   include /etc/tgt/conf.d/cinder_tgt.conf
+      include /etc/tgt/conf.d/cinder_tgt.conf
-   include /etc/tgt/conf.d/cinder.conf
+      include /etc/tgt/conf.d/cinder.conf
-   default-driver iscsi
+      default-driver iscsi
 
-Restart ``tgt`` and `cinder-*` services so they pick up the new
+   Restart ``tgt`` and ``cinder-*`` services so they pick up the new
-configuration.
+   configuration.

doc/admin-guide-cloud-rst/source/ts_non_existent_host.rst

@@ -0,0 +1,24 @@
+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.

doc/admin-guide-cloud-rst/source/ts_non_existent_vlun.rst

@@ -0,0 +1,21 @@
+Non-existent VLUN
+~~~~~~~~~~~~~~~~~
+
+Problem
+-------
+
+This error occurs if the 3PAR host exists with the correct host name
+that the OpenStack Block Storage drivers expect but the volume was
+created in a different Domain.
+
+::
+
+   HTTPNotFound: Not found (HTTP 404) NON_EXISTENT_VLUN - VLUN 'osv-DqT7CE3mSrWi4gZJmHAP-Q' was not found.
+
+
+Solution
+--------
+
+The ``hp3par_domain`` configuration items either need to be updated to
+use the domain the 3PAR host currently resides in, or the 3PAR host
+needs to be moved to the domain that the volume was created in.

doc/admin-guide-cloud-rst/source/ts_vol_attach_miss_sg_scan.rst

@@ -0,0 +1,27 @@
+Failed to Attach Volume, Missing sg_scan
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Problem
+-------
+
+Failed to attach volume to an instance, ``sg_scan`` file not found. This
+warning and error occur when the sg3-utils package is not installed on
+the compute node. The IDs in your message are unique to your system:
+
+::
+
+   ERROR nova.compute.manager [req-cf2679fd-dd9e-4909-807f-48fe9bda3642 admin admin|req-cf2679fd-dd9e-4909-807f-48fe9bda3642 admin admin]
+   [instance: 7d7c92e0-49fa-4a8e-87c7-73f22a9585d5|instance:  7d7c92e0-49fa-4a8e-87c7-73f22a9585d5]
+   Failed to attach volume  4cc104c4-ac92-4bd6-9b95-c6686746414a at /dev/vdcTRACE nova.compute.manager
+   [instance:  7d7c92e0-49fa-4a8e-87c7-73f22a9585d5|instance: 7d7c92e0-49fa-4a8e-87c7-73f22a9585d5]
+   Stdout: '/usr/local/bin/nova-rootwrap: Executable not found: /usr/bin/sg_scan'
+
+
+Solution
+--------
+
+Run this command on the compute node to install the sg3-utils package:
+
+.. code-block:: console
+
+   # apt-get install sg3-utils