Hi Vikas,

Please debug on these lines:

- are you able to launch the instance based on the fedora-21-atomic-3 image in 
horizon ?  If not, check if the image download was fine (by comparing the size)
- get the nova list output (your should see kube_master and kube-minion up and 
running)
-  Log into the console of these 2 instances from horizon and check if it has 
booted up fine and if its in login prompt (I have seen an issue where it got 
stuck at some point during boot and I had to reload
   the instance)
- After this, cloud-init should start and complete
- get the output of "heat stack-list –nā€

Thanks,
Ganesh

From: Adrian Otto <[email protected]<mailto:[email protected]>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, 26 August 2015 10:51 am
To: "OpenStack Development Mailing List (not for usage questions)" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [openstack-dev] [Containers] Magnum bay-create is getting stuck at 
CREATE_IN_PROGRESS

Vikas Choudhary,

Try heat event-show to get more information about what's happening in the 
creation of the resource group for the k8s master. You might not have enough 
storage free to create the nova VM to run the bay master.

Regards,

Adrian

On Aug 25, 2015, at 9:52 PM, Vikas Choudhary 
<[email protected]<mailto:[email protected]>> wrote:


I am following 
https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-quickstart.rst#using-kubernetes
 to try containers/magnum.After running "magnum bay-create --name k8sbay 
--baymodel k8sbaymodel --node-count 1" , it keeps showing :

root@PRINHYLTPHP0400:/home/devstack/devstack# magnum bay-list 
+--------------------------------------+--------+------------+--------------+--------------------+
 | uuid | name | node_count | master_count | status | 
+--------------------------------------+--------+------------+--------------+--------------------+
 | e121254f-8bca-497b-9bd9-e9f37305592e | k8sbay | 1 | 1 | CREATE_IN_PROGRESS |

root@PRINHYLTPHP0400:/home/devstack/devstack# heat resource-list 
${BAY_HEAT_NAME}

+-------------------+-------------------------------------------------------------------------------------+------------------------------+--------------------+---------------------+
 | resource_name | physical_resource_id | resource_type | resource_status | 
updated_time | 
+-------------------+-------------------------------------------------------------------------------------+------------------------------+--------------------+---------------------+
 | api_pool | 23694171-b787-4c15-9188-3c693e3702c8 | OS::Neutron::Pool | 
CREATE_COMPLETE | 2015-08-26T04:09:00 |

| api_pool_floating | 6410a233-03fe-451e-9b52-cd9fac1fcf31 | 
OS::Neutron::FloatingIP | CREATE_COMPLETE | 2015-08-26T04:09:00 |

| etcd_monitor | 2a5c325c-7f24-4c82-a252-64211b67d195 | 
OS::Neutron::HealthMonitor | CREATE_COMPLETE | 2015-08-26T04:09:00 |

| etcd_pool | 4578db12-5a88-4b1e-afe2-4f7f90bcbad1 | OS::Neutron::Pool | 
CREATE_COMPLETE | 2015-08-26T04:09:00 |

*| kube_masters | 8ba9d12f-3567-4d54-969c-99077818ffa3 | 
OS::Heat::ResourceGroup |CREATE_IN_PROGRESS | 2015-08-26T04:09:00 |*

| kube_minions | | OS::Heat::ResourceGroup | INIT_COMPLETE | 
2015-08-26T04:09:00 |

| api_monitor | 09a569ca-334a-4576-91e2-fa98a30f3e50 | 
OS::Neutron::HealthMonitor | CREATE_COMPLETE | 2015-08-26T04:09:01 | | 
extrouter | f7fb19db-2be7-4624-bf20-4867e1d7572c | OS::Neutron::Router | 
CREATE_COMPLETE | 2015-08-26T04:09:01 | | extrouter_inside | 
f7fb19db-2be7-4624-bf20-4867e1d7572c:subnet_id=fdc539a0-9ce7-4faa-a6e1-bddd83d99df9
 | OS::Neutron::RouterInterface | CREATE_COMPLETE | 2015-08-26T04:09:01 |

| fixed_network | 15748ee9-af6e-445a-a3f2-175a866c51a9 | OS::Neutron::Net | 
CREATE_COMPLETE | 2015-08-26T04:09:01 |

| fixed_subnet | fdc539a0-9ce7-4faa-a6e1-bddd83d99df9 | OS::Neutron::Subnet | 
CREATE_COMPLETE | 2015-08-26T04:09:01 |

________________________________

Kube-master gets stuck at create_in_progress.In magnum-con.log or heat-eng.log 
, i could not find any error messages.Can anybody please suggest how to debug 
this issue, any pointers?


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
[email protected]<mailto:[email protected]>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to