Swarm bay reports create complete before swarm is ready

Bug #1457596 reported by Andrew Melton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Andrew Melton

Bug Description

Currently, our call back to report that each node is complete only reports that cloud init has finished its run. This is not a good indicator for completeness because the swarm containers may not be running by the time cloud init has finished. What we should do is wait until the swarm services are running before reporting stack complete in heat.

Revision history for this message
Guangya Liu (Jay Lau) (jay-lau-513) wrote :
Changed in magnum:
assignee: nobody → Andrew Melton (andrew-melton)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/184841
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=4933edd80428820056f3b023a37c5d2332e814e4
Submitter: Jenkins
Branch: master

commit 4933edd80428820056f3b023a37c5d2332e814e4
Author: Andrew Melton <email address hidden>
Date: Thu May 21 10:58:07 2015 -0700

    Add wait condition on swarm services in swarm bay

    This blocks the heat stack from going into CREATE_COMPLETE status until
    all of the swarm services have completely started. This also means that
    if the swarm services fail to start, the bay will eventually timeout
    instead of going into CREATE_COMPLETE.

    Change-Id: I050e206b99793e0a07ba670d141b64592549c61b
    Closes-bug: #1452936
    Closes-bug: #1457596

Changed in magnum:
status: New → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.