yahoo-eng-team team mailing list archive

[xulei <605423512@xxxxxx>]

Public bug reported:

  I install a production cluster with ocata version for nfv project. During the testing, a compute node(hostname:normal-node2) is reclaimed., and I install a new node with the same hostname. The new nova-compute just has warning in logs, but instances can be created in this compute node with no error.
  For example（devstack for master branch,just for check the bug）:

  # /usr/bin/nova-compute --config-file /etc/nova/nova-cpu.conf
  .............
  INFO nova.compute.resource_tracker [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] Final resource view: name=devstack-com phys_ram=15708MB used_ram=512MB phys_disk=492GB used_disk=0GB total_vcpus=8 used_vcpus=0 pci_stats=[]
  INFO nova.scheduler.client.report [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] [req-3857fb52-6ca3-44c0-8974-fc30abf038b4] Another thread already created a resource provider with the UUID d494e537-0790-4dfd-9ca2-28905e085f58. Grabbing that record from the placement API.
  WARNING nova.scheduler.client.report [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] Unable to refresh my resource provider record
  ..............

  This code just work in two compute nodes with same hostname and restrict the following node. But if the previous node was destroyed, it's useless.
  I think it's danger in production environment, with no error in logs can let operators ignore the potential risk. For my project, the new node with wrong resource provider work two weeks before I delete the old record in nova-api database.

** Affects: nova
     Importance: Undecided
     Assignee: xulei (605423512-j)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => xulei (605423512-j)

** Summary changed:

- existing resource provider record will make computenode abnormally
+ existing resource provider record will make computenode abnormal

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

Title:
  existing resource provider record will make computenode abnormal

Status in OpenStack Compute (nova):
  New

Bug description:
    I install a production cluster with ocata version for nfv project. During the testing, a compute node(hostname:normal-node2) is reclaimed., and I install a new node with the same hostname. The new nova-compute just has warning in logs, but instances can be created in this compute node with no error.
    For example（devstack for master branch,just for check the bug）:

    # /usr/bin/nova-compute --config-file /etc/nova/nova-cpu.conf
    .............
    INFO nova.compute.resource_tracker [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] Final resource view: name=devstack-com phys_ram=15708MB used_ram=512MB phys_disk=492GB used_disk=0GB total_vcpus=8 used_vcpus=0 pci_stats=[]
    INFO nova.scheduler.client.report [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] [req-3857fb52-6ca3-44c0-8974-fc30abf038b4] Another thread already created a resource provider with the UUID d494e537-0790-4dfd-9ca2-28905e085f58. Grabbing that record from the placement API.
    WARNING nova.scheduler.client.report [None req-4330d5b5-ccb3-41d9-954a-43d42373a325 None None] Unable to refresh my resource provider record
    ..............

    This code just work in two compute nodes with same hostname and restrict the following node. But if the previous node was destroyed, it's useless.
    I think it's danger in production environment, with no error in logs can let operators ignore the potential risk. For my project, the new node with wrong resource provider work two weeks before I delete the old record in nova-api database.

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