Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
Hi Bernd, Got warning, Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. When we set up OpenStack manually without Devstack, we go the above warning. We fixed by setting up environment variables. I don't know the below error/s log is coming due to the above warning or not. When we use Devstack for setting up Ocata, stack.sh has environment variables. After running stack.sh when we echo the environment variables(exported thru the stack.sh), not able to echo. We suspect that environment variables are not set properly. Could you please help us to resolve the issues. Find below the detailed log: 2017-12-01 02:50:04.646 DEBUG nova.scheduler.client.report [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] /opt/stack/nova/nova/scheduler/client/report.py --> update_resource_stat from (pid=4833) update_resource_stats /opt/stack/nova/nova/scheduler/client/report.py:633 2017-12-01 02:50:04.647 DEBUG oslo_messaging._drivers.amqpdriver [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] CALL msg_id: 272c4a91012245b08b5f95a6a557ef63 exchange 'nova' topic 'conductor' from (pid=4833) _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562 2017-12-01 02:50:04.669 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: 272c4a91012245b08b5f95a6a557ef63 from (pid=4833) __call__ /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419 2017-12-01 02:50:04.670 DEBUG nova.scheduler.client.report [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] _ensure_resource_provider --> uuid :: 6deda2bf-68ff-470f-b23f-392ca1e2b9b5 from (pid=4833) _ensure_resource_provider /opt/stack/nova/nova/scheduler/client/report.py:393 2017-12-01 02:50:04.670 ERROR keystoneauth1.session [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] url ---> /resource_providers/6deda2bf-68ff-470f-b23f-392ca1e2b9b5 2017-12-01 02:50:04.670 DEBUG keystoneauth1.session [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] url ---> /resource_providers/6deda2bf-68ff-470f-b23f-392ca1e2b9b5 from (pid=4833) get /usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:759 2017-12-01 02:50:04.670 ERROR keystoneauth1.session [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] url ---> http://10.105.166.213:35357/v3 2017-12-01 02:50:04.671 DEBUG keystoneauth1.session [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] url ---> http://10.105.166.213:35357/v3 from (pid=4833) get /usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:759 2017-12-01 02:51:19.669 WARNING keystoneauth.identity.generic.base [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. 2017-12-01 02:51:19.670 DEBUG keystoneauth1.identity.v3.base [req-2d4bcbcb-f0b3-44dc-9659-dd781f97c7cc None None] http://10.105.166.213:35357/v3/auth/tokens from (pid=4833) get_auth_ref /usr/local/lib/python2.7/dist-packages/keystoneauth1/identity/v3/base.py:164 From: Ramu, MohanX Sent: Thursday, November 30, 2017 9:03 PM To: Bernd Bausch <berndbau...@gmail.com>; openstack@lists.openstack.org Subject: RE: [Openstack] Devstack -Ocata - Failed to launch instance on Host Hi Bernd When we add logs to find the URL: got below logs, Still the issue is not resolved. 017-11-30 07:14:56.942 ERROR keystoneauth1.session [req-3d55cc14-8ff1-4c26-b58e-64cd7e128bb2 None None] url ---> /resource_providers/62041017-580c-449c-937d-edd634b40d23 2017-11-30 07:14:56.942 DEBUG keystoneauth1.session [req-3d55cc14-8ff1-4c26-b58e-64cd7e128bb2 None None] url ---> /resource_providers/62041017-580c-449c-937d-edd634b40d23 ---> http://10.105.166.213:35357/v3/auth/tokens from (pid=16436) get_auth_ref /usr/local/lib/python2.7/dist-packages/keystoneauth1/identity/v3/base.py:164 found below error in n-cpu logs. ' from (pid=28861) _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562 2017-11-29 22:48:00.158 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: 2d9d2c01cec0498b9d580b7abab4621e from (pid=28861) __call__ /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419 2017-11-29 22:48:05.825 DEBUG oslo_messaging._drivers.amqpdriver [-] CALL msg_id: e29f30b9952c4318874f768d03b4d8d8 exchange 'nova' topic 'conductor' from (pid=24675) _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562 2017-11-29 22:48:05.846 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: e29f30b9952c4318874f768d03b4d8d8 from (pid=24675) __call__ /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419 2017-11-29 22:48:07.511 DEBUG oslo_concurrency.lockutils [req-6f2e55e0-6b80-41ad-9c23-e333d75c1ec6 None None] L
Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
:
":04:00.0"}, {"dev_id": "pci__00_1d_0", "product_id": "8c26",
"dev_type": "type-PCI", "numa_node": null, "vendor_id": "8086", "label":
"label_8086_8c26", "address": ":00:1d.0"}, {"dev_id": "pci__00_1f_0",
"product_id": "8c56", "dev_type": "type-PCI", "numa_node": null, "vendor_id":
"8086", "label": "label_8086_8c56", "address": ":00:1f.0"}, {"dev_id":
"pci__00_1f_2", "product_id": "8c02", "dev_type": "type-PCI", "numa_node":
null, "vendor_id": "8086", "label": "label_8086_8c02", "address":
":00:1f.2"}, {"dev_id": "pci__00_1f_3", "product_id": "8c22",
"dev_type": "type-PCI", "numa_node": null, "vendor_id": "8086", "label":
"label_8086_8c22", "address": "0000:00:1f.3"}, {"dev_id": "pci__00_1f_6",
"product_id": "8c24", "dev_type": "type-PCI", "numa_node": null, "vendor_id":
"8086", "label": "label_8086_8c24", "address": ":00:1f.6"}] from
(pid=28861) _report_hypervisor_resource_view
/opt/stack/nova/nova/compute/resource_tracker.py:679
2017-11-29 22:48:44.464 DEBUG oslo_concurrency.lockutils
[req-2dcfd462-169e-4da6-b83d-e4893e0c566b None None] Lock "compute_resources"
acquired by "nova.compute.resource_tracker._update_available_resource" ::
waited 0.000s from (pid=28861) inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:270
2017-11-29 22:48:44.465 DEBUG oslo_messaging._drivers.amqpdriver
[req-2dcfd462-169e-4da6-b83d-e4893e0c566b None None] CALL msg_id:
6c5aedb48e92409ba86e18bd9585790e exchange 'nova' topic 'conductor' from
(pid=28861) _send
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562
2017-11-29 22:48:44.491 DEBUG oslo_messaging._drivers.amqpdriver [-] received
reply msg_id: 6c5aedb48e92409ba86e18bd9585790e from (pid=28861) __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419
2017-11-29 22:48:50.140 DEBUG oslo_messaging._drivers.amqpdriver [-] CALL
msg_id: 9dc559af0607442dac94a10a1e883576 exchange 'nova' topic 'conductor' from
(pid=28861) _send
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562
2017-11-29 22:48:50.162 DEBUG oslo_messaging._drivers.amqpdriver [-] received
reply msg_id: 9dc559af0607442dac94a10a1e883576 from (pid=28861) __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419
2017-11-29 22:48:55.831 DEBUG oslo_messaging._drivers.amqpdriver [-] CALL
msg_id: 2e97d1a11dfa4dacbf251d7e1bd2e4ef exchange 'nova' topic 'conductor' from
(pid=24675) _send
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:562
2017-11-29 22:48:55.850 DEBUG oslo_messaging._drivers.amqpdriver [-] received
reply msg_id: 2e97d1a11dfa4dacbf251d7e1bd2e4ef from (pid=24675) __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:419
Thanks
Mohan Ramu
-Original Message-
From: Bernd Bausch [mailto:berndbau...@gmail.com]
Sent: Wednesday, November 29, 2017 3:03 PM
To: Ramu, MohanX <mohanx.r...@intel.com>; openstack@lists.openstack.org
Subject: RE: [Openstack] Devstack -Ocata - Failed to launch instance on Host
Things you could check:
- on the compute node, nova compute log (DevStack names it n-cpu), are there
messages indicating that the node can't contact the placement service.
- if so, find out why.
The error message might contain clues. Likely causes are misconfiguration in
nova.conf, some networking misconfiguration, firewall etc. Ultimately, the root
of the problem is in local.conf, I would guess.
- if it can contact the placement service, something is wrong at a different
level. Again, I would hope that the compute log contains useful information.
-Original Message-
From: Ramu, MohanX [mailto:mohanx.r...@intel.com]
Sent: Tuesday, November 28, 2017 4:47 PM
To: Brian Haley <haleyb@gmail.com<mailto:haleyb@gmail.com>>;
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
After running discover host command also not able to populate the compute node
data into Resource_providers table.
The cell mapping table ahs cello and Null not cell0, post updating cell1 also
-nothing resolved.
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
nova-manage cell_v2 discover_hosts
-Original Message-
From: Brian Haley [mailto:haleyb@gmail.com]
Sent: Monday, November 27, 2017 10:21 PM
To: Ramu, MohanX <mohanx.r...@intel.com<mailto:mohanx.r...@intel.com>>;
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
On 11/27/2017 10:24 AM, Ramu, MohanX wrote:
> Hi All,
>
> Not bale to launch an instance on Compute Node. instead of it,
> instance is trying to launch on the same controller.
>
> The added compute node is not there in resource provider table.
>
> Could you please help us what we missed.
>
> Is placement API not configured on compute node side and Is there
> Placement API configurations coming by default along with basic
> Devstack set up?
There is a section on multinode setup in the devstack repo,
doc/source/guides/multinode-lab.rst, that I think covers the issue you're
seeing. Assuming your compute node shows up in 'nova service-list' output,
you need to run ./tools/discover_hosts.sh to have a cell mapping added for the
node.
-Brian
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to :
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
Things you could check: - on the compute node, nova compute log (DevStack names it n-cpu), are there messages indicating that the node can't contact the placement service. - if so, find out why. The error message might contain clues. Likely causes are misconfiguration in nova.conf, some networking misconfiguration, firewall etc. Ultimately, the root of the problem is in local.conf, I would guess. - if it can contact the placement service, something is wrong at a different level. Again, I would hope that the compute log contains useful information. -Original Message- From: Ramu, MohanX [mailto:mohanx.r...@intel.com] Sent: Tuesday, November 28, 2017 4:47 PM To: Brian Haley <haleyb@gmail.com>; openstack@lists.openstack.org Subject: Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host After running discover host command also not able to populate the compute node data into Resource_providers table. The cell mapping table ahs cello and Null not cell0, post updating cell1 also -nothing resolved. su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova nova-manage cell_v2 discover_hosts -Original Message- From: Brian Haley [mailto:haleyb@gmail.com] Sent: Monday, November 27, 2017 10:21 PM To: Ramu, MohanX <mohanx.r...@intel.com>; openstack@lists.openstack.org Subject: Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host On 11/27/2017 10:24 AM, Ramu, MohanX wrote: > Hi All, > > Not bale to launch an instance on Compute Node. instead of it, > instance is trying to launch on the same controller. > > The added compute node is not there in resource provider table. > > Could you please help us what we missed. > > Is placement API not configured on compute node side and Is there > Placement API configurations coming by default along with basic > Devstack set up? There is a section on multinode setup in the devstack repo, doc/source/guides/multinode-lab.rst, that I think covers the issue you're seeing. Assuming your compute node shows up in 'nova service-list' output, you need to run ./tools/discover_hosts.sh to have a cell mapping added for the node. -Brian ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
After running discover host command also not able to populate the compute node data into Resource_providers table. The cell mapping table ahs cello and Null not cell0, post updating cell1 also -nothing resolved. su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova nova-manage cell_v2 discover_hosts -Original Message- From: Brian Haley [mailto:haleyb@gmail.com] Sent: Monday, November 27, 2017 10:21 PM To: Ramu, MohanX <mohanx.r...@intel.com>; openstack@lists.openstack.org Subject: Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host On 11/27/2017 10:24 AM, Ramu, MohanX wrote: > Hi All, > > Not bale to launch an instance on Compute Node. instead of it, > instance is trying to launch on the same controller. > > The added compute node is not there in resource provider table. > > Could you please help us what we missed. > > Is placement API not configured on compute node side and Is there > Placement API configurations coming by default along with basic > Devstack set up? There is a section on multinode setup in the devstack repo, doc/source/guides/multinode-lab.rst, that I think covers the issue you're seeing. Assuming your compute node shows up in 'nova service-list' output, you need to run ./tools/discover_hosts.sh to have a cell mapping added for the node. -Brian ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Devstack -Ocata - Failed to launch instance on Host
On 11/27/2017 10:24 AM, Ramu, MohanX wrote: Hi All, Not bale to launch an instance on Compute Node. instead of it, instance is trying to launch on the same controller. The added compute node is not there in resource provider table. Could you please help us what we missed. Is placement API not configured on compute node side and Is there Placement API configurations coming by default along with basic Devstack set up? There is a section on multinode setup in the devstack repo, doc/source/guides/multinode-lab.rst, that I think covers the issue you're seeing. Assuming your compute node shows up in 'nova service-list' output, you need to run ./tools/discover_hosts.sh to have a cell mapping added for the node. -Brian ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
