openstack/openstack-manuals
Code Issues Proposed changes

Remove section_ts_attach_vol_fail_not_JSON.xml

Browse Source 
This error message is not anymore in current cinder.

Change-Id: I814c776eae9cf47a653fd058db1dbd31e28a04ad
This commit is contained in:
Andreas Jaeger 2014-03-11 22:41:15 +01:00
parent 61f3a21547
commit 09857018b6
2 changed files with 0 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/admin-guide-cloud/ch_blockstorage.xml
View File

@ -131,7 +131,6 @@
<xi:include href="section_ts_vol_attach_miss_sg_scan.xml"/> <xi:include href="section_ts_vol_attach_miss_sg_scan.xml"/>
<xi:include <xi:include
href="section_ts_HTTP_bad_req_in_cinder_vol_log.xml"/> href="section_ts_HTTP_bad_req_in_cinder_vol_log.xml"/>
<xi:include href="section_ts_attach_vol_fail_not_JSON.xml"/>
<xi:include href="section_ts_duplicate_3par_host.xml"/> <xi:include href="section_ts_duplicate_3par_host.xml"/>
<xi:include <xi:include
href="section_ts_failed_attach_vol_after_detach.xml"/> href="section_ts_failed_attach_vol_after_detach.xml"/>

29
doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml
View File

@ -1,29 +0,0 @@
<?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_attach_vol_fail_not_JSON">
<title>Volume attach error, not JSON serializable</title>
<section xml:id="section_ts_attach_vol_fail_not_JSON_problem">
<title>Problem</title>
<para>When you attach a volume to a VM, you will see the error
with stack trace in
<filename>/var/log/cinder/volume.log</filename>. The
JSON serializable issue is caused by an RPC response
timeout.</para>
</section>
<section xml:id="section_ts_attach_vol_fail_not_JSON_solution">
<title>Solution</title>
<para>Make sure your iptables allow port 3260 communication on
the ISC controller. Run this command:</para>
<screen><prompt>#</prompt> <userinput>iptables -I INPUT &lt;Last Rule No> -p tcp --dport 3260 -j ACCEPT</userinput></screen>
<para>If the port communication is properly configured, you
can try running this command.</para>
<screen><prompt>#</prompt> <userinput>service iptables stop</userinput></screen>
<note os="debian;ubuntu">
<para>This service does not exist on Debian or
Ubuntu.</para>
</note>
<para>If you continue to get the RPC response time out, your
ISC controller and KVM host might be incompatible.</para>
</section>
</section>