Heat stack error - when creating a new swarmbay

Bug #1520308 reported by Khoi Vo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Magnum
Fix Committed
Undecided
hongbin

Bug Description

Have Liberty Devstack with Magnum running on baremetal server with more than enough resources.

Was able to successfully create a swarmbay no problem for "demo tenant".

Tried to create another Openstack project/tenant and create an additional swarmbay for this tenant. I created a similar bay model and when I tried to create bay, Heat logs showing:

Resource CREATE failed: ResourceInError: resources.docker_volume: Went to status error due to \"Unknown\"

Magnum API logs show:

screen-m-cond.log:2015-11-25 15:12:46.198 ERROR magnum.conductor.handlers.bay_conductor [-] Bay error, stack status: CREATAILED, stack_id: 005318e1-d219-4c4f-aeec-fd0738bb0c3d, reason: Resource CREATE failed: ResourceInError: resources.docker_vme: Went to status error due to "Unknown"

Any ideas?

Thanks
Khoi

Revision history for this message
hongbin (hongbin034) wrote :

Volume has been recently added to swarm bay, but it seems the document is outdated. Could you try to create a new baymodel by specifying the docker-volume-size. Like below:

magnum baymodel-create --name swarmbaymodel \
                       --image-id fedora-21-atomic-5 \
                       --keypair-id testkey \
                       --external-network-id public \
                       --dns-nameserver 8.8.8.8 \
                       --flavor-id m1.small \
                       --coe swarm \
                       --docker-volume-size 5

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/250541

Changed in magnum:
assignee: nobody → hongbin (hongbin034)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/250541
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=13bf647a013d7d9ce0fa36e5c261839fadc76f93
Submitter: Jenkins
Branch: master

commit 13bf647a013d7d9ce0fa36e5c261839fadc76f93
Author: Hongbin Lu <email address hidden>
Date: Thu Nov 26 17:26:05 2015 -0500

    Docs: specify --docker-volume-size for swarm bay

    If this option is not specified, the default is 25GB which is too big
    to fail the stack creation.

    Change-Id: I75fca1ab150f2df76c2464647c3d4f73dd7463f7
    Closes-Bug: #1520308

Changed in magnum:
status: In Progress → Fix Committed
Revision history for this message
Khoi Vo (khoi-vo) wrote :

Hi

I've tried to specify the docker volume size to 5 as requested but still getting heat and m-conductor errors:

"Resource CREATE failed: resources.swarm_masters: ResourceInError: resources[0].resources.docker_volume: Went to status error due to \"Unknown\""

, "stack_status_reason": "Resource CREATE failed: resources.swarm_masters: ResourceInError: resources[0].resources.docker_volume: Went to status error due to \"Unknown\"

Thanks
Khoi

Revision history for this message
hongbin (hongbin034) wrote :

Several things:

* Does the error reproducible? If yes, could you share the steps the reproduce the error (e.g. the exact set of commands you ran).
* Did you see any error from Cinder? (check c-vol tab) If yes, could you paste the cinder logs?

Revision history for this message
Khoi Vo (khoi-vo) wrote :

Indeed, there was a cinder volume error:

had to perform the following to fix:

https://ask.openstack.org/en/question/83666/service-cinder-volume-ubuntulmdriver-1-problem/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 2.0.0

This issue was fixed in the openstack/magnum 2.0.0 release.

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.