Thanks Prashant, I have chkd that. Does it have anything to run controller and compute on single node as solution ?
On Tue, Mar 14, 2017 at 8:52 PM, Prashant Shetty < prashantshetty1...@gmail.com> wrote: > Couple of things to check, > > - On controller in nova.conf you should have [placement] section with > below info > - [placement] > os_region_name = RegionOne > project_domain_name = Default > project_name = service > user_domain_name = Default > password = <password> > username = placement > auth_url = <auth_url> > auth_type = password > - If nova service-list shows your nova-compute is UP and RUNNING, you > need to run discover commands on controller as below > - nova-manage cell_v2 map_cell0 --database_connection <db_url> > - nova-manage cell_v2 simple_cell_setup --transport-url > <transport_url> > - nova-manage cell_v2 discover_hosts --verbose > > Discover command should show message that it has discovered your compute > nodes. In case still instance launch fails check nova-conductor and > nova-scheduler logs for more info. > > For more information refer, https://docs.openstack.org/ > developer/nova/cells.html > > > Thanks, > > Prashant > > On Tue, Mar 14, 2017 at 8:33 PM, Vikash Kumar < > vikash.ku...@oneconvergence.com> wrote: > >> That was the weird thing. nova-compute doesn't had any error log. >> nova-compute logs also didn't had any instance create request also. >> >> On Tue, Mar 14, 2017 at 7:50 PM, luogangyi@chinamobile < >> luogan...@chinamobile.com> wrote: >> >>> From your log, we can see nova scheduler has already select target node >>> which is u’nfp’. >>> >>> >>> So you should check the nova-compute log from node nfp. >>> >>> >>> Probably, you are stuck at image downloading. >>> >>> 原始邮件 >>> *发件人:* Vikash Kumar<vikash.ku...@oneconvergence.com> >>> *收件人:* openstack-dev<openstack-dev@lists.openstack.org> >>> *发送时间:* 2017年3月14日(周二) 18:22 >>> *主题:* [openstack-dev] [nova][nova-scheduler] Instance boot stuck >>> in"Scheduling" state >>> >>> All, >>> >>> I brought up multinode setup with devstack. I am using Ocata >>> release. Instances boot are getting stuck in "scheduling" state. The state >>> never gets changed. Below is the link for scheduler log. >>> >>> http://paste.openstack.org/show/602635/ >>> >>> >>> -- >>> Regards, >>> Vikash >>> >>> ____________________________________________________________ >>> ______________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> -- >> Regards, >> Vikash >> >> ____________________________________________________________ >> ______________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Regards, Vikash
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev