Public bug reported: Hello! I've encountered the bug when configuring nova-compute service on new node: ... 2018-04-04 14:55:42.082 41113 INFO nova.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Starting compute node (version 17.0.1) 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Error starting thread.: PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service Traceback (most recent call last): 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 729, in run_service 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service service.start() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/service.py", line 161, in start 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service self.manager.init_host() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1137, in init_host 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service raise exception.PlacementNotConfigured() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. ...
Steps to reproduce ------------------ 1. Install and configure nova on controller node, make sure that all nova services are running correctly 2. Configure nova on compute node: follow Queens Series Release Notes (https://docs.openstack.org/releasenotes/nova/queens.html), in [placement] comment out deprecated 'os_region_name' and configure 'region_name' 3. Restart nova-compute service Expected result ------------------ Nova-compute service started and running without errors Actual result ------------------ Nova-compute service failed with PlacementNotConfigured error Workaround ------------------ 1. Comment out 'region_name' in [placement] and configure deprecated 'os_region_name': [placement] os_region_name = RegionOne auth_type = password auth_url = project_name = service project_domain_name = default username = placement user_domain_name = default password = #region_name = RegionOne 2. Restart nova-compute service, сheck your log ... 2018-04-04 15:08:59.684 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Compute node record created for compute01-api:compute01.demo.infra.cloud.loc with uuid: d2d36c03-e597-4831-84f6-03c78f331354 2018-04-04 15:09:07.380 41544 INFO nova.scheduler.client.report [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] [req-9a468e08-7eaa-4f91-a8d9-dca8bbad3b8f] Created resource provider record via placement API for resource provider with UUID d2d36c03-e597-4831-84f6-03c78f331354 and name compute01.demo.infra.cloud.loc. 2018-04-04 15:09:15.774 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Final resource view: name=compute01.demo.infra.cloud.loc phys_ram=257004MB used_ram=512MB phys_disk=243174GB used_disk=0GB total_vcpus=48 used_vcpus=0 pci_stats=[] ... My Environment ------------------ Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 ** Affects: nova Importance: Undecided Status: New ** Attachment added: "nova-compute_ERROR.conf" https://bugs.launchpad.net/bugs/1761150/+attachment/5101246/+files/nova-compute_ERROR.conf ** Attachment removed: "nova-compute_ERROR.conf" https://bugs.launchpad.net/nova/+bug/1761150/+attachment/5101246/+files/nova-compute_ERROR.conf ** Description changed: Hello! I've encountered the bug when configuring nova-compute service on new node: ... 2018-04-04 14:55:42.082 41113 INFO nova.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Starting compute node (version 17.0.1) 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Error starting thread.: PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service Traceback (most recent call last): 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 729, in run_service 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service service.start() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/service.py", line 161, in start 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service self.manager.init_host() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1137, in init_host 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service raise exception.PlacementNotConfigured() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. ... Steps to reproduce ------------------ - 1. Install and configure nova on controller node, make sure that all nova services are running correctly + 1. Install and configure nova on controller node, make sure that all nova services are running correctly 2. Configure nova on compute node: - follow Queens Series Release Notes (https://docs.openstack.org/releasenotes/nova/queens.html), in [placement] comment out deprecated 'os_region_name' and configure 'region_name' + follow Queens Series Release Notes (https://docs.openstack.org/releasenotes/nova/queens.html), in [placement] comment out deprecated 'os_region_name' and configure 'region_name' 3. Restart nova-compute service Expected result ------------------ Nova-compute service started and running without errors Actual result ------------------ - Nova-compute service failed when + Nova-compute service failed with PlacementNotConfigured error Workaround ------------------ 1. Comment out 'region_name' in [placement] and configure deprecated 'os_region_name': - [placement] - os_region_name = RegionOne - auth_type = password - auth_url = - project_name = service - project_domain_name = default - username = placement - user_domain_name = default - password = - #region_name = RegionOne - 2. Restart nova-compute service, сheck your log for errors + [placement] + os_region_name = RegionOne + auth_type = password + auth_url = + project_name = service + project_domain_name = default + username = placement + user_domain_name = default + password = + #region_name = RegionOne + 2. Restart nova-compute service, сheck your log ... 2018-04-04 15:08:59.684 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Compute node record created for compute01-api:compute01.demo.infra.cloud.loc with uuid: d2d36c03-e597-4831-84f6-03c78f331354 2018-04-04 15:09:07.380 41544 INFO nova.scheduler.client.report [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] [req-9a468e08-7eaa-4f91-a8d9-dca8bbad3b8f] Created resource provider record via placement API for resource provider with UUID d2d36c03-e597-4831-84f6-03c78f331354 and name compute01.demo.infra.cloud.loc. 2018-04-04 15:09:15.774 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Final resource view: name=compute01.demo.infra.cloud.loc phys_ram=257004MB used_ram=512MB phys_disk=243174GB used_disk=0GB total_vcpus=48 used_vcpus=0 pci_stats=[] ... - + My Environment ------------------ Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1761150 Title: service fails when deprecated 'os_region_name' is not configured in [placement] Status in OpenStack Compute (nova): New Bug description: Hello! I've encountered the bug when configuring nova-compute service on new node: ... 2018-04-04 14:55:42.082 41113 INFO nova.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Starting compute node (version 17.0.1) 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service [req-be886a45-032a-441b-8934-0d586d159edb - - - - -] Error starting thread.: PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service Traceback (most recent call last): 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 729, in run_service 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service service.start() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/service.py", line 161, in start 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service self.manager.init_host() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1137, in init_host 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service raise exception.PlacementNotConfigured() 2018-04-04 14:55:42.083 41113 ERROR oslo_service.service PlacementNotConfigured: This compute is not configured to talk to the placement service. Configure the [placement] section of nova.conf and restart the service. ... Steps to reproduce ------------------ 1. Install and configure nova on controller node, make sure that all nova services are running correctly 2. Configure nova on compute node: follow Queens Series Release Notes (https://docs.openstack.org/releasenotes/nova/queens.html), in [placement] comment out deprecated 'os_region_name' and configure 'region_name' 3. Restart nova-compute service Expected result ------------------ Nova-compute service started and running without errors Actual result ------------------ Nova-compute service failed with PlacementNotConfigured error Workaround ------------------ 1. Comment out 'region_name' in [placement] and configure deprecated 'os_region_name': [placement] os_region_name = RegionOne auth_type = password auth_url = project_name = service project_domain_name = default username = placement user_domain_name = default password = #region_name = RegionOne 2. Restart nova-compute service, сheck your log ... 2018-04-04 15:08:59.684 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Compute node record created for compute01-api:compute01.demo.infra.cloud.loc with uuid: d2d36c03-e597-4831-84f6-03c78f331354 2018-04-04 15:09:07.380 41544 INFO nova.scheduler.client.report [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] [req-9a468e08-7eaa-4f91-a8d9-dca8bbad3b8f] Created resource provider record via placement API for resource provider with UUID d2d36c03-e597-4831-84f6-03c78f331354 and name compute01.demo.infra.cloud.loc. 2018-04-04 15:09:15.774 41544 INFO nova.compute.resource_tracker [req-58502787-deca-4c5a-b4b9-8c9f59531720 - - - - -] Final resource view: name=compute01.demo.infra.cloud.loc phys_ram=257004MB used_ram=512MB phys_disk=243174GB used_disk=0GB total_vcpus=48 used_vcpus=0 pci_stats=[] ... My Environment ------------------ Ubuntu 16.04.4 LTS, 4.4.0-116-generic Openstack Queens Release Nova 17.0.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1761150/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
