Ask Your Question
0

Can't launch a swarm cluster using Magnum, any help ?

asked 2016-11-16 16:28:08 -0600

roquej gravatar image

updated 2017-01-16 08:16:56 -0600

zaneb gravatar image

Hi all,

i have a lab that works fine with Openstack Newton on Ubuntu 16.04. I recently installed Heat and Magnum projects inside my environment.

I have created a cluster template successfully using the command below magnum cluster-template-create --name swarm-cluster-template --image-id fedora-atomic-latest --keypair-id network-root-key --external-network-id provider --dns-nameserver 8.8.8.8 --master-flavor-id m1.tiny --flavor-id m1.tiny --coe swarm

But it failed when i create a cluster with the command: magnum cluster-create --name swarm-cluster --cluster-template swarm-cluster-template --master-count 1 --node-count 1

The result of the command is:

root@Controller:~# magnum cluster-show swarm-cluster
+---------------------+---------------------------------------------------------------------------------------------------------------------------------------+
| Property            | Value                                                                                                                                 |
+---------------------+---------------------------------------------------------------------------------------------------------------------------------------+
| status              | CREATE_FAILED                                                                                                                         |
| cluster_template_id | fd305330-4472-4e9a-a315-d805d0dafade                                                                                                  |
| uuid                | 6fde9710-7cb8-4b20-bbfc-137741fa1e56                                                                                                  |
| stack_id            | -                                                                                                                                     |
| status_reason       | ERROR: Failed to validate: Failed to validate: resources[0]: The Resource Type (Magnum::Optional::Cinder::Volume) could not be found. |
| created_at          | 2016-11-16T22:26:16+00:00                                                                                                             |
| name                | swarm-cluster                                                                                                                         |
| updated_at          | -                                                                                                                                     |
| discovery_url       | https://discovery.etcd.io/cfb3d2eb90fd8564d017e9a5f0ce6376                                                                            |
| faults              | {}                                                                                                                                    |
| api_address         | -                                                                                                                                     |
| coe_version         | -                                                                                                                                     |
| master_addresses    | []                                                                                                                                    |
| create_timeout      | 60                                                                                                                                    |
| node_addresses      | []                                                                                                                                    |
| master_count        | 1                                                                                                                                     |
| container_version   | -                                                                                                                                     |
| node_count          | 1                                                                                                                                     |
+---------------------+---------------------------------------------------------------------------------------------------------------------------------------+

Do you have any suggestions?

Thank you. JP

edit retag flag offensive close merge delete
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-11-24 03:02:28 -0600

ashish235 gravatar image

updated 2019-01-30 04:18:32 -0600

yasin lachiny gravatar image

Have a similar issue. Trying to create a cluster (swarm and kubernetes both). Both the clusters are failing.

When I see the reason using magnum command, I see the below reasons. 

 magnum cluster-show swarm-cluster
-- Swarm cluster --
| status_reason       | Resource CREATE failed: resources[0]: resources.swarm_masters.Property error: resources.swarm_master.properties.image: Error validating value 'fedora-atomic-latest': No images matching {'name': u'fedora-atomic-latest'}. (HTTP 404) |
| created_at          | 2016-11-24T07:11:25+00:00        



magnum cluster-show k8s-cluster2
---kubernetes cluster --
| status_reason       | Resource CREATE failed: resources[0]: resources.kube_masters.Property error: resources.kube_master.properties.image: Error validating value 'fedora-atomic-latest': No images matching {'name': u'fedora-atomic-latest'}. (HTTP 404) |
| created_at          | 2016-11-24T07:55:17+00:00                   



And BTW I 've the mentioned image in my glance. 


alepo@controller:~$ openstack image list
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
+--------------------------------------+----------------------+--------+
| ID                                   | Name                 | Status |
+--------------------------------------+----------------------+--------+
| 27f1a0bf-e038-4156-83c6-c610f980c4ae | docker-cirros        | active |
| 1d5fe9d3-6710-45b7-ade4-e3181d01f9a0 | busybox              | active |
| 7d8ad4ca-c891-4df2-a1f7-d1a5e83c2398 | hipache              | active |
| 4fe95e25-cdaf-43a1-9ead-6a4d4ebf7995 | fedora-atomic-latest | active |
| 1c3eebc0-be2b-43b4-8a03-a224a440af5c | centos6              | active |
| fec87e1e-15e7-4b4a-97be-87eb8d6182dc | cirros               | active |

+--------------------------------------+----------------------+--------+

edit flag offensive delete link more
add a comment
0

answered 2017-01-15 03:54:51 -0600

niv gravatar image

updated 2017-01-15 10:54:38 -0600

did u solve the issue? the same issue occurs to me

"error : failed to validate : resources.network : the resource type (Magnum::Optional::Neutron::Net) could not be found"

edit flag offensive delete link more

Comments

Hi,

I do have the same error. Unable to create cluster. I had tried with fedora, fedora atomic image to create cluster template for kubernetes. There is not proper solution,I could find yet. Please give any solution as well as any proper configuration for kubernetes cluster template creation if any

pp_wh gravatar imagepp_wh ( 2018-03-01 23:47:01 -0600 )edit
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2016-11-16 16:28:08 -0600

Seen: 847 times

Last updated: Jan 30 '19

Related questions

Magnum Swarm - master_lb_enabled

Ways to Create Docker Instance.

How to configure docker endpoint?

error when launch a magnum cluster

when running - docker run busybox echo "Hello from Docker!" - command, it gives an error - Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Unable to use magnum cluster-create

how to setup dynamic resource allocation?

nova-docker setup in devstack

AWS::EC2::InternetGateway does not work

Once we deploy a stack in openstack, and openstack tells us the stack CREATE_COMPLETE. Then how can we know the services in all VMs are ready?