admin-guide-cloud-rst: Fix trouble shooting
The trouble shooting section was part of blockstorage.rst but also part of blockstorage-troubleshoot.rst, thus include it only once. Add ts_no_emulator_x86_64.rst to blockstorage-troubleshoot.rst. Update all files with proper markup heading. Sort trouble shooting section to follow order of DocBook version. Change-Id: I0a3c2234837da300a7e308fb6120fd813d60e795
This commit is contained in:
Andreas Jaeger
parent
3e71b640a7
commit
02048eb8a7
@ -10,15 +10,14 @@ Storage installation.
|
||||
|
||||
ts_cinder_config.rst
|
||||
ts_multipath_warn.rst
|
||||
ts_vol_attach_miss_sg_scan.rst
|
||||
ts_non_existent_host.rst
|
||||
ts_non_existent_vlun.rst
|
||||
ts-eql-volume-size.rst
|
||||
ts_vol_attach_miss_sg_scan.rst
|
||||
ts-HTTP-bad-req-in-cinder-vol-log.rst
|
||||
ts-duplicate-3par-host.rst
|
||||
ts-failed-attach-vol-after-detach.rst
|
||||
ts-failed-attach-vol-no-sysfsutils.rst
|
||||
ts-failed-connect-vol-FC-SAN.rst
|
||||
ts_no_emulator_x86_64.rst
|
||||
ts_non_existent_host.rst
|
||||
ts_non_existent_vlun.rst
|
||||
|
||||
.. TODO (MZ) Convert and include the following sections
|
||||
include: blockstorage/section_ts_no_emulator_x86_64.xml
|
||||
|
||||
@ -67,29 +67,3 @@ system.
|
||||
include: blockstorage/section_driver_filter_weighing.xml
|
||||
include: blockstorage/section_ratelimit-volume-copy-bandwidth.xml
|
||||
include: blockstorage/section_over_subscription.xml
|
||||
|
||||
Troubleshoot your installation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
This section provides useful tips to help you troubleshoot your Block
|
||||
Storage installation.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
ts_cinder_config.rst
|
||||
ts_vol_attach_miss_sg_scan.rst
|
||||
ts_non_existent_host.rst
|
||||
ts_non_existent_vlun.rst
|
||||
ts_no_emulator_x86_64.rst
|
||||
|
||||
|
||||
.. TODO (MZ) Convert and include the following sections
|
||||
include: blockstorage/section_ts_multipath_warn.xml
|
||||
include: blockstorage/section_ts_eql_volume_size.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
|
||||
|
||||
|
||||
@ -1,11 +1,12 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
=====================================
|
||||
HTTP bad request in cinder volume log
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
=====================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
These errors appear in the :file:`cinder-volume.log` file::
|
||||
|
||||
@ -40,7 +41,7 @@ These errors appear in the :file:`cinder-volume.log` file::
|
||||
HTTPBadRequest: Bad request (HTTP 400)
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
You need to update your copy of the :file:`hp_3par_fc.py` driver which
|
||||
contains the synchronization code.
|
||||
|
||||
@ -1,11 +1,12 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
===================
|
||||
Duplicate 3PAR host
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
===================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
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.
|
||||
@ -17,7 +18,7 @@ using iSCSI::
|
||||
'cld4b5ubuntu'.
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
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
|
||||
|
||||
@ -1,11 +1,12 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
========================================================================
|
||||
Addressing discrepancies in reported volume sizes for EqualLogic storage
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
========================================================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
There is a discrepancy between both the actual volume size in EqualLogic
|
||||
(EQL) storage and the image size in the Image service, with what is
|
||||
@ -131,7 +132,7 @@ The attempt to create a new volume based on the size reported by the
|
||||
``cinder`` tool will then fail.
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
To work around this problem, increase the target size of the new image
|
||||
to the next whole number. In the problem example, you created a 1 GB
|
||||
|
||||
@ -1,16 +1,17 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
=======================================
|
||||
Failed to attach volume after detaching
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
=======================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
Failed to attach a volume after detaching the same volume.
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
You must change the device name on the ``nova-attach`` command. The VM
|
||||
might not clean up after a ``nova-detach`` command runs. This example
|
||||
|
||||
@ -1,11 +1,12 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
=================================================
|
||||
Failed to attach volume, systool is not installed
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
=================================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
This warning and error occurs if you do not have the required
|
||||
``sysfsutils`` package installed on the compute node::
|
||||
@ -20,7 +21,7 @@ This warning and error occurs if you do not have the required
|
||||
Failed to attach volume 13d5c633-903a-4764-a5a0-3336945b1db1 at /dev/vdk.
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
Run the following command on the compute node to install the
|
||||
``sysfsutils`` packages::
|
||||
|
||||
@ -1,11 +1,12 @@
|
||||
.. highlight:: console
|
||||
:linenothreshold: 5
|
||||
|
||||
==================================
|
||||
Failed to connect volume in FC SAN
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
==================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
Compute node failed to connect to a volume in a Fibre Channel (FC) SAN
|
||||
configuration. The WWN may not be zoned correctly in your FC SAN that
|
||||
@ -23,7 +24,7 @@ links the compute host to the storage array::
|
||||
operation.(HTTP 500)(Request-ID: req-71e5132b-21aa-46ee-b3cc-19b5b4ab2f00)
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
The network administrator must configure the FC SAN fabric by correctly
|
||||
zoning the WWN (port names) from your compute node HBAs.
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
.. highlight:: ini
|
||||
:linenothreshold: 1
|
||||
|
||||
============================================
|
||||
Troubleshoot the Block Storage configuration
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
============================================
|
||||
|
||||
Most Block Storage errors are caused by incorrect volume configurations
|
||||
that result in volume creation failures. To resolve these failures,
|
||||
|
||||
@ -1,14 +1,15 @@
|
||||
=========================================
|
||||
Cannot find suitable emulator for x86_64
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
=========================================
|
||||
|
||||
Problem
|
||||
-------
|
||||
~~~~~~~
|
||||
|
||||
When you attempt to create a VM, the error shows the VM is in the
|
||||
``BUILD`` then ``ERROR`` state.
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
On the KVM host run, ``cat /proc/cpuinfo``. Make sure the ``vme`` and
|
||||
``svm`` flags are set.
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
=================
|
||||
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
|
||||
@ -15,7 +16,7 @@ host was exported using iSCSI.
|
||||
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,
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
=================
|
||||
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
|
||||
@ -14,7 +15,7 @@ created in a different Domain.
|
||||
|
||||
|
||||
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
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
========================================
|
||||
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
|
||||
@ -18,7 +19,8 @@ the compute node. The IDs in your message are unique to your system:
|
||||
|
||||
|
||||
Solution
|
||||
--------
|
||||
~~~~~~~~
|
||||
|
||||
|
||||
Run this command on the compute node to install the sg3-utils package:
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user