<div dir="ltr"><div><div><div>Roger, Sayali,<br><br></div>Are there any more races that we might need to fix in the existing cluster for Juno? Apart from the ones mentioned above and metadata service being flaky for Juno?<br><br></div>Regards,<br></div>Pranav<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 8:15 PM, Roger Luethi <span dir="ltr"><<a href="mailto:rl@patchworkscience.org" target="_blank">rl@patchworkscience.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, 27 Mar 2015 23:52:52 +0530, Sayali Lunkad wrote:<br>
> - *Host not found while launching an instance.* (happens very frequently<br>
<span class="">> when they try to launch the instance for the first time). It normally gets<br>
> resolved by restarting the compute node or increasing the RAM for compute<br>
> and then restarting it. I am not sure why this should happen only on some<br>
> machines though even thought the configuration of the machines was the<br>
> same.<br>
<br>
</span>This sounds like the controller not realizing that the space for an<br>
instance has been freed (our default config has enough space for only one<br>
instance). If so, just wait a minute or so after deleting all instances,<br>
then it should work.<br>
<br>
> - *HTTP 500 errors*. This is notices frequently after a using the CLI<br>
<span class="">> for sometime. After running a few CLI commands this error shows up.<br>
<br>
</span>There might be some useful information in the logs when that happens.<br>
<br>
> - *Cluster breaks at horizon repeatedly about 4 times. *As spotted<br>
<span class="">> earlier there is a race while osbash tried to setup horizon. It is found<br>
> that this could be a problem with apache2 server when you start it for the<br>
> first time. But the root cause is unknown. We should take a look at this as<br>
> it is happening frequently.<br>
<br>
</span>Hopefully fixed by <a href="https://review.openstack.org/#/c/168711/" target="_blank">https://review.openstack.org/#/c/168711/</a>.<br>
<br>
> - *Cluster breaks while setting up Nova compute. *The second time the<br>
<span class="">> cluster breaks is while setting up nova compute. On checking the logs<br>
> it is shows that it is unable to fetch some archives. But again I<br>
> don't see why it would only break at nova compute if it was a problem<br>
> with the connection.<br>
<br>
</span>We pre-download everything into the basedisk so we don't need a network<br>
connection when building the cluster. Only I failed to add a new package<br>
to pre-download when updating the scripts for Juno. Patch forthcoming.<br>
<br>
> - *VMs do not poweroff automatically on windows host. *Bug has been<br>
<span class="">> filed for this by one of the attendees.<br>
> <a href="https://bugs.launchpad.net/openstack-training-guides/+bug/1435932" target="_blank">https://bugs.launchpad.net/openstack-training-guides/+bug/1435932</a><br>
<br>
</span>Not sure I understand that bug report. On all operating systems, the<br>
cluster is up and running after the cluster build is finished. You can<br>
log in to shut it down, or you can just power off the node VMs and<br>
restore them to the last snapshot. What am I missing?<br>
<br>
Roger<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote></div><br></div>