Open Stack

Hi Stanislaw,

Your host with Fedora should have special config file, which will send
signal to WaitCondition.
For good example please take a look this template
 https://github.com/openstack/heat-templates/blob/819a9a3fc9d6f449129c8cefa5e087569340109b/hot/native_waitcondition.yaml
<https://github.com/openstack/heat-templates/blob/819a9a3fc9d6f449129c8cefa5e087569340109b/hot/native_waitcondition.yaml>

Also the best place for such question I suppose will be
https://ask.openstack.org/en/questions/
<https://ask.openstack.org/en/questions/>

Regards,
Sergey.

On 26 August 2015 at 09:23, Pitucha, Stanislaw Izaak <
stanislaw.pitucha at hp.com> wrote:

> Hi all,
>
> I’m trying to stand up magnum according to the quickstart instructions
> with devstack.
>
> There’s one resource which times out and fails: master_wait_condition. The
> kube master (fedora) host seems to be created, I can login to it via ssh,
> other resources are created successfully.
>
>
>
> What can I do from here? How do I debug this? I tried to look for the
> wc_notify itself to try manually, but I can’t even find that script.
>
>
>
> Best Regards,
>
> Stanisław Pitucha
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150826/5157c2f9/attachment-0001.html>