Unable to get the status of bay with model as Docker swarm

Bug #1489725 reported by bharaththiruveedula
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
bharaththiruveedula

Bug Description

When I am trying to create a bay with baymodel as Docker swarm I got the status of the bay as None. But when I tried using kubernetes it works fine.

How to Reproduce the Bug:
1)Create the baymodel with coe as kubernetes:
magnum baymodel-create --name k8sbaymodel \
                       --image-id fedora-21-atomic-3 \
                       --keypair-id testkey \
                       --external-network-id public \
                       --dns-nameserver 8.8.8.8 \
                       --flavor-id m1.small \
                       --docker-volume-size 5 \
                       --coe kubernetes
2)Create a bay with baymodel as the above one.
magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1
3)Check the status of the bay you created above
magnum bay-list

+--------------------------------------+---------+------------+-----------------+
| uuid | name | node_count | status |
+--------------------------------------+---------+------------+-----------------+
| 12ccb1e6-02dc-4e2b-b897-10656c5339ce | k8sbay | 1 | CREATE_IN_PROGESS |
+--------------------------------------+---------+------------+-----------------+
4)Create the baymodel with coe as swarm:
magnum baymodel-create --name swarmbaymodel \
                       --image-id fedora-21-atomic-3 \
                       --keypair-id testkey \
                       --external-network-id public \
                       --dns-nameserver 8.8.8.8 \
                       --flavor-id m1.small \
                       --coe swarm
5)Create a bay with baymodel as "swarmbaymodel"(created in step #4)
magnum bay-create --name swarmbay --baymodel swarmbaymodel --node-count 1

6)Check the status of the bay you created in step #6
magnum bay-list

+--------------------------------------+---------+------------+-----------------+
| uuid | name | node_count | status |
+--------------------------------------+---------+------------+-----------------+
| 89abdf63-02dc-4e2b-b897-10656c5339ce | swarmbay | 1 |None |
+--------------------------------------+---------+------------+-----------------+

In the above output the status should be other than None(ex:CREATE_IN_PROGRESS, CREATE_COMPLETE)

Changed in magnum:
assignee: nobody → bharaththiruveedula (bharath-ves)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/218582

Changed in magnum:
status: New → In Progress
Revision history for this message
Ton Ngo (ton-i) wrote :

If you can cut & paste some of the command line and output of the error, it would help others to reproduce and better understand the problem.

Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

@ton-i, Hope the steps how to reproduce the bug will give the clarity on this bug report

description: updated
Revision history for this message
Ton Ngo (ton-i) wrote :

Thanks bharaththiruveedula, excellent description.

Revision history for this message
Steve Adams (sa240s) wrote :

Any temporary work-around for this issue? I'm seeing it too.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/218582
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=6a264b6f1169675af3056d53524e2fd8c860274f
Submitter: Jenkins
Branch: master

commit 6a264b6f1169675af3056d53524e2fd8c860274f
Author: Bharath Thiruveedula <email address hidden>
Date: Sat Aug 29 21:15:05 2015 +0530

    Updates the node count key for all types of bay

    By default the key to get node count is "number_of_minions"
    which is not true for baymodels other than kubernetes
    and it raises "KeyError" so that status of bay will not
    be updated.

    Closes-Bug: #1489725
    Change-Id: I9f6a8ebbc26f501d54ef97937329845a12002d6c

Changed in magnum:
status: In Progress → 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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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