yahoo-eng-team team mailing list archive

[Sam Betts <sam@xxxxxxxxxxxxxx>]

** Also affects: nova
   Importance: Undecided
       Status: New

-- 
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/1589575

Title:
  nova-compute is not starting after adding ironic configurations

Status in Ironic:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  I am trying to configure Ironic. I am doing this on Centos Mitaka.
  After writing the ironic configurations in nova.conf nova-compute is
  going down due to not able get the node list from ironic. tail -f
  /var/log/ironic/ironic-api.log 2016-06-06 08:46:37.634 3748 INFO
  keystonemiddleware.auth_token [-] Rejecting request 2016-06-06
  08:46:37.635 3748 INFO ironic_api [-] 192.168.56.105 "GET
  /v1/nodes/detail HTTP/1.1" status: 401 len: 234 time: 0.0009820
  2016-06-06 08:46:39.639 3749 INFO keystonemiddleware.auth_token [-]
  Rejecting request 2016-06-06 08:46:39.640 3749 INFO ironic_api [-]
  192.168.56.105 "GET /v1/nodes/detail HTTP/1.1" status: 401 len: 234
  time: 0.0009780 2016-06-06 08:46:41.644 3748 INFO
  keystonemiddleware.auth_token [-] Rejecting request 2016-06-06
  08:46:41.645 3748 INFO ironic_api [-] 192.168.56.105 "GET
  /v1/nodes/detail HTTP/1.1" status: 401 len: 234 time: 0.0010638
  2016-06-06 08:46:43.649 3749 INFO keystonemiddleware.auth_token [-]
  Rejecting request 2016-06-06 08:46:43.650 3749 INFO ironic_api [-]
  192.168.56.105 "GET /v1/nodes/detail HTTP/1.1" status: 401 len: 234
  time: 0.0009439 2016-06-06 08:46:45.656 3748 INFO
  keystonemiddleware.auth_token [-] Rejecting request 2016-06-06
  08:46:45.657 3748 INFO ironic_api [-] 192.168.56.105 "GET
  /v1/nodes/detail HTTP/1.1" status: 401 len: 234 time: 0.0014479
  2016-06-06 08:46:47.663 3748 INFO keystonemiddleware.auth_token [-]
  Rejecting request 2016-06-06 08:46:47.664 3748 INFO ironic_api [-]
  192.168.56.105 "GET /v1/nodes/detail HTTP/1.1" status: 401 len: 234
  time: 0.0011349 2016-06-06 08:46:49.670 3749 INFO
  keystonemiddleware.auth_token [-] Rejecting request 2016-06-06
  08:46:49.670 3749 INFO ironic_api [-] 192.168.56.105 "GET
  /v1/nodes/detail HTTP/1.1" status: 401 len: 234 time: 0.0010211

  ironic in nova.conf 
  [DEFAULT] 
  compute_driver=ironic.IronicDriver
  firewall_driver=nova.virt.firewall.NoopFirewallDriver scheduler_host_manager=nova.scheduler.ironic_host_manager.IronicHostManager 
  ram_allocation_ratio=1.0 
  reserved_host_memory_mb=0 
  scheduler_use_baremetal_filters=True 
  scheduler_tracks_instance_changes=False 
  [ironic] 
  auth_uri = http://192.168.56.105:5000 
  auth_url = http://192.168.56.105:35357 
  auth_region = RegionOne 
  auth_type = password 
  project_domain_id = default 
  user_domain_id = default 
  project_name = service 
  username = ironic 
  password = cloud123 
  api_endpoint=http://192.168.56.105:6385/v1

  I tried with keeping the keystone V2.0 confgurations but that is giving authentication problems.
  admin_username=ironic
  admin_password=IRONIC_PASSWORD
  admin_url=http://IDENTITY_IP:35357/v2.0
  admin_tenant_name=service
  api_endpoint=http://IRONIC_NODE:6385/v1

  when i try the above values in ironic as per officeial document I am getting below error
   oslo_service.service DiscoveryFailure: Could not determine a suitable URL for the plugin

  Keystone endpoints are with v3
  +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------------------+
  | ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                                              |
  +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------------------+
  | 043d8c1077a14f8f970631e0ce5a95f6 | RegionOne | keystone     | identity     | True    | internal  | http://192.168.56.105:5000/v3                    |

  
  Ironic api and conductor services are up and running.

  ironic node-list
  +------+------+---------------+-------------+--------------------+-------------+ | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | +------+------+---------------+-------------+--------------------+-------------+ +------+------+---------------+-------------+--------------------+-------------+

  Ironic api and conductor services are up and running.

  Please suggest me what is missing here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1589575/+subscriptions