<html>
<head>
<meta content="text/html; charset=ISO-2022-JP"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
<br>
thanks Adam.<br>
<br>
Both <span>rabbitmq and </span><span>neutron-openvswitch work
fine.<br>
<br>
The output of cinder service-list only includes
cinder-scheduler,no cinder-volume.<br>
<br>
I think this causes "</span>No valid host was found".<br>
<br>
<br>
On 2014年09月11日 20:00, Ambadas Ramanna Adam wrote:<br>
</div>
<blockquote
cite="mid:C41177029DA4734C952A31410738EACC140FE2EC@PUNITPMBX14.ad.infosys.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=iso-2022-jp">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span>Hi Yang,</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Please check your message queue
service (rabbitmq) and neutron-openvswitch services in
output of openstack-status command.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>If neutron-openvswitch is not active
then you will first need to fix it and get it started.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Regards,</span></p>
<p class="MsoNormal"><span>Ambadas Ramanna Adam</span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span> yanghq
[<a class="moz-txt-link-freetext" href="mailto:yanghq@neusoft.com">mailto:yanghq@neusoft.com</a>]
<br>
<b>Sent:</b> Thursday, September 11, 2014 2:55 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
<b>Subject:</b> [Openstack] error about Block Storage
service node</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><br>
According to <a moz-do-not-send="true"
href="http://docs.openstack.org/icehouse/install-guide/install/apt/content/cinder-node.html">http://docs.openstack.org/icehouse/install-guide/install/apt/content/cinder-node.html</a>,
I configure a Block Storage service node.<br>
<br>
But I try to create a volume, I get error like this:<br>
<br>
2014-09-07 11:37:31.020 33190 ERROR
cinder.scheduler.flows.create_volume
[req-87712243-8548-485a-8b48-30455e05dd4a
e4936e1ce4bf4a5db7850ef606513f88
fc8cc603cbb74c87999bc9cf8e24eb06 - - -] Failed to
schedule_create_volume: No valid host was found.<br>
<br>
In this page <a moz-do-not-send="true"
href="http://docs.openstack.org/havana/install-guide/install/apt/content/cinder-node.html">http://docs.openstack.org/havana/install-guide/install/apt/content/cinder-node.html</a><br>
<br>
there are discussions about it, but no solutions.<br>
<br>
thanks for any help.<br>
<br>
<br>
<br>
On 2014<span lang="JA">年</span>08<span lang="JA">月</span>25<span
lang="JA">日</span> 19:49, Markus Zoeller wrote:</p>
</div>
<blockquote>
<pre>javed alam <a moz-do-not-send="true" href="mailto:javedamar@gmail.com"><javedamar@gmail.com></a> wrote on 08/23/2014 02:39:38 PM:</pre>
<pre> </pre>
<blockquote>
<pre>From: javed alam <a moz-do-not-send="true" href="mailto:javedamar@gmail.com"><javedamar@gmail.com></a></pre>
<pre>To: openstack <a moz-do-not-send="true" href="mailto:openstack@lists.openstack.org"><openstack@lists.openstack.org></a>, Masoom Alam </pre>
<pre><a moz-do-not-send="true" href="mailto:masoom.alam@gmail.com"><masoom.alam@gmail.com></a></pre>
<pre>Date: 08/23/2014 02:49 PM</pre>
<pre>Subject: [Openstack] Fwd: nova instance</pre>
<pre> </pre>
<pre>...</pre>
<pre>"Error: Failed to launch instance "nova_testing": Please try again </pre>
<pre>later [Error: No valid host was found. ]. "</pre>
<pre>...</pre>
<pre>i m even unable to find the log files.</pre>
</blockquote>
<pre> </pre>
<pre>Hi Javed,</pre>
<pre> </pre>
<pre>the error "no valid host found" is thrown by the `nova-scheduler` </pre>
<pre>service (see [1] for details). </pre>
<pre> </pre>
<pre>Depending on your testing environment you have to check different things:</pre>
<pre> </pre>
<pre>1) An "All-In-One" DevStack[2] setup:</pre>
<pre> * check your `local.conf` file in your devstack folder. There should </pre>
<pre> be the following lines: </pre>
<pre> DEST=/opt/stack</pre>
<pre> LOGFILE=$DEST/logs/stack.sh.log</pre>
<pre> VERBOSE=True </pre>
<pre> SCREEN_LOGDIR=$DEST/logs/screen</pre>
<pre> * The log of the scheduler is then available at:</pre>
<pre> /opt/stack/logs/screen/screen-n-sch-log</pre>
<pre> * The scheduler log should contain more information about the cause</pre>
<pre>Afaik the changes will be applied when the services are restarted. You </pre>
<pre>can either execute the DevStack scripts `unstack.sh` and `stack.sh` or</pre>
<pre>use the screen tool (see [4]).</pre>
<pre> </pre>
<pre>2) A dedicated controller node:</pre>
<pre>The default folder for nova logs is `/var/log/nova`. The scheduler log </pre>
<pre>should be there. Maybe you have to turn on debugging in the file </pre>
<pre>`/etc/nova/nova.conf` in the line `debug=true` and `verbose=true`.</pre>
<pre> </pre>
<pre>More infos about working with logs can be found at [3].</pre>
<pre> </pre>
<pre>Sources:</pre>
<pre>[1] OpenStack configuration reference; Juno Release (draft); </pre>
<pre> Section "Scheduling<a moz-do-not-send="true" href="http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html%5b2%5dDevStack;http:/devstack.org/guides/single-machine.html%5b3%5dOpenStackCloudAdministratorGuide;Section">" </a><span class="MsoHyperlink"></span></pre>
<pre><span class="MsoHyperlink"><a moz-do-not-send="true" href="http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html%5b2%5dDevStack;http:/devstack.org/guides/single-machine.html%5b3%5dOpenStackCloudAdministratorGuide;Section">http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html </a></span></pre>
<pre><span class="MsoHyperlink"><a moz-do-not-send="true" href="http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html%5b2%5dDevStack;http:/devstack.org/guides/single-machine.html%5b3%5dOpenStackCloudAdministratorGuide;Section">[2] DevStack; http://devstack.org/guides/single-machine.html </a></span></pre>
<pre><span class="MsoHyperlink"><a moz-do-not-send="true" href="http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html%5b2%5dDevStack;http:/devstack.org/guides/single-machine.html%5b3%5dOpenStackCloudAdministratorGuide;Section">[3] OpenStack Cloud Administrator Guide; Section "</a></span>Manage Logs";</pre>
<pre> </pre>
<pre><a moz-do-not-send="true" href="http://docs.openstack.org/admin-guide-cloud/content/section_manage-logs.html">http://docs.openstack.org/admin-guide-cloud/content/section_manage-logs.html</a></pre>
<pre>[4] IBM Developer Works; 2013-12-06; Restart services of devstack based </pre>
<pre> openstack; </pre>
<pre><a moz-do-not-send="true" href="https://www.ibm.com/developerworks/community/blogs/8160eff1-dedf-408e-9395-9dffeb68749f/entry/working_with_screens_to_restart_service_of_devstack_based_openstack?lang=en">https://www.ibm.com/developerworks/community/blogs/8160eff1-dedf-408e-9395-9dffeb68749f/entry/working_with_screens_to_restart_service_of_devstack_based_openstack?lang=en</a></pre>
<pre> </pre>
<pre> </pre>
<pre>_______________________________________________</pre>
<pre>Mailing list: <a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></pre>
<pre>Post to : <a moz-do-not-send="true" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a></pre>
<pre>Unsubscribe : <a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></pre>
<pre> </pre>
</blockquote>
<p class="MsoNormal"> </p>
<p>---------------------------------------------------------------------------------------------------<br>
Confidentiality Notice: The information contained in this
e-mail and any accompanying attachment(s)
<br>
is intended only for the use of the intended recipient and may
be confidential and/or privileged of
<br>
Neusoft Corporation, its subsidiaries and/or its affiliates.
If any reader of this communication is
<br>
not the intended recipient, unauthorized use, forwarding,
printing, storing, disclosure or copying
<br>
is strictly prohibited, and may be unlawful.If you have
received this communication in error,please
<br>
immediately notify the sender by return e-mail, and delete the
original message and all copies from
<br>
your system. Thank you. <br>
---------------------------------------------------------------------------------------------------</p>
</div>
<table>
<tbody>
<tr>
<td>
<pre>**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***</pre>
</td>
</tr>
</tbody>
</table>
</blockquote>
<br>
<p>---------------------------------------------------------------------------------------------------<br>
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) <br>
is intended only for the use of the intended recipient and may be confidential and/or privileged of <br>
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is <br>
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying <br>
is strictly prohibited, and may be unlawful.If you have received this communication in error,please <br>
immediately notify the sender by return e-mail, and delete the original message and all copies from <br>
your system. Thank you. <br>
---------------------------------------------------------------------------------------------------</p></body>
</html>