swarm bay is "CREATE_COMPLETE" but the bay is not usable acutally
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
High
|
Eli Qiao |
Bug Description
I created a bay with atomic-5 image with coe=swarm
+------
| Property | Value |
+------
| status | CREATE_COMPLETE |
| uuid | 0c7fea29-
| status_reason | Stack CREATE completed successfully |
| created_at | 2015-09-
| updated_at | 2015-09-
| bay_create_timeout | 0 |
| api_address | 172.24.4.206 |
| baymodel_id | 57614820-
| node_count | 1 |
| node_addresses | [u'172.24.4.207'] |
| master_count | 1 |
| discovery_url | token:/
| name | swarmbay |
after some time I see it is 'CREATE_COMPLETE' state, but when I login into the bay's vms
swarm-master, and swarm-node failed to run..
[fedora@
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6aaadf3a26d4 swarm:0.2.0 "/swarm manage -H tc 42 minutes ago Exited (137) 42 minutes ago swarm-manager
417356a72d82 swarm:0.2.0 "/swarm join --addr 53 minutes ago Exited (2) 53 minutes ago swarm-agent
we need some validation before the bay is usable.
Changed in magnum: | |
status: | New → Confirmed |
Changed in magnum: | |
assignee: | nobody → Eli Qiao (taget-9) |
Changed in magnum: | |
milestone: | none → mitaka-2 |
status: | Fix Committed → Fix Released |
Changed in magnum: | |
milestone: | mitaka-2 → mitaka-1 |
Basically, we need to fix the swarm template to make it work with the new image. This is a high priority bug.